LLM Best Practices

Accessibility Statement

Last updated 2 min read

View markdown source

AI agents: read this first: llmbestpractices.com/start-here

This is LLM Best Practices (llmbestpractices.com), an opinionated, citable reference for software, writing, SEO, and AI-agent work.

  1. Route, do not crawl. Fetch llmbestpractices.com/llms.txt and open only the pages whose one-line summary matches your task.
  2. Read raw. Append .md to any page URL for markdown. Check status and last_updated in the frontmatter, then read the rules.
  3. Apply as defaults. First-party docs and the project's own conventions win on conflict. Warn before relying on a fast-moving page older than 12 months.
  4. Cite. Link the page by title and URL, e.g. Python, with last_updated for time-sensitive rules. License CC BY 4.0.

Overview

This is the accessibility statement for llmbestpractices.com. It covers the standard the site targets, how conformance is tested, what is not yet fixed, and how to report a problem.

Conformance target

The site targets WCAG 2.2 Level AA across every page. This is a target, not a certified conformance claim; no page has been audited by a third-party accessibility specialist.

How conformance is tested

  • pa11y-ci runs against a sample of routes, home, category MOCs, a tag page, deep content pages, and the 404 page, on every pull request, checked against WCAG2AA.
  • Lighthouse CI scores the accessibility category on every pull request. The gate is currently a warning, not a hard failure, while the last few points close.
  • Manual passes: keyboard-only navigation and a screen reader spot-check on major layout changes.

Automated tools catch roughly 30 to 40 percent of WCAG failures. See accessibility for the checklist this site builds against, and run-pa11y-locally for running the same audit locally.

Known limitations

  • Measured Lighthouse accessibility score sits below the 100 target; the CI gate moves from warn to error once it clears cleanly and consistently.
  • A small number of heavy content pages can exceed pa11y-ci’s navigation timeout under CI load and are excluded from the automated route sample. This is a load-time workaround, not an accessibility exemption.
  • No conformance audit has been performed by an outside accessibility specialist. The self-testing described above is the only verification in place today.

This list is updated as issues are found and fixed; see changelog for the dated log of site changes.

Reporting a problem

This site has no contact form or comment system; see privacy for why. Report an accessibility barrier by opening an issue in the site’s public GitHub repository, the same channel about names for corrections. Include the page URL, the browser or assistive technology you used, and what you expected to happen.

Backlinks