Publishing standards
Editorial Policy
How Accessibility.build researches, writes, reviews, updates, and corrects public content.
Last reviewed: July 12, 2026
Traceable sources
Material factual claims should link to primary standards, government publications, court records, research papers, or clearly identified datasets whenever practical.
Named accountability
Author and reviewer identities are published when known. Generic team bylines are not used as a substitute for the person responsible for the work.
Human-reviewed AI use
AI may support research organization, drafting, or editing. It does not replace source verification, technical judgment, or author accountability.
Qualified legal coverage
Legal and regulatory content is educational, identifies jurisdiction and date, cites authoritative material, and is not represented as legal advice.
Ownership and responsibility
Accessibility.build is founder-owned. Khushwant Parihar is responsible for the editorial standards on this page and for ensuring that published bylines identify the accountable author. Contributor and specialist-reviewer roles are credited separately when applicable.
Research and sourcing
- Primary standards and official sources are preferred over summaries.
- Statistics identify the source, covered period, population, and meaningful limitations.
- Third-party research synthesis is not described as original Accessibility.build data collection.
- Anonymous sources are avoided unless the information is important, independently corroborated, and anonymity is explained.
- Affiliate, sponsored, or paid-placement relationships must be disclosed near the affected content. Accessibility.build does not currently publish paid rankings.
Technical accessibility content
Code and testing guidance should distinguish requirements, sufficient techniques, common patterns, and professional judgment. Examples are reviewed for semantics, keyboard use, names and relationships, status communication, focus behavior, contrast, and relevant assistive-technology considerations.
Passing an automated test is not described as proof of WCAG conformance. Tool limitations and manual-testing requirements are stated where they affect interpretation.
AI assistance
AI may help summarize notes, generate candidate outlines, compare wording, or draft code examples. The named author remains responsible for checking sources, dates, code behavior, legal qualifications, citations, and the final published text. AI output is not treated as a source.
Updates and corrections
Time-sensitive pages include an updated or reviewed date. Material corrections are handled under the Corrections Policy. Minor spelling or formatting changes may be corrected without a formal note when they do not change meaning.
Reader feedback
Report a factual, technical, accessibility, or attribution concern to contact@accessibility.build. Include the page URL, the disputed passage, supporting evidence, and the correction you believe is required.