- From: James Craig <jcraig@apple.com>
- Date: Mon, 18 Jul 2016 18:06:13 -0700
- To: "Siegman, Tzviya - Hoboken" <tsiegman@wiley.com>
- Cc: Rich Schwerdtfeger <richschwer@gmail.com>, Joanmarie Diggs <jdiggs@igalia.com>, ARIA Working Group <public-aria@w3.org>, Fred Esch <fesch@us.ibm.com>, "DPUB-ARIA (public-dpub-aria@w3.org)" <public-dpub-aria@w3.org>
Siegman, Tzviya - Hoboken wrote: > Rich Schwerdtfeger wrote: > >> James provided mappings for things like appendix and acknowledgements below. Rather than expose these as appendix and acknowledgements he believes they only need be exposed as a group as the headers for those section will include those words i. Them at all times > > While it is true that often there is a heading for these elements (e.g. <h1>Bibliography</h1>), it is not always the case, especially for something like doc-endnotes. If these sections (acknowledgements, etc) have no heading, then there is no indication to sighted users that it's different from any other section. Therefore assistive technology users don't need additional context either. Both sighted and blind users could be equally confused by the lack of an explanatory heading, but that does not make it an accessibility issue. A specific accessibility API role mapping would only be necessary if some context was conveyed visually but was not clear to say, a screen reader user. James
Received on Tuesday, 19 July 2016 01:07:05 UTC