On 19 September 2012 20:48, Toshio Kuratomi <a.badger(a)gmail.com> wrote:
Accessibility of Web Apps
* Stop worrying about accessibility
- We can use whatever works in our standard graphical browsers since we
no longer target people who cannot use them with (up to) all five senses.
* Continue to target screen readers for things we write
- Unless someone can find some better news than I've been able to, this
means, among other things, having fallbacks for pages in apps that use
javascript, imagemaps, or other things that don't work in text-mode browsers so
people using screen readers have a method of accessing the same functionality.
This is usually implemented by rendering the fallback as the html page. Then
having javascript replace the contents of the page with whatever is needed to
implement the more dynamic view.
* Query people with accessibility needs to see how we can better serve them.
I think we need to find out how people who are blind or amputees are
using our site so we can a) see what solutions they are using, b) if
our site is working for them really now, and c) what things we do work
and don't work. Without that we are in a guess mode and everything we
do is flailing in some way or another.
--
Stephen J Smoogen.
"Don't derail a useful feature for the 99% because you're not in it."
Linus Torvalds
"Years ago my mother used to say to me,... Elwood, you must be oh
so smart or oh so pleasant. Well, for years I was smart. I
recommend pleasant. You may quote me." —James Stewart as Elwood P. Dowd