Accessibility audit

[knowler]

I intend on performing an rolling accessibility audit of npmx.dev over the coming weeks (with the exception of the coordinated vacation week from February 15 to 21—I hope I got those days correct actually repo sleepy time is a great time to do an audit 😅). I’ll fill in this issue with the plan as well as keep it updated with the results as I go.

If anyone is interested in helping, let me know here or on Discord, and we can coordinate together.

Tools

I plan providing the audit using the WCAG-EM Report Tool. The report is exported as a JSON file which can be loaded into the tool for further modifications as well as viewing the results in a rich format (i.e. HTML).

Current progress

Work in progress… reported on 28 of 55 WCAG 2.2 AA Success Criteria…

• 2026-02-17 (JSON); 2026-02-17 (HTML)
  • WIP summary: 5 Passed, 11 Failed, 1 Cannot tell, 11 Not present, 27 Not checked
• 2026-02-14 (JSON); 2026-02-14 (HTML)
  • WIP summary: 0 Passed, 5 Failed, 1 Cannot tell, 10 Not present, 39 Not checked
• 2026-02-13 (JSON); 2026-02-13 (HTML)
  • WIP summary: 0 Passed, 3 Failed, 0 Cannot tell, 10 Not present, 42 Not checked
    • Bear in mind that I’m apply “failed” for the entire sample even if I’ve evaluated a partial sample so far, while I won’t apply “passed” until I have evaluated the entire sample.
• 2026-02-09 (JSON)
  • Created report and filled in some initial details

[gameroman]

Hi @knowler anything we should do here?