Accessibility statement

 

Accessibility statement for Brotathan

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

  • zoom in up to 300% without the text spilling off the screen

  • navigate most of the website using just a keyboard

  • navigate most of the website using speech recognition software

  • use most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We’ve also made the website text as simple as possible to understand.

AbilityNet has advice on making your device easier to use if you have a disability.

How accessible this website is

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

  • the text will not reflow in a single column when you change the size of the browser window

  • you cannot modify the line height or spacing of text

  • most older PDF documents are not fully accessible to screen reader software

  • live video streams do not have captions

  • some of our online forms are difficult to navigate using just a keyboard

  • you cannot skip to the main content when using a screen reader

What to do if you cannot access parts of this website

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:

We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements.

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


Technical information about this website’s accessibility

The Government Digital Service is committed to making its websites accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard.

accessible content

The content that is not accessible is outlined below with details of:

  •  where it fails the success criteria

  • planned dates for when issues will be fixed

Non compliance with the accessibility regulations

Some images do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).

We plan to add text alternatives for all images by September 2020. When we publish new content we’ll make sure our use of images meets accessibility standards.

Disproportionate burden

Not applicable

Navigation and accessing information

There’s no way to skip the repeated content in the page header (for example, a ‘skip to main content’ option). This fails WCAG 2.1 success criterion 2.4.1 (bypass blocks).

It’s not always possible to change the device orientation from horizontal to vertical without making it more difficult to view the content. This fails WCAG 2.1 success criterion 1.3.4 (orientation).

It’s not possible for users to change text size without some of the content overlapping. This fails WCAG 2.1 success criterion 1.4.4 (resize text).

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

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

Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access our services, and forms published as Word documents. By September 2020, we plan to either fix these or replace them with accessible HTML pages.

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 [example of non-essential document].

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

Live video

Live video streams do not have captions. This fails WCAG 2.1 success criterion 1.2.4 (captions - live).

We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.

How we tested this website

This website was and is currently being tested for compliance with the Web Content Accessibility Guidelines V2.1 level A and level AA, and these tests have been carried out internally.

We used the Website Accessibility Conformance Evaluation Methodology (WCAG-EM) approach to deciding on a sample of pages to test.

What we’re doing to improve accessibility

We plan to identify and fix issues according to the timescales shown for each area above.

This statement was prepared on 14 February 2020. It was last updated on 14 February 2020.