Accessibility statement for AfC Info
This accessibility statement applies to the Achieving for Children website for Kingston and Richmond, at http://kr.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 colours, contrast levels and fonts.
- 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.
- listen to 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
- Some third-party plugins such as Google Maps, Google Captcha, Google translate and YouTube iframes
Feedback and contact information
- email email@example.com
- call 020 8547 4722
Reporting accessibility problems with this website
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, contact us on the details above.
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).
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.
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
We have done everything within our power to make the website comply but some third-party plugins such as Google Maps, Google Recaptcha, Google translate and YouTube video embeds that are used on this website do not meet WCAG 2.1 success criterion 4.1.1 (parsing) and / or success criterion 4.1.2 (name, role, value) and must be resolved by said third parties. As such, we cannot be sure when these issues will be resolved.
As some of the content does not contain image alt tags, 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 aim to fix this by 23 Sep 2020.
Content that’s not within the scope of the accessibility regulations
PDFs and other documents: some of our PDFs and Word documents may be essential to providing our services.
For example we may 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 are not essential to providing our services.
For example, we do not plan to fix ‘Protecting your GP online record PDF’ https://www.england.nhs.uk/wp-content/uploads/2017/09/protecting-your-gp-online-record.pdf
Any new PDFs or Word documents we publish will meet accessibility standards.
Live video: we do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.
What we’re doing to improve accessibility
Preparation of this accessibility statement
This statement was prepared on 28th August 2020. It was last reviewed on 28th August 2020.
The test was carried out by This is Focus Limited, using https://alphagov.github.io/wcag-primer/checklist.html#checklist and the ARC Toolkit. We used this approach to test a sample of key pages, actions and user journeys against the above checklist.
View the full report.