You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This ticket covers the troubleshooting of additional issues identified with using Narrator.
We should wait to complete this ticket until we have access to NVDA on our USTP laptops, so that we can directly compare Narrator to NVDA and VoiceOver. If an issue exists in just Narrator, but not NVDA or VoiceOver, I believe it can be safely ignored.
Screen Reader issues discovered using Narrator
Case Overview
The phone number is not read as a phone number. It should probably skip the hyphens.
The main landmark is read as “Contains Style. Main Landmark.” That’s a bit odd.
It starts reading the navigation on the left when it starts getting into the Main landmark. Should it skip that?
Case Filed Date and Debtor Tax ID are parsed strangely on Narrator. Reads the field label, but not the value.
It does not audibly tell the screen reader that Case Overview is selected. It should probably have a selected state.
Court Docket
The “Filter By Summary” dropdown is not labeled as such when tabbing through. Don’t know what you’re filtering.
The docket entry numbers are just read as “two” and “three”. No other context.
When you tab through the filters in the docket entry list, it disables scan mode (which it’s supposed to when you have a text input field), but it doesn’t re-enable it when you leave. You have to remember to re-activate scan mode.
The “start reading continuously from this point on” control seems to be broken, it always starts at the top of the main landmark. That’s annoying. Unsure if there’s anything we can do about it, though.
Audit History
Depending on how the screen reader parses through the page, it either does or does not read the info alert (only saying “status”).
The text was updated successfully, but these errors were encountered:
This ticket covers the troubleshooting of additional issues identified with using Narrator.
We should wait to complete this ticket until we have access to NVDA on our USTP laptops, so that we can directly compare Narrator to NVDA and VoiceOver. If an issue exists in just Narrator, but not NVDA or VoiceOver, I believe it can be safely ignored.
Screen Reader issues discovered using Narrator
The text was updated successfully, but these errors were encountered: