AI-Ready Knowledge Base

Accessibility knowledge,
structured for AI.

neura11y is a structured accessibility knowledge base built for AI context loading and RAG pipelines. 178 markdown files covering WCAG, WAI-ARIA, seven social platforms, document workflows, voice UI, kiosk guidance, legal compliance, component patterns, and more — all with YAML frontmatter for clean ingestion.

v0.3.0 expanded AI validation, screen-reader provenance, tooling references, and refresh automation updates

Example file frontmatter
domains/web/web-accessibility-checklist.md
---
title: "Web Accessibility Checklist — WCAG Level AA"
standard: "WCAG"
source_url: "https://w3.org/TR/WCAG22/"
domain: ["web"]
last_fetched: "2026-03-13"
status: "prescriptive"
tags: ["wcag", "checklist", "audit", "aa", "web"]
ai_context: "Load for any WCAG
  audit or remediation pass."
---

# Web Accessibility Checklist — WCAG Level AA
## Principle 1: Perceivable
### 1.1 Text Alternatives
  • 178 markdown files
  • 12 prompt packs
  • 7 social platforms
  • 6 applied domains
01 Process

Four simple steps to get started

Give your AI tool the repo, start with the guide files, and then ask for the exact accessibility help you need.

  1. STEP 01

    Clone or download the repo

    Put it in the same workspace or project context your AI tool can access — a local folder, a Claude project, or a RAG pipeline.

  2. STEP 02

    Reference the guide files

    Have the AI reference AI-USAGE-GUIDE.md and INDEX.md. These files explain what is in the repo and how to use it.

  3. STEP 03

    Define the task

    Tell the AI what you want help with, such as auditing a page, reviewing a document, writing a social post, or checking compliance.

  4. STEP 04

    Review the AI output

    Treat results as assisted draft work. Verify thresholds, SC numbers, and any platform-specific claims against official sources.

03 Use cases

What you can do with it

Load the relevant files for your task and let the model do the work — grounded in real standards, not general knowledge.

  • Web

    Build or audit a page

    Generate accessible components, review HTML for WCAG issues, and get ARIA patterns for modals, tabs, carousels, comboboxes, and more.

  • Documents

    Create accessible documents

    Get step-by-step guidance for Word, PowerPoint, Excel, and PDF. Covers heading structure, alt text, reading order, PDF forms, charts, and plain language.

  • Social media

    Write accessible social posts

    Generate alt text, captions, sign-language-aware video guidance, and accessible copy for Twitter/X, Instagram, LinkedIn, YouTube, TikTok, Facebook, and Mastodon.

  • Compliance

    Navigate legal requirements

    Understand WCAG conformance levels, Section 508, EN 301 549, ISO 9241-171, and regional law — US ADA, EU EAA, UK regulations, Canada, and Australia.

  • Voice

    Design accessible voice flows

    Spec voice commands, spoken confirmations, label-in-name support, multimodal fallback, and recovery patterns for speech-driven interfaces.

  • Physical ICT

    Review kiosk and embedded UX

    Use the kiosk playbook for closed functionality, timed sessions, non-visual access, hardware controls, and self-service transaction flows.

04 Coverage

What is in the repository

