-
-
Notifications
You must be signed in to change notification settings - Fork 529
[A11y] MODX Manager Accessibility #16612
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
override .ext-webkit *:focus{ outline: none !important; }
override .ext-webkit *:focus{ outline: none !important; }
override .ext-webkit *:focus{ outline: none !important; }
…ck fires on keyboard navigation modxcms#16612
…e for create/refresh modxcms#16612
override .ext-webkit *:focus{ outline: none !important; }
…ck fires on keyboard navigation modxcms#16612
…e for create/refresh modxcms#16612
### What does it do? Make the MODX manager interface more accessible when using the keyboard ### How to test Minify CSS and compress JS via grunt first. Use the `Tab` key to navigate through the Manager UI. Use the `Esc` key to close the subnavigation. Use the tab key to navigate through the tabs. ### Related issue(s)/PR(s) See #16612 --------- Co-authored-by: Jason Coward <[email protected]>
@jenswittmann looks like this may have been addressed. Are there still outstanding items that should be handled still? It looks like you closed #16614, perhaps those items? |
@rthrash here are lots of other things to do in the future. Like screenreader annoucement, aria states, color contrast and so on. Maybe keep this as a parent issue to track the sub-issues (the new GitHub Feature)? Here is a small issue by @Jako that needs to be resolved in the next release and could be tracked as a sub-issue with a separate PR? #16613 (comment) There was also a conversation between myself and Henk Everts before the Snowup to get rid of the ExtJS side by side. So new features will be developed on VanillaJS and have a better accessibility than trying to change the old ExtJS. But this needs more discussion how to do it 🤔 |
Feature request
Summary
The MODX Manager is based on ExtJS and is not accessible for keyboard navigation and screen readers. The manager should therefore also be accessible to the employees of a company who maintain the website.
See this for public discussion: https://community.modx.com/t/modx-manager-accessibilty/7990
Why is it needed?
The Barrierefreiheitsstärkungsgesetz (BFSG) 2 comes into force on 28 June 2025.
Suggested solution(s)
Bring Keyboardnavigation and Screenreadertest in the MODX Dev Workflow.
Related issue(s)/PR(s)
Commits/PR will be prefixed with
[A11y]
.The text was updated successfully, but these errors were encountered: