Accessibility Statement for Public Institutions: What to Include
An accessibility statement explains how accessible a public institution's website or digital service is, which accessibility standards it follows, what limitations remain, and how users can report accessibility problems.
For public institutions, an accessibility statement can also be a legal requirement. The exact requirements depend on the country and jurisdiction, but public-sector accessibility frameworks commonly require organizations to communicate the accessibility status of their digital services.
A useful accessibility statement should therefore be more than a generic declaration that a website is "accessible."
It should give users clear, current and transparent information about the accessibility of the website and what to do if they encounter a barrier.
The W3C recommends that accessibility statements explain the accessibility standard being used, the current conformance status, known limitations, how accessibility was evaluated and how users can provide feedback.
What is an accessibility statement?
An accessibility statement is a dedicated page that explains the accessibility status of a website, mobile application or other digital service.
It typically communicates:
- which accessibility standards apply;
- the current accessibility or conformance status;
- known accessibility issues;
- how accessibility was evaluated;
- what the organization is doing to address known issues;
- how users can report accessibility barriers;
- when the accessibility assessment was performed or the statement was last reviewed.
The exact information required varies by jurisdiction.
For a public institution, the statement should be written primarily for the people using the service. Technical information can be included where useful, but the main purpose is to help users understand the accessibility of the service and what they can do if they experience a problem.
Why do public institutions need an accessibility statement?
An accessibility statement serves two important purposes.
First, it provides transparency.
A public institution should be able to communicate whether its website is accessible, what standards it is working against and whether known limitations remain.
Second, it gives users a clear channel for reporting accessibility problems.
A visitor who cannot complete an online form, access a document or navigate a service using a keyboard should not have to search through the website to find out who to contact.
For some public-sector organizations, publishing an accessibility statement is also a specific legal obligation.
For example, UK public-sector bodies are required to publish accessibility statements under the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018. GOV.UK provides specific guidance on what these statements should contain.
The legal requirements differ in other jurisdictions, so public institutions should always check the framework applicable to their country and type of organization.
What should an accessibility statement for a public institution contain?
Although requirements differ between jurisdictions, a useful accessibility statement generally covers several key areas.
1. Which website or service does the statement cover?
The statement should clearly identify the website, application or digital service to which it applies.
For example:
"This accessibility statement applies to the example.gov website."
This is particularly important when an institution operates multiple websites or digital services.
Users should not have to guess whether the statement applies to the service they are currently using.
2. Which accessibility standard is being used?
The statement should identify the accessibility standard against which the website has been evaluated.
For many organizations, this means referencing the Web Content Accessibility Guidelines (WCAG) and specifying the relevant version and conformance level.
For example:
- WCAG 2.1 Level AA
- WCAG 2.2 Level AA
Where a country has adopted a national accessibility standard or methodology based on WCAG, the statement should also reference the applicable framework.
The important point is to describe the actual standard used for the assessment, rather than simply stating that the website is "WCAG compliant."
3. What is the current accessibility status?
The statement should tell users the current status of the website.
Depending on the applicable framework, this could be described as:
- fully conformant;
- partially conformant;
- non-conformant;
- not yet assessed.
If the website is only partially conformant, the statement should explain which parts are not accessible.
A statement is more useful when it gives users an honest picture of what they can expect rather than presenting accessibility as an all-or-nothing claim.
4. What accessibility issues are known?
If known accessibility barriers remain, the statement should describe them.
Examples could include:
- PDFs that are not fully accessible;
- images without appropriate alternative text;
- keyboard-navigation problems;
- inaccessible forms;
- videos without captions;
- third-party components with accessibility limitations.
The level of detail should be appropriate for the audience.
The statement does not need to reproduce every finding from a technical audit, but users should be able to understand the most relevant limitations.
5. Are accessible alternatives available?
If some content cannot currently be accessed, the statement should explain whether an alternative is available.
For example, if a PDF is not accessible, the institution might provide an accessible HTML version or a way for users to request the information in another format.
This is particularly important when the inaccessible content is necessary to complete a public service or obtain important information.
6. How can users report an accessibility problem?
An accessibility statement should provide a clear way for users to report barriers.
This might include:
- an accessibility email address;
- an online contact form;
- a telephone number;
- another accessible communication channel.
The process should be as straightforward as possible.
Users should know what to report, where to report it and what happens after they submit their feedback.
7. How was accessibility evaluated?
The statement should explain how the accessibility status was determined.
This could involve:
- automated accessibility testing;
- manual testing;
- testing with assistive technologies;
- an internal assessment;
- an external accessibility audit;
- a combination of these methods.
This information provides useful context for the accessibility claims made in the statement.
An automated scan alone should not be presented as proof that every aspect of a website is accessible.
8. When was the website last assessed?
The statement should include the date of the latest accessibility assessment or review, where required or relevant.
This helps users understand how current the information is.
It is particularly important for public websites because their content and functionality can change significantly after an assessment.
9. When was the accessibility statement last updated?
The publication or update date should also be clear.
If the statement has not been updated for several years, users may reasonably question whether it still reflects the current website.
A regular review process helps prevent this problem.
What is the difference between an accessibility statement and an accessibility audit?
An accessibility statement and an accessibility audit are related, but they serve different purposes.
An accessibility audit evaluates the website.
An accessibility statement communicates the relevant results and accessibility status to users.
For example, an audit might identify:
- missing alternative text;
- insufficient color contrast;
- keyboard-navigation issues;
- inaccessible forms;
- incorrect heading structures;
- problems with interactive components.
The accessibility statement can then communicate the relevant accessibility limitations in language that users can understand.
The statement should therefore be based on the actual accessibility status of the website rather than being treated as a standalone compliance document.
For more detail on how scanning, auditing, monitoring and remediation fit together, see Wawsome's Accessibility Widget, Audit & Monitoring article.
Does an accessibility statement prove that a website is WCAG compliant?
No. An accessibility statement is a description of the website's accessibility status. It does not itself establish conformance.
If an organization states that a website conforms to WCAG, that claim should be supported by an appropriate evaluation.
The statement should also specify:
- which WCAG version was used;
- which conformance level applies;
- what was evaluated;
- when the evaluation took place;
- whether any known limitations remain.
This distinction is important because an accessibility statement should accurately represent the evidence behind the organization's accessibility claims.
Is an automated accessibility scan enough for an accessibility statement?
No. Automated testing can identify many common accessibility issues quickly, particularly across large websites.
However, some accessibility requirements require human judgment.
For example, automation cannot reliably determine whether:
- alternative text accurately communicates the purpose of an image;
- a form is understandable;
- a keyboard-only user can successfully complete a task;
- instructions are clear;
- a complex interaction works correctly with assistive technology.
This is why automated testing should be combined with manual evaluation where appropriate.
Wawsome similarly positions scanning and reporting as part of the broader accessibility process rather than as a replacement for human evaluation.
How often should an accessibility statement be updated?
An accessibility statement should be reviewed regularly and whenever significant changes affect the accessibility status of the website.
Important triggers include:
- a website redesign;
- a major CMS change;
- new forms or digital services;
- new document libraries;
- significant content changes;
- a new accessibility assessment;
- resolution of previously reported issues;
- discovery of new accessibility barriers.
The exact update frequency may be defined by the legislation applicable to the institution.
For example, UK public-sector guidance recommends reviewing accessibility statements regularly and at least annually.
The underlying principle is simple:
The accessibility statement should reflect the current state of the website, not the state of the website when the statement was originally written.
Where should an accessibility statement be published?
The accessibility statement should be easy for users to find.
A common approach is to place a clearly labelled "Accessibility" or "Accessibility Statement" link in the website footer.
Some jurisdictions establish specific requirements for where the statement must be linked.
For example, UK public-sector guidance states that the statement should be easy to find from the homepage and recommends making it available from every page. ADR
For public institutions, a persistent footer link is generally a practical way to make the statement discoverable.
Should an accessibility statement include every accessibility issue?
No. An accessibility statement should not simply reproduce the entire technical audit report.
Instead, it should summarize the accessibility status and explain the limitations that are relevant to users.
For example, instead of listing dozens of technical WCAG findings, a statement could explain:
"Some older PDF documents are not fully accessible. We are progressively replacing these documents with accessible versions."
The detailed technical findings can remain in the organization's audit or remediation documentation.
Can an accessibility widget replace an accessibility statement?
No. An accessibility widget and an accessibility statement serve different purposes.
A widget can provide users with additional accessibility controls and can help address certain accessibility barriers at runtime.
An accessibility statement communicates:
- the accessibility standard being used;
- the current accessibility status;
- known limitations;
- how the website was evaluated;
- how users can report problems.
Installing a widget therefore does not eliminate the need for an accessibility statement where one is required.
Likewise, publishing an accessibility statement does not make an inaccessible website accessible.
Both should be part of a broader accessibility process.
For a deeper explanation of the different roles of widgets, audits and monitoring, see Accessibility Widget, Audit & Monitoring.
How can Wawsome help public institutions with accessibility statements?
Wawsome combines accessibility scanning, monitoring, reporting and user-facing accessibility features to support an ongoing accessibility process.
Start with an accessibility assessment
The Wawsome Accessibility Scanner can identify accessibility issues that can be detected automatically and provide an initial view of the website's accessibility status.
This can help teams establish a baseline before creating or updating an accessibility statement.
Monitor accessibility over time
The Wawsome Accessibility Monitor continuously monitors website changes and helps identify new accessibility issues as content and pages change.
This is particularly useful for public institutions where websites may be updated by multiple teams over time. Wawsome describes the Monitor as continuously scanning new or modified elements and providing actionable accessibility reporting.
Create an accessibility statement
Wawsome includes functionality for generating an accessibility statement that can be published on a dedicated page.
The Wawsome accessibility features page lists automated accessibility statement generation among the platform's dashboard capabilities, including contact-details integration, custom statement URLs and multilingual accessibility statements.
For a practical explanation of what an accessibility statement should contain, see Wawsome's How to Write an Accessibility Statement guide.
Keep accessibility information up to date
Generating the statement is only one part of the process.
The information should be reviewed whenever the accessibility status of the website changes.
Regular scanning and monitoring can help teams identify changes that may require the accessibility statement to be reviewed.
You can also see an example of an accessibility statement in practice in Wawsome's own Accessibility Statement.
What should a public institution do after publishing its accessibility statement?
Publishing the statement should not be the end of the accessibility process.
Continue testing the website
Regular accessibility testing helps identify new issues that may appear as the website evolves.
Track known accessibility issues
Maintain a record of known problems, their status and the teams responsible for resolving them.
Fix problems at their source
Where possible, correct accessibility problems in the underlying code, content, design or components.
Monitor website changes
New pages, documents, forms and features should be included in the organization's accessibility process.
Collect user feedback
Feedback from people who experience accessibility barriers can reveal issues that automated testing does not detect.
Review the accessibility statement
When the website or its accessibility status changes significantly, review the statement to ensure that it remains accurate.
Frequently Asked Questions About Accessibility Statements
What is an accessibility statement?
An accessibility statement is a public page explaining the accessibility status of a website or digital service, the standards used, known limitations, how accessibility was evaluated and how users can report accessibility barriers.
Do public institutions need an accessibility statement?
This depends on the applicable jurisdiction and type of public institution. In some countries, publishing an accessibility statement is a specific legal requirement for public-sector websites and applications.
What should an accessibility statement contain?
It should generally explain which website or service is covered, which accessibility standard applies, the current accessibility status, known limitations, how accessibility was evaluated, when it was assessed and how users can report accessibility problems.
Should an accessibility statement mention WCAG?
Yes, when WCAG is the applicable accessibility standard or forms part of the applicable technical framework. The statement should specify the relevant WCAG version and conformance level.
Is an accessibility statement the same as an accessibility audit?
No. An audit evaluates the website. An accessibility statement communicates the relevant accessibility status and information to users.
Is an automated scan enough to create an accessibility statement?
No. Automated testing can identify many accessibility issues, but some aspects require manual testing and human judgment.
How often should an accessibility statement be updated?
It should be reviewed regularly and whenever significant changes affect the accessibility of the website. Some jurisdictions also establish specific update requirements.
Can Wawsome generate an accessibility statement?
Yes. Wawsome provides an accessibility statement generator that can create a dedicated statement page. The platform's public Features page also lists contact-details integration, custom statement URLs and multilingual accessibility statements among its capabilities.
Does an accessibility statement make a website accessible?
No. The statement communicates the website's accessibility status. It does not replace accessibility testing, remediation or ongoing monitoring.
Can an accessibility widget replace an accessibility statement?
No. A widget provides user-facing accessibility features, while an accessibility statement documents the accessibility status of the website and explains how users can report problems.
How to create an accessibility statement for a public institution website
Start by establishing the current accessibility status of the website.
Identify the applicable accessibility requirements, perform an appropriate assessment, document known limitations and establish a clear process for addressing accessibility issues.
Then create an accessibility statement that accurately reflects those findings and provides users with a straightforward way to report accessibility barriers.
Most importantly, treat the statement as a living document rather than a one-time compliance page.
As the website changes, its accessibility status can change too.