See also: IRC log
<scribe> scribe: clapierre
title: Accessibility DPUB Task Force Weekly Meeting
http://w3c.github.io/dpub-accessibility/
Tzviya: Peter added to our note on Math and some other edits.
Romain: how this came up. talking about a11y note, with the IDPF meeting list. some books are optimized for audiences audio books which don't comply to WCAG for universal a11y. but these books need to be a11y. in epub we have metadata to identify these books. DPUB a11y is not about universal a11y. not sure where this belongs, future work, or tailoring wcag
Tzviya: initially: review WCAG, and identify gaps. we would have to frame it that way that there is a gap. discoverability is an area which WCAG doesn't address.
Avneesh: would be good to
register this with the W3C Note.
... , written down discovery here would be great to have
Romain: criteria for discoverability. is there other things missing in note?
George: materials that are optimized for a specific group and not universally design.
Romain: sensitive topic: we need to filter out WCAG and focus on one type of group. that is a big can of worms.
Avneesh: talking about 1 group of needs is a problem, but discoverability is really the focus here.
Tzviya: when I mentioned the
metadata with Deborah, since it is so easy to falsify it. But
its not a reason to not have it.
... laying ground work for future. we outline these very broad
issues. wether content is accessible or all encompassing, is
all we need to say.
Romain: Not sure what you said.
Tzviya: I think DPUB Note needs to do add a section (Discoverability) current w3C documentation that there is a way to say that content is accessible or how to find it.
Romain: if there is no way to profile WCAG there there is no way to a11y of specialized publications it won't reach A. so there is nothing you can do. so claiming that a specific publication is a11y is an issue. workaround: need a way to have custom profile but that is not universal.
Matt: there are forms of digital publications for specific groups and this is a know issue for these publications. Outline there are guidelines needed. without specifying how to solve this.
Tzviya: we want to soften the
tone. metadata issue and specialized version. maybe 2
issues.
... , so 2 new sections for metadata and optimized
versions.
Romain: I can try both if you need volenteers.
Avneesh: what is the original plan for this Note beyond this state (1-2 years)
Tzviya: when we started working on this in 2015 this was to get our feet wet and working with other groups WAI. we didn't think it would take this long. at least 6 months ago and just to do a gap analysis and then publish it and work with other groups in WAI.
George: do we think we are complete in our gap analysis.
Avneesh: we are adding 2 and there may be more.
Tzviya: there is supposed to be examples there. WCAG, UAG/ATAG and if they are relevant to publishing.
Avneesh: two kinds of audiences. this note is for W3C and informative (what are missing pieces) and on epub side is publishers and concrete side.
George: this affirms that WCAG do
apply to DPUB
... , this note says that it does apply and the epub a11y
points to the note that WCAG is relevant and then go onto other
things that we describe in our document. this is where this doc
is important.
Avneesh: when this document W3C process says that these things are missing from WCAG for DPUB help WCAG areas to work on future / extensions. can help us harmonize WCAG to epub3 accessiblity.
George: do we say that things are missing from WCAG.
Tzviya: yes but we will tone it
down a little.
... , expressing this is a gap analysis and not saying XYZ.
Matt: reads like tracker issues which is his concern.
Tzviya: we said time is limited
and I haven't touched this. I may not be able to get to this
depending on what happens.
... , we are all stretched right now. Jean is available but is
not part of this group. we can unofficially take her
help.
... , Matt you offered or may be able to help with some word
smitthing.
... , Michael's recommendations is to tone down the note.
Matt: I think explaining these issues and how you are expressing the issue. I can go through and try to clean up some of these things. I will do one and see if its what you want/expect then can do the rest.
Tzviya: I can do this with you 15 min after this call if you want.
Matt: I can fork the repo and do a quick clean up and send it to you.
Charles: the conversion from Google docs to wiki is done but could need more work missing usecases etc.
Tzviya: I think lets get to a
cleaner doc first.
... , we talked about removing DropCap. ARIA changed how
footnotes are handled so I can clean that up.
Charles: we should remove DropCap from this Note since it is handled already by W3C so I say lets remove it…. objections?
All: None.
Tzviya: we need update the references. I will fix the ones I know about and will email the list for others.
Charles: I will remove the DropCap section.
Tzviya: looking at Alastair the most important is updating the abstract.
George: we should email them
thanking them for their comments and we are acting on
them
... , headings issue as well.
Tzviya: he had some really valuable points.
George: will Matt take on the abstract?
Tzviya: I think Deborah will be able to work on the abstract. There are some detailed comments and maybe we should go through them. in the remaining 20 minutes.
<tzviya> https://lists.w3.org/Archives/Public/public-digipub/2016Feb/0000.html
Avneesh: conveys that most of W3C note be phrased as a WCAG extension in the future.
George: this was started way before the wcag extension.
Tzviya: 2.1 Navigating Among
Multiple Documents
... , why back button doesn't solve all our problems
... , Use-case 2 appears to be a miss-linking issue, on the web
such an issue would affect everyone, I don’t understand why it
would affect a non-sighted reader only?
... , point was: there is no way to test a11y of a package I
can't check if the Nav doc links are correct. but there is no
tool to test this… can not access a particular script.
George: its a boundary for these
kind of documents. you want to restrict your links to one
package.
... , is the word publication the issue?
Tzviya: its just a matter of link
checking. criteria Bypass Blocks (2.4.1), Multiple Ways (2.4.5)
and Location (2.4.8) could all have new dPub techniques added
within the current SC.
... , its about the packaging is the issue.
George: Boundry (constraint) on identifying the links that those bounded documents and those which are outside. You can create a toc and point to the various parts of the publication. There is a wrapper around this documents that are core to the core to TOC which makes up the publication.
Tzviya: identifier or
locator.
... we need find a way to have these two meetings back to
back.
George: key get this note
done.
... how many hours do you think would take you and Jean to get
this done?
Tzviya: don't know lets let Matt take a first crack at this .
George: let me see what I can do.
Charles: Matt will take first crack of this. Thanks Matt, I know you were volunteered for this, we do really appreciate this!
Charles: Peter who couldn't make this meeting has already completed most if not all of this new section. Thank you for doing this work for us Peter you are awesome!
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) Succeeded: s/soposto/supposed to/ Found Scribe: clapierre Inferring ScribeNick: clapierre Present: Charles LaPierre George Kerscher Avneesh Romain_Deltour Matt_Garrish Mia_Lipner Regrets: Deborah Peter K 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: 11 Mar 2016 Guessing minutes URL: http://www.w3.org/2016/03/11-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]