Preparing an Accessibility Conformance Report for your site
This page is for project managers and suppliers who are asked in a tender or by a buyer for an Accessibility Conformance Report (ACR), often in the form of a VPAT. There is no VPAT and no ACR for Exponential (Accessibility standards: Section 508). What you can produce is a report for your configuration: a given Exponential version, administration design, public design and set of extensions. This page shows how.
Note This page describes features and common practice; it is not legal advice. Check the law that applies to your organization with your legal counsel.
Contents
- Scope the product
- Choose the standards
- Test
- Write each row
- What you may reuse from the project
- Related pages
Scope the product
Write the scope on the first page of the report:
| Item | Where to read it |
|---|---|
| Exponential version | Setup > System information, or composer show se7enxweb/exponential |
| Administration design | the admin siteaccess's [DesignSettings] SiteDesign (admin4 recommended) |
| Online editor engine | ezoe.ini [EditorSettings] EditorEngine (TinyMCE 3 by default, TinyMCE 8 opt-in) |
| Public design | your design and its extension |
| Activated extensions | Setup > Extensions |
| Browsers and assistive technologies tested | your test plan |
Anything outside the scope is "Not evaluated" in the report.
Choose the standards
Ask the buyer which edition they expect: WCAG 2.x (A and AA), Revised Section 508, EN 301 549, or all. The VPAT template editions are published by the ITI, outside this project; use the one the buyer names.
Test
- Public site: evaluate with WCAG-EM (see "Auditing your public design with WCAG-EM").
- Administration: choose editor tasks (sign in, find content, create and publish an article with an image, upload a file, read versions, sign out) and test them with the keyboard, a screen reader, 200% zoom and forced colors.
- Online editor: test separately (see "The online editor and accessibility").
- Keep test notes per criterion: date, page or task, tool, result.
Write each row
| Conformance level | Use it when |
|---|---|
| Supports | every tested page and task meets the criterion |
| Partially supports | some do, some do not; name which |
| Does not support | most do not |
| Not applicable | the criterion cannot occur (for example no audio on the site) |
| Not evaluated | you did not test it; never guess |
In the remarks, say where a limitation comes from (your template, a content item, an extension, the online editor) and what the workaround or plan is.
What you may reuse from the project
You may cite, with the link, the project's own evidence for the administration:
- the status words of Accessibility standards (Partly complies, Unverified);
- the list of design tests and what they hold (form labels, landmarks, keyboard patterns, contrast tokens, error summaries);
- the manual axe results recorded in the 6.0.15 changelog.
Do not turn "Partly complies" into "Supports". The project's tests read template sources; they are evidence for your remarks, not a substitute for your test.
Related pages
- Accessibility standards
- System information
- 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.