Closed Bug 1638580 Opened 4 years ago Closed 4 years ago

about:config broken with JAWS screen reader

Categories

(Firefox :: Disability Access, defect)

defect

Tracking

()

RESOLVED FIXED

People

(Reporter: asa, Unassigned)

Details

In Firefox 76.0.1 (and perhaps since the re-write?) about:config isn't working with the JAWS screen reader. JAWS does not read any preferences after entering a filtering search - just sees an empty list box.

Setting as S2 severity because there's a workaround with the old about:config.

Severity: -- → S2

There's nothing in our code that would cause this table to be reported as a list box. My guess is that JAWS has special case code to treat any table on the about:config page as a list box, perhaps because the old about:config page had an interactive table (as opposed to the non-interactive table on the new page) that they wanted reported as a list box. I've contacted Vispero (the JAWS vendor) about this.

Vispero confirmed that JAWS was special casing this and has fixed it on their side for future versions.

We could probably hack around this for older versions by reporting something other than about:config for the URL of the page via a11y APIs, but I'm not thrilled about that idea.

Asa, what are your thoughts on how important it is for us to hack around this for older versions of JAWS? On one hand, JAWS users tend to update slowly due to cost. On the other hand, the issue is on the JAWS side and about:config is a pretty rare and advanced use case.

Flags: needinfo?(asa)

about:config is advanced and for now at least there's still the older about:config at chrome://global/content/config.xhtml I don't think we should invest in a workaround.

Flags: needinfo?(asa)

Okay. Closing as fixed, since this is fixed for future JAWS versions.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED

Thank you for working on this even though it ended up being a JAWS issue. FWIW I think folks need to keep their AT updated at this point to keep up with the frequent OS and core application and API changes, so I tend to agree that legacy versions of JAWS are less of a concern.

You need to log in before you can comment on or make changes to this bug.