This template cannot be used as is. You will need to tailor it to your site. Other bits need to be left verbatim, assume left as is, unless prompted, and check the HTML comments.

Accessibility Statement for SITE_URL (SITE NAME)

This website is run by the School of Informatics. We want as many people as possible to be able to use this website. For example, that means you should be able to:

AbilityNet has advice on making your device easier to use if you have a disability. The University also provides a page on how to alter your browser to improve the accessibility of web pages -

How accessible this website is

We know some parts of this website are not fully accessible:

Feedback and contact information

[only include options that you can actually provide, can you really provide it in braille?]

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille: [two forms of contact, best not to us a personal email address] email [email address] call [phone number] [add any other contact details, eg in person at support desk] We'll consider your request and get back to you in [number] days.

Reporting accessibility problems with this website

We're always looking to improve the accessibility of this service. If you find any problems not listed on this page or think we're not meeting accessibility requirements, contact: [note the details below should be tailored to what's applicable to your site, and could be the same as above]

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).

See also Reporting an accessibility problem on a public sector website.

Contacting us by phone or visiting us in person

[this may need tweaked if the people responsible for the site are not at the Forum]

Technical information about this website's accessibility

The University of Edinburgh is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to [insert one of: the non-compliances the exemptions the non-compliances and exemptions] listed below.

Non-accessible content

The following items do not comply with the WCAG 2.1 AA success criteria:

We aim to improve our websites accessibility on a regular and continuous basis. See the section below ('What we're doing to improve accessibility') on how we are improving our site accessibility.

Disproportionate burden

We are not currently claiming that any accessibility problems would be a disproportionate burden to fix.

[don't claim disproportionate burden unless you really can justify it. The regulator is likely to look at the Uni as a whole, not just Informatics, and see what's it's income is when deciding if its disproportionate or not]

Content that's not within the scope of the accessibility regulations

[ list content that you think is not covered by the regs eg ]

PDFs and other documents

Many of our older PDFs and Word documents do not meet accessibility standards - for example, they may not be structured so they're accessible to a screen reader. This does not meet >WCAG 2.1 success criterion 4.1.2 (name, role value).

The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they are not essential to providing our services. For example, we do not plan to fix archive material such as news articles published before 2018.

Regulations for PDFs or other documents published before 23 September 2018

What we are doing to improve accessibility

[list what you are doing! eg]

Preparation of this accessibility statement

This statement was prepared on [date]. It was last reviewed on [date].

This website was last tested on [date of test]. The test was carried out by [ how was it tested: manual, automated, both, 3rd party. eg]
our own computing staff. With a mixture of automated (Lighthouse) and manual testing.

We used this approach to deciding on a sample of pages to test: [state the method you used eg most visited pages, oldest, newest]
[possibly link to the result of any testing report]

Change log

[as you revisit and review your statement, and improve things, note them here.]