Marius Dumitru Florea Yes, from what I could understand, CKEditor has its own system to handle focus order. With the time I've spent on this issue so far I could not figure out how to add this button (and also other custom objects that we have added) to their tab order. This means that keyboard accessibility on those elements is not respected even if we have the right HTML.
Fixing the HTML would usually be a sufficient fix, but here we should find a way to fit this in the CKEditor system too.
Charpentier Lucas on 04/Nov/24 17:30
[~mflorea] Yes, from what I could understand, CKEditor has its own system to handle focus order. With the time I've spent on this issue so far I could not figure out how to add this button (and also other custom objects that we have added to this modal) to their tab order. This means that keyboard accessibility on those elements is not respected even if we have the right HTML.
Fixing the HTML would usually be a sufficient fix, but here we should find a way to fit this in the CKEditor system too.
Charpentier Lucas on 04/Nov/24 17:32
[~mflorea] Yes, from what I could understand, CKEditor has its own system to handle focus order. With the time I've spent on this issue so far I could not figure out how to add this button (and also other custom objects that we have added to this modal) to their tab order. This means that keyboard accessibility on those elements is not respected even if we have the right HTML.
Fixing the HTML would usually be a sufficient fix, but here we should find a way to fit this in the CKEditor system too.
Note that using automated tests (or most test tools in browsers) do not show these issues since the UI would work properly if not for the extra layer of javascript catching the Tab events to handle them with the focusManager from CKE.
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.
