Re:Asking for accessibility gets you nothing but grief.
by prodigal_erik on Saturday September 03, 2011 @05:00PM
(#2958102)
> basic HTML interface, preferably no AJAX at all
This mode is step one, just basic competence in authoring. If your content isn't available in a self-describing form at a stable URL (regardless of any presentation you may layer on top of that later), you are building a lowly client/server app that leeches off the Web rather than contributing to it.
Re:Asking for accessibility gets you nothing but grief.
by comex on Saturday September 03, 2011 @10:41PM
(#2958671)
What's wrong with [gear icon] -> "Search settings", select "Do not use Google Instant"? I accidentally kept Google Instant off for months by selecting that option.
Re:Asking for accessibility gets you nothing but grief.
by masklinn on Sunday September 04, 2011 @08:41AM
(#2959310)
Try that one with VoiceOver and your eyes closed. Then, consider that you know it exists.
Re:Asking for accessibility gets you nothing but grief.
by jquery on Saturday September 03, 2011 @05:31PM
(#2958160)
Most people would consider it Internet Explorer's fault if it crashed on the majority of webpages.
Re:Asking for accessibility gets you nothing but grief.
by CJefferson on Saturday September 03, 2011 @06:06PM
(#2958235)
If people, and in particular libraries like jquery, didn't specialise for IE, many websites would be unreadable and leak so much memory they would rapidly crash IE.
Also in this case, even if Google Instant wasn't crashing Jaws, Google Instant plays havoc with screen readers (yes, I have experience of this), and as the article says, Google haven't provided a global off option, which would be really useful.
All most screen-readers want is a really basic HTML interface, preferably no AJAX at all. Even if it is slow and needs to re-load a lot, that is still preferable to no access.