E-mail List Archives
Re: ARIA difficult for non-screenreader users?
From: Bryan Garaventa
Date: May 13, 2013 11:18AM
- Next message: Alastair Campbell: "Re: ARIA difficult for non-screenreader users?"
- Previous message: Alastair Campbell: "Re: ARIA difficult for non-screenreader users?"
- Next message in Thread: Alastair Campbell: "Re: ARIA difficult for non-screenreader users?"
- Previous message in Thread: Alastair Campbell: "Re: ARIA difficult for non-screenreader users?"
- View all messages in this Thread
True, but not to the extent of using ARIA hacks to do so.
This is where full keyboard accessibility comes in. If a component is fully
keyboard accessible, meaning that you can tab to it, use the arrow keys to
navigate it, use the Enter or Space keys to invoke it, then you can voice
all of these commands in Dragon. This is really the only way it can work
when using simulated controls.
An ARIA Button is a simple example of this.
E.G
<A class="button" href="#" role="button"> Do Something </a>
So if it is styled like a button, and the role reclasses it as a button for
screen reader users, voice navigation software like Dragon should also be
able to look at the accessibility tree and recognize that this should be
treated like a button.
Unfortunately it doesn't, and will only work as a link.
This doesn't mean that the ARIA implementation is wrong, or that offscreen
buttons should be used in conjunction with the ARIA Button so that Dragon
users can interact differently with the control. It does mean that pressure
needs to be put on the makers of Dragon to add basic support for ARIA.
You are welcome to do as you wish, but adding arrow support for ARIA Tabs
combined with making all such elements tabbable at the same time, will make
it impossible for screen reader users to determine the level of nested tab
groups when tabbing if present, since it breaks the metaphor.
----- Original Message -----
From: "Alastair Campbell" < <EMAIL REMOVED> >
To: "WebAIM Discussion List" < <EMAIL REMOVED> >
Sent: Monday, May 13, 2013 9:32 AM
Subject: Re: [WebAIM] ARIA difficult for non-screenreader users?
> Bryan Garaventa wrote:
>
>> It's important to note also that Dragon has no support for ARIA.
>
>
> Which makes it a pretty clear WAI-ARIA vs other audiences issue, therefore
> another good reason that we need more of a bridge between using ARIA and
> not.
>
> -Alastair
> > >
- Next message: Alastair Campbell: "Re: ARIA difficult for non-screenreader users?"
- Previous message: Alastair Campbell: "Re: ARIA difficult for non-screenreader users?"
- Next message in Thread: Alastair Campbell: "Re: ARIA difficult for non-screenreader users?"
- Previous message in Thread: Alastair Campbell: "Re: ARIA difficult for non-screenreader users?"
- View all messages in this Thread