Corpus targets RGAA 4.1, fully conformant - the French accessibility standard, built on WCAG 2.1 AA. It is a demanding goal, and this page says honestly where what the template can guarantee stops.
A template does not make a site accessible. It makes the site capable of being accessible. Conformance is decided by the content - your text, your images, your links, your documents - and you answer for it.
What Corpus guarantees, whatever you do
Interface contrast. Text on its background, the focus ring, control outlines, link colours: verified by calculation, across all 360 possible hues, in both themes. You cannot produce an unreadable accent by turning the slider.
Focus visible everywhere. A solid ring in the site's hue, plus a halo. No focusable element is without one.
Keyboard navigation. The menu opens with the arrow keys, Escape closes one level at a time and returns focus to the button that opened it. Panels that block the page trap focus while open and return it where it came from.
Panels that do not block do the opposite, deliberately: the announcement panel never takes the keyboard, neither when it opens nor when a page loads. It announces itself politely to screen readers and can be reached by tabbing. Stealing focus from someone reading or filling in a field would be worse than announcing nothing at all.
Zoom. Up to 400%, and down to 320 px wide, with no loss of content and no horizontal scrolling. Verified at 301 px.
Text spacing. A reader can force line height 1.5, letter spacing 0.12 em and word spacing 0.16 em with nothing being clipped.
No text below 1 rem. Modules, cards, captions and small print included.
Colour never carries meaning alone. Every message carries a pictogram and its wording. A field in error carries text, not just a red outline.
Motion respects prefers-reduced-motion.
A level 1 heading on every article. If you hide an article title (Show Title: Hide) and the menu item does not show a page heading, Corpus still writes the article title as an h1, hidden on screen but read by screen readers. It does not when your text already contains an h1.
A main region on every page. The "Skip to main content" link always leads somewhere, including on a page made of bands only, with the Content section switched off (see The Layout).
What Corpus cannot guarantee
The alternative text of your images. The template does not know what your photo shows. This is the point that fails the most audits.
The wording of your links. "Click here" stays "click here". A link must make sense out of context.
The hierarchy of your headings. Corpus will correctly style an h2 followed by an h4 - it cannot guess that an h3 is missing.
Your attached documents. An untagged PDF stays inaccessible.
Your videos. Captions and transcripts are your responsibility.
Third-party extensions. A component or module from another vendor produces its own markup. Corpus dresses it, it does not fix it.
The four message colours if you change them. See Appearance: the default values are verified, yours are not.
The accessibility statement
In France, a public-sector site - and many private ones - must publish an accessibility statement giving its level of conformance, the non-conformant content and a way to report problems. Similar duties exist across the EU under the European Accessibility Act.
That statement is about your site, not about the template. Corpus cannot write it for you: it depends on your content and on the audit you have had carried out.
What is still outstanding in Corpus
For honesty, the list of known and untreated points to date:
forced-colors- rules have existed since 4 August 2026, but they were written by reading the compiled stylesheet, not by looking at a screen: that mode cannot be emulated. To be checked under Windows.- The 106-criterion RGAA audit grid is not kept, and no audit has been carried out by a third party. See Corpus's accessibility statement: what the template guarantees is written there, along with how each point is verified - and what is not.
- The pictograms are a first pass; two of them do not hold up perfectly at 16 px.
These are tracked and will be dealt with. They are written here rather than passed over in silence: documentation claiming total conformance without reserve is documentation you cannot believe.
Up to date for Corpus 2.1.704.