WebAIM - Web Accessibility In Mind

E-mail List Archives

weirdness with NVDA reading multidecimal numbers

for

From: glen walker
Date: May 10, 2021 6:54PM

If you have a number with three parts, such as a success criteria, and the
third number is double digit, such as 1.4.10, NVDA seems to think the
number is a date, sort of. It thinks the first two numbers are a date and
the third number is just a number.

I tried this with html, with and without list structures, and tried it in a
word doc both with and without multilevel list formatting, and with a
simple text document.

Numbers like 1.2 or 1.2.3 read just fine. In fact, 1.2.X reads fine from
1.2.1 up to 1.2.9. But when the last number goes to double digit, 1.2.10,
1.2.11, all the way up to 1.2.99, NVDA says "January 2nd" and then the
third number. When I hit 1.2.100, NVDA is back to announcing all three
numbers.

(Note, depending on your locale settings, 1.2.10 might read as January 2nd
or it might read as Febuary 1st.)

I think it's a bug in NVDA. Nothing in the settings seems to prevent it.
It's somewhat related to this github issue, but not exactly.

https://github.com/nvaccess/nvda/issues/8103

Has anyone else noticed this? It's not a problem with JAWS.