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

Re: Using ARIA in HTML

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Fri, 29 Jun 2012 14:24:19 +0100
Message-ID: <CA+ri+VnwTh7q7h1nc3CO1vAGMYBHBD5aZwz=-vouC388r9i_DA@mail.gmail.com>
To: Lee Kowalkowski <lee.kowalkowski@googlemail.com>
Cc: HTMLWG WG <public-html@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>
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.



On 29 June 2012 13:58, Lee Kowalkowski <lee.kowalkowski@googlemail.com>wrote:

> On 29 June 2012 13:23, Steve Faulkner <faulkner.steve@gmail.com> wrote:
>
>> I have posted an intial draft of a document I have been working on which
>> attempts to provide practical advice to developers on what ARIA to use in
>> HTML.
>>
>> http://dvcs.w3.org/hg/aria-unofficial/raw-file/tip/index.html
>>
>>
>> My intention is to provide a non normative resource that fills in the
>> gaps in the current HTML5 specification and a document that is more
>> readable (i.e. less jargonist) It does deviate from HTML5 in some of its
>> suggestions, these deviations are based on current implementation realities.
>>
>> all feedback welcome
>>
>
> This is extremely useful!  It took me a short while to understand the "Use
> default ARIA semantics?" column.  Can I just check?
>
> It looks like NO means that ARIA attributes are NOT REQUIRED if you wish
> them to be their default values.
>
> However, I'm not sure whether YES means they are REQUIRED or OPTIONAL, as
> in, whether you MUST use them or whether you MAY use them, if you wish them
> to be their implied defaults.
>
> Where the default says NONE, N/A for this column makes sense (because
> there is no default), and this is the value for most rows, but a few rows
> have YES or NO.  I *guess* NO means an ARIA attribute is NEVER required and
> YES means an ARIA attribute is ALWAYS required, but on these particular
> rows I'm not 100% sure what's right.
>
> --
> Lee
>
>


-- 
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
Received on Friday, 29 June 2012 13:25:42 UTC

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