Accessibility Conformance
Conformance claim
Date of claim: 2026-08-28
Guidelines: Web Content Accessibility Guidelines 2.2 at https://www.w3.org/TR/WCAG22/
Conformance level satisfied: Level AA
Pages covered: the following URI patterns on https://docs.cosyte.com. Subdomains of
cosyte.com are not included in this claim.
| Pattern | What it covers |
|---|---|
https://docs.cosyte.com/ | the site landing page |
https://docs.cosyte.com/accessibility | this page, and other standalone site pages |
https://docs.cosyte.com/search | the search results page |
https://docs.cosyte.com/<package>/ | a package root, and each archived version root |
https://docs.cosyte.com/<package>/<page> | narrative documentation pages, including the placeholder a package serves before its first release |
https://docs.cosyte.com/<package>/api/ | generated API reference pages |
https://docs.cosyte.com/<any unrouted path> | the "Page Not Found" response |
Web content technologies relied upon: HTML, CSS, JavaScript, WAI-ARIA.
JavaScript is on that list deliberately. The pages are statically rendered, so their text and structure are present with scripting disabled, but the colour-mode control, the in-page navigation and the search field are scripted components: with JavaScript unavailable they do not operate.
What this claim rests on, and what it does not
Automated testing evaluates only a subset of the WCAG 2.2 Level AA success criteria. This claim is supported by an automated gate that must pass before the site deploys. It is not a substitute for a manual audit, and it is not a proof of conformance. No automated tool can decide whether alternative text is meaningful, whether a heading structure describes the content beneath it, or whether a page is operable end to end with a screen reader.
What the gate does do, on every build:
- It runs axe-core over the union of the axe rule tags for WCAG 2.0, 2.1 and 2.2 at Levels A and AA. It is the union and not the newest tag, because axe's WCAG tags are version-scoped and additive.
- It explicitly enables every rule those tags select, including the ones axe does not run by default: the WCAG 2.2 rules, the rules axe has deprecated, and the rules axe marks experimental. It then checks that each of them actually ran, so a rule that is selected but silently skipped fails the build instead of passing it.
- It scans at least one route of every page template this site publishes, in both the light and dark colour modes, and fails if a route it was told to scan will not load, resolves to a different template, or renders in a mode other than the one requested.
- It fails the build on any violation reported at
seriousorcriticalimpact.
One route per template is a floor, not a ceiling. The gate proves that no page template is unmeasured. It does not scan every page: documentation content is written in each package's own repository, and a defect authored into one narrative page is not something a scan of a different narrative page can see.
Known limitations
- Success criteria that require human judgement are not covered by the automated gate. See above.
- Documentation content is contributed from other repositories and published from release artifacts. Those artifacts are immutable once published, so a correction to content reaches this site when the owning package cuts its next release.
- This claim covers
docs.cosyte.comonly. Other Cosyte sites make their own claims or none.
Reporting an accessibility problem
If something on this site does not work with your assistive technology, please tell us through https://cosyte.com. It helps to include the page address, the assistive technology and browser you were using, and what you expected to happen.
Documentation content is contributed from each package's own repository, so a problem in the words on a documentation page and a problem in the site around them are fixed in different places. You do not need to work out which: report it either way and we will route it.