4 ms·

And a screen reader would have no idea how to parse it without a special case... I've seen stuff tagged with this a lot and every so often someone mentions this

And a screen reader would have no idea how to parse it without a special case... I've seen stuff tagged with this a lot and every so often someone mentions this issue and I've yet to find an explanation other than if you already know about it it's easier to search for. I appreciate the advice nonetheless but it's just such an odd choice for making it discoverable.

ChadNauseam 4y ago
Why would a screen reader have any more trouble with it than someone reading it normally? I usually read it as "ay-one-one-why" or "ally", is that how a screen reader would interpret it?
- neltnerb 4y ago
  Right, it would read it as "ay-one-one-why". And if you're trying to dictate it, you'd have to say "ay-one-one-why". I don't want to distract from the main point, which is that you should make your websites accessible and that doing so mostly involves not letting some UI designer use a cool trick that lets them do some cute effect that has the side effect of breaking the experience when using accessibility tools. Because they're usually written by people without a need for accessibility tools they don't even notice what they're doing. This is extremely important educational work. And 'a11y' is less horizontal width, so someone who needs to zoom in really far to read text would probably appreciate it, or someone who can still type but doesn't do dictation has to hit fewer keys. But what other situation does it help with? It's jargon, You have to just kind of know that there are 11 characters between the 'a' and the 'y' in accessibility? If the goal is to educate people who don't need accessibility tools themselves it should not be a challenge for people who aren't in the know to find the information. I appreciate the effort and recognize that it caught on. I just don't get why, it seems like it is throwing a needless barrier in the way of the target audience finding the resources. I still try to follow the ideas presented, I just don't understand making it require jargon to find.
  - tarboreus 4y ago
    I use a screen reader and it says "A eleven Y." (As in the letters being said out loud.) It's really not confusing.

ChadNauseam 4y ago

Why would a screen reader have any more trouble with it than someone reading it normally? I usually read it as "ay-one-one-why" or "ally", is that how a screen reader would interpret it?

neltnerb 4y ago
Right, it would read it as "ay-one-one-why". And if you're trying to dictate it, you'd have to say "ay-one-one-why". I don't want to distract from the main point, which is that you should make your websites accessible and that doing so mostly involves not letting some UI designer use a cool trick that lets them do some cute effect that has the side effect of breaking the experience when using accessibility tools. Because they're usually written by people without a need for accessibility tools they don't even notice what they're doing. This is extremely important educational work. And 'a11y' is less horizontal width, so someone who needs to zoom in really far to read text would probably appreciate it, or someone who can still type but doesn't do dictation has to hit fewer keys. But what other situation does it help with? It's jargon, You have to just kind of know that there are 11 characters between the 'a' and the 'y' in accessibility? If the goal is to educate people who don't need accessibility tools themselves it should not be a challenge for people who aren't in the know to find the information. I appreciate the effort and recognize that it caught on. I just don't get why, it seems like it is throwing a needless barrier in the way of the target audience finding the resources. I still try to follow the ideas presented, I just don't understand making it require jargon to find.
- tarboreus 4y ago
  I use a screen reader and it says "A eleven Y." (As in the letters being said out loud.) It's really not confusing.