Accessibility - keyboard traps

[ghowardibm]

Hi,

The product I work on consumes the monaco-editor and we're currently ensuring accessibility compliance throughout our user experiences. One thing we noticed during our keyboard navigation testing is that user can get trapped once focus is inside the editor. We're aware of the shortcutCtrl+Shift+M and then Tab that allows focus to shift forward away from the editor so it's possible for the user to escape. However the same cannot be said for using the same shortcut and then Shift+Tab to go to previous element. There are a few things I wanted to start a discussion on and get some guidance, or even if this is a bug that I should raise an issue for.

1. The standard recognised Esc key is not supported to remove focus from the editor, has this been considered at all or is there a conflict with using this shortcut or other standard recognised keys to be used as the main escape from focus?
2. I'm reading some different things about keyboard traps and violating this accessibility requirement. Some content describes not being able to move freely (forwards and backwards) as a keyboard trap. Moving forward via the custom shortcuts documented and listed above at least means the user is not completely trapped. But I wondered if you had considered this issue of only being able to escape forwards to next element?
3. A side note to the above, Ctrl+Shift+M on Macbook keyboards would be rather difficult to execute with one hand for a user that requires this type of accessibility.

Any thoughts, guidance and comments appreciated.

Thanks.

[theFoxCost]

is this tool still supported or archived