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

Thank you, Rich.

If I'm reading the text correctly, the following would also be a conforming use case, as it should be:

<p><img src="graph.png" alt="Graph of global average temperatures from 1970-2015" aria-details="t1">
[...]
<table id="t1">
[header row and rows of data]
</table>

I am assuming that the table element (or a section, div, etc.) ensures that the enclosed material qualifies as being "included in a container that exposes the content to the user". Is this correct? Perhaps it should be stated explicitly that the content is "exposed to the user" even if the user has to perform an action to reveal it; otherwise, it isn't clear that the above-quoted text is satisfied by details/summary elements.

To be clear, I am comfortable with the proposal. ARIA currently treats descriptions referred to with aria-describedby as flat text strings regardless of markup, and I think we should define a property that allows an entire document subtree (elements preserved) to be designated as a description, which then wouldn't be simply converted to a string for inclusion in the accessible description field of an accessible object at the platform level. This proposal meets the need, but I think the usage requirement could be clarified somewhat.


________________________________

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.


Thank you for your compliance.

________________________________