- From: <kerscher@montana.com>
- Date: Thu, 10 Nov 2022 10:33:44 -0700
- To: "'Avneesh Singh'" <avneesh.sg@gmail.com>, <public-epub3@w3.org>, <public-publishingcg@w3.org>
- Message-ID: <010b01d8f52a$a1283cf0$e378b6d0$@montana.com>
Dear All, We are close to finishing the Accessibility Summary work. I have created an issue with comments and questions at: https://github.com/w3c/publ-a11y/issues/135 Feel free to make comments there or on this mailing list. I have reproduced the full issue below. The major questions are: Is there anybody else that should be listed in the acknowledgements? Should the Conformance table head say, "Example text" instead of "Suggested summary?" Do we want one or more additional examples? If yes, who wants to write them? To view the current Accessibility Summary in its entirety visit: https://w3c.github.io/publ-a11y/drafts/schema-a11y-summary/ Best George Full issue below: Accessibility Summary final questions We agreed that a single issue would be created that identifies what yet remains to be done. That list is below. * Should the table in the section Accessibility Conformance Related Statements use Example statement instead of Suggested Summary? * In the features table: In long description is missing, protraying. is misspelled and should be portraying. * Reading order is not filled in. If the proper reading order is not present, it should be noted. I think this should be filled in. * In structural navigation there is a dangling word "navigation" * Transcript has no information field. It should say that if transcripts of audio are provided, it should be noted. * TTS markup has no example. We should get something from the Pronunciation task force. George sent an email requesting this. Also, there is a typo in the information, it should be provided, missing the d. * We have two examples. Do we want to add more? If yes, who wants to write it? * Is the acknowledgements complete? The editors are in the acknowledgements, is that customary?
Received on Thursday, 10 November 2022 17:34:19 UTC