Bram,

Yes, an example would be helpful. We hope to address some of this in future versions as well.

Aaron

On 3/28/2011 1:58 AM, Bram Duvigneau wrote:
Hi Aaron,

It's a system used by one of our clients internally and so it is protected by a login. I'll see if I can save a dump of the page to show you what's going on.

Furthermore, before I started working in the AT business recently I did web development. I know quite some people who write HTML/CSS/Javascript on a professional basis and as far as I know, they all think that display: none hides content from all screenreaders. If they are building the type of menu system you're describing, a negative position is mostly used these days. The negative position positions the element outside of the browser viewport, but as far as I know all screenreaders will render such elements.

Besides the assumption I mentioned above, more and more websites are starting to show/hide parts of the page using Javascript dynamically. I think the use of such web pages/apps might outgrow the number of menu systems you are describing. So, please consider changing the behavior for such elements in the next version of Window-eyes, or make it configurable if you don't want to break backwards compatibility.

Bram

On 28 mrt 2011, at 02:37, Aaron Smith wrote:

Window-Eyes takes a different approach to DIVs with a display: none style to provide access to some dynamic menu systems. Typically, they'll only be announced when their position is also set to absolute (or are a child of some element whose position is absolute, I believe). Can you provide a URL to the page in question?

Aaron

On 3/27/2011 3:07 PM, Bram Duvigneau wrote:
Hi all,

I'm currently looking into a somewhat inaccessible web application. The
application shows/hides some form fields based on certain conditions.
For example, the user has to specify an address and if he/she has moved.
If the user indicates that he/she has moved, some new fields appear
where the user could enter the new address.

The showing/hiding of the fields is done by setting the display CSS
attribute to block/none of the<div>  surrounding the fields. NVDA as
well as JAWS hide the fields when display is set to none and that's the
behavior I'd expect. However, Window-eyes shows this fields regardless
of the value of display. I would like to change the CSS style on this
elements to let Window-eyes do the right thing. It's unsure for now if
the developers of this web app are willing to change their code, if not
I'm probably going to write a script that changes the style via Internet
Explorers' DOM.

The only relevant article I can find on this matter is from a few years
ago and can be found here:

http://juicystudio.com/article/screen-readers-display-none.php

My question is if there is some official documentation on the way
Window-eyes determines when to hide HTML elements?

Cheers,

Bram


--
Aaron Smith
Web Development * App Development * Product Support Specialist
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 *gwmicro.com  <http://gwmicro.com>

To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.


--
Aaron Smith
Web Development * App Development * Product Support Specialist
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com

To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.

Reply via email to