553117 - Don't map aria-required state for all elements

Status: REOPENED

(Core :: Disability Access APIs, defect)

Description

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

aria-required is not a global aria state/property. We want to allow it on html elements that make sense (like input type="checkbox") even when there is no role. We probably should create some {per-native-element : allowed-aria-states} map.

Comment 1

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

I'll own this for now, but am not active yet.

Comment 2

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

I might add some smarts to ARIAStateMap.cpp - is anyone planning to mess with that code in the near future?

Comment 3

[alexander :surkov (:asurkov)]

afaik nobody works in this area but things are changed fast but you shouldn't afraid a merging, that's unfortunate but it shouldn't affect on your decision to work on the bug or not.

Comment 4

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

Given html5 has 'required' for the use cases in comment 0 this bug is obsolete.

Comment 5

[alexander :surkov (:asurkov)]

we have reference to this bug from our code. spec says that aria-required is applied to number of roles (http://www.w3.org/TR/wai-aria/states_and_properties#aria-required). I'm not sure I understood resolution of this bug (comment #4).

Comment 6

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

Comment 4 was a reaction to hearing that aria-required would be deprecated/removed (sorry I am not good at remembered venue/medium), but if that inertia has changed we should reopen this bug.

Comment 7

[alexander :surkov (:asurkov)]

reopen per comment 6

Comment 8

[alexander :surkov (:asurkov)]

we might need to morph this bug later if aria-required proposal to make it inheritable gets into the spec (https://www.w3.org/WAI/PF/Group/track/issues/554), in this case I assume aria-required will be a global state.