laudrain: we have a working group called norms and standards and in France we have taken a standards document (see jeanne's notes) and made it available in French with a sample epub file

george: the techniques are great and the knowledge base is excellent, especially when used with an accessibility checker but what we are seeing people ask for are best practices in terms of the publishing process
... that are SPECIFIC to publishing

(emphasis added by rachel who is a publisher)

scribe: for example - a grammar textbook will have handwritten markup
... what is the best technique for this in terms of accessibility?

shawn: what doesn't work well for you around accessibility guidelines

James: General guidelines (e.g. maintain minimum contrast in *any* UI) work well. It also makes sense for the World Wide Web Consortium to patterns specific to web technologies. Problems arise when general guidelines (not intended or phrased as rule-making) are being used as prescriptive ways to force low performers up to a minimum standard. This approach can inadvertently penalize the flexibility and progress of high performers. For example, the old expectation that everything must be “keyboard-accessible” slowed the progress toward accessible touch screen interfaces.
... the guidelines to improve accessibility overall are useful in a number of contexts
... my recommendation is that w3c scope is "the web"

george: remember that publishing is now a part of the w3c

James: EPUB is a web technology, so it makes sense that the W3C shoud specify technology-specific accessibility expectations for EPUB.

Anne Thyme: people that build web sites often don't understand WCAG according to a set of very specific steps (that are not technology specific) and it creates a hand holding process

shawn: now there are all these adaptations

stein: from our standpoint the important elements are interoperability and testability

rdeltour: when applying guidelines it is sometimes difficult to know if you have support for specific features

laudrain: we are able to implement publishing techniques - how can we map these details to WCAG levels A,AA, AAA

rdeltour: in the publishing context we sometimes find that wcag is designed inclusively - but publications can be tailored to a specific groups of users
... a publication targeting a specific range of people can fail but meet the needs of it's users

Jenn_Chadwick: I missed that - can you add your comment here

Avneesh: some elements are more useful for one industry than another

shawn: what's on your wishlist

stein: testability, more testable statements

rdeltour: complete ACTs rulesets

<marisa_> UA accessibility testing for EPUB: http://epubtest.org/testsuite/accessibility

george: epubtest.org and the "perfect" epub has a full list of user agents and their accessibility status
... there's no definitive testing for content WITH user agents

<jcraig> /

shadi: given the expanded scope of the standard and the expanded scope of the web itself, web of things, digital publishing etc... does this need to have a more modular approach?
... with specific layers that address different verticals/domains but without getting into the html
... then there would be another level for implimentation and testing

george: can we kill pdf? people believe that we can make pdf accessible and that misconception is a problem

Avneesh: 3 strands - industry specific, user specific/user optimized, a minimal criteria for what is meant by accessible material and accessible user agent

shadi: translatability

jeanne: we are looking for volunteers to help push this work internationally

stein: how are you doing the research/data collection you mentioned

shawn: we are reviewing what has been done before, trying to work within existing research...

<jcraig> s/\///

jeanne: we have a literture review team that uses the zotaro(?) tool which protects copyright

george: who do we contact with suggestions

shawn: the task force mailing list

<jeanne> public-silver@w3.org

Avneesh: who is responsible for the accessibility of the content when a snapshot is embedded in the content package

<jcraig> s////

<jcraig> s////

shawn: I would say the content creators

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/James Craig/James/
Succeeded: s/???/Anne Thyme/
Succeeded: s/sometimes these guidelines are very HTML focused but don't address a broader context of the web and elsewhere./General guidelines (e.g. maintain minimum contrast in *any* UI) work well. It also makes sense for the World Wide Web Consortium to specific patterns specific to web technologies./
Succeeded: s/It is fine to recommend guidelines that work in any context - the issue is that more recently some of these new things are being lobbied by people in the accessibility working group to become law. This creates conflicts./Problems arise when general guidelines (not intended or phrased as rule-making) are being used as prescriptive ways to force low performers up to a minimum standard. This approach can inadvertently penalize the flexibility and progress of high/
Succeeded: s/progress of high General/progress of high performers. General/
Succeeded: s/specific patterns specific/patterns specific/
Succeeded: s/General guidelines work well. An example of a problematic standard is everything must be keyboard/For example, the old expectation that everything must be “keyboard-accessible” slowed the progress toward accessible touch screen interfaces./
Succeeded: s/publishing is largely web focused/EPUB is a web technology, so it makes sense that the W3C shoud specify technology-specific accessibility expectations for EPUB./
Succeeded: s/accessible but how does that apply on mobile? does it prevent innovation//
FAILED: s/performers.\///
Succeeded: s/public-silver@w3.org Mail Archives/public-silver@w3.org/
WARNING: Bad s/// command: s//performers.//
WARNING: Bad s/// command: s//performers.//
Succeeded: s/performers.//
Succeeded: s/performers.//
Succeeded: s/performers.//
Succeeded: s/performers.//

WARNING: No "Present: ... " found!
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy
        <amy> Present+

No ScribeNick specified.  Guessing ScribeNick: rachel
Inferring Scribes: rachel

WARNING: No "Topic:" lines found.


WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


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


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

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


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)