Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The goal of this issue is simply to provide a place for general discussions about CkEditor accessibility and track any accessibility issue of its drupal integration.
related issues
- #1872206: Improve CKEditor toolbar configuration accessibility
- #1879120: Use Drupal-specific image and link plugins — use core dialogs rather than CKEditor dialogs, containing alterable Drupal forms
- #1900246: Menu item labels have been lost
- #1904986: Make Keyboard Controls Discoverable in CKEditor
Comments
Comment #1
mgiffordJust adding link to accessibility discussion on CKEditor #1260052-161: Candidate WYSIWYG editors to this central thread.
Comment #2
Wim LeersTagging; this helps the CKEditor folks track the "CKEditor in core" status on the Drupal side. On the CKEditor side, see http://dev.ckeditor.com/query?keywords=~Drupal.
Comment #3
Wim LeersSlightly better title.
Comment #3.0
Wim Leersadding first related issue
Comment #4
Wim Leersjessebeach reported this a11y problem: http://dev.ckeditor.com/ticket/10004 — they're following up on it.
Comment #5
mgifford@jessebeach - thanks!
I added this issue here - #1904986: Make Keyboard Controls Discoverable in CKEditor
Comment #6
the_g_bomb CreditAttribution: the_g_bomb commentedAlt+F10 the keyboard shortcut to get to the toolbar is already bound to "Open the indicator menu" in Ubuntu 12.04 with the Unity desktop. Probably worth noting that somewhere. The upshot is without changing the Alt+F10 shortcut in Ubuntu using the toolbar is impossible by keyboard.
There is a current ticket regarding the previous binding that Alt+F10 had in Ubuntu which was to resize the browser window, which I have updated to highlight the new use: http://dev.ckeditor.com/ticket/7505
Comment #6.0
the_g_bomb CreditAttribution: the_g_bomb commentedadding related issues
Comment #7
falcon03 CreditAttribution: falcon03 commentedMoving this issue to core, now that #1890502: WYSIWYG: Add CKEditor module to core has been committed.
Comment #8
catchI'm going to downgrade this to normal since there's nothing actionable here, some of the individual accessibility issues are already marked major which sounds right.
Comment #8.0
catchupdated trelated issues, added section for upstream CKEditor issue links
Comment #9
Hanno CreditAttribution: Hanno commentedAdded 7987: Implement Language toolbar button to support WCAG 3.1.2 Language of Parts
Comment #10
mgiffordThere are also all of the reported issues with CKEditor.
I was disappointed to find that there were so many that had been opened (and unresolved) for so long. The one Hanno pointed out had been opened for over 2 years.
Comment #11
mgiffordI'm going to close this as a duplicate as CKEditor problems should be reported in their issue queue. All issues related to the Drupal integration should be set up with a new issue in the Component ckeditor.module. No need to have an open meta issue.
Comment #11.0
mgiffordadded language button
Comment #12
hadi_gsf CreditAttribution: hadi_gsf commentedHello
I'm not sure where to post my question, but regarding ckeditor's accessibility on drupal 8:
I'm trying to test drupal 8. The ckeditor that is preinstalled seems to mis lots of features including the (h1 h2 h3) elements.
Should I do something to make those features visible to me?
Comment #13
mgifford@hadi_gsf - is it possible that you were using the Text format "Basic HTML" when editing the Node?
"Full HTML" Under the Format box gives you the ability of using H1-H6.
Both use CKEditor by default in D8. Try the Full HTML and see if that gives you what you need.
Comment #14
hadi_gsf CreditAttribution: hadi_gsf commented@mgifford
Thanks, That is right, i needed to use the full html