Model accessibility statement
Tell users how accessible your website or mobile app is in your accessibility statement, based on recent testing.
How to use the model statement
Public sector websites and mobile apps must publish an accessibility statement. The model statement contains mandatory wording to use in your accessibility statement. You need to replace the words in square brackets from the template statement.
A link to your statement should be easy to find on your website homepage, or made available on every web page. It should be prominent, for example in a static header or footer.
For mobile applications, the statement should be available on the website of the public sector body that developed the app, or with other information available when downloading the app. The statement may also be made available from within the app.
Other information helpful to users can be included. You can view examples in the sample accessibility statement.
Accessibility Statement
[Name of organisation] is committed to making its [website(s)/mobile application(s), as appropriate] accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
This accessibility statement applies to [insert scope of statement, for example, website(s)/mobile application(s) to which the statement applies, as appropriate].
[For mobile applications, please include version information and date.]
Compliance status
[Choose one of the options below, for example, (a), (b), or (c) and delete those not applicable.]
[Select (a) only if all requirements of the technical specification are fully met without exceptions for WCAG version 2.2.]
(a) [This] [These] [website(s)] [mobile application(s)] [is] [are] fully compliant with the Web Content Accessibility Guidelines (WCAG) version 2.2 AA standard.
[Select (b) if most requirements of the technical specification are met, but with some exceptions. This means not yet fully compliant and that the necessary measures are to be taken in order to reach full compliance.]
(b) [This] [These] [website(s)] [mobile application(s)] [is] [are] partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to [the non-compliance(s)] [and/or] [the exemptions] listed below.
[Select (c) if most requirements of the technical specification are not met]
(c) [This] [These] [website(s)] [mobile application(s)] [is] [are] not compliant with the Web Content Accessibility Guidelines version 2.2 AA standard. The [non-compliance(s)] [and/or] [the exemptions] are listed below.
Non-accessible content
[This section or individual headings within this section can be deleted if not applicable.]
The content listed below is non-accessible for the following reason(s):
(a) non-compliance with the accessibility regulations
[List the non-compliance(s) of the website(s)/mobile application(s), and/or, describe which section(s)/content/function(s) are not yet compliant].
[Describe in non-technical terms, as far as possible, how the content is not accessible, including reference(s) to the applicable requirements in the relevant standards and/or technical specifications that are not met.]
(b) disproportionate burden
[List non-accessible section(s)/content/function(s) for which the disproportionate burden exemption, within the meaning of the accessibility regulations is being temporarily invoked]
(c) the content is not within the scope of the accessibility regulations
[List non-accessible section(s)/content/function(s) which is/are out of scope of the accessibility regulations].
[Indicate accessible alternatives, where appropriate].
Preparation of this accessibility statement
This statement was prepared on [date].
[Insert date of the first preparation, or a subsequent update, of the accessibility statement following an evaluation of the websites/mobile applications to which it applies. It is recommended that an evaluation is carried out and the statement updated following a substantial revision of the website/mobile application.]
[Indicate the method used to prepare the statement. The method should be an actual evaluation of the website’s or mobile application’s compliance, such as a self-assessment done by the public sector body or an assessment carried out by a third party, for example a certification].
The statement was last reviewed on [insert date of latest review].
[It is recommended that the claims made in the accessibility statement are reviewed as regards their accuracy on a regular basis, and at least once per year. If such a review has taken place without a full evaluation of the website/mobile app, whether or not such a review has led to any changes in the accessibility statement, please indicate the date of the last such review.]
Feedback and contact information
[Provide a description of, and a link to, the feedback mechanism to be used to notify the public sector body of any compliance failures and to request information and content excluded from the scope of the Directive].
[Provide the contact information of the relevant entity(ies)/unit(s)/person(s) (as appropriate) responsible for accessibility and for processing requests sent through the feedback mechanism].
Enforcement procedure
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’).
If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).
[Note: if your organisation is based in Northern Ireland, refer users who want to complain to the Equalities Commission for Northern Ireland (ECNI) instead of the EASS and EHRC.]
[The statement should link to the website of EASS or ECNI]
Updates to this page
Last updated 30 September 2024 + show all updates
-
References to WCAG 2.1 have been removed.
-
Updated the model accessibility statement to include options for new success criteria in WCAG 2.2.
-
First published.