The repo spans standards, applied guidance, prompt templates, and supporting reference material across major accessibility domains, including voice UI and physical ICT.

  • WCAG Standards

    All 86 active WCAG success criteria with levels, sufficient techniques, advisory techniques, failure techniques, and understanding guides, plus notes on obsolete SC 4.1.1. WCAG 2.1 full text, 3.0 overview, and conformance levels are also included.

  • WAI-ARIA

    Roles, states, and properties reference plus AccName, split Core-AAM and HTML-AAM files, ARIA in HTML, APG patterns, and a curated common mistakes guide.

  • Web Domain

    HTML semantics, focus management, forms, images, SPA patterns, mobile web, PWAs, color/contrast, keyboard navigation, 8 component patterns, and a testing suite covering automated tools, checker and CLI references, manual checklist, and a screen-reader testing matrix.

  • Social Media

    Platform guides for all 7 major platforms. Alt text principles and examples, caption standards, audio description, sign language video notes, subtitle terminology, and inclusive writing guides.

  • Documents

    Word, PowerPoint, Excel, and PDF accessibility guides with focused files for PDF forms, remediation, export workflows, readability, and Excel data visualization.

  • Voice UI

    Guidance for speech commands, label-in-name alignment, spoken confirmations, multimodal fallback, privacy, and recovery for voice-driven interfaces.

  • Physical ICT

    Kiosk and embedded system playbook covering closed functionality, non-visual access, timed sessions, hardware controls, transaction review patterns, and WCAG2ICT interpretation support for non-web software and documents.

  • Screen Readers

    Support guides and testing matrices for JAWS, NVDA, VoiceOver, and TalkBack. Covers HTML and ARIA support levels, cross-tool testing workflows, mobile SR checks, and fetched vendor provenance for command and workflow traceability.

  • EPUB & PDF/UA

    EPUB Accessibility 1.1 with metadata schema, PDF/UA overview, and the Matterhorn Protocol checklist for verifying PDF conformance. Covers ATAG 2.0 and UAAG 2.0 overviews.

  • Cognitive

    COGA overview and design patterns. SC 3.3.8 authentication, SC 3.3.7 redundant entry, error patterns. Dyslexia and ADHD guidance.

  • Color & Visual

    Complete WCAG contrast thresholds, common color pairs, tools. Typography accessibility. Color blindness types, design patterns, and testing.

  • Legal

    US ADA and Section 508, EU European Accessibility Act, UK accessibility regulations, Canada accessibility coverage, Australia guidance, plus EN 301 549 alignment.

05 Starter prompt

Paste this into Claude Code or Codex

Run it from your repo root. The knowledge files do the heavy lifting.

starter-prompt.txt

Context

You have access to the neura11y accessibility repository.

Instructions

1. Read AI-USAGE-GUIDE.md and INDEX.md to understand the repository structure and guidelines. 2. Identify and load only the tight, focused bundle of files relevant to this exact task. 3. Use strictly those files as your source material. If they do not fully cover the request, state that clearly rather than filling gaps from general knowledge.

Task

Help me create or review an accessible [HTML page / component / Markdown document / social post]. Pay special attention to WCAG compliance for elements like multimedia captions and semantic structure. Ensure the final code or content prioritizes an intuitive, aesthetic flow rather than relying on dry, rigid logic.

Get the repository

Clone or download at github.com/AYJAYY/neura11y/releases (opens in a new tab). Contributions, corrections, and new platform guides are welcome.

Star on GitHub (opens in a new tab)
06 Maintenance

How to fetch new data

When W3C, vendor, or government sources update, use the fetch scripts from the repo root. Large sources regenerate split canonical files for AI use plus raw *-full-fetched.md or *-fetched.md provenance captures.

Full refresh

Run the standard maintenance pass

  • python3 scripts/fetch-all.py
  • python3 scripts/refresh-repo.py

This refreshes tracked sources, syncs release metadata, rebuilds AI chunk artifacts, and reruns the structural plus fixture validation suite.

Targeted fetches

Refresh only one source family

  • python3 scripts/fetch-aria.py for WAI-ARIA, AccName, Core-AAM, HTML-AAM, and ARIA in HTML
  • python3 scripts/fetch-w3c-other.py for WCAG2ICT, WAI tutorials, ATAG, UAAG, EPUB, WebVTT, COGA, and the alt-text decision tree
  • python3 scripts/fetch-screen-readers.py for NVDA, VoiceOver, TalkBack, and JAWS vendor support docs
  • python3 scripts/fetch-wcag.py for WCAG full text, quick refs, techniques, and understanding docs

See meta/update-schedule.md for cadence and AI-USAGE-GUIDE.md for which split canonical files to load after each refresh.

Accessibility statement

Designed to work with keyboard, zoom, and assistive tech

This statement applies to the public neura11y.com landing page. The repository's markdown corpus lives on GitHub and is maintained separately from this site shell.

The landing page targets WCAG 2.1 Level AA for core interactions. It includes semantic landmarks, a skip link, visible focus states, keyboard-operable controls, and reduced-motion handling.

Accessibility work is ongoing. If you hit a barrier, please open a GitHub issue (opens in a new tab) with the page, browser, device, and assistive technology you were using.

Last reviewed: March 21, 2026