- From: Joseph Scheuhammer <clown@alum.mit.edu>
- Date: Tue, 1 Sep 2015 13:34:31 -0400
- To: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>, Richard Schwerdtfeger <schwer@us.ibm.com>
- Cc: "cooper@w3.org" <cooper@w3.org>, PF <public-pfwg@w3.org>
Hi Bryan,
On 2015-09-01 1:04 PM, Bryan Garaventa wrote:
>> Likely, we should review all "text container" roles for this pattern and evaluate the situation for each -- what I'm saying is that this problem may be more than just listitem and link roles.
> Technically, since any ARIA role can be applied to a Div, this includes every role, interactive or otherwise, which is where I'm seeing this as being a huge problem.
I don't see <div role="button"> as a "text container role". Buttons are
not a text containers. Yes, a <div> is a text container, but adding
role="button" to a <div> transforms it to something other than a simple
<div>. I'm proposing to check each ARIA role, decide if it's a text
container, and then look to see if that role lists a requirement of an
accessible name.
Given that, we can ignore all roles that inherit from the widget role.
They are interactive and, well, widgets (although the link role is
categorized as a widget. Hmmm). On the other hand, the "document
structure" roles [1] are prime targets.
Nonetheless, it is a bit of a task. Maybe it belongs under ARIA 2.0.
[1] http://w3c.github.io/aria/aria/aria.html#document_structure_roles
--
;;;;joseph.
'Array(16).join("wat" - 1) + " Batman!"'
- G. Bernhardt -
Received on Tuesday, 1 September 2015 17:35:02 UTC