- From: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
- Date: Thu, 23 Dec 2010 10:14:26 +0000
- To: Steve Faulkner <faulkner.steve@gmail.com>
- Cc: Maciej Stachowiak <mjs@apple.com>, HTMLWG WG <public-html@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>, David Bolter <dbolter@mozilla.com>, Marco Zehe <marco.zehe@googlemail.com>, Richard Schwerdtfeger <schwer@us.ibm.com>, Cynthia Shelly <cyns@microsoft.com>
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
Received on Thursday, 23 December 2010 10:16:01 UTC