Re: Document accessibility questions
Re: Document accessibility questions
- Subject: Re: Document accessibility questions
- From: Mike Engber <email@hidden>
- Date: Thu, 10 Feb 2005 16:12:10 -0800
We generally treat object that are invisible due to clipping as visible
and make them accessible. This applies to stuff that is scrolled out of
view, content of windows that are hanging off the bottom of the
monitor, ...
Those items are, conceptually, still available as part of the ui (e.g.
you can tab to them).
We have provided ways for assistive apps to make themselves robust
against problems like the 50,000 page document. Text can be asked for
in chunks. There's a way to find out what the visible text is.
Similar issues arise in large tables and lists. Any array valued
attribute (e.g. AXChildren) can be accessed in chunks.
Our philosophy has been to leave it up to the assistive app to handle
the problem of asking for too much data.
That being said, sometimes you may have widgets that are smart and the
only information available is that which is actually being show. In
this case I would _not_ advocate going to great lengths to create the
invisible information.
So, in general, my advice is to return as much information as you have
readily available.
-ME
_______________________________________________
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