Accessibility for public bodies
This section is for public bodies that run a website with Exponential and must make it accessible: project managers, accessibility coordinators, editors, designers, developers and administrators. Every statement about the product is backed by the project's own statement, Accessibility standards, whose status words are kept as written: WCAG 2.2 AA Partly complies (admin4 and admin4l administration), EN 301 549 and Section 508 Unverified, public designs not audited, no VPAT or Accessibility Conformance Report, and no accessibility statement template. This section never claims conformance.
Note This section describes features and common practice; it is not legal advice. Check the law that applies to your organization with your legal counsel.
Contents
Reading order
- Decision makers and project managers: What Exponential provides, What accessibility law asks of public bodies, What Exponential does not cover, Accessibility roles and responsibilities, Procurement clauses.
- Accessibility coordinators: add the mappings, Auditing your public design, Writing an accessibility statement, Preparing an ACR, Monitoring and feedback.
- Editors: Accessible content for editors, then the pages on alternative text, headings, link text, tables, documents and media.
- Designers and developers: the four principle pages, Color and contrast, Keyboard and focus, Accessible forms, Testing with axe and the keyboard, Right-to-left accessibility, Language of the page and its parts.
Pages in this section
| Page | Answers |
|---|---|
| What Exponential provides for accessibility | the status per standard, what is tested, software versus site |
| What accessibility law asks of public bodies | the three families of rules and the duties they share |
| The EU Web Accessibility Directive and Exponential | duty by duty: what the software does and what you do |
| The European Accessibility Act and Exponential | when the act may concern a public body; the evidence available |
| Section 508 and Exponential | status Unverified, no VPAT; what to evaluate |
| Mapping WCAG 2.2 AA to Exponential | criterion by criterion, admin4 evidence and who does it on the public site |
| Mapping EN 301 549 to Exponential | clauses 9, 10, 11 (11.8 authoring tools) and 12 |
| What Exponential's admin4 covers | the tested features and how to make admin4 the editors' design |
| What Exponential does not cover | the known gaps and how to plan around them |
| The online editor and accessibility | TinyMCE 3 and 8, status Unverified, how to test |
| Auditing your public design with WCAG-EM | scope, sample by template, evaluate, report |
| Writing an accessibility statement | no template ships; an outline and how to publish it |
| Preparing an Accessibility Conformance Report for your site | scoping and writing an honest ACR for your configuration |
| Accessible content for editors | seven habits and the tools that support them |
| Alternative text for images | writing it, making it required, decorative images, finding gaps |
| Headings and structure | rich text level 1 becomes h2; rules for editors and designers |
| Link text | meaningful links, documents, new windows, link management |
| Tables in content | header cells, captions, what the templates render |
| Documents and PDFs | page first; checks before upload; the PDF export is not tagged |
| Accessible forms | labels, errors, CAPTCHAs, time limits for information collector forms |
| Color and contrast in your theme | ratios, tokens as admin4 does it, brand colors |
| Keyboard and focus | admin4's keyboard support, keys for staff, rules for your design |
| Captions and media | what the media field renders (no caption track) and how to add captions |
| Testing with axe and the keyboard | a repeatable routine and how the project tests |
| Right-to-left accessibility | direction and language in the administration, content and your design |
| Language of the page and its parts | lang per siteaccess, translations, passages |
| Procurement clauses for accessibility | sample requirements, evidence requests and contract clauses |
| Monitoring and feedback | a feedback channel, spot checks, records to keep |
| The perceivable principle | WCAG principle 1 by role |
| The operable principle | WCAG principle 2 by role |
| The understandable principle | WCAG principle 3 by role |
| The robust principle | WCAG principle 4 by role |
| Accessibility roles and responsibilities | who does what, a responsibility matrix, training |
Tasks that put these pages into practice (require alternative text on an image field, run an accessibility spot check, publish an accessibility statement page, check alternative text across images) are in the compliance tasks of this help (Compliance tasks).
Related pages
- Up: Governments: start here
- Accessibility standards
- Accessibility for site builders
- Testing your site's accessibility
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.