I know that JAWS, by default, will ignore <span/>
tags. My team got around that issue. Now, however, we have some content that is displayed using <span/>
tags where the text displayed for sighted users doesn't play well with JAWS reading the information out. In our specific case, it would be international bank account numbers, which can contain letters. In this case, instead of reading individual digits, JAWS attempts to read the content as a word, resulting in predictably poor output.
So, a couple of questions:
- Given that this is part of a large page that I have neither the time nor the permission to refactor, is there a way to get this working within the constraints I've described?
- If you were to write a page like this from scratch, what's the best practice for crafting the page such that I would have the ability to supply "alternate" text for read-only, non-interactive content?
If it helps, the outcome I'm envisioning is something like this:
<span id="some-label" aria-label="1 2 3 4 5 A">12345A</span>
We have been unable to come up with any combination of techniques that would have JAWS read: "1 2 3 4 5 A" instead of reading "12345A" as a single word.