-
Notifications
You must be signed in to change notification settings - Fork 0
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom Widgets #58
Comments
@gabalafou to look into this and research the WCAG requirement (similar to #57) |
Both of items in the issue description have to do with the version switcher. We can check off the first item because it's about making sure that any visible labels or instructions can be picked up by assistive tech like screen readers. As far as I can tell, all visible text in the version switcher shows up in the accessibility tree, so we should be good here. (Looking at the latest version of the PyData theme site.) So I'm going to go ahead and check the first item. For the second item, it boils down to making sure that our use of the "listbox" role is correct. Should the version switcher menu have role equal to listbox? And if so, have we correctly implemented that design pattern. In particular, does it support the keyboard shortcuts that it should. That's actually been on my own to-do list, so it's good we're tracking it. |
Ref on version button: pydata/pydata-sphinx-theme#1357 |
1. 馃摐 Instructions Compliance
If a custom widget has a visible label or instructions, they must be programmatically determinable - WCAG 1.3.1, WCAG 2.5.3
Path
.me-auto > .navbar-item:nth-child(1) > .version-switcher__container.dropdown > .version-switcher__button[role="button"][aria-haspopup="listbox"]
Snippet
Accordion, Button, Disclosure (Show/Hide), Menu Button.
-
-
2.鈱笍 Keyboard Interaction
A custom widget must support the keyboard interaction specified by its design pattern - WCAG 2.1.1
Path
div[data-bs-popper="static"]
Snippet
Listbox
-
The text was updated successfully, but these errors were encountered: