Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Custom Fonts: Improve Accessibility on Settings screen
See original GitHub issueBug Description
In #9966 we added a custom fonts section to the settings screen, to allow adding custom fonts by URL. It did not contain any a11y work, but there was also no follow-up ticket for that yet.
This feature right now is completely unusable with keyboard or assistive technologies. It’s impossible to tab into it in the first place.
Expected Behaviour
The Current Fonts list needs proper role="list" and role="listitem" attributes and keyboard support so that users can tab into it, select fonts using ArrowUp/ArrowDown keys and delete a font using the keyboard as well.
Steps to Reproduce
Screenshots
Additional Context
- Plugin Version: 1.18.0
- WordPress Version: 5.9
- Operating System: macOS
- Browser: Chrome
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
IIRC in a listbox there always needs to be a selected element. Even before focus and even when tabbing out of it.
My Preferred Languages WP plugin does that, if looking for inspiration.
@timarney is this where the failing e2e tests are getting flagged? https://github.com/GoogleForCreators/web-stories-wp/runs/5630868893?check_suite_focus=true#step:9:27
I’m trying to figure out the best path forward for making sure that enabling the floating menu isn’t messing with other tests. If what you’re working on will solve it then I will sit tight. Please let me know. thanks!