W3C home > Mailing lists > Public > public-aria@w3.org > February 2016

ACTION-1734: /1709 Proposal for ARIA Figure Role response to Jason White

From: Rich Schwerdtfeger <richschwer@gmail.com>
Date: Tue, 9 Feb 2016 16:50:44 -0600
Message-Id: <003A8F8F-784C-4AE6-93DB-A97E36F7C6C5@gmail.com>
Cc: ARIA Working Group <public-aria@w3.org>
To: jjwhite@ets.org
Hi Jason, 

This is in response to this email post regarding extended descriptions:
https://lists.w3.org/Archives/Public/public-pfwg/2015Oct/0025.html <https://lists.w3.org/Archives/Public/public-pfwg/2015Oct/0025.html>

This actually dovetails into the extended description discussion. For DPUB we need to provide the ability to have an extended description that essentially must be visible on the screen or be made available in a <details> / <summary> container. 

This new attribute is associated with Issue 1009. Here is my post to the aria-dpub list:
https://lists.w3.org/Archives/Public/public-dpub-aria/2016Feb/0003.html <https://lists.w3.org/Archives/Public/public-dpub-aria/2016Feb/0003.html>

Here is a link to the proposal contained in the issue 1009 branch. This removes aria-describedat and replaces it with ARIA-details:
https://rawgit.com/w3c/aria/issue1009/aria/aria.html#aria-details <https://rawgit.com/w3c/aria/issue1009/aria/aria.html#aria-details>
The advantage of aria-details is the extended description can be made available to every user if it references to an html5 details element. Inside of this you can create alternative content and details/summary is almost implemented in every browser. 

Cheers,
Rich

Rich Schwerdtfeger





Received on Tuesday, 9 February 2016 22:51:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:58:20 UTC