4 ms·

> I guess I'm saying don't be a jerk, be mindful of sight-impaired people when designing your products. Agreed. Or name your javascript tool the same thing as

> I guess I'm saying don't be a jerk, be mindful of sight-impaired people when designing your products. Agreed. Or name your javascript tool the same thing as the most popular screen reader. JAWS: https://news.ycombinator.com/item?id=10005415 https://news.ycombinator.com/item?id=10005415 JAWS: http://www.freedomscientific.com/Products/Blindness/JAWS http://www.freedomscientific.com/Products/Blindness/JAWS They even preserved the all caps. Now when vision impaired people search for their screen reader, they get results for a javascript framework, since they're both in the context of software as far as a search engine is concerned.

Kiro 11y ago
Seems like a very minor problem.
- stedaniels 11y ago
  For someone who's sighted.
  - j42 11y ago
    Really, though? I always design with accessibility in mind, but I feel like there are more visceral complications than having to add a little extra context to a web search. Almost everyone in development has encountered unfortunate name collisions that make what you're looking for hard to find... it's a pretty common inconvenience. Usually you just refine the query, like: "JAWS screenreader." The first result takes you where you probably intended to go, and it's at most 1-2 keystrokes away. I think the real lesson here is to design inclusively. HTML has a lot of handy attributes to augment content; knowing & implementing the essentials means someone can follow the core flow of your site/application without relying on visual cues. And for the pragmatists... it has the added benefit of self-documenting and increasing semantic conformity in your markup.
  - Kiro 11y ago
    I don't see how this problem is related to vision at all. Besides, why would someone need to google JAWS all the time? It's a software you install once. It's such a trivial issue compared to the accessibility problem on websites.
poizan42 11y ago
Seems like exactly what trademark law was designed to prevent.
aw3c2 11y ago
Oh come on, surely they get results for the animal as well? If you want a unique name, you have to invent one.

Kiro 11y ago

Seems like a very minor problem.

stedaniels 11y ago
For someone who's sighted.
- j42 11y ago
  Really, though? I always design with accessibility in mind, but I feel like there are more visceral complications than having to add a little extra context to a web search. Almost everyone in development has encountered unfortunate name collisions that make what you're looking for hard to find... it's a pretty common inconvenience. Usually you just refine the query, like: "JAWS screenreader." The first result takes you where you probably intended to go, and it's at most 1-2 keystrokes away. I think the real lesson here is to design inclusively. HTML has a lot of handy attributes to augment content; knowing & implementing the essentials means someone can follow the core flow of your site/application without relying on visual cues. And for the pragmatists... it has the added benefit of self-documenting and increasing semantic conformity in your markup.
- Kiro 11y ago
  I don't see how this problem is related to vision at all. Besides, why would someone need to google JAWS all the time? It's a software you install once. It's such a trivial issue compared to the accessibility problem on websites.

poizan42 11y ago

Seems like exactly what trademark law was designed to prevent.

aw3c2 11y ago

Oh come on, surely they get results for the animal as well? If you want a unique name, you have to invent one.