Ticket #3213 (closed Bug: fixed)
Change the voice readout of the editing area from "CKEditor" to "Rich Text Area"
| Reported by: | martinkou | Owned by: | martinkou |
|---|---|---|---|
| Priority: | High | Milestone: | CKEditor 3.0 |
| Component: | Accessibility | Version: | SVN (CKEditor) - OLD |
| Keywords: | Oracle Review+ | Cc: | Senthil |
Description
When focus is brought into CKEditor's editing area in our samples right now, the voice readout by JAWS is typically like this:
"Output, CKEditor Editor 1, type in text"
Output is the outer frameset's title in our sample pages. CKEditor is always read to tell the user that they're in CKEditor. Editor 1 is the editor instance's name.
It is more descriptive for screen reader users if the CKEditor part of the readout is changed to "Rich Text Editor" - so they'll know what to expect, instead of hearing a name which they may or may not understand immediately.
Attachments
Change History
comment:2 Changed 4 years ago by fredck
- Keywords Review- added; Review? removed
"text area" is developers' language.
There is not reason to not accept localization for this text. So, please move it to the language file. The entry should look like this:
editorTitle : 'Rich text editor, %1'
comment:4 Changed 4 years ago by fredck
- Keywords Review- added; Review? removed
Please remove the '. Type in text.' part of it.
comment:7 Changed 4 years ago by martinkou
- Status changed from new to closed
- Resolution set to fixed
Fixed with [3306].
Click here for more info about our SVN system.
comment:8 Changed 4 years ago by Senthil
- Status changed from closed to reopened
- Keywords Review+ removed
- Resolution fixed deleted
After i tested the fix the reported issue still exist in IE and Safari.
comment:9 Changed 4 years ago by fredck
The word "CKEditor" is not anymore present in the editor code, so there is no way for JAWS to ready it. Wasn't it a cache issue?
Can you confirm it Martin, and close this ticket?
comment:10 Changed 4 years ago by martinkou
I've just performed a test on Senthil's machine today - I found the JAWS in Senthil's computer isn't reading the <label> in front of the editing iframe. However, if I add a <legend> instead, it's read.
Still testing <legend> on my local machines, and then I'll propose a new patch for this.
comment:11 Changed 4 years ago by martinkou
- Keywords Review? added
There's no way to make JAWS to read anything from Safari - it won't read anything even in Google.
So we can only fix the voice readout for IE. For Safari we'll have to wait until JAWS is properly integrated with the browser - we can't do anything to fix JAWS and Safari from JavaScript.
comment:12 Changed 4 years ago by fredck
- Keywords Review- added; Review? removed
The usage on "join()" with no parameters is wrong, as it add commas between the array entries. Also, there is no benefit on using the "join trick" for small string concatenations.
I'm coming with a new patch, just to accelerate the process.
comment:13 Changed 4 years ago by fredck
- Keywords Review+ added; Review- removed
Martin, I've attached a new patch, please be sure my changes are ok before committing.
comment:14 Changed 4 years ago by martinkou
- Status changed from reopened to closed
- Resolution set to fixed
Fixed with [3338].
Click here for more info about our SVN system.
