keyboard/tab trap in advanced editor and other form fields
keyboard/tab trap in advanced editor and other form fields
When writing in a text field such as the advanced editor, or even the bug report form, tab does not move on to the next field as expected, but indents the current paragraph with two spaces. While this may be desirable behavior for manuscripts, for the shorter fields in articles, it makes more sense for tab to be used for navigation. You can tab INTO these fields, but not out of them. This is problematic for accessibility. Not only does it not meet WCAG standards for universal design, which we should all attempt to adhere to, It also has a real, practical impact on users who either use a screen reader to navigate, or have limited mobility. Accessibility benefits everyone, and as such, my day to day navigation as an able-bodied individual would be vastly improved with this change in behavior.
Steps to Reproduce
Click or tab into a text field, hit the tab key.
Operating System
LinuxBrowser
FirefoxRelated Entity
All text fieldsHistory
Find your way!
Resources
WHO WE ARE
LEGAL
Listen to our Podcast
