4 ms·

"# Google (for the search engine) – Google Instant crashes Jaws, and the current “solution” is to have a link to turn Instant off. Except it only works for a si

"# Google (for the search engine) – Google Instant crashes Jaws, and the current “solution” is to have a link to turn Instant off. Except it only works for a single pageview at a time, ARRRRGH)." How is this Google and not Jaws fault?

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 ago
  Most people would consider it Internet Explorer's fault if it crashed on the majority of webpages.
  - CJefferson 15y ago
    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.
- comex 15y ago
  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.
  - masklinn 15y ago
    Try that one with VoiceOver and your eyes closed. Then, consider that you know it exists.
lini 15y ago
We've been using NVDA (http://www.nvda-project.org/ http://www.nvda-project.org/) for a while now and it works (for our screen reader needs) better than JAWS. Plus it's free and open source.
- jquery 15y ago
  Interesting, I may begin contributing to that. I strongly believe this a problem to be solved by technology, not heavy-handed legislation that will add billions of dollars of costs to web development and innovation.
skermes 15y ago
The same way that it's your fault if your new building doesn't provide adequate wheelchair access, not the wheelchair's fault for not being able to climb stairs.
masklinn 15y ago
> How is this Google and not Jaws fault? Not making it easy to disable is definitely google's fault.

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 ago
Most people would consider it Internet Explorer's fault if it crashed on the majority of webpages.
- CJefferson 15y ago
  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.
comex 15y ago
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.
- masklinn 15y ago
  Try that one with VoiceOver and your eyes closed. Then, consider that you know it exists.

lini 15y ago

We've been using NVDA (http://www.nvda-project.org/ http://www.nvda-project.org/) for a while now and it works (for our screen reader needs) better than JAWS. Plus it's free and open source.

jquery 15y ago
Interesting, I may begin contributing to that. I strongly believe this a problem to be solved by technology, not heavy-handed legislation that will add billions of dollars of costs to web development and innovation.

skermes 15y ago

The same way that it's your fault if your new building doesn't provide adequate wheelchair access, not the wheelchair's fault for not being able to climb stairs.

masklinn 15y ago

> How is this Google and not Jaws fault? Not making it easy to disable is definitely google's fault.