Re: role=presentation must not be applied to focusable elements

hi Ben,

you wrote
"Remembering the intent of the ARIA obligation is to ensure operable
controls ("in order to ensure that the element is both
understandable and operable"), is there any *harm* to a MUST NOT rule
banning role="presentation" on the elements that HTML5 says "should"
be focusable, and on any element with a tabindex attribute? That would
be machine-checkable and clear."

I don't think there is any harm and would support it.


regards
steve

On 23 December 2010 10:14, Benjamin Hawkes-Lewis
<bhawkeslewis@googlemail.com> wrote:
> On Thu, Dec 23, 2010 at 9:41 AM, Steve Faulkner
> <faulkner.steve@gmail.com> wrote:
>> "The presentation role MAY be used on any element, but SHOULD NOT be
>> used on focusable elements."
>
> I don't think demoting an obligation from MUST to a SHOULD on the
> grounds that focusable is ambiguous fixes things.
>
> SHOULD be reserved for obligations that are clear but might be inapplicable.
>
> Given this text, it would be hard for authors to make informed
> decisions about whether the SHOULD applies in their case.
>
> Remembering the intent of the ARIA obligation is to ensure operable
> controls ("in order to ensure that the element is both
> understandable and operable"), is there any *harm* to a MUST NOT rule
> banning role="presentation" on the elements that HTML5 says "should"
> be focusable, and on any element with a tabindex attribute? That would
> be machine-checkable and clear.
>
> --
> Benjamin Hawkes-Lewis
>



-- 
with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html