Opened 10 years ago
Closed 10 years ago
#29815 closed defect (bug) (fixed)
Text editor content not accessible for screen readers
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 4.1 | Priority: | normal |
Severity: | normal | Version: | 4.0 |
Component: | Editor | Keywords: | has-patch needs-testing |
Focuses: | accessibility, javascript | Cc: |
Description
Investigating on what's been reported on IRC by @_Redd
Strange, I find that NVDA will "read" what's in the TinyMCE editor for the visual tab, but not the text one. It will read what you're typing in, of course, but it won't read what's already there. Pretty bad scenario.
and of course that's true and I could reproduce testing with Chrome and NVDA.
Turns out that when TinyMCE is initialized, it adds an attribute aria-hidden="true"
to the textarea. Of course this doesn't happen when TinyMCE is not initialized yet, when on page load the active editor is the "Text" one. It will when you switch to "Visual" and switch back to "Text".
At this point, the "Text" editor textarea content is hidden for screen-readers.
When switching to the "Text" editor, the aria-hidden attribute needs to be set to "false" and then set back to "true" when switching to the "Visual" editor. See proposed attached patch.
Attachments (1)
Change History (10)
#3
follow-up:
↓ 6
@
10 years ago
One follow-up; it occurred to me as I was going home last night that the patch may well be perfect--that the possible reason not all is read in the content area of the TinyMCE "Text Editor" may be because of NVDA, not WordPress or your patch.
Definitely, more testing is needed--other browsers, other versions of NVDA, other screen readers.
Thanks again, afercia, for the amazing insight into the problem, and the amazing patches.
#5
@
10 years ago
- Owner set to SergeyBiryukov
- Resolution set to fixed
- Status changed from new to closed
In 29815:
#6
in reply to:
↑ 3
@
10 years ago
Replying to sharonaustin:
Thanks again, afercia, for the amazing insight into the problem, and the amazing patches.
Thanks Sharon :) for your feedback, enthusiasm and your nice words.
Replying to afercia: Amazing insight into the problem--the explanation is greatly appreciated--as of course, is the patch.
This patch worked for me using Firefox 32.0.3 NVDA 2013.3. NVDA read out loud the content that was previously unseen by NVDA in the "Text Editor"---but further testing is required, there is some level of inconsistency with the sequence of steps I can't track down.
Example of what I'm talking about (In the "Text Editor" Screen of the TinyMCE editor):
This page: http://red-hound.com/trunk29802/trunk/src/?page_id=14
NVDA reads the first text, all the hyperlink information, but not "A paragraph", "A second paragraph", or "A third paragraph"
So, great success, but I don't think it is quite complete success yet. Thanks so much for the patch!