-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Workshop accessibility category: Operable #8
Comments
This category is about ensuring a smooth interface between the user and the page. I don't think we are in danger of ausing any seizures and there are no timed elements on the page. So this will boil down to making sure that the worshop reader works with keyboard navigation, screenreaders, etc. And making sure that site is well-organized. The macOS built-in reader (VoiceOver) can navigate the page by these categories:
They are often cluttered with duplicate "navigation" sections, Links with repetitive name like "Anchor" (Every section header) or "copy text" (one for every code chunk). There are plenty of other inconsistent elements |
The "multiple navigation sections in the Landmarks Rotor" issue is due to there being multiple uses of |
The "Anchor" links are at the section headers because there is a link hidden there that is made visible when the mouse is hovered over the header. It has the |
Disabling Javascript turns off the anchors and the section links still work, so I thin we could do without the AnchorJS library. The links rotor is still full of links where the text of the link isn't very informative (like "here"). That is the text that is shown by default in the rotor, and we sh |
WCAG guidelines in this category:
The text was updated successfully, but these errors were encountered: