Non Accessible Content
Some documents and content are exempt from the regulations (such as live video content and PDFs or other documents published before 23 September 2018 as they’re not essential to providing our services), so we do not currently have any plans to make them accessible. But if you need to access information in one of these document types, you can contact us and ask for an alternative format.
| Principle 1 - Perceivable | |
|---|---|
| Information and user interface components must be presentable to users in ways they can perceive. | |
| Guideline 1.1 – Text Alternatives | |
| Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language. | |
| 1.1.1 Non-text Content Level A | |
| All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below. | |
| Situation A: If a short description can serve the same purpose and present the same information as the non-text content: | |
| Guideline and Description | Met Success Criteria? |
| G94: Providing short text alternative for non-text content that serves the same purpose and presents the same information as the non-text content | No. Action: to provide a short text alternative for the map on the contact page and to provide a short text alternative for signature images on the news page. |
| Short text alternative techniques for Situation A: | |
| ARIA6: Using aria-label to provide labels for objects | No. Action: to provide aria-label for divisions on website such as map on contact page and for the signature images on the news page. |
| H37: Using alt attributes on img elements | No. Action: provide alt attributes to the signature images on the news page. |
| Situation F: If the non-text content should be ignored by assistive technology: | |
| Implementing or marking the non-text content so that it will be ignored by assistive technology | No. Action: to mark the map on the contact page as a non-text object so that it will be ignored. |
| F20: Failure of Success Criterion 1.1.1 and 4.1.2 due to not updating text alternatives when changes to non-text content occur | No. Action: to update text alternatives. |
| F30: Failure of Success Criterion 1.1.1 and 1.2.1 due to using text alternatives that are not alternatives (e.g., filenames or placeholder text) | No. Action: use text alternatives for links to files instead of file names |
| F65: Failure of Success Criterion 1.1.1 due to omitting the alt attribute or text alternative on img elements, area elements, and input elements of type "image" | No. Action: to add alt text to signature images on the news page. |
| F71: Failure of Success Criterion 1.1.1 due to using text look-alikes to represent text without providing a text alternative | No. Action: to add text alternatives to the signature images on the news page. |
| Guideline 1.3 – Adaptable | |
| Create content that can be presented in different ways (for example simpler layout) without losing information or structure. | |
| 1.3.1 Info and Relationships Level A | |
| Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. | |
| Situation A: The technology provides semantic structure to make information and relationships conveyed through presentation programmatically determinable: | |
| ARIA11: Using ARIA landmarks to identify regions of a page | No. Action: Use aria to create landmarks on the pages such as identifying the footer from the main content of the page. |
| ARIA12: Using role=heading to identify headings | No. Action: use role=heading to identify headings on pages. |
| ARIA13: Using aria-labelledby to name regions and landmarks | No. Action: Use aria-labelledby to name regions and landmarks on the pages - such as identifying the contact details in the footer of the page |
| ARIA20: Using the region role to identify a region of the page | No. Action: to specifiy the regions of news posts to identify them from each other. |
| G115: Using semantic elements to mark up structure AND H49: Using semantic markup to mark emphasized or special text | No. Action: use boldening and slanted words for emphasis in text. Most text does not contain any emphasised elements. |
| H48: Using ol, ul and dl for lists or groups of links | No. Action: to use ul for lists within site. |
| H42: Using h1-h6 to identify headings | No. Action: use h1-h6 to identify headings. |
| H97: Grouping related links using the nav element | No. Action: use nav element on site links. |
| Advisory Techniques | |
| G141: Organizing a page using headings | No. Action: to use headings on all pages. |
| F2: Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without using the appropriate markup or text | No. Action: to make sure all headings use h1-h6 tags. |
| F43: Failure of Success Criterion 1.3.1 due to using structural markup in a way that does not represent relationships in the content | No. Action: remove h1 tag from content of contact page and only have a h1-h6 tag apply to the contact heading of the page. |
| 1.3.2 Meaningful Sequence Level A | |
| When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. | |
| Sufficient Techniques | |
| G57: Ordering the content in a meaningful sequence | No. Action: to group text from publications into separate div tags or li tags with descriptions so that they are easy to follow with a screen reader. |
| C6: Positioning content based on structural markup | No. Action: Publications list does not use h1-h6 tags for dates as titles. Screenreader would not be able to define titles. |
| 1.3.3 Sensory Characteristics Level A | |
| Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound. | |
| Sufficient Techniques | |
| G96: Providing textual identification of items that otherwise rely only on sensory information to be understood | No. Action: to identify map on contact page. |
| Guideline 1.4 – Distinguishable | |
| Make it easier for users to see and hear content including separating foreground from background. | |
| 1.4.1 Use of Color Level A | |
| Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. | |
| Sufficient Techniques | |
| Situation A: If the color of particular words, backgrounds, or other content is used to indicate information: | |
| G14: Ensuring that information conveyed by color differences is also available in text | No. Action: make active links and contact links distinguishable |
| G183: Using a contrast ratio of 3:1 with surrounding text and providing additional visual cues on focus for links or controls where color alone is used to identify them | No. Action: provide additional visual cues on focus for links. |
| Failures | |
| F73: Failure of Success Criterion 1.4.1 due to creating links that are not visually evident without color vision | No. Action: to add underline links when hovered upon. |
| 1.4.3 Contrast (Minimum) Level AA | |
| The visual presentation of text and images of text has a contrast ratio of at least 4.5:1 | |
| Sufficient Techniques | |
| Situation A: text is less than 18 point if not bold and less than 14 point if bold | |
| G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text | No. Action: to adjust contrast ratio between background of footer and footer contact details. |
| G148: Not specifying background color, not specifying text color, and not using technology features that change those defaults | No. Action: to remove text colour and background colour from the site. |
| G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast | No. Action: to make sure the contrast level is met for the footer links. |
| Situation B: text is at least 18 point if not bold and at least 14 point if bold | |
| G148: Not specifying background color, not specifying text color, and not using technology features that change those defaults | No. Action: to remove the text colour and to use underline to present an active link. |
| Advisory Techniques | |
| G156: Using a technology that has commonly-available user agents that can change the foreground and background of blocks of text | No. Action: to remove text and background colours. |
| Failures | |
| F24: Failure of Success Criterion 1.4.3, 1.4.6 and 1.4.8 due to specifying foreground colors without specifying background colors or vice versa | No. Action: to remove background and foreground colours. As only foreground colours have been set. |
| F83: Failure of Success Criterion 1.4.3 and 1.4.6 due to using background images that do not provide sufficient contrast with foreground text (or images of text) | No. Action: to adjust background images to provide sufficient contrast with foreground text. |
| 1.4.4 Resize text Level AA | |
| Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. | |
| Sufficient Techniques | |
| C28: Specifying the size of text containers using em units | No. Action: change links to em unit. |
| Techniques for relative measurements | |
| C12: Using percent for font sizes | No. Action: use percentage or em for font sizes. |
| C14: Using em units for font sizes | No. Action: to use either em or percentage for font sizes. |
| Techniques for text container resizing | |
| G178: Providing controls on the Web page that allow users to incrementally change the size of all text on the page up to 200 percent | No. Action: to add controls to web pages to resize text up to 200%. |
| Advisory Techniques | |
| C20: Using relative measurements to set column widths so that lines can average 80 characters or less when the browser is resized | No. Action: use max width for columns. |
| 1.4.5 Images of Text Level AA | |
| If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: | |
| Sufficient Techniques | |
| G140: Separating information and structure from presentation to enable different presentations | No. Action: to add named css classes to html to create semantic structure. |
| Advisory Techniques | |
| C12: Using percent for font sizes | No. Action: to use percent or em for font sizes. |
| C14: Using em units for font sizes | No. Action: To use percent or em for font sizes. |
| 1.4.10 Reflow Level AA | |
| Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for: | |
| Advisory Techniques | |
| C34: Using media queries to un-fixing sticky headers / footers | No. Action: remove sticky header from site. |
| C37: Using CSS max-width and height to fit images | No. Action: to add max-width and height to fit images. |
| Failures | |
| @@ Using fixed sized containers and fixed position content (CSS) | No. Action: to make fixed sized mobile menu used on site to be made flexible. |
| 1.4.11 Non-text Contrast Level AA | |
| The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s): | |
| Sufficient Techniques | |
| User Interface Component contrast | |
| G195: Using an author-supplied, highly visible focus indicator | No. Action: to exaggerate the display of the focus indicator. |
| Text in or over graphics | |
| G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text | No. Action: to ensure the contrast ratio is met for the footer text on the background image. |
| G145: Ensuring that a contrast ratio of at least 3:1 exists between text (and images of text) and background behind the text | No. Action: to ensure the contrast ratio is met for the footer text on the background image. |
| Advisory Techniques | |
| G183: Using a contrast ratio of 3:1 with surrounding text and providing additional visual cues on focus for links or controls where color alone is used to identify them | No. Action: to add additional visual cues on focus for different states of links. |
| 1.4.12 Text Spacing Level AA | |
| In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property: | |
| Advisory Techniques | |
| C21: Specifying line spacing in CSS | No. Action: to provide line spacing between 1.5 - 2 to help users to read content more easily. |
| 1.4.13 Content on Hover or Focus Level AA | |
| Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true: | |
| Failures | |
| @@ Failure to make content dismissable without moving pointer hover or keyboard focus | No. Action: to make links open up in new tabs instead of existing tabs. |
| Principle 2 – Operable | |
| User interface components and navigation must be operable. | |
| Guideline 2.4 – Navigable | |
| Provide ways to help users navigate, find content, and determine where they are. | |
| 2.4.1 Bypass Blocks Level A | |
| A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. | |
| Sufficient Techniques | |
| Creating links to skip blocks of repeated material using one of the following techniques: | No. Action: to create links to bypass header links and footer details. |
| G123: Adding a link at the beginning of a block of repeated content to go to the end of the block | No. Action: to add a link at the beginning of a block of repeated content to go to the end of the block. |
| Grouping blocks of repeated material in a way that can be skipped, using one of the following techniques: | |
| ARIA11: Using ARIA landmarks to identify regions of a page | No. Action: to use aria landmarks to identify regions of the page. |
| H69: Providing heading elements at the beginning of each section of content | No. Action: to provide heading elements at the beginning of each section of content. |
| SCR28: Using an expandable and collapsible menu to bypass block of content | No. Action: to use expandable and collapsible menu to bypass blocks of content. |
| Advisory Techniques | |
| for Success Criterion 2.4.1 C6: Positioning content based on structural markup A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. | No. Action: a mechanism needs to be created to bypass blocks of content which are repeated. |
| 2.4.3 Focus Order Level A | |
| If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. | |
| Sufficient Techniques for Success Criterion 2.4.3 | |
| Giving focus to elements in an order that follows sequences and relationships within the content using one of the following techniques: | |
| H4: Creating a logical tab order through links, form controls, and objects | No. Action: to provide a tab index to each link in a list of links. |
| C27: Making the DOM order match the visual order | No. Action: to provide a tab index to each element in the site. |
| 2.4.4 Link Purpose (In Context) Level A | |
| The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. | |
| Sufficient Techniques for Success Criterion 2.4.4 | |
| G91: Providing link text that describes the purpose of a link | No. Action: to change voog links to meaningful descriptions. |
| H24: Providing text alternatives for the area elements of image maps | No. Action: to provide alt text for area elements. |
| Allowing the user to choose short or long link text using one of the techniques below: | |
| G189: Providing a control near the beginning of the Web page that changes the link text | No. Action: to provide links to another version of the document. |
| SCR30: Using scripts to change the link text | No. Action: to provide long text names for alternate document versions. |
| G53: Identifying the purpose of a link using link text combined with the text of the enclosing sentence | No. Action: to give more meaningful names to links in sentences. |
| Providing a supplemental description of the purpose of a link using one of the following techniques: | |
| H33: Supplementing link text with the title attribute | No. Action: to provide title attributes to links. |
| C7: Using CSS to hide a portion of the link text | No. Action: to provide visually hidden links for accessibility. |
| Identifying the purpose of a link using link text combined with programmatically determined link context using one of the following techniques: | |
| ARIA7: Using aria-labelledby for link purpose | No. Action: to provide aria-labelled by for links. |
| ARIA8: Using aria-label for link purpose | No. Action: to provide aria-label for links. |
| H77: Identifying the purpose of a link using link text combined with its enclosing list item | No. Action: to provide link text for links in sentences. |
| H78: Identifying the purpose of a link using link text combined with its enclosing paragraph | No. Action: to provide link text with its enclosing paragraph. |
| H81: Identifying the purpose of a link in a nested list using link text combined with the parent list item under which the list is nested | No. Action: to provide link text with parent element text. |
| G91: Providing link text that describes the purpose of a link | No. Action: to change text of some of the links to provide a more meaningful description. |
| Advisory Techniques for Success Criterion 2.4.4 | |
| H80: Identifying the purpose of a link using link text combined with the preceding heading element | No. Action: to create link text including preceding heading element. |
| Failures for Success Criterion 2.4.4 | |
| F63: Failure of Success Criterion 2.4.4 due to providing link context only in content that is not related to the link | No. Action: to provide descriptive names for links. |
| 2.4.5 Multiple Ways Level AA | |
| More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process. | |
| Sufficient Techniques for Success Criterion 2.4.5 | |
| Using two or more of the following techniques: | |
| G63: Providing a site map | No. Action: a site map could be provided. |
| G161: Providing a search function to help users find content | No. Action: to provide a search function. |
| 2.4.6 Headings and Labels Level AA | |
| Headings and labels describe topic or purpose. | |
| Sufficient Techniques for Success Criterion 2.4.6 | |
| G130: Providing descriptive headings | No. Action: to provide more descriptive headings. |
| G131: Providing descriptive labels | No. Action: to provide descriptive labels. |
| 2.4.7 Focus Visible Level AA | |
| Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. | |
| Sufficient Techniques for Success Criterion 2.4.7 | |
| G149: Using user interface components that are highlighted by the user agent when they receive focus | No. Action: To provide highlighting to links when they receive focus. |
| C15: Using CSS to change the presentation of a user interface component when it receives focus | No. Action: to use css to change presentation of a link when it receives focus |
| G165: Using the default focus indicator for the platform so that high visibility default focus indicators will carry over | No. Action: to create a highly visible focus indicator |
| G195: Using an author-supplied, highly visible focus indicator | No. Action: to create a highly visible focus indicator |
| @@@ Using a change of contrast ratio to provide a visible focus indicator | No. Action: to use a high contrast ratio to create a highly visible focus indicator |
| Guideline 2.5 – Input Modalities | |
| Make it easier for users to operate functionality through various inputs beyond keyboard. | |
| 2.5.3 Label in Name Level A (Added in 2.1) | |
| For user interface components with labels that include text or images of text, the name contains the text that is presented visually. | |
| Sufficient Techniques for Success Criterion 2.5.3 | |
| G208: Including the text of the visible label as part of the accessible name | No. Action: to create a hidden accessible name for links. |
| G211: Matching the accessible name to the visible label | No. Action: to match accessible name to the visible label. |
| Failures for Success Criterion 2.5.3 | |
| F96: Failure due to the accessible name not containing the visible label text | No. Action: to create accessible names for links with visible label text. |
| @@ Accessible name contains the visible label text, but the words of the visible label are not in the same order as they are in the visible label text | No. Action: to create accessible names for links with visible label text in the same order. |
| @@ Accessible name contains the visible label text, but one or more other words are interspersed in the label | No. Action: to create accessible names for links with visible label text without interspersed words in the label. |
| Principle 3 – Understandable | |
| Information and the operation of the user interface must be understandable. | |
| Guideline 3.2 – Predictable | |
| Make Web pages appear and operate in predictable ways. | |
| 3.2.1 On Focus Level A | |
| When any user interface component receives focus, it does not initiate a change of context. | |
| Advisory Techniques for Success Criterion 3.2.1 | |
| G200: Opening new windows and tabs from a link only when necessary | No. Action: to make all links go to the same tab apart from external links. |
| G201: Giving users advanced warning when opening a new window | No. Action: an advanced warning should be created to let users know that they are being navigated away from the main content. |
| 3.2.4 Consistent Identification Level AA | |
| Components that have the same functionality within a set of Web pages are identified consistently. | |
| Sufficient Techniques for Success Criterion 3.2.4 | |
| G197: Using labels, names, and text alternatives consistently for content that has the same functionality | No. Action: to provide labels, names and text alternatives consistently throughout all pages. |
| Principle 4 – Robust | |
| Content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies. | |
| 4.1.2 Name, Role, Value Level A | |
| For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. | |
| Sufficient Techniques for Success Criterion 4.1.2 | |
| Situation A: If using a standard user interface component in a markup language (e.g., HTML): | |
| ARIA14: Using aria-label to provide an invisible label where a visible label cannot be used | No. Action: to provide aria-labels throughout the site. |
| ARIA16: Using aria-labelledby to provide a name for user interface controls | No. Action: to provide aria-labelledby throughout the site. |
| G108: Using markup features to expose the name and role, allow user-settable properties to be directly set, and provide notification of changes | No. Action: to expose the name and role and allow user-settable properties to be directly set. |
| Failures for Success Criterion 4.1.2 | |
| F68: Failure of Success Criterion 4.1.2 due to a user interface control not having a programmatically determined name | No. Action: to give user interface controls names. |
| F79: Failure of Success Criterion 4.1.2 due to the focus state of a user interface component not being programmatically determinable or no notification of change of focus state available | No. Action: to make the focus state of ui components determinable. |
Non compliance with the accessibility regulations
Aspects that do not meet WCAG 2.1 AA standards and WCAG A standards:
- Non text content does not have text alternatives
- Non text content isn’t ignored by assistive technology.
- Links of downloadable documents are missing descriptive terms.
- Keyboard navigation of site could be more efficient
- Navigation of the site could be easier using assistive technology by using code to identify key areas of the site.
- Lack of semantic meaning for content and content layout.
- Ungrouped lists of links prevents easy navigation through site
- Headings missing categorisation so that they are easily identifiable using a screen reader.
- Links when activated are missing state definition
- Poor visibility of some text on the website
- Users are unable to choose how they improve site visibility for themselves
- Some text is difficult to scale
- Mobile menu button is unscalable
- Line spacing in paragraphs of text is not within the required boundaries
- Users are navigated away from the site by links on the site
- No identification of repeated content so that it can be easily bypassed
- Missing detailed sequence in which links should be navigated on the site.
- No alternate versions of the same document via different extensions.
- Some descriptions of links to other documents are not detailed
- Not enough information to identify links on the website for screen readers.
- Missing site map
- Missing search functionality
- Users aren't alerted when they are being navigated away from the site
The aspects mentioned above fail to meet success criterions:
- 1.1.1 Non-text Content, Level A
- 1.3.1 Info and Relationships, Level A
- 1.3.2 Meaningful Sequence, Level A
- 1.3.3 Sensory Characteristics, Level A
- 1.4.1 Use of Colour, Level A
- 1.4.3 Contrast (Minimum), Level AA
- 1.4.4 Resize text, Level AA
- 1.4.5 Images of Text Level AA
- 1.4.10 Reflow, Level AA
- 1.4.11 Non-text Contrast, Level AA
- 1.4.12 Text Spacing, Level AA
- 1.4.13 Content on Hover or Focus, Level AA
- 2.4.1 Bypass Blocks, Level A
- 2.4.3 Focus Order, Level A
- 2.4.4 Link Purpose (In Context), Level A
- 2.4.5 Multiple Ways, Level AA
- 2.4.6 Headings and Labels, Level AA
- 2.4.7 Focus Visible, Level AA
- 2.5.3 Label in Name, Level A
- 3.2.1 On Focus, Level A
- 3.2.4 Consistent Identification, Level AA
- 4.1.2 Name, Role, Value, Level A
We plan to fix these issues next year around 1st November 2021.