Re: Fw: ARIA role restrictions in HTML5

HTML5 simply restricts the use of ARIA Roles on some Controls as the
addition of ARIA states and properties could cause a conflict.

The cases where it is restricted are plades where I have not seen anyone
use it. If anything we are going to expand on ARIA and we will be doing so
on ARIA 1.1 to be in line with HTML 5.1.

Note: We recently added ARIA to SVG2. It is also part of ePub3.

Rich


Rich Schwerdtfeger



From:	Phill Jenkins/Austin/IBM
To:	Richard Schwerdtfeger/Austin/IBM@IBMUS,
Date:	03/20/2013 03:05 PM
Subject:	Fw: ARIA role restrictions in HTML5


Have you been following these concerns?

____________________________________________
Regards,
Phill Jenkins,
+1 (512) 791-4517 mobile

----- Forwarded by Phill Jenkins/Austin/IBM on 03/20/2013 03:03 PM -----

From:	"Bryan Garaventa" <bryan.garaventa@whatsock.com>
To:	"David Ashleydale" <david@randomlife.com>,
Cc:	"Jonathan Avila" <jon.avila@ssbbartgroup.com>,
            <w3c-wai-ig@w3.org>
Date:	03/20/2013 02:33 PM
Subject:	Re: ARIA role restrictictions in HTML5



My concern is that ARIA works well right now when properly implemented.

Many others have thought the same, and have implemented  ARIA within web
applications across the web, not just on single page implementations, but
have built ARIA support into CMSs as well.

In short, ARIA is now entrenched in the web, and it will likely never leave
it regardless what the standards are.

 So it would be good to know whether ARIA recognition will ever be pulled
 out of browser and Assistive Technology support, sort of like pulling out
 the rug from all of these implementations, making previously accessible
 components suddenly inaccessible?

 ----- Original Message -----
 From: David Ashleydale
 To: Bryan Garaventa
 Cc: Jonathan Avila ; w3c-wai-ig@w3.org
 Sent: Wednesday, March 20, 2013 12:07 PM
 Subject: Re: ARIA role restrictictions in HTML5

 It's funny -- I always thought that ARIA would be kind of a preview for
 HTML 5. That the ARIA attributes would become part of the HTML spec.

 But it doesn't seem to be turning out like that.

 David

 On Wednesday, March 20, 2013, Bryan Garaventa wrote:
  I agree, anchor elements work well for this purpose, especially for
  graceful degradation with radio buttons.

  Regarding buttons, I often see A tags styled as buttons for form
  submission elements.

  Not having the ability to put role="button" on such elements to aid
  screen reader interaction, would impair accessibility, not enhance it.
  The same is true for Toggle Buttons, and Checkboxes.

  A tags are also used for Listbox Option elements, which is also used to
  support graceful degradation.

  This brings me to a question I've been wondering about.

  Is HTML5 supposed to replace ARIA, or will they work together? In other
  words, will components built using current standards compliant ARIA still
  be valid ten or twenty years from now?


   ----- Original Message -----
   From: Jonathan Avila
   To: w3c-wai-ig@w3.org
   Sent: Wednesday, March 20, 2013 7:25 AM
   Subject: ARIA role restrictictions in HTML5



   I was looking at the latest draft version of the HTML5 specification and
   noticed in the implicit aria semantics table it indicates that only a
   limited set of ARIA roles can be used with certain elements such as the
   anchor element to conform to the HTML5 specification.  Specifically you
   could not use a role of button, radio button, etc. on anchor elements.
   This seems problematic but makes good semantic sense.  One advantage of
   using anchors with hrefs for diverse ARIA roles is there is some
   progressive enhancement support.





   http://www.w3.org/html/wg/drafts/html/master/dom.html#sec-implicit-aria-semantics





   Jonathan