[Bug 25614] @required and @disabled need to be moved to the Strong native semantics table

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25614

James Craig <jcraig@apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jcraig@apple.com

--- Comment #7 from James Craig <jcraig@apple.com> ---
(In reply to steve faulkner from comment #5)
> >If you leave the second piece in, we get conflicts where HTML5 @required is >false (implicit via missing boolean attribute)
> 
> the ARIA mapping tables is full of conflicts - authors can override many
> native accessibility semantics

But attributes with identical semantics (disabled, required, etc.) are the one
place ARIA defers to the host language. I understand the conflict here. I just
think we should discourage it with a validation error. Something like this:

"""
Error: aria-required="true" is used on a form element that does not include the
required attribute. Note: The input, select, and textarea elements support the
boolean 'required' attribute in HTML5. If the element is required, use
required="" in addition to aria-required="true".
"""

Mike Smith, since you work on the validator, what do you think of this?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 13 May 2014 16:20:58 UTC