W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2010

RE: Using ARIA to control screen readers

From: Jonathan Avila <jon.avila@ssbbartgroup.com>
Date: Fri, 12 Nov 2010 08:26:09 -0500
Message-ID: <eb77fcea9f024989f085152fccb6b659@mail.gmail.com>
To: w3c-wai-ig@w3.org, Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
Benjamin, I think you may have missed part of the conversation.  The point
was is that in the example you give which I am very familiar with you can
NOT know where the screen reader virtual cursor is current at.  With a
solution that provides a hotkey for reading items as well as description you
WILL know what the screen reader is reading because you will be directing it
to be announced via ARIA.


-----Original Message-----
From: Benjamin Hawkes-Lewis [mailto:bhawkeslewis@googlemail.com]
Sent: Friday, November 12, 2010 2:10 AM
To: Jonathan Avila
Cc: w3c-wai-ig@w3.org
Subject: Re: Using ARIA to control screen readers

On Fri, Nov 12, 2010 at 1:51 AM, Jonathan Avila
<jon.avila@ssbbartgroup.com> wrote:
> This would however require
> the user to learn some keystrokes for this site.  In addition, some screen
> reader like JAWS would not pass the single letter keystrokes through to
> the
> web application.

I think these are strong arguments against trying to attach this
functionality to the "D" key.

Typical screen readers provide a universal interface by which users
can jump from list item to list item and from heading to heading,
skipping intermediate content.

So in this case what's wrong with markup like:

     <h2>Ford Focus</h2>
     <p>description goes here</p>
    <p>description goes here</p>
... and so on ...

which would allow users to use the interface they already know?

Benjamin Hawkes-Lewis
Received on Friday, 12 November 2010 13:26:43 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:41 UTC