Cannot speech whitelist textarea with NVDA screen reader

[riku22]

Prerequisites

• I verified that this is not a filter issue
  • Filter issues MUST be reported at filter issue tracker
• This is not a support issue or a question
  • Support issues and questions are handled at /r/uBlockOrigin
• I performed a cursory search of the issue tracker to avoid opening a duplicate issue
  • Your issue may already be reported.
• I tried to reproduce the issue when...
  • uBlock Origin is the only extension
  • uBlock Origin with default lists/settings
  • using a new, unmodified browser profile
• I am running the latest version of uBlock Origin
• I checked the documentation to understand that the issue I report is not a normal behavior

Description

I use NVDA software which reads character information on the screen of my computer.
However, NVDA can not make the text area of the whitelist read correctly.

Steps to Reproduce

1. Install NVDA.
2. Open the UBlock setting screen.
3. Open a whitelist.
4. Focus on the text field where the whitelist is written.
5. Press the up arrow, down arrow, left arrow, or right arrow, to speak.

Expected behavior:

• When I press the up arrow or down arrow, it reads as "about-scheme".
• When I press the left arrow or right arrow, it reads as "a", "b", "o".

Actual behavior:

It reads it as "blank".

Remarks

In older versions, I read it correctly.

Your environment

• uBlock Origin version: 1.18.4
• Browser Name and version: Google Chrome 72.0.3626.109
• Operating System and version: Windows10 1809 64bit

[uBlock-user]

Something to do with the translation perhaps..

@gorhill

[riku22]

I switched Chrome's language to English and tried it, but it did not change.

[uBlock-user]

Does it occur on Firefox ?

[gorhill]

Probably related to using CodeMirror. CodeMirror's issue tracker will need to be investigated to find out if such issue has been reported.

[riku22]

Does it occur on Firefox ?

No.

[gorhill]

Related: nvaccess/nvda#7285

Using contentEditable is supposed to help. I can't remember what exactly, there were glitches when I set CodeMirror widgets to use contentEditable. However these might be acceptable if it solves the issue here, as long as that rendering mode is opt-in so as to not inconvenience those who do not need NVDA support.

Also, my understanding is that the creators of CodeMirror do want to address accessibility issues as a core design factor in their ongoing refactoring of CodeMirror, so if I add a setting in uBO to deal with the issue here, such setting might become obsolete in the future. Because if this, I think it should be a advanced setting rather than one with a dedicated UI.

[DimitrisKalaboukas]

@gorhill Also, refer to nvaccess/nvda#8691.

I close the issue as unrelated to NVDA, waiting for new version of CodeMirror library with improved accessibility, as reported by @Neurrone. Until that moment, obviously the problem still occurs, after release I consider if open this issue again.

[krystian3w]

new version of CodeMirror library with improved accessibility

It will this fix be incorporated into raw CodeMirror 5?