Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Accessibility: run axe on every studio in the end-to-end tests

Closed
  • Is something wrong?
#405 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
66/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
playwright, typescript
Domain
accessibility, testing

Research direction

Start with tests/e2e/routes.spec.ts and tests/e2e/studio-skip-links.spec.ts to see how studio routes and panels are exercised; check .github/workflows/e2e.yml for the e2e environment. Add axe coverage for every studio in light and dark, including opened panels, and report serious or critical violations with the rule, selector, and studio. Done means violations are fixed or documented exclusions link to issues, and the added runtime stays under a minute.

Written by the indexing model from the issue text.

Description

accessibility area: ui difficulty: medium help wanted testing v2.0.0

Summary

DesignHub scores 100 for accessibility in Lighthouse on its main routes, but Lighthouse runs a subset of rules on the first view of a page. Run axe on every studio in light and dark, with the studio's main panels open, and fail on serious and critical violations.

Part of the 2.0.0 plan: fewer, better and fully tested studios.

Where to look

  • tests/e2e/routes.spec.ts: it already loops over studios from lib/navigation.ts
  • tests/e2e/studio-skip-links.spec.ts
  • .github/workflows/e2e.yml

Behaviour

  • Add @axe-core/playwright as a dev dependency (it is not shipped to users).
  • For each studio route, in light and dark, run axe after the page settles and again with each tab or panel opened (the studios have several), and fail on serious and critical impacts.
  • Keep a short, commented list of exclusions (a third-party canvas, for example) with a reason for each. No blanket disables.

Acceptance criteria

  • Every studio is covered in both themes.
  • Any violation found is fixed in the same pull request, or listed as an exclusion with a linked issue.
  • The failure message names the rule, the selector and the studio.
  • The test adds under a minute to the e2e run.

Getting started: fork the repo, then pnpm install and pnpm dev (Node 22+, pnpm 11, no API keys). Before opening a PR, run pnpm typecheck && pnpm test && pnpm lint && pnpm format:check && pnpm check:dashes && pnpm build (CI fails on unformatted files, so pnpm format first). See CONTRIBUTING.md and the first contribution walkthrough.

Everything needed is in the repository. This doesn't need maintainer access, secrets or paid services. Comment below to claim it, and ask questions here any time.

Dominant language
TypeScript
Stars
11
Forks
3
Avg merge
4h 4m
Merged PRs (30d)
74

Getting set up

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.

More from yakew7/DesignHub

All issues in yakew7/DesignHub

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.