Tedd Sperling wrote: > > Can you explain what a screen reader would do with this? > > > > <h2>Please click the accessibility icon.</h2> > > <object type="application/x-shockwave-flash" name="movie" > > data="access.swf" style="width: 30px; height: 30px;"> > > <param name="movie" value="access.swf"> > > </object> > > No, I can't explain what a screen reader would do with it. However, > if someone could explain to me what a screen-reader/user combination > expects, then I probably can write the code.
Just to be clear, I wasn't trying to be facetious. I'm curious. Many accessibility guidelines make a lot of sense to me when I'm looking at the source. Simple things like labels give software a chance to communicate important information: <label for="email">Email</label> <input name="email"... Visually, this association is easy, but it requires an extra step when visual interpretation is not an option. That's why it's not obvious to me how a user knows how to find the accessibility icon in your example. That doesn't mean it's necessarily broken; I just want to know for my own education. > It seems that every time I come up with a CAPTCHA that is a bit more > accessible, I have very vocal members of the accessibility movement > telling me "Think about it!" without discussing what's wrong. It's > as if CAPTCHA's are to be shot on site regardless. Maybe if we > changed the name to something more politically correct. It's the approach I'm not particularly fond of, not the name. The name's clever enough. :-) Chris -- Chris Shiflett http://shiflett.org/ _______________________________________________ New York PHP Community Talk Mailing List http://lists.nyphp.org/mailman/listinfo/talk NYPHPCon 2006 Presentations Online http://www.nyphpcon.com Show Your Participation in New York PHP http://www.nyphp.org/show_participation.php
