Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,110 of 9,110 pages
About the help in other languages
All help pages

Accessibility statement for non-profits

How a non-profit writes and maintains an honest accessibility statement for its Exponential site - what it contains, how to describe the software's part without overstating it (the project rates admin4 Partly complies…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/non-profits/accessibility/accessibility-statement-for-non-profits.md

On this page

Accessibility statement for non-profits

This page is for the communications lead or director who signs the statement. An accessibility statement tells visitors how accessible your site is, what you know does not work, and how to reach you if something blocks them. Public bodies are often required to publish one; for a non-profit it is good practice and sometimes a funder's condition. The detailed guide is Writing an accessibility statement.

Contents

  1. What it contains
  2. Describing the software honestly
  3. Known issues
  4. Feedback and response
  5. An outline to fill in
  6. Keeping it current

What it contains

PartContent
CommitmentThat you want everyone to be able to use the site
StandardThe standard you measure against, for example WCAG 2.2 level AA
StatusYour honest assessment: fully, partly or not conforming, based on testing you actually did
Known issuesWhat does not work, and the alternative meanwhile
FeedbackHow to report a problem and get the content another way
Method and dateHow and when you tested; when you will review

Describing the software honestly

Your statement is about your site. If you mention the software, use the project's own words and do not upgrade them (What Exponential provides):

  • The admin4 administration is designed and regression-tested against WCAG 2.2 AA; the project rates it "Partly complies" and makes no conformance claim.
  • There is no VPAT, no Accessibility Conformance Report and no WCAG-EM report for Exponential.
  • Public designs are not audited by the project; your public design is your responsibility.

Never write "our CMS is WCAG certified". If you need a formal report, see Preparing an ACR.

Known issues

List them plainly, with what you do about them. Typical entries for a non-profit site:

IssueAlternative meanwhilePlanned fix
Older PDF annual publications are not taggedSummaries on HTML pages; send on requestAccessible PDFs from next year
Some older videos lack captionsTranscript on requestCaptions by a date
The CAPTCHA on the volunteer form may be hard to solveApply by mail or phoneReview provider settings
The embedded donation form (if used) has not been tested by usThe Donate link opens the platform's own pageTest, or replace by a link

Write your own list from your own tests (Accessibility basics for non-profits).

Feedback and response

  • A contact form or address on the statement page, and a link to the statement in every page footer.
  • Promise a response time you can keep.
  • Track what people report and what you fixed (Monitoring and feedback).
  • A contact form is built with the information collector (Building a contact form).

An outline to fill in

Accessibility statement for [site address]

[Organization] wants as many people as possible to be able to use this website.

Standard: We aim to meet WCAG 2.2 level AA.

Status: This website is [fully / partly / not] conforming. We last tested it on [date]
by [method: keyboard testing, automated checks, testing with users, outside audit].

What does not work yet:
- [issue] - meanwhile [alternative] - we plan to fix it by [date]

Feedback: If you cannot use part of this site, contact [address / form / phone].
We reply within [days].

This statement was prepared on [date] and will be reviewed by [date].

Keeping it current

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.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x