Accessibility statement for rbwm.afcinfo.org.uk

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

  • Change the website's text size.

  • Change the contrast / colours of the website.

  • Find content in two or more ways.

  • Control distracting flickering or movement.

  • Navigate most of the website using just a keyboard.

  • Access the content in a logical order even if styling is removed.

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 aren’t fully accessible:

  • Not all images have an appropriate text equivalent and some essential visual information may not be available as text. 

  • Some information may be communicated using visual characteristics. 

  • Not all text has sufficient contrast against the background colour. 

  • HTML autocomplete tokens may not be added to all forms collecting information about the user. 

  • Not all important graphical objects, interface components, and states have a colour contrast of 3:1. 

  • Not all menus, links, buttons, and other controls can be operated by keyboard. 

  • Not all content that moves or auto updates can be stopped. 

  • Not all blocks of links and other interactive elements can be bypassed by keyboard users. 

  • The purpose of every link may not clear from its link text. 

  • Some features with the same functionality are not labelled consistently. 

  • Not all web pages are coded using valid HTML. We make every effort minimise invalid markup, however 100% validated HTML is challenging to achieve. 

  • Not all interactive components have an accessible name, role or state (when required). Some incorrect ARIA markup may be present and may not validate. 

  • Not all status messages and updates are given appropriate roles that can be understood by AT, without receiving focus. 

What to do if you can’t 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’ll consider your request and get back to you in [7] days.

 

Reporting accessibility problems with this website

We’re always looking to improve the accessibility of this website. If you find any problems that aren’t listed on this page or think we’re not meeting accessibility requirements, contact: [local.offer@achievingforchildren.org.uk].

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

Contacting us by phone or visiting us in person

We provide a text relay service for people who are D/deaf, hearing impaired or have a speech impediment.

Our offices have audio induction loops, or if you contact us before your visit we can arrange a British Sign Language (BSL) interpreter.

Find out how to contact us: https://rbwm.afcinfo.org.uk/enquiries/new

Technical information about this website’s accessibility

Achieving for Children is committed to making its website 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, due to the non-compliances listed below.

Non accessible content

The content listed below is non-accessible for the following reasons.

Non compliance with the accessibility regulations

Not all images have an appropriate text equivalent and some essential visual information may not be available as text. This doesn’t meet 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.

Some information may be communicated using visual characteristics. This doesn’t meet WCAG 2.1 success criterion 1.3.3 (sensory characteristics).

We plan to make sure information is not communicated using only visual characteristics by September 2020. When we publish new content we’ll make sure use of visual characteristics meets accessibility standards.

 

Not all text has sufficient contrast against the background colour. This doesn’t meet WCAG 2.1 success criterion 1.4.3 (contrast [minimum]).

We plan to make sure all text has sufficient contrast against the background colour by September 2020. When we publish new content we’ll make sure use of text on background colours meets accessibility standards.

 

HTML autocomplete tokens may not be added to all forms collecting information about the user. This doesn’t meet WCAG 2.1 success criterion 1.3.5 (identify input purpose).

We plan to add missing HTML autocomplete tokens by September 2020. When we publish new content we’ll make sure use of HTML autocomplete tokens meets accessibility standards.

 

Not all important graphical objects, interface components, and states have a colour contrast of 3:1. This doesn’t meet WCAG 2.1 success criterion 1.4.11 (non-text contrast).

We plan to make sure all important graphical objects, interface components, and states have a colour contrast of 3:1 by September 2020. When we publish new content we’ll make sure use of non-text contrast meets accessibility standards.

 

Not all menus, links, buttons, and other controls can be operated by keyboard. This doesn’t meet WCAG 2.1 success criterion 2.1.3 (keyboard [no exception]).  

We plan to make sure menus, links, buttons, and other controls can be operated by keyboard by September 2020. When we publish new content we’ll make sure use of keyboard control meets accessibility standards.

 

Not all content that moves or auto updates can be stopped. This doesn’t meet WCAG 2.1 success criterion 2.2.2 (pause, stop, hide).

We plan to make sure content that moves or auto updates can be stopped, by September 2020. When we publish new content we’ll make sure content that moves or auto updates meets accessibility standards.

 

Not all blocks of links and other interactive elements can be bypassed by keyboard users. This doesn’t meet WCAG 2.1 success criterion 2.4.1 (bypass blocks).

We plan to make sure blocks of links and other interactive elements can be bypassed by keyboard users by September 2020. When we publish new content we’ll make sure use of keyboard control and bypassing meets accessibility standards.

 

The purpose of every link may not clear from its link text. This doesn’t meet WCAG 2.1 success criterion 2.4.4 (link purpose [in context]).

We plan to make sure the purpose of all links are clear from their link text by September 2020. When we publish new content we’ll make sure the purpose of all links meets accessibility standards.

 

Some features with the same functionality are not labelled consistently. This doesn’t meet WCAG 2.1 success criterion 3.2.4 (consistent identification).

We plan to make sure features with the same functionality are labelled consistently by September 2020. When we publish new content we’ll make sure features with the same functionality meet accessibility standards.

 

Not all web pages are coded using valid HTML. We make every effort minimise invalid markup, however 100% validated HTML is challenging to achieve. This doesn’t meet WCAG 2.1 success criterion 4.1.1 (parsing).

We plan to work towards having 100% validated HTML by September 2020. When we publish new content we’ll work hard to meet validated HTML accessibility standards.

 

Not all interactive components have an accessible name, role or state (when required). Some incorrect ARIA markup may be present and may not validate. This doesn’t meet WCAG 2.1 success criterion 4.1.2 (name, role, value).

We plan to make sure interactive components have an accessible name, role or state (when required) by September 2020. When we publish new content we’ll make sure interactive components meet accessibility standards.

 

Not all status messages and updates are given appropriate roles that can be understood by AT, without receiving focus. This doesn’t meet WCAG 2.1 success criterion 4.1.3 (status messages).

We plan to make sure status messages and updates are given appropriate roles that can be understood by AT, without receiving focus, by September 2020. When we publish new content we’ll make sure status messages and updates meet accessibility standards.

 

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

PDFs and other documents

Many of our older PDFs and Word documents don’t meet accessibility standards - for example, they may not be structured so they’re accessible to a screen reader. This doesn’t 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 don’t require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services. Any new PDFs or Word documents we publish will meet accessibility standards.

How we tested this website

This website was last tested on 13th September 2019. The test was carried out by This is Focus Limited, using https://alphagov.github.io/wcag-primer/checklist.html#checklist

We highlighted key pages, actions and user journeys to test as a sample against the above checklist.

This is the testing report: https://docs.google.com/spreadsheets/d/1-Ow_bhEb4tmXMa3OYq9gYBl4CRP4vTpCKfNAcfoXDA0/edit?usp=sharing

We tested our main website platform, available at https://rbwm.afcinfo.org.uk/

What we’re doing to improve accessibility

We recognise there is room for improvement, particularly in the following areas: Content and functionality from third parties. We monitor other websites to assess best practice for website accessibility on an ongoing basis and we work with external vendors to ensure the solutions they provide us with are as accessible as possible.    If you would like to provide feedback about the accessibility of the website then please contact us using our online form: https://rbwm.afcinfo.org.uk/enquiries/new.

​Developments to the website in line with user feedback about accessibility will be evaluated in line with what is likely to make the largest impact to our users and the cost of achieving these objectives.

This statement was prepared on 16th September 2019. It was last updated on 27th September 2019.