nuxt / nuxt/nuxt.com

fix: improve a11y

Open
#1,837 1 comment 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
457
Forks
272
Avg merge
13h 33m
Merged PRs (30d)
23

Description

the current a11y score on nuxt.com is 83 (from lighthouse), pretty sure we can max it out

  • I can work on this if no one's gonna take it?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running Lighthouse against nuxt.com and review the accessibility findings behind the reported score of 83. Work through the identified issues and rerun the audit; done means the accessibility score is improved toward the stated goal of maximizing it.

Written by the indexing model from the issue text.

Assessment

Tech stack
nuxt, typescript
Domain
accessibility, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.