Joseph Selbie kirjoitti 5.10.2007 kello 20:40: > I'll make it even more complicated: it isn't just a matter of > whether the > screen reader (say Jaws) can read your code. The question will > become can > the reader effectively make every feature and function usable by > the user.
And even more complicated: let's assume that the code works perfectly and you have perfect understanding between the screen reader and yourself. Effectively: you'd have someone who you know and someone who knows you handling the mouse and the keyboard. You know, like a considerate human. Now, how would you navigate the site and how effective would that be? I guess that would set the bar for screen reader usability. But that wouldn't be the high mark. The mind's eye can see with touch. It would be faster to "see" the pixels if there was a perfect touchscreen that can display edges, maybe even grades of gray as little bumps - and such screen would respond to taps and gestures. Blindsight! Downgrading those to something that can actually be implemented is hard if not impossible during our careers. I'm all in with making technology accessible, and I like standards, but suing companies for not reaching such an arbitrary bar is questionable. Best, Petteri -- Petteri Hiisilä Senior Interaction Designer iXDesign / +358505050123 / [EMAIL PROTECTED] "Simple is better than complex. Complex is better than complicated." - Tim Peters ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] List Guidelines ............ http://beta.ixda.org/guidelines List Help .................. http://beta.ixda.org/help Unsubscribe ................ http://beta.ixda.org/unsubscribe Questions .................. [EMAIL PROTECTED] Home ....................... http://beta.ixda.org
