Accessibility Roadmap

Submitted by markhook on Thu, 2020-09-17 10:01

Known issues

WCAG A 1.3.1 Ensure labels in the document fragment point to valid IDs
WCAG AA 1.3.5 Identify the purpose of fields programmatically

We have some embedded form elements from third-party suppliers which do not have correctly labelled fields. We are in touch with those suppliers requesting that they remedy these issues.

WCAG A 1.3.1 - Ensure labels in the document point to valid IDs

A review of the whole website is underway, and we hope to have  resolved issue by the end of Q2 2023.

WCAG A 2.4.4 - Avoid using the same link text for different destinations

In some cases we have images embedded in slideshow galleries that have the same title, in nearly all cases this is because they are multiple images of the same thing. Because these images are linked from thumbnails to larger versions they register to assistive technologies as links with duplicate titles. We plan to review these and edit the text where possible to minimise any potential confusion. Additionally some of our Navigation in our Main menu sometimes duplicates links in lower sections of the site which go to alternate locations. A review of the whole website is underway, and we hope to have resolved duplicates by end Q2 2023.

WCAG AA 1.4.3 Ensure text has sufficient contrast

One page exhibits this issue, it relates to text embedded in a plugin from a third party, we are looking to see what options are available from them to get this remedied.

https://www.chch.ox.ac.uk/oxford-cathedral/lectures

PDF Documents

We currently have a significant number of PDFs on our website which are less than 2 years old. Most of these are not fully accessible.

We plan to prioritise these documents by those most essential for the largest numbers of our users, and work to make them accessible or to make accessible web pages which present the same content.

They fail on one or more of the following criteria:

WCAG A 1.1.1 Ensure PDFs are machine readable
WCAG A 1.3.1 Fix untagged PDFs
WCAG A 1.3.1 Specify headings for every PDF
WCAG A 3.1.1 Ensure PDFs specify a default language
WCAG A 2.4.2 Define a title for all PDFs
WCAG A 2.4.2 Improve weak PDF titles
WCAG AA 2.4.5 Ensure long PDFs use bookmarks to aid navigation

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

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 1.3.1 (info and relationships).

The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services. For example, we do not plan to fix old copies of the Christ Church Library Newsletter.

Any new PDFs or Word documents we publish will meet accessibility standards.

 

Updated 7 November 2022