- From: Bailey, Bruce <Bruce_Bailey@ed.gov>
- Date: Fri, 17 Nov 2000 09:04:15 -0500
- To: "'Brian Lee Richwine'" <brichwin@indiana.edu>
- Cc: "'w3c-wai-ig@w3.org'" <w3c-wai-ig@w3.org>
Thanks Brian! The "Select a Channel" is exactly the kind of counter-example that I am looking for at URL: <http://www.internet.com/home-d.html> For those using a screen reader, there are about two hundred choices (in fourteen drop down menus) between the links for "Dig Deeper: Power Search" and "internetnews.com". Much to my amazement, these hidden links ARE accessible in Lynx. (The category headers are lost however, due to missing ALT tags). The underlying JavaScript is quite daunting. From what I can tell, large blocks of text (at the end of the source) are inside <div id="xyz"> tags. JavaScript is used to hide the blocks and float them to assigned areas. OnMouseOver events toggle the hide attribute. Can any JavaScript junkies on the list boil the techniques being used down better than this? Are there things to look for in the source code that indicate that the JavaScript will be problematic? It seems to me that none of the individual techniques are necessarily inaccessible, but the combination of them is quite problematic. Is this assessment correct? By the way, the raw text IS in the source code. I was have some interesting effects using the browsers "Find (on this page)" command. I am curious as to how JFW handles these phantom finds. Since the hidden text is real text and not images, it is also worth noting that the drop-down menus scale nicely (except at the largest setting, the lowest items drop off the screen and are not available). Cheers, Bruce > -----Original Message----- > From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org] On > Behalf Of Brian Lee Richwine > Sent: Thursday, November 16, 2000 5:55 PM > To: Bailey, Bruce > Cc: 'Marti'; w3c-wai-ig@w3.org > Subject: Re: Looking for bad JavaScript examples! > > try www.internet.com > I think the menus across the top of the screen might be what you are > looking for. They only appear when the mouse cursor runs > across the dots > beneath the menu titles (they are the diaganol ones...). > I work in an adaptive technology lab and have users using > Jaws 3.7 with > refreshable brail and voice. We haven't figured out a way to > access those > menus yet. > > -brian
Received on Friday, 17 November 2000 09:04:41 UTC