Skip to content

Known findings from the documentation accessibility check #267

Closed

Description

@accesswatch

This issue tracks the findings the documentation accessibility check recorded when it was added. The check is scripts/check-docs-accessibility.js; it runs on every pull request that changes Markdown (.github/workflows/docs-accessibility.yml) and fails only when a pull request adds a finding. The findings it started with are counted per file and rule in scripts/docs-accessibility-baseline.json, and those counts may only go down.

Baseline on 2026-10-28: 264 findings in 37 of the 152 Markdown files it checks (root, docs/, admin/, classroom/; learning-room/ is excluded because it has deliberate defects for learners to fix).

Rule Findings What a reader meets Where
emoji 172 Emoji names read aloud, often at the start of headings admin/CURRICULUM_2.0_ORGANIZATION.md (123), admin/FACILITATOR_GUIDE.md (26), admin/FACILITATOR_RESOURCES.md (20), admin/FACILITATOR_OPERATIONS.md (3)
code-fence-language 88 Code blocks that do not say what they contain 34 files; the most in docs/appendix-ac-document-developer-tools.md (16) and docs/appendix-ab-advanced-agent-patterns.md (7)
link-text 3 Not a barrier: the "bad example" column of the link text table in docs/appendix-c-markdown-reference.md, kept on purpose
heading-single-h1 1 admin/classroom admin access.md is a single URL with no title

Fixed in the same pull request that added the check: a skipped heading level in Appendix Z, a second H1 in Appendix L, empty table headers on both registration pages, and a stray line above the title of CONTRIBUTING.md.

Pieces to pick up

To see every finding with its line number: node scripts/check-docs-accessibility.js --report. When you fix some, lower the matching counts in the baseline in the same pull request.

Related, in the site template rather than the Markdown: #265 and #266.


Generated by Claude Code

Activity

  1. added
    documentationImprovements or additions to documentation
    accessibilityAccessibility barriers, reports and improvements
    on Oct 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    accessibilityAccessibility barriers, reports and improvementsdocumentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions