[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

--- Comment #8 from steve faulkner <faulkner.steve@gmail.com> ---
(In reply to James Craig from comment #7)
> (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.


As I pointed out the semantics are not identical in Comment 2

>aria-required does not equal HTML5 required:

>Setting required on a control sets the state of the control to required and >invalid the equivalent of:

> <input aria-required=true aria-invalid=true>

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

Received on Tuesday, 13 May 2014 16:30:37 UTC