- From: Jonathan Avila <jon.avila@ssbbartgroup.com>
- Date: Wed, 23 Nov 2016 18:03:19 +0000
- To: WCAG <w3c-wai-gl@w3.org>
- Message-ID: <DM5PR03MB278088CAE8A240180B9AD3389BB70@DM5PR03MB2780.namprd03.prod.outlook.com>
>>was developed the consensus opinion was that applying 2.4.1, 2.4.5, 3.2.3 and 3.2.4 to documents using the “set of documents” definition did not capture the key accessibility needs. Ø Can you explain this further? I was an active member of the WCAG2ICT TF with you on all of those calls for a year. David, if all the pages of a document are seen as one document then 2.4.1, 2.4.5, 3.3. and 3.2.4 cannot be applied within that document unless it is part of a set. Since most documents are not part of a set of documents then these SC are effectively removed from the requirements for documents and software even if the software is screen based. In addition, SC like 2.4.2 apply to the software app as a whole and not to screens within a software app. While I understand that not all software is screen based I don’t know why the definition could have been updated to include screens when software was screen based. The same flaw would apply to single page apps – 2.4.2 would only require a single title and as written may not require the title to change. The user needs for a clear title apply to screen based software just as they apply to web – why have a lower standard for software. Jonathan Jonathan Avila Chief Accessibility Officer SSB BART Group jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com> 703.637.8957 (Office) Visit us online: Website<http://www.ssbbartgroup.com/> | Twitter<https://twitter.com/SSBBARTGroup> | Facebook<https://www.facebook.com/ssbbartgroup> | Linkedin<https://www.linkedin.com/company/355266?trk=tyah> | Blog<http://www.ssbbartgroup.com/blog/> Join SSB at Accessing Higher Ground This Month!<http://www.ssbbartgroup.com/blog/join-ssb-accessing-higher-ground-month/> The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited. From: David MacDonald [mailto:david100@sympatico.ca] Sent: Wednesday, November 23, 2016 10:52 AM To: Matt Garrish Cc: WCAG; Katie Haritos-Shea GMAIL; Wilco Fiers; Siegman, Tzviya - Hoboken; George Kerscher; Charles LaPierre; Avneesh Singh Subject: Re: DPUB Set of Web Pages Hi Mike >was developed the consensus opinion was that applying 2.4.1, 2.4.5, 3.2.3 and 3.2.4 to documents using the “set of documents” definition did not capture the key accessibility needs. Can you explain this further? I was an active member of the WCAG2ICT TF with you on all of those calls for a year. Cheers, David MacDonald CanAdapt Solutions Inc. Tel: 613.235.4902 LinkedIn <http://www.linkedin.com/in/davidmacdonald100> twitter.com/davidmacd<http://twitter.com/davidmacd> GitHub<https://github.com/DavidMacDonald> www.Can-Adapt.com<http://www.can-adapt.com/> Adapting the web to all users Including those with disabilities If you are not the intended recipient, please review our privacy policy<http://www.davidmacd.com/disclaimer.html> On Wed, Nov 23, 2016 at 10:32 AM, David MacDonald <david100@sympatico.ca<mailto:david100@sympatico.ca>> wrote: Hi Matt I think including a epub example in a set of web pages wouldn't preclude a more specific definition of epub at a later time, or even in a later version of WCAG ... on the other hand, maybe we could introduce a new term in 2.1 if we have it very soon. It just seems to me that "a set of web pages" and inherent in that the "web page definition" of the base URL and associated assets, is a perfect short term definition that would accomplish what George mentioned about working epub into the web page framework so that the WCAG Success Criteria can explicitly apply to epub. Although just the fact that they sit at a URL already allows WCAG Success Criteria to apply to epub, and WCAG2ICT applies when its offline. Cheers, David MacDonald CanAdapt Solutions Inc. Tel: 613.235.4902<tel:613.235.4902> LinkedIn <http://www.linkedin.com/in/davidmacdonald100> twitter.com/davidmacd<http://twitter.com/davidmacd> GitHub<https://github.com/DavidMacDonald> www.Can-Adapt.com<http://www.can-adapt.com/> Adapting the web to all users Including those with disabilities If you are not the intended recipient, please review our privacy policy<http://www.davidmacd.com/disclaimer.html> On Wed, Nov 23, 2016 at 8:16 AM, Matt Garrish <matt.garrish@gmail.com<mailto:matt.garrish@gmail.com>> wrote: Thanks, David, this is a good start. I'd just suggest that we keep any definition of a web publication agnostic to specific formats. As Tzviya mentioned on the call, the DPUB group will be taking up the issues from yesterday on their next call, so we'll have more to say about example wording and metadata after we can involve the full group. Matt From: David MacDonald [mailto:david100@sympatico.ca<mailto:david100@sympatico.ca>] Sent: November 22, 2016 3:26 PM To: WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>; Katie Haritos-Shea GMAIL <ryladog@gmail.com<mailto:ryladog@gmail.com>>; Wilco Fiers <w.fiers@accessibility.nl<mailto:w.fiers@accessibility.nl>>; Siegman, Tzviya - Hoboken <tsiegman@wiley.com<mailto:tsiegman@wiley.com>>; George Kerscher <kerscher@montana.com<mailto:kerscher@montana.com>>; markus.gylling@idpf.org<mailto:markus.gylling@idpf.org>; matt.garrish@bell.net<mailto:matt.garrish@bell.net>; Charles LaPierre <Charlesl@benetech.org<mailto:Charlesl@benetech.org>>; Avneesh Saxena <Avneesh.s@gmail.com<mailto:Avneesh.s@gmail.com>> Subject: DPUB Set of Web Pages Note: DPUB members, this is my personal opinion, not speaking for WG Today we discussed ways that we could role a DPUB package into our definition of web page. DPUB packages have more than one URL, and as such cannot be considered under our current definition as a web page. However, we have a useful definition in WCAG which lends itself ideally to a DPUB document. That is a "Set of Web Pages" set of Web pages collection of Web pages<https://www.w3.org/TR/WCAG20/#webpagedef> that share a common purpose and that are created by the same author, group or organization Note: Different language versions would be considered different sets of Web pages. https://www.w3.org/TR/WCAG20/#set-of-web-pagesdef We could add something like this to the definition "Example: An epub publication has a table of contents and 25 separate URLs representing each chapter of a digital book." If the DPUB team has Success Criteria they would like to propose for WCAG, for DEC 1st, I suggest they submit them using this definition. For instance, if they want ways to link from a TOC to another chapter of the document and back, they could propose something like: "Every link from a Table of Contents in a set of web pages has a corresponding link back to the Table of Contents" Of course this SC is just off the top of my head but it gives an idea of how this type of SC could be written with this language. ============= Also we discussed meta data as a means of reporting conformance. WCAG 2 has a discussion of meta data in Appendix C which may be useful. https://www.w3.org/TR/UNDERSTANDING-WCAG20/appendixC.html Cheers, David MacDonald CanAdapt Solutions Inc. Tel: 613.235.4902<tel:613.235.4902> LinkedIn <http://www.linkedin.com/in/davidmacdonald100> twitter.com/davidmacd<http://twitter.com/davidmacd> GitHub<https://github.com/DavidMacDonald> www.Can-Adapt.com<http://www.can-adapt.com/> Adapting the web to all users Including those with disabilities If you are not the intended recipient, please review our privacy policy<http://www.davidmacd.com/disclaimer.html>
Received on Wednesday, 23 November 2016 18:03:55 UTC