Skip to content

ci(dashboard): add accessibility validation to the pipeline#72

Open
shaaibu7 wants to merge 1 commit into
Core-Foundry:mainfrom
shaaibu7:feat/notification-types-and-a11y-ci
Open

ci(dashboard): add accessibility validation to the pipeline#72
shaaibu7 wants to merge 1 commit into
Core-Foundry:mainfrom
shaaibu7:feat/notification-types-and-a11y-ci

Conversation

@shaaibu7

@shaaibu7 shaaibu7 commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

Closes #40

Integrate accessibility validation into the CI pipeline to catch common UI issues before deployment.

What changed

  • Configure accessibility testing tool: a dedicated a11y suite (dashboard/src/a11y/) renders the key UI surfaces — the wallet connect button (disconnected / connected / error states), event filters bar, event card, event list, and event list panel — and validates them with jest-axe (axe-core), plus a reusable audit helper. It runs through its own jest.a11y.config.cjs via npm run test:a11y and is excluded from the default test run.
  • Run checks during pull requests: a new Accessibility (axe audit) job in .github/workflows/ci.yml runs on every PR.
  • Generate readable reports: produces a11y-report.md (per-component results plus an impact-count table), written even when audits fail, and uploaded as a CI artifact (if: always()).
  • Fail builds on critical violations: the build is gated on critical-impact violations only; lesser findings are reported but non-blocking. Both paths were verified (7 audits pass; a deliberate critical violation fails with a readable message).

Incidental fixes (required to make the frontend pipeline run)

  • Repaired the corrupted dashboard/package-lock.json — several hand-inserted dependency entries were missing closing braces, which broke npm ci.
  • De-duplicated package.json devDependencies.
  • Wired @testing-library/jest-dom matcher types into tsc so npm run build passes.

Verification

Locally green: npm ci, npm run lint, npm run build, npm test, and npm run test:a11y.

🤖 Generated with Claude Code

Catch common UI accessibility issues before deployment by auditing key
components with axe-core and gating pull requests on critical violations.

- Add a dedicated a11y suite (src/a11y) that renders the wallet button,
  event filters, event card/list and panel and validates them with
  jest-axe, plus a reusable audit helper.
- Generate a readable Markdown report (a11y-report.md) covering every
  audited component, written even when audits fail.
- Fail the build only on critical-impact violations; lesser findings are
  reported but non-blocking.
- Add an "Accessibility (axe audit)" CI job that runs on pull requests
  via `npm run test:a11y` and uploads the report as an artifact.
- Run the suite through its own jest.a11y.config.cjs and exclude it from
  the default test run.

Also repair the corrupted dashboard package-lock.json (several
hand-inserted dependency entries were missing closing braces, which
broke `npm ci`), de-duplicate package.json devDependencies, and wire the
@testing-library/jest-dom matcher types into tsc so the build passes.
@shaaibu7 shaaibu7 force-pushed the feat/notification-types-and-a11y-ci branch from 6285700 to 7973484 Compare June 19, 2026 07:55
@shaaibu7 shaaibu7 changed the title feat: notification category filtering + accessibility CI ci(dashboard): add accessibility validation to the pipeline Jun 19, 2026
@Abd-Standard

Copy link
Copy Markdown
Collaborator

please fix CI and resolve conflicts please

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Contracts] Add Contract Version Information

2 participants