Read on Twitter
this is really obvious in hindsight, but if you have a d66 table and the entries are indexed with "11", "12", "13" etc, screenreaders are gonna say "eleven, twelve, thirteen"
The one built into Windows 10 does the following. I don't have other screenreader software with which to test it.
1 1 --> "one one"
1-1 --> "one to one"
1,1 --> "one, comma, one"
1, 1 --> "one [pause] one"
1 1 --> "one one"
1-1 --> "one to one"
1,1 --> "one, comma, one"
1, 1 --> "one [pause] one"
(still the default Windows one)
⚀⚀ --> [says nothing]
1[zero width space]1 --> "eleven"
so if you're writing a blog post or ebook you want to be intelligible, I'd stick with "1 1", "1 2" etc.
⚀⚀ --> [says nothing]
1[zero width space]1 --> "eleven"
so if you're writing a blog post or ebook you want to be intelligible, I'd stick with "1 1", "1 2" etc.
side note: the default windows screenreader has disappointingly inconsistent behaviour with speaking basic arithmetic.
"1-1" (hyphen) --> "one to one"
"1−1" (minus sign) --> "one one"
"1×1" --> "one times one"
"1÷1" --> "one divided by one"
Why does Microsoft hate subtraction?
"1-1" (hyphen) --> "one to one"
"1−1" (minus sign) --> "one one"
"1×1" --> "one times one"
"1÷1" --> "one divided by one"
Why does Microsoft hate subtraction?
this is true whether or not you use html5's <math> tag.
I *hope* dedicated screenreaders are more reliable with this, otherwise if your RPG is even remotely mathy you're gonna have to write "1 d 20 minus 5" or something.
I *hope* dedicated screenreaders are more reliable with this, otherwise if your RPG is even remotely mathy you're gonna have to write "1 d 20 minus 5" or something.
Oh! Super important!
Again, don't know how dedicated screenreaders handle it, but the Microsoft one won't pronounce the numbers in ordered lists.
So a sighted reader might see:
"Mien:
1. Hungry
2. Scared
3. Grumpy"
but the windows screenreader says "hungry, scared, grumpy"
Again, don't know how dedicated screenreaders handle it, but the Microsoft one won't pronounce the numbers in ordered lists.
So a sighted reader might see:
"Mien:
1. Hungry
2. Scared
3. Grumpy"
but the windows screenreader says "hungry, scared, grumpy"
You can sorta cheat this by having the text as a paragraph with line breaks instead of an ordered list,
<p>1. Hungry<br>
2. Scared<br>
3. Grumpy</p>
but the cadence of the reading will be off. It won't pause for linebreaks but it will pause for full stops after each number.
<p>1. Hungry<br>
2. Scared<br>
3. Grumpy</p>
but the cadence of the reading will be off. It won't pause for linebreaks but it will pause for full stops after each number.
so setting up a d6 table as an actual html table is probably the best solution here.
