6 comments (6 comments)11 reactions (11 reactions)0 assignees (0 assignees)HTML20,530 stars (20,530 stars)1,496 forks (1,496 forks)batch import
help wanted
Description
Some of these examples do not work with keyboard only navigation.
Contributor guide
- Tech stack
- htmlcss
- Domain
- accessibilityfrontend
- Issue type
- bug
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 3
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- 1-3 hours
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- stale
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- needs investigation
- Prerequisites
- HTMLkeyboard navigation concepts
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 60
- Research direction
- First, identify which examples in the repository are not keyboard navigable. Review the HTML and CSS of each example to find missing focus indicators or improper tabindex usage. Check existing comments on the issue for any specific examples mentioned. Once identified, add appropriate ARIA roles or semantic HTML elements (like buttons, links) and ensure all interactive elements are reachable via Tab. Test fixes with keyboard only navigation.