WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: order of nesting when using ARIA and html 5

for

From: Jim Allan
Date: Jun 5, 2013 12:15PM

Has anyone filed a bug against the browsers for keyboard navigation to
these structural element? Most folks with disabilities are not using AT
that can modify how the user interacts with the browser/webpage (like
screen readers). This has huge implications for people who just use the
browser from the keyboard with no other AT.
Jim


On Tue, Jun 4, 2013 at 2:05 PM, Jared Smith < <EMAIL REMOVED> > wrote:

> On Tue, Jun 4, 2013 at 1:00 PM, Angela French < <EMAIL REMOVED> > wrote:
> > Would it suffice then to just use the ARIA role and skip the html5
> structural elements? Are there any "cons" for doing so?
>
> Probably not, at least right now. If other systems were to utilize the
> HTML5 structural element, such as a browser providing keyboard
> navigation to them (if only!), then these would not be available if
> you only use the ARIA attribute. There are advantages to using both,
> so if you're really doing HTML5, then I'd suggest using both... for
> now. As soon as assistive technology support improves for the native
> HTML5 elements, we can eventually drop the ARIA attributes - yet
> another argument for using both now.
>
> Jared
> > > >



--
Jim Allan, Accessibility Coordinator & Webmaster
Texas School for the Blind and Visually Impaired
1100 W. 45th St., Austin, Texas 78756
voice 512.206.9315 fax: 512.206.9264 http://www.tsbvi.edu/
"We shape our tools and thereafter our tools shape us." McLuhan, 1964