When the CKEditor is in Basic or Full HTML mode, the field is resizable via the mouse; however, the user cannot access the resize option via the keyboard.
Steps to reproduce:
1. Navigate to /block/add to add a new custom block (can navigate to any page that has a body field or similar CKEditor field)
2. Use the tab button to navigate through the fields on the page
3. Once in the Body field, select Alt + F10 to access toolbar or Alt + F10 to access element path bar.
4. User is unable to access resize button, which appears to be part of the element path bar.
Issue seen on IE11 and Chrome Version 63.0.3239.108.
Reference: Section 508 Refresh, 2.1.1 – Keyboard.
| Comment | File | Size | Author |
|---|---|---|---|
| Resize Button.png | 20.4 KB | findleys |
Comments
Comment #2
findleys commentedComment #3
cilefen commentedYou set the version to 8.2.8. Have you tried on a supported release?
Comment #4
findleys commentedOur system is currently on 8.2.8. We are in the process of upgrading to 8.4.x. Once we do we can retest there.
Comment #5
andrewmacpherson commented@findleys: Thanks for reporting this.
The resize control mentioned here comes from CKEditor's Editor Resize plugin. As reported by @findleys, it isn't keyboard accessible. I haven't found an upstream CK issue for this.
[Aside: note that a plain HTML
<textarea>(without a JS editor) can't be resized by using the keyboard either. This basic case is really something that needs to be solved by user agents. There are some approaches like Textarea resize user script but I wouldn't recommend this for Drupal core unless there's a way to make it discoverable.]Since 8.3.0 the CKEditor Autogrow plugin is included with core, and enabled by default. See #2239419: Include CKEditor's AutoGrow plug-in. Meanwhile, the Editor Resize plugin is no longer included with core.
We no longer have the inaccessible resize handle, so let's close this one as outdated (or, as-designed, because the design has changed really).
Comment #6
mgifford@findleys thanks for all your posts.
With this one it would be good to place the issue in the CKEditor Issue Queue https://github.com/ckeditor/ckeditor-dev/issues
We can then link to it here so that we can monitor it. I wonder though if this should be listed as Postponed rather than Won't Fix.