- From: Joseph Scheuhammer <clown@alum.mit.edu>
- Date: Wed, 27 Apr 2016 10:31:16 -0400
- To: Rich Schwerdtfeger <schwer@yahoo.com>, Amelia Bellamy-Royds <amelia.bellamy.royds@gmail.com>, Fred Esch <fesch@us.ibm.com>
- Cc: ARIA Working Group <public-aria@w3.org>, SVG-A11y TF <public-svg-a11y@w3.org>
Hi Rich,
On 2016-04-26 4:59 PM, Rich Schwerdtfeger wrote:
> I modified the role=“presentation” section to separate out the overriding of role “presentation” so that it may be referenced by the SVG and Core AAMs:
>
> https://rawgit.com/w3c/aria/action2044/aria/aria.html#override_presentation_none
>
> Let me know if you have any issues.
Some suggested tweaks follow.
Regarding the fourth paragraph about global and non-global ARIA states
and properties, put the second sentence first. Since this is a section
about overrides, state the factor that overrides. I'm not sure you need
the statement that non-global states/properties don't override. I
suggest this rewording (I've kept the statement about non-globals):
"User agents MUST always expose global WAI-ARIA states and properties to
accessibility APIs, even if an element has an explicit or inherited role
of presentation. In this case, the user agent ignores the
presentation/none role and exposes the element according to its implicit
native semantics. However, user agents MUST ignore any non-global,
role-specific WAI-ARIA states and properties."
Secondly, the comment in the first example is a holdover from the older
version of the example.
<change>
<!-- 1. [role="presentation"] negates the implicit 'heading' role
semantics but does not affect the global hidden state. -->
</change>
<to>
<!-- 1. [role="presentation"] is ignored due to the global 'haspopup'
property. -->
</to>
Finally, I don't understand what the numbers in the examples mean. They
are both "1." Maybe they should be "1." and "2."? Dunno.
Hope that's useful.
--
;;;;joseph.
'Die Wahrheit ist Irgendwo da Draußen. Wieder.'
- C. Carter -
Received on Wednesday, 27 April 2016 14:31:46 UTC