popcodeorg / popcodeorg/popcode

Automate accessibility audits

Open
#1,360 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

deployment development tooling ux
Dominant language
JavaScript
Stars
191
Forks
143
Avg merge
4d 11h
Merged PRs (30d)
5

Description

Chrome comes with built-in accessibility auditing tools. You can try these out by clicking the audits tab in dev tools => Perform an audit => Accessibility

I believe that we can automate running this audit on popcode by using Puppeteer. There are a few considerations/steps that need to be taken for this to work:

  • confirm that Puppeteer can indeed automate this audit
  • implement Puppeteer in Popcode
  • configure the accessibility audit to correctly weight the different accessibility tests (ie, color contrast is very important to us, but popcode may never be fully screen reader accessible)
  • create a way for snapshot queries not to be stripped out (accessibility audit is based on location, not the content on the current page)
  • create a variety of snapshots testing popcode in different states
  • fix current failures in accessibility audit ?
  • figure out the best way to build integration testing into the development process

Contributor guide

No contributing guide indexed for this repository

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 confirming whether Puppeteer can automate Chrome’s DevTools accessibility audit for Popcode. Then investigate snapshot queries, audit weighting, snapshots for different Popcode states, current audit failures, and how accessibility integration tests could fit into development. Done means a documented, repeatable audit process with appropriate checks and test coverage.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
accessibility, testing-qa
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.