Re: [a11y] Final review of User experience guide for accessibility metadata: Deadline Jan 21, 2021

Thanks Laurent for going through the document in so much detail.
Regarding:
"While every user has different accessibility needs, meeting the Web Content Accessibility Guidelines (WCAG) 2.0 requirements, even at level A, is a baseline that ensures a book will be widely accessible."

Right now we are strongly recommending level AA in EPUB Accessibility 1.1, while explaining why it is the recommended level, and why publishers should not settle on level A. The further discussion is at https://github.com/w3c/epub-specs/issues/1459
We will keep this document in sync whenever we raise the floor in EPUB Accessibility.

Great to see that you are implementing these recommendations well in the Thorium/Readium 2 world!

With regards
Avneesh

From: Laurent Le Meur 
Sent: Friday, January 15, 2021 23:20
To: Avneesh Singh 
Cc: public-epub3@w3.org ; public-publishingcg@w3.org 
Subject: Re: [a11y] Final review of User experience guide for accessibility metadata: Deadline Jan 21, 2021

Hi Avneesh,


In section 2 I read: 
"While every user has different accessibility needs, meeting the Web Content Accessibility Guidelines (WCAG) 2.0 requirements, even at level A, is a baseline that ensures a book will be widely accessible."


I suppose that this will evolve to level AA if AA is finally chosen as outcome of https://github.com/w3c/epub-specs/issues/1459. This would be a matter of consistency. 


Apart from that, when we start seing EPUB files with accessibility metadata in the wild (I hear that there are currently 350 such ebooks in the global "French" catalog, tagged via ONIX; but I'm not sure the corresponding EPUB files have equivalent metadata), we'll add to Thorium Reader the features described in this document.
- A search filter in the catalog, on the boolean "Accessible" criteria associated with WCAG A or AA
- A11y information in the ebook info panel, starting with the "universal man" logo (visually appealing there at least for sighted users) with alt text "Accessible Publication" I think. 


The fact that a publication is an Audiobook is already clear in Thorium, therefore we won't duplicate it with an "Audiobook" property. UI details will be defined by a designer before implementation.  


Best regards
Laurent







  Le 13 janv. 2021 à 15:27, Avneesh Singh <avneesh.sg@gmail.com> a écrit :

  Dear all,

  This is a reminder for final review of User experience guide for displaying accessibility metadata.
  The review period will end on Thursday, January 21, 2021. Therefore please suggest improvements on or before this date.

  Further details are in the following email.

  With regards
  Avneesh Singh
  From: Avneesh Singh
  Sent: Thursday, December 17, 2020 21:52
  To: public-epub3@w3.org ; public-publishingcg@w3.org
  Subject: [a11y] Final review of User experience guide for accessibility metadata: Deadline Jan 21, 2021

  Dear all,
   
  This is the announcement for the final review of User experience guide for displaying accessibility metadata. 
  The review period will end on Thursday, January 21, 2021. Therefore please suggest improvements on or before this date.
   
  Thanks to Gregorio, Madeleine and Charles for editing the documents and harmonizing schema.org accessibility metadata with ONIX accessibility metadata. And many thanks to all participants of accessibility task force for providing the valuable guidance.
   
  The list of documents to review are:
  - User experience guide for displaying accessibility metadata
  - Techniques for schema.org accessibility metadata
  - Techniques for ONIX accessibility metadata
  User experience guide for displaying accessibility metadata is at the following link. It also points to the two techniques documents.
  https://w3c.github.io/publ-a11y/UX-Guide-Metadata/principles/

  The issue tracker for suggesting improvements is at:
  https://github.com/w3c/publ-a11y/issues

  Wishing all of you a very Happy New Year!

  With regards
  Avneesh Singh