3 ms·
Most people would consider it Google's fault if their main page crashed Internet Explorer, even though it would technically be IE's fault. The internet is full
by CJefferson 15y ago
Most people would consider it Google's fault if their main page crashed Internet Explorer, even though it would technically be IE's fault. The internet is full of compromises.
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.
- prodigal_erik 15y ago> 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.
- jquery 15y agoMost people would consider it Internet Explorer's fault if it crashed on the majority of webpages.
- CJefferson 15y agoIf 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.
- comex 15y agoWhat'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.
- masklinn 15y agoTry that one with VoiceOver and your eyes closed. Then, consider that you know it exists.