Accessibility
The Council's approach to accessibility of the CCSA standard site, its current conformance status and how to report an issue.
The Council aims to make the CCSA standard materials accessible to all users, including those who navigate by keyboard or rely on assistive technologies. This statement sets out the target conformance level, the measures already in place and an honest account of the v0.2 draft's known limitations.
Statement updated2026-06-10
Target level
The site is built toward WCAG 2.1 Level AA. This is a target for the v0.2 draft, not an independently audited result. A formal accessibility audit is planned for the v1.0 release.
Conformance summary
A self-assessment across key areas. "Partial" means a measure is in place but does not yet cover every screen or scenario.
| Area | Status | Note |
|---|---|---|
Landmarks and page structure | Full | Semantic landmarks and a single top-level heading per page. |
Keyboard access | Full | Full keyboard navigation; visible focus; dialogs trap focus. |
Contrast and not-by-color | Full | Status is conveyed by glyph, weight and outline, not color alone. |
Heading hierarchy | Partial | Some section headings are styled visually and will become programmatic headings by v1.0. |
Page language | Full | The lang attribute changes correctly on RU/EN switching. |
What is already in place
Measures implemented at this stage:
Semantic landmarks (header, nav, main, footer), a single top-level heading per page, and a "skip to main content" link for keyboard users.
Status is never conveyed by color alone: a glyph, font weight and outline carry the meaning (✓, ✕, –, ≈, ★). The single accent color is used sparingly.
Keyboard navigation across links, buttons and forms; a visible focus state on every interactive element; the search dialog traps focus, closes on Escape and restores focus to its opener.
The page language attribute (lang) is set on RU/EN switching, so a screen reader announces text in the right language.
Form fields are associated with their labels; decorative glyphs and arrows are hidden from assistive technology (aria-hidden).
Known limitations
The site is a v0.2 draft. We note honestly where work is still ongoing:
On some pages, section headings are currently styled visually and do not yet form a complete programmatic heading hierarchy.
A few composite widgets (for example, tabs) do not yet fully implement arrow-key control from the keyboard.
An independent accessibility review and resolution of the remaining issues are planned for the v1.0 release.
Report an issue
If you hit an accessibility barrier, let the Council know — we will consider it as part of the standard's public consultation. Where you can, please include the page, browser and assistive technology.