3 ms·

In throwing out the complexity of HTML, Gemini is also disposing of some markup that really helped screenreaders properly handle content. It would be a real sha

In throwing out the complexity of HTML, Gemini is also disposing of some markup that really helped screenreaders properly handle content. It would be a real shame if this "return to the good internet" left out the visually impaired. I agree with the goals of returning to a more bare-bones, text-heavy internet, but please, include the disabled in your vision from day one!

Munksgaard 6y ago
I must admit that I don't know anything about screenreading or accessibility in general, but I think you raise a valid concern: Certainly, the "next-generation good internet" should be accessible to all. However, I would think that being much simpler (also, mind you, content-wise) would be a positive thing for gemini, in this context? Would you care to elaborate on what kinds of things are made harder by the choices gemini made? And what do you think could be done to alleviate those problems?
blindgeek 6y ago
As a blind person, I dearly miss the textual Internet as it was. The original Internet -- the textual one -- was perfectly accessible. The extra markup added to HTML to help screen readers was added because the web stack had gotten too complex, not because it was too simple.
- Mediterraneo10 6y ago
  The lang attribute added to the span tag in HTML really helps with ensuring that a screenreader outputs quoted foreign-language text in that language, instead of just pronouncing gibberish. And this tag and attribute go pretty far back into the 1990s, it is not part of the modern-web-gone-mad. So, similar markup is one of those little things that Gemini should have thought about from the very beginning, and it would not have made their stack appreciably more complex.
  - selfhoster11 6y ago
    Foreign language text could potentially be auto-detected. You could either use some sort of an NN based approach, or use an algorithm like the one that browsers use for detecting the text encoding of a page where that's not given.

Munksgaard 6y ago

I must admit that I don't know anything about screenreading or accessibility in general, but I think you raise a valid concern: Certainly, the "next-generation good internet" should be accessible to all. However, I would think that being much simpler (also, mind you, content-wise) would be a positive thing for gemini, in this context? Would you care to elaborate on what kinds of things are made harder by the choices gemini made? And what do you think could be done to alleviate those problems?

blindgeek 6y ago

As a blind person, I dearly miss the textual Internet as it was. The original Internet -- the textual one -- was perfectly accessible. The extra markup added to HTML to help screen readers was added because the web stack had gotten too complex, not because it was too simple.

Mediterraneo10 6y ago
The lang attribute added to the span tag in HTML really helps with ensuring that a screenreader outputs quoted foreign-language text in that language, instead of just pronouncing gibberish. And this tag and attribute go pretty far back into the 1990s, it is not part of the modern-web-gone-mad. So, similar markup is one of those little things that Gemini should have thought about from the very beginning, and it would not have made their stack appreciably more complex.
- selfhoster11 6y ago
  Foreign language text could potentially be auto-detected. You could either use some sort of an NN based approach, or use an algorithm like the one that browsers use for detecting the text encoding of a page where that's not given.