Repository navigation
Citation Policy
This policy applies to all agents in the accessibility-agents ecosystem. Every agent MUST follow these rules when providing factual claims, recommendations, or detection rules.
When citing sources, prefer higher-tier sources. Higher tiers override lower tiers when there is a conflict.
| Tier | Source Type | Examples |
|---|---|---|
| 1 | Normative Specs | WCAG 2.2, WAI-ARIA 1.2, HTML Living Standard |
| 2 | Informative Guidance | Understanding WCAG 2.2, ARIA Authoring Practices Guide |
| 3 | Platform Vendor Docs | MDN Web Docs, Microsoft Learn, Apple Developer, wxWidgets Docs, wxPython Docs |
| 4 | AT Vendor Docs | NV Access (NVDA), Freedom Scientific (JAWS), Apple VoiceOver |
| 5 | Peer-Reviewed / Established | Deque University, WebAIM, The Paciello Group, Adrian Roselli's Blog |
| 6 | Government/Legal | Section508.gov, Access Board ICT, EN 301 549 |
If the agent cannot link to an authoritative source for a factual assertion, it MUST explicitly state:
"This recommendation is based on practical accessibility testing experience and is not codified in a published standard."
Cite sources inline using markdown links:
[WCAG 2.2 SC 1.4.3](https://www.w3.org/TR/WCAG22/#contrast-minimum)
Every substantive response ends with a ## Sources section listing all cited references with full URLs:
## Sources
- [WAI-ARIA 1.2 Specification](https://www.w3.org/TR/wai-aria-1.2/)
- [ARIA Authoring Practices Guide](https://www.w3.org/WAI/ARIA/apg/)
- [WCAG 2.2 Success Criterion 4.1.3: Status Messages](https://www.w3.org/TR/WCAG22/#status-messages)Prefer current specifications and documentation versions:
- WCAG 2.2 over WCAG 2.1 for guidance. W3C says 2.2 does not deprecate or supersede 2.1, and several laws still name an earlier version (ADA Title II and the HHS Section 504 rule: WCAG 2.1 AA; Section 508: WCAG 2.0 AA; EN 301 549 V3.2.1, the version cited for presumption of conformity in the EU: WCAG 2.1). When a finding or report is about one of those obligations, cite the version the law names.
- WAI-ARIA 1.2 over WAI-ARIA 1.1. WAI-ARIA 1.3 is a Working Draft: cite it as a draft, never as the Recommendation.
- Current screen reader documentation over archived versions
- Latest platform vendor docs over older releases
When sources disagree:
- Cite both sources and note the conflict
- Normative specs (Tier 1) outrank all others
- Informative guidance (Tier 2) outranks vendor docs (Tier 3)
- State which interpretation the agent is following and why
Each agent domain, with its primary sources.
| Agent Domain | Primary Sources |
|---|---|
| WCAG / General Web | w3.org/TR/WCAG22/, w3.org/WAI/WCAG22/Understanding/, w3.org/WAI/ARIA/apg/ |
| ARIA Patterns | w3.org/WAI/ARIA/apg/patterns/, w3.org/TR/wai-aria-1.2/ |
| Color Contrast | w3.org/TR/WCAG22/#contrast-minimum, w3.org/TR/WCAG22/#contrast-enhanced |
| wxPython | docs.wxpython.org, docs.wxwidgets.org, wiki.wxpython.org |
| Desktop Accessibility | learn.microsoft.com/windows/win32/winauto/, developer.apple.com/accessibility/ |
| NVDA Addons | nvaccess.org docs, github.com/nvaccess/nvda (source), github.com/nvdaaddons/DevGuide |
| Screen Readers | nvaccess.org, support.freedomscientific.com, support.apple.com/guide/voiceover/ |
| PDF/UA | pdfa.org, iso.org 14289-1/2 |
| Mobile | developer.apple.com/accessibility/, developer.android.com/guide/topics/ui/accessibility/ |
| Section 508 | section508.gov, access-board.gov/ict/ |
| Markdown | github.github.com/gfm/, commonmark.org |
| Document Accessibility | support.microsoft.com/accessibility, adobe.com/accessibility |
When providing recommendations based on specifications or documentation that may have been updated since training data:
- Use
context7MCP server to fetch current library documentation for framework-specific advice - Use
fetch_webpageto verify specific WCAG/ARIA specification content when the user asks about edge cases or recent changes - Always note the version of the specification being cited
- If currency cannot be verified, state: "This is based on [spec version X]. Check [URL] for the latest version."
The machine-readable source registry at source-registry.json tracks authoritative URLs with content fingerprints. .github/scripts/check_source_currency.py reads this registry, compares the fingerprints and reports a source that changed or went away in one issue per source, which later runs update rather than duplicate. A 401, 403 or 429 is a site refusing automated requests, not a moved page, so it files nothing and asks for a check by hand. No workflow runs it at present. Until one does, the lastVerified dates in the registry record when each source was last checked by hand.
- Agents Overview
- Accessibility Lead
- Web Accessibility Wizard
- Document Accessibility Wizard
- Markdown Assistant
- Developer Hub
- GitHub Hub