See also: IRC log
<scribe> scribe: clapierre
title: Accessibility DPUB Task Force Weekly Meeting
tzviya: we are hoping to have this done by TPAC and section #2 is the model section. These sections should be updated via pull requests.
<tzviya> http://w3c.github.io/dpub-pwp-ucr/#accessibility
deborah: everyone knows about vision a11y, we need to add other forms of disability, cognitive, mobility, hearing etc…
tzviya: yes I agree with you, unless we don't need to add more personalization examples we can kill this section. 9.1
charles: we should just say this is covered in 2.1.9 link, since someone maybe just skip to the accessibility and we want it covered there to be complete.
tzviya: that is fine kill the section and keep a link to section#2
deborah: I will wordsmith this section
Tzviya: refer to one of the
section to fundamental features.
... and if its not a fundamental feature it should be.
tzviya: it needs an intro and the example needs to be fleshed out a bit more, maybe the braille example expanded.
deborah: I think Charles should take this one.
charles: ok I will flesh this out and then you can word smith it Deborah afterwards.
tzviya: I think this is covered under fundamentals as a package not individual pages.
Deborah: I think we can go away.
Tzviya: If you want to make a
particular use case add AT. must be perceivable by all
assistive technologies. Not sure if we even need it, then it
should go in the first paragraph.
... or it could be both places.
... . we can talk about this Monday 2.1.1 and 2.1.2
Charles: I will remove it from here 9.4
Deborah: I will take this. and cognitive and deafness examples.
Tzviya: do not use mention picture books or fixed layout here
Deborah: yeah learning to read, sync turning pages etc...
Tzviya: I agree Braille is
important, and can talk about this with the group on
Monday.
... I don't want to blur the line between use-cases relevant to
use-cases packaging, and those relevant to the publishing
industry.
charles: ability to download for a particular AccessMode.
deborah: I frequently do this, I know there is lot of javascript that isn't accessible so I will find a way to load the page without any of that stuff. But I am not sure how to do this as a use case.
Tzviya: we have a section 2.1.8
that eludes to this, which does say see section on
Accessibility.
... full package may not be available to all users for example
a user who prefers braille and would create a package
containing only the braille files and excludes the CSS…
Deborah: I can find a way to word this, to create a package that excludes elements… by the same token most users won't want to download the braille, and a deaf user may want to exclude the big audio files. deaf users on mobile choosing to exclude audio files.
Tzviya: this is great but we need to link back to the fundamental use cases of the jogger, or while doing the dishes and turn on voice over etc…
Deborah: I will take on 9.7
deborah, this is a duplicate or should be merged together. I will do this since I am also working on 9.5
Tzviya: is there anything else.
Deborah: this is specifically use
cases with respect to portability and packaging correct?
... so the fundamental use cases it is worth adding, a
portability issue 2.1.1 it is important to specify AT devices,
it is a portability issue. if I have an eReader which meet my
assistive tech needs, can it be read with my xyz with a read
aloud function.
Tzviya: we should add something about using all the tools of the web including AT.
Deborah: what about 2.1.2 should be richer or another section added afterwards.
Tzviya: maybe we are thinking should have another … (make use of all standard tools of the web including AT. and swap 2.1.1 and 2.1.2 with adding this new use case inbetween.
Deborah: this would be a great place to call out WCAG...
Tzviya: W3C is asking for a horizontal review, internationalization, accessible and secure. We don't have security section and need one. that could be the swapped 1.1 and 1.2
Deborah: the publication needs to
make use of all open web technologies, accessibility,
internationalization and security.
... its weird to have this since we are not requiring that a
publishing for other languages.
Tzviya: we will look at this
before we publish to discuss this with other
internationalization.
... we need to call this out, we either rewrite the existing
2.1.1 or we add a new section.
Deborah: I can write up a two sentence thing and we can discuss this Monday.
Tzviya: sure or it can be pushed
to the following week, although I won't be at that
meeting.
... we can push off the accessibility section to discuss with
the group the following Monday.
This is scribe.perl Revision: 1.144 of Date: 2015/11/17 08:39:34 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found Scribe: clapierre Inferring ScribeNick: clapierre Present: Charles_LaPierre Deborah_Kaplan Tzviya Regrets: George WARNING: No meeting title found! You should specify the meeting title like this: <dbooth> Meeting: Weekly Baking Club Meeting Got date from IRC log name: 12 Aug 2016 Guessing minutes URL: http://www.w3.org/2016/08/12-DPUB-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]