[Accessibility] - Screen reader reads unnecessary contents before reading the textbox aria-label in a dialog while navigating with tab key
Type of report
Bug
Provide detailed reproduction steps (if any)
- Launch CKEditor 4 demo URL https://ckeditor.com/ckeditor-4/demo/
- Click on image toolbar item to open image dialog.
- Open NVDA.
- Tab till "URL" and "Alternative Text" field.
- Check whether it reads unnecessary contents before reading the aria-label of textbox.
Expected result
Screenraeder reads unnecessary contents before reading the field name while navigating through tab key. Issue is observed in Chrome + NVDA and ChromiumEdge+Narrator
Actual result
Screenreader should not read unnecessary contents before reading the field name while navigating through tab key.
Other details
- Browser: Chorme, Chromium based EDGE
- OS: Windows 10
- CKEditor version: 4
- Installed CKEditor plugins: Image
- Screen reader: NVDA, Narrator.
Note: Attached video recording for the same.
https://user-images.githubusercontent.com/66038900/105109898-52642b00-5a72-11eb-891e-e3bf23cb3921.mp4
It's been a while since we last heard from you. We are marking this issue as stale due to inactivity. Please provide the requested feedback or the issue will be closed after next 7 days.
Hi, @sryarama ,
Thank you for your report.
I can only confirm ChromiumEdge + Narrator.
For Chrome + NVDA I can't experience such an issue. What kind of version of NVDA you are using? I use NVDA 2020.3 to verify, but I wasn't able to get the same results as yours.
Could you provide more details about your configuration that might be helpful? Like NVDA version, non-standard NVDA settings, more detailed CKEditor version, or browser build number.
@sculpt0r - Thank you for confirming the issue on ChromiumEdge + Narrator. Below are the requested details for NVDA: NVDA version - 2020.3 (no changes to the default settings). CKEditor version - 4.11.4
Thank you @sryarama for the details.
I must apologize, since it appears I tested it on NVDA + Firefox, instead of Chrome...
However, I mark both cases as a valid report. Also, I can confirm it on 4.16.0. Please, notice that we won't make any back-patches.
Thank you for your effort. Also, @Comandeer could you look at the expected result in such cases?
Hi Team, is there any update on this? It is impacting our accessibility compliance.
Hey @sryarama, so far we have no progress on this issue due to other priorities in CKEditor 4.
If you looking for a way to push this issue forward, you may contact our support team to see if there are any options to speed things up.