W3C

- DRAFT -

Digital Publishing Interest Group Teleconference

27 Mar 2015

See also: IRC log

Attendees

Present
dkaplan3, +1.415.400.aaaa, clapierre, Liam, Mia, George_Kerscher
Regrets
Chair
SV_MEETING_CHAIR
Scribe
clapierre, liam

Contents


<trackbot> Date: 27 March 2015

<liam> [ mihnea_____ is Mihnea Ovidenie ]

<liam> scribenick: clapierre

our meetings will change from 1PM / 4PM EST starting next week will be 8AM/ 11 AM EST every Friday.

Mia, Flash conversation is very controversial, but all was said in the email exchange.

<liam> http://www.w3.org/TR/WCAG20-TECHS/flash.html

liam, javascript should be more accessible than flash

deborah, 99% javascript should be accessible if done right

liam, what does w3C need to provide to publishers to help them make their content accessible

mia, we know publishers doesn't want to be sued, and to sell their content

… digital publications ties into user agent in a way, its not different than browsers but you can't really do that with readers.

deborah, no good accessible epub authoring tools and we probably won't get around to ATAG.

mia, how do we really make this work when not all readers even support the current standards.

…, nvda now supports MathML

clapierre, Tzyvia said that we are tasked to create a W3C Note for the W3C audience. Not Publishers that will be handled by BISG and other groups.

liam, epub does use HTML5 and css and w3c can change those specs

…, BISG can write their best practices and reference the W3C standards.

mia, we need to define "DPUB" epub, web publications, self publishing

liam, professionally mediated digital publications could be our definition of DPUB.

…, if a publisher (wiley, time, etc..) need something more than open web platform provides then this is what we are here to accommodate

<liam> scribenick: liam

clapierre: for WCAG general techniques we have about a dozen not required, and 6 or so we're not sure of

Not required:

<clapierre> WCAG A11Y DPUB General - Technique Development Assignments

<clapierre> Not Required

<clapierre> G1: Adding a link at the top of each page that goes directly to the main content area

<clapierre> G9: Creating captions for live synchronized media

<clapierre> G63: Providing a site map

<clapierre> G71: Providing a help link on every Web page

<clapierre> G157: Incorporating a live audio captioning service into a Web page

<clapierre> G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast

<clapierre> G175: Providing a multi color selection tool on the page for foreground and background colors

<clapierre> G178: Providing controls on the Web page that allow users to incrementally change the size of all text on the page up to 200 percent

<clapierre> G180: Providing the user with a means to set the time limit to 10 times the default time limit

<clapierre> G181: Encoding user data as hidden or encrypted data in a re-authorization page

<clapierre> G185: Linking to all of the pages on the site from the home page

<clapierre> G188: Providing a button on the page to increase line spaces and paragraph spaces

<clapierre> G189: Providing a control near the beginning of the Web page that changes the link text

<clapierre> G200: Opening new windows and tabs from a link only when necessary

<clapierre> G201: Giving users advanced warning when opening a new window

<clapierre> G180: we need an adapted version for DPUB.

<clapierre> mia, this may be a UA issue?

<clapierre> deborah, too often that is hard coded by developers and has to be overrriden.

G178 - may be part of the document

http://www.w3.org/TR/WCAG20-TECHS/G181.html on session timeout and not hving to reenter data

may be relevant

(G181)

liam: e.g. for saving an annotation or notes on a remote server

G185 - no

G189 no, it's awful :)

but we have to think about this - you've got omething that can't be made accessible but there's an alteriative

so we need to make sure we cover that case but we may cover it somewhere else

<clapierre> http://www.w3.org/TR/WCAG20-TECHS/G200.html

GK: longdesc often in another window

footnotes, endnotes

bibliographic refs

<clapierre> I think G200 is relevant to DPUB.

G201 - yes

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.140 (CVS log)
$Date: 2015/03/27 21:05:28 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/sribenic, me//
Succeeded: s/professionally mediated publications/professionally mediated digital publications/
Found ScribeNick: clapierre
Found ScribeNick: liam
Inferring Scribes: clapierre, liam
Scribes: clapierre, liam
ScribeNicks: clapierre, liam

WARNING: No "Topic:" lines found.

Default Present: dkaplan3, +1.415.400.aaaa, clapierre, Liam, Mia, George_Kerscher
Present: dkaplan3 +1.415.400.aaaa clapierre Liam Mia George_Kerscher

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 27 Mar 2015
Guessing minutes URL: http://www.w3.org/2015/03/27-dpub-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


[End of scribe.perl diagnostic output]