[Bug 23371] Strong Native Semantics table appears to imply @hidden trumps @aria-hidden


Rich Schwerdtfeger <schwer@us.ibm.com> changed:

           What    |Removed                     |Added
                 CC|                            |schwer@us.ibm.com

--- Comment #6 from Rich Schwerdtfeger <schwer@us.ibm.com> ---

In the case of aria-hidden="true" FF does indeed expose the tree to the AT but
provides the attribute. In the case of hidden being present we are asking you
to do the same thing. Expose the subtree to the AT and expose the object
attribute to the AT. All the other browser agreed with this approach and FF is
not being consistent with its implementation if it is not following this

So, all the other browsers agree with exposing the tree when @hidden is applied
and exposing the aria-hidden attribute. FF should support consistency in its
implementation with the other browsers and with its own implementation. 

Allowing this would allow future browser implementations to expose structural
semantics of hidden elements - which is the use case we are trying to meet. 

As for aria-disabled and disabled having aria-disabled="false" override it
makes no sense for the following reasons:

- It will still be functionally disabled as aria is not allowed to override the
functionality of the interface. 
- making it false provides no value to the disabled user and there is no use
case benefit that would help the disabled user by allowing
aria-disabled="false" to override it. 

So, for these reasons aria-disabled="false" really does not buy anything for
the disabled user and the two examples really can't be compared.

Please correct the Firefox implementation to be consistent with what was agreed
on by the other browsers.

You are receiving this mail because:
You are on the CC list for the bug.

Received on Thursday, 9 January 2014 16:55:57 UTC