Opened 10 years ago
Last modified 10 years ago
#13100 confirmed Bug
No indication of page break presence using JAWS
Reported by: | oplatt | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | General | Version: | 3.0 |
Keywords: | Cc: |
Description
When a page break is present in the editor, no indication of its presence is given to screen reader users. Users can still insert/delete page breaks, but are not told that it is there.
I've seen a previous bug raised (#5975) 5 years ago reporting something similar, and I can see now that there is an aria-label attribute on the page break div, but it does not seem that the screen reader acknowledges this.
Reproduction Steps
1 - Open the full featured editor demo at http://ckeditor.com/demo#full
2 - Add a page break to the editor
3 - Move the cursor around the document near the page break with JAWS active
When moving up and down lines, the page break is skipped altogether and without the use of sight it seems like the paragraph under the break follows straight on from the paragraph that is above it.
When moving left and right over the end of the preceding paragraph the screen reader reads out "blank" when the cursor is on the break.
Environment
OS - Windows 7 (64-bit) international version
Browser - Firefox 36.0.4
Screen Reader - JAWS 16.0.1925 (64-bit)
CKEditor - This issue was found in 4.4.6 and can be reproduced in 4.4.7. It may have existed before then, but I am not sure.
This has also been reproduced with version 15 of JAWS and on IE9. Using this combination, IE allows you to tab to focus on the page break, but the screen reader just reads out the editor description as if you had just entered it.
Change History (2)
comment:1 Changed 10 years ago by
comment:2 Changed 10 years ago by
Keywords: | jaws page break removed |
---|---|
Status: | new → confirmed |
Version: | 4.4.6 → 3.0 |
I hasn't I have checked versions 3.x and in all of them JAWS reads "blank".
I have checked it with Win 8, Firefox 36.0.4 and JAWS 16.0.1.925 (64-bit).
I would be interested if this worked before CKEditor 4.3. Since then we implemented fully custom way how non-editable elements are selected and this mechanism is known to be not integrated with screen readers, though it was so far only reported for widgets (see #12235). Perhaps this issue is caused by the same problem.