- From: Siegman, Tzviya - Hoboken <tsiegman@wiley.com>
- Date: Mon, 31 Aug 2015 18:21:29 +0000
- To: "Michael Cooper (cooper@w3.org)" <cooper@w3.org>
- CC: "DPUB-ARIA (public-dpub-aria@w3.org)" <public-dpub-aria@w3.org>, "public-dpub-accessibility@w3.org" <public-dpub-accessibility@w3.org>
- Message-ID: <2ddea93000fa49d59da3664aa116dabf@CAR-WNMBP-006.wiley.com>
Hi Michael, I've gathered feedback from DPUB on yjr extended descriptions analysis grid [1]. Everyone was very impressed with the grid and thanks you for the work that went into this. I know Janina had some recommendations about adding columns regarding JavaScript and AT requirements as well. longdesc mitigation: Could be extended to cover more elements beyond <img> (eg. "All block-level elements.") aria-describedby cons: cannot link to documents outside the primary document (note: this was not in our original list of requirements, but came up in discussions around issues such as using other formats to render content, as in ChartML and is implicit in the "reuse" requirement) No standard way to hide visually but expose on demand or to AT. (Can hide but expose to screen-readers, can expose, or can right custom JS tools.) All three figure + details options cons: Doesn't inherently clarify that this figcaption is the accessibility description as opposed to a general caption cons: "special support" and "depend on script-support long term" are unclear: all three of these should just say, "will require scripting to hide visually but expose on demand or to AT." mitigation: Add a role attribute (or other attribute to ARIA) which AT, extensions, or user agent settings could recognize to expose as appropriate. mitigation: Add the "Add role attribute to clarify overloading" to all of them. mitigation: Add a role attribute which AT, extensions, or user agent settings could recognize to expose as appropriate. hidden iFrame and figure with iframe: cons: iFrames can require implementer effort to make accessible. cons: "special support" and "depend on script-support long term" are unclear: all three of these should just say, "will require scripting to hide visually but expose on demand or to AT." SVG wrapping bitmap: cons: Using SVG as a wrapper for non-graphics overloads a graphical format as a descriptor container. [1] http://www.w3.org/2015/08/extended-description-analysis Thank you, Tzviya Tzviya Siegman Digital Book Standards & Capabilities Lead Wiley 201-748-6884 tsiegman@wiley.com<mailto:tsiegman@wiley.com>
Received on Monday, 31 August 2015 18:22:10 UTC