- From: Stephani Roberts Lincoln <stephani@MIT.EDU>
- Date: Tue, 18 May 2004 13:37:24 -0400
- To: "Jim Thatcher" <jim@jimthatcher.com>, w3c-wai-ig@w3.org
Hi Jim, Thanks for testing this. So, as far you know, is there a safe way to hide something visually in CSS but have it visible to a screen reader? We have a number of web applications that are for financial folks here at MIT and the developers are always looking for a clever way to give cues to screen reader users that may not be necessary for sighted users, mainly because the extra information creates additional "noise" in these apps -- many of which are already jam packed with information. thanks, steph At 11:25 AM 5/18/2004 -0500, you wrote: >Hi Steph, > >I am using JAWS 4.51 and for me visibility:hidden hides the text from JAWS. >Visibility:none is not valid style but display:none is. Display:none hides >the text from JAWS for me. Both Visibility:hidden and display:none hide the >text from both Window-Eyes (4.5) and HPR (3.02) as well. My test file is >http://jimthatcher.com/test/visibility.htm. Bottom line, both >visibility:hidden and display:none hide JAWS, Window-Eyes, and HPR on my >machine. > >Jim >Accessibility, What Not to do: http://jimthatcher.com/whatnot.htm. >Web Accessibility Tutorial: http://jimthatcher.com/webcourse1.htm. > > >-----Original Message----- >From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org] On Behalf >Of Stephani Roberts Lincoln >Sent: Tuesday, May 18, 2004 10:52 AM >To: 'WAI-IG' >Subject: RE: "Blind for a Day" - visibility: hidden vs none > > >Hi, > >Related to some comments here and screen readers response to visibility: >none. With JAWS visibility:hidden works to hide text from the browser >display while the screen reader picks up the text and voices it (not true >of visibility:none). Can anyone tell me if this true for IBM HPR and Window >Eyes? > >thanks, >Steph > > >At 07:11 PM 5/17/2004 -0500, Jim Thatcher wrote: > > >Joe, > > > >It has nothing to do with verbosity settings. His recommendations are > >absolutely right on; every one. He did mention putting main content near >the > >top because "the thing I hated the most was having to blast past five > >hundred links in a sidebar in order to get to the actual content." I am > >impressed with how well this guy understood the problems of listening to >web > >content. Very unusual. > > > >Jim > >Accessibility, What Not to do: http://jimthatcher.com/whatnot.htm. > >Web Accessibility Tutorial: http://jimthatcher.com/webcourse1.htm. > > > > > >-----Original Message----- > >From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org] On >Behalf > >Of Joe Clark > >Sent: Monday, May 17, 2004 1:36 PM > >To: WAI-IG > >Subject: "Blind for a Day" > > > > > >Bloggeur tries out IBM Home Page Reader and shares tips. He should > >learn about verbosity settings, though. > > > ><http://www.mojombo.com/archives/000034.html> > >-- > > > > Joe Clark | joeclark@joeclark.org | <http://joeclark.org/access/> > > Author, _Building Accessible Websites_ | <http://joeclark.org/book/> > > Expect criticism if you top-post
Received on Tuesday, 18 May 2004 13:42:52 UTC