Rich text editor- keyboard trap for accessibility users
Hello,
A screen with a Rich Text Editor will trap keyboard users within the editing text box. The user can tab into the text box, but cannot tab out of it to move focus to controls outside of the rich text editor.
Is there a way to fix this issue where the user can either press TAB out of the editing text box or press ESC to move out of the Rich Text Editor?
We do not want to add the PegaWAI ruleset to resolve this issue, since we do not want all features included in the ruleset enabled in our framework.
***Edited by Moderator: Pallavi to change category from General to Product, add platform version and Feedback ID***
Sky Solutions LLC
US
When the cursor is in the editing text box of the Rich Text Editor, I am able to exit out of the Rich Text Editor by pressing ESC+TAB, which will then set focus on the next control element in the for
Although I am not seeing a focus indicator anywhere on the screen nor is the screen reader detecting a new control being focused.
Is this a common keyboard shortcut for existing a Rich Text Editor?
Pegasystems Inc.
US
Can you check below pdn link?
Sky Solutions LLC
US
Hi Susan,
Thank you for your response! I was able to review the link you sent and the resolution requires the PegaWAI accessibility ruleset to be added and enabled. For right now, we do not want to use this ruleset.
I was able to figure out a keyboard shortcut to exit out of the rich text editor by pressing ESC + Tab but I am not sure if this is a common practice and would not want to leave it as is if it is not best practice for accessibility.
Would you happen to know if this is the expected behavior for exiting out of rich-text editors via keyboard?
Pegasystems Inc.
US
Please check this.
https://community.pega.com/support/support-articles/unable-move-cursor-out-rich-text-editor
It looks that this is a known issue.
Current behavior: Cursor is not moving out of the RTE when using TAB from keyboard , if there is any image or signature present in the RTE.
Issue is present in EDGE browser and working fine in CHROME and IE browser.
Expected behaviour :
User is expecting with accessibility enabled Tab key press should take cursor out of RTE
It is considered it as an enhancement.
Pegasystems Inc.
US
Hi, I checked it for you. For the enhancement request, FDBK-64300, there is no ETA yet. You can come back and check it later on.
Sky Solutions LLC
US
Hi @SusanLiu_GCS ,
Are there any updates to FDBK-64300? I am currently in a different project but the same issue persists with the user unable to press the TAB key to exit the Rich Text Editor.
Using Pega Customer Service App in version 8.3.0
Sincerely,
Regina
Pegasystems Inc.
US
@ReginaS9 Since Pega uses the CKEditor software for rich text editor controls, I believe this article detailing some of the keyboard shortcuts for RTE's is applicable to your situation: https://ckeditor.com/docs/ckeditor4/latest/features/shortcuts.html
As you mentioned previously, Esc+Tab is the keyboard shortcut to move focus out of the text area of the RTE, and it should move to the next focusable element on the screen. To verify, you could use a screenreader and navigate through the RTE using the shortcuts. The screenreader can help identify exactly where focus is as you navigate through.
Sky Solutions LLC
US
Thanks @pastr1!
We will be documenting the keyboard shortcuts for the RTE in our application. We also submitted FDBK-76382 - 'RTE Toolbar Keyboard Shortcut Documentation' for Pega to provide documentation/instructions for the RTE keyboard shortcuts since this information is not currently available in the Pega platform.
Lastly, we submitted INC-156912 for this issue. We further discovered the following:
Issue: When in a modal dialog with an RTE control inside, ESC key does bring the focus to RTE text area but since the keypress event is further propagated to modal dialog, the code that closes the modal dialog is executed.
Expected behaviour: If the focus is on RTE toolbar, if user presses ESC button in modal dialog, the focus should come back to RTE text area.
Solution description: The releases that the issue is estimated to be addressed in are: 8.3.6, 8.4.5, 8.5.3, and 8.6.