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

Re: How to make highlighted text accessible?

From: Devarshi Pant <devarshipant@gmail.com>
Date: Sat, 19 Oct 2013 11:05:30 -0400
Message-ID: <CAJGQbjtoe7EbFL1Ti4KN3-v5NwhxXvo7dwdMYcp1fnX-ek_0AQ@mail.gmail.com>
To: Lars Holm Sørensen <post@diversa.dk>
Cc: WAI Interest Group <w3c-wai-ig@w3.org>
Some tips:

A) Provide keyboard access to the active step indicator. So, on tabbing,
keyboard focus will go through the active step and into the form fields,
etc. You can even send focus to the next step as the user completes the
previous step.

B) State the active step in the page title as screen readers always voice
it.

Not sure if the following would be an effective solution, so posing it as a
question:
If the active step (text) receives focus, would aria role=tooltip,
aria-describedby and aria-hidden expose content / tooltip, like "step name,
active"? Although it works in form fields [3], I would be interested to
know your thoughts.
[3] http://oaa-accessibility.org/example/40/

-Devarshi
On Oct 19, 2013 7:32 AM, "Lars Holm Sørensen" <post@diversa.dk> wrote:

> Hello
>
> Can you suggest a good solution for the following case?
>
> I have a website, where the user goes through a 3 step workflow.
> The 3 steps are listed on top of the page, where the currently active step
> is highlighted with a CSS-colored background to tell the user which step
> she is performing right now.
>
> The 3 steps are just clean text, - no buttons or tabs, - not used for
> navigation.. They are just there to indicate where in the workflow we are.
>
> In the given situation there is no information for the screenreader user
> about where in the workflow she is right now.
> It might also be a problem if the page us used with customized styles.
>
> What would be the best way to let all users know about the current active
> step?
> Does aria provide any solution for this?
>
>
> Everything best:
> Lars Holm Sørensen
>
>
Received on Saturday, 19 October 2013 15:05:57 UTC

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