WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: ARIA difficult for non-screenreader users?

for

From: Bryan Garaventa
Date: May 13, 2013 8:59AM

Here is one possibility, if you need to provide additional instructions for
keyboard usage, you can do this using CSS like so:

.tab:focus:after {
position: absolute;
content: 'Use the arrow keys to navigate through each tab';
}

This will display the message visually when the tab has focus.

----- Original Message -----
From: "Patrick H. Lauke" < <EMAIL REMOVED> >
To: < <EMAIL REMOVED> >
Sent: Monday, May 13, 2013 7:55 AM
Subject: Re: [WebAIM] ARIA difficult for non-screenreader users?


On 13/05/2013 15:38, Bryan Garaventa wrote:
> Actually combining different keyboard interaction models with ARIA that
> don't follow the spec, causes many more accessibility issues than it seems
> to solve.
>
> E.G Tabbing through menu items that contain role=menuitem makes it seem
> like
> many menus are on the same page, the same with Listbox options, the same
> with ARIA Tabs, and so on.
>
> If the scripting can't be made to work properly for an ARIA widget, then
> ARIA should not be used, otherwise this perpetuates bad ARIA
> implementations
> across the web.

So either do it right (as per ARIA) and risk having keyboard users not
knowing/being able to operate a site, or avoid using ARIA? Hmm...there
must be some solution that satisfies both camps...(but I guess it's
difficult without a concrete example to rip apart)

P
--
Patrick H. Lauke
re·dux (adj.): brought back; returned. used postpositively
[latin : re-, re- + dux, leader; see duke.]

www.splintered.co.uk | www.photographia.co.uk
http://redux.deviantart.com | http://flickr.com/photos/redux/
twitter: @patrick_h_lauke | skype: patrick_h_lauke