Skip to main content

Non-focusable controls and JAWS

3 replies [Last post]
kyle
Offline
Joined: 2003-06-11
Points: 0

I have a number of labels that display useful information, but that are not focusable because that would put things into the tab cycle that shouldn't be. However I don't see how to get JAWS to access this information. Note: I'm not an experienced JAWS user. Is there a way to make non-focusable labels accessible to screen readers like JAWS?

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
kyle
Offline
Joined: 2003-06-11
Points: 0

I think I have my own answer. It looks like all labels need to be focusable to
be used by JAWS.

Is it common to provide two traversal policies with an application-- one for screenreader-enabled mode, and one for non-screenreader-enabled mode?

For non-screenreader users, it would be optimal to leave all of the labels
and similar controls out of the traversal policy.

zpm
Offline
Joined: 2003-06-16
Points: 0

> Is it common to provide two traversal policies with
> an application-- one for screenreader-enabled mode,
> and one for non-screenreader-enabled mode?

Yes, you can employ any number of traversal policies. You can even switch
between them on the fly without having to restart your application. Since
policies are inherited, you need to change policy for the top-level focus
cycle root container only, which is most likely to be your application's
Window. Of course, if your application has more than one Window, you'll
have to change the policy for all of them.

--
Peter

kyle
Offline
Joined: 2003-06-11
Points: 0

OK. I'll poll our users and see if it makes sense to have two different traversal policies, one for screenreader and one for nonscreenreader.

Thanks.