WWW: Improve keyboard and screen reader accessibility of project grid cards
@Okd2006 is already working on this.
Since Mar 2, 2026.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- accessibility, frontend, web-dev
Research direction
Start at the homepage project grid on aboutcode.org and inspect the project card div and its icon alt attribute. Verify that each card is reachable with Tab, activates with Enter or Space, is announced with its project name and button role, and opens the detail popup.
Written by the indexing model from the issue text.
Description
Problem
The project cards on the homepage (aboutcode.org) cannot be reached or activated using keyboard navigation. A user who navigates via the Tab key cannot focus on any project card, and therefore has no way to open the project detail popup without a mouse.
This affects:
- Keyboard-only users (e.g., power users, users with motor impairments) who cannot access project details at all
-
- Screen reader users who are not informed that cards are interactive, since the cards lack semantic roles and labels
Current behavior
- Pressing Tab on the homepage skips over the entire project grid - cards receive no focus.
-
- Screen readers announce the cards as generic container elements with no indication that they are clickable.
-
- Every card's icon has the same alt text (
"logo"), which provides no meaningful information to assistive technology users.
- Every card's icon has the same alt text (
Expected behavior
- Users should be able to Tab through project cards and press Enter (or Space) to open the detail popup.
-
- Screen readers should announce each card as an interactive element (e.g.,
"dejacode, button") so users know it can be activated.
- Screen readers should announce each card as an interactive element (e.g.,
-
- Image alt text should be descriptive (e.g., the project name) rather than generic.
Why this matters
The project grid is the primary content of the homepage - it's how visitors discover AboutCode projects. Users who rely on keyboard navigation or assistive technology are currently locked out of this core content. Addressing this would improve the user experience for a wider audience and bring the site closer to WCAG 2.1 Level A conformance.
Suggested approach
- Add
tabIndex="0",role="button", and a keyboard event handler (onKeyDownfor Enter/Space) to each project card<div> -
- Update the card icon's
altattribute to use the project name instead of the generic"logo"
- Update the card icon's
References
- Related to the current focus on improving website content and user experience
- Dominant language
- JavaScript
- Stars
- 9
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aboutcode-org/www.aboutcode.org
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Add hover effects to adopter logos in the Community and Adopters sectionPossibly taken @riddheshkadu3637-ui claimed this 3 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Making all post button.Possibly taken @sarthaklole claimed this 90 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
aboutcode-org/www.aboutcode.org#117 · 3 comments ·
-
WWW: Reduce frequency of update-releasesMay be free again @johnmhoran claimed this 71 days ago, and no pull request is open. Openci-workflow
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
aboutcode-org/www.aboutcode.org#180 · 1 assignee ·
-
DOCS: Create new AboutCode stack diagram(s)May be free again @hixvikas claimed this 72 days ago, and no pull request is open. Opendocumentation
Difficulty 5/5 Over a week Newbie friendliness 35/100
aboutcode-org/www.aboutcode.org#166 · 1 comment ·
All issues in aboutcode-org/www.aboutcode.org
Similar issues
-
bug pydanty:is-working
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
pydantic/pydantic-ai#13939 ·
Maintainers usually reply within 1 day
-
self-host
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
funmusicplace/mirlo#2625 ·
Maintainers usually reply within 1 day
-
Bug Tests
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
JSPrismarine/JSPrismarine#3271 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 85/100
sindresorhus/eslint-plugin-unicorn#4034 ·
Maintainers usually reply within 1 day
-
Content:WebExt needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day