What to make visible to accessibility API?
What to make visible to accessibility API?
- Subject: What to make visible to accessibility API?
- From: Ray Fischer <email@hidden>
- Date: Wed, 19 Jan 2005 16:27:42 -0800
Accessibility Cadets:
I've been working on making my app be accessible and work with
VoiceOver for a little
while now, and it's generally been going pretty well, but and I came
across a design
question which I don't know the answer to and can't find the answer to.
Simply: What do I make accessible?
There are LOTS of UI elements that I control. Some are on the screen
and visible, others
are not visible at all, and still others would be visible be if they
were on the screen or in
the window. It's this last category that is ambiguous.
Examples of visible-but-hidden objects include menu items and document
contents that
are scrolled out of the view. VoiceOver is supposed to be a screen
reader, meaning that
it's presumably going to represent objects that are actually on the
screen (as opposed to
apps like JAWS which is a document reader and will read document
contents that are not
actually visible on the screen).
To verify my assumption I tried VoiceOver with menu items and
discovered that they can
be navigated even when closed. That could be a bug, so I'm asking here.
Is there a rule about what I make visible via the accessibility API?
----
Ray Fischer
Adobe Systems
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden