631015 - When no role is specified, fill role object attribute with closest match

Status: RESOLVED WONTFIX

(Core :: Disability Access APIs, defect)

Description

[David Bolter [:davidb] (NeedInfo me for attention)]

When no role is specified, fill role object attribute with closest match, based on the native markup.

WAI-XTECH thread starts here:
http://lists.w3.org/Archives/Public/wai-xtech/2011Jan/0004.html

Let's gather our thoughts and feedback here.

Comment 1

[David Bolter [:davidb] (NeedInfo me for attention)]

Jamie, do you have any thoughts on this?

Comment 2

[James Teh [:Jamie]]

Practically, I don't care. NVDA doesn't use the role object attribute and probably never will even if it's implemented. We do use xml-roles, but only for landmarks and only because there is no specific landmark object attribute. (I've argued about this before, but that bird has flown now.)

From a principle standpoint, I agree that ARIA states and properties should be allowable on elements based on their implicit role (which is the reason Rich gives for this proposal), but I really don't see the point of exposing this role in an object attribute. The role abstraction should come from the native accessibility API; e.g. IA2. Otherwise, we're developing another mechanism to expose the same information, which is confusing and inconsistent.

Comment 3

[alexander :surkov (:asurkov)]

basically we have xml-roles for that
1) for ARIA roles
2) for native elements
2.1) when no proper accessible role (like figure xml-roles)
2.2) when native element acts as landmark

I think I'm fine with proposal but use 'xml-roles', at least this adds more consistence

Comment 4

[David Bolter [:davidb] (NeedInfo me for attention)]

I no longer see this bug as useful.