W3C home > Mailing lists > Public > public-html@w3.org > June 2012

Re: Using ARIA in HTML

From: Lee Kowalkowski <lee.kowalkowski@googlemail.com>
Date: Fri, 29 Jun 2012 15:38:11 +0100
Message-ID: <CAGpS7GOos124KuAveNBpPnYO_qMhWBMEDv06L48NXxA1Bm0L3g@mail.gmail.com>
To: Steve Faulkner <faulkner.steve@gmail.com>
Cc: HTMLWG WG <public-html@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>
On 29 June 2012 14:24, Steve Faulkner <faulkner.steve@gmail.com> wrote:

> Hi Lee, thanks for the feedback
>
> I have added the following legend, let me know if it makes things clearer:
>
>
>    - *NO* = the default semantics are already implementated by browsers,
>    so the default implied role, state or property associated with an element
>    or attribute does not need to be used. There are notes indicating under
>    certain circumstances default semantics are useful.
>    - *N/A* = there are no default ARIA semantics, but there may well be accessibility
>    AP <http://dvcs.w3.org/hg/html-api-map/raw-file/tip/Overview.html>I
>    semantics implemented by the browser.
>    - *Yes* = the default semantics are not implementated across browsers,
>    so the default implied role, state, property.or suggested semantics (if no
>    ARIA default) may be used.
>
> It certainly does, that's really helpful, thanks.

I just spotted a typo too: input type =
text<http://dev.w3.org/html5/spec/states-of-the-type-attribute.html#text-type-text-state-and-search-state-type-search>
, tearch<http://dev.w3.org/html5/spec/states-of-the-type-attribute.html#text-type-text-state-and-search-state-type-search>,
...

-- 
Lee
Received on Friday, 29 June 2012 14:38:48 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:32 UTC