Accessibility Statement

Here at the Camden Children’s Safeguarding and Social Work Portal (CCSSWP) , we aim to make our website accessible to the widest audience possible and to comply with UK government accessibility guidelines.

This website is run by Camden Council. 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.
● Not all visually communicated content structure is available to assistive technologies. 
● The content may not always be in a logical order when the styling is removed. 
● There may be some images of text used. 
● HTML autocomplete tokens may not be added to all forms collecting information about the user. 
● Where extra content is shown or hidden on focus, it may not be dismissed, interacted with (or may disappear when the user moves to it) and may not stay visible until dismissed by the user. 
● Not every page has a unique title that indicates its purpose and context. 
● When using a keyboard to move through a page the order may not make sense. 
● When using a keyboard to move through a page you may not always be able to tell where you are. 
● Not all web pages are coded using valid HTML. We make every effort to minimise invalid markup, however 100% validated HTML is challenging to achieve.
● 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:
You can contact us via the website; https://www.camden.gov.uk/report-an-accessibility-issue 
Thank you for your feedback we will consider your request. The feedback has been sent to our information access team who will help us improve our online services. 


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:
 https://www.camden.gov.uk/report-an-accessibility-issue 
Thank you for your feedback we will consider your request. The feedback has been sent to our information access team who will help us improve our online services 
We are continually working to make improvements to this website and plan to work with residents and external agencies for testing in the future.


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


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: call 020 7974 4444


Technical information about this website’s accessibility


Camden Council 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.


Not all visually communicated content structure is available to assistive technologies. This doesn’t meet WCAG 2.1 success criterion 1.3.1 (information and relationships).


We plan to make visually communicated content structure available to assistive technologies by September 2020. When we publish new content we’ll make sure our use of visually communicated content meets accessibility standards.


The content may not always be in a logical order when the styling is removed. This doesn’t meet WCAG 2.1 success criterion 1.3.2 (meaningful sequence).


We plan to make content follow a logical order when styling is removed by September 2020. When we publish new content we’ll make sure our use of content following a logical order when styling is removed meets accessibility standards.


There may be some images of text used. This doesn’t meet WCAG 2.1 success criterion 1.4.5 (images of text).


We plan to replaces images of text, with text, by September 2020. When we publish new content we’ll make sure our use of images of text 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.


Where extra content is shown or hidden on focus, it may not be dismissed, interacted with (or may disappear when the user moves to it) and may not stay visible until dismissed by the user. This doesn’t meet WCAG 2.1 success criterion 1.4.13 (content on hover or focus).


We plan to ensure content on hover or focus stays visible and can be dismissed by September 2020. When we publish new content we’ll make sure use content on hover or focus meets accessibility standards.
Not every page has a unique title that indicates its purpose and context. This doesn’t meet WCAG 2.1 success criterion 2.4.2 (page titled).


We plan to make sure every page has a unique title that indicates its purpose and context by September 2020. When we publish new content we’ll make sure use of unique page titles meets accessibility standards.


When using a keyboard to move through a page the order may not make sense. This doesn’t meet WCAG 2.1 success criterion 2.4.3 (focus order).


We plan to make sure when using a keyboard to move through a page in order makes sense by September 2020. When we publish new content we’ll make sure use of keyboard control order meets accessibility standards.


When using a keyboard to move through a page you may not always be able to tell where you are. This doesn’t meet WCAG 2.1 success criterion 2.4.7 (focus visible).


We plan to make sure when using a keyboard to move through a page makes sense by September 2020. When we publish new content we’ll make sure use of keyboard control meets 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 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 I have 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.


Disproportionate burden


We’ve assessed the cost of fixing the issues with navigation and accessing information, and with interactive tools and transactions. We believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations, however we will make a web analytics assessment on 18th September 2020.


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/1i5Ge9pi62vupqFzt71IUNHO1RQYKXFs35PGFKzNG2Vg/edit?usp=sharing
We tested our main website platform, available at https://www.camdenchildrenssocialwork.info/
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 by email info@camden.gov.uk or call 020 7974 4444.


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 4th December 2019.

XHTML and CSS

This website has been built using web standard XHTML and CSS. If CSS is turned off then the website remains functional and all content can still be accessed.

JavaScript

We have used JavaScript on some areas of our website to add interactivity and to enhance the experience for all users. Where JavaScript isn’t available, we have implemented graceful degradation to ensure a lack of JavaScript doesn’t break the site or block access to content.

Website Evaluation

The accessibility of our website has been evaluated using the Web Accessibility Evaluation Tool (WAVE) powered by WebAim:
http://wave.webaim.org this is a technical evaluation of the website against guidelines rather than an assessment of usability.

Images and ALT tags

We add ALT tags to images where an image conveys essential information, and endeavour to convey that same information using the ALT tag. We do not add ALT attributes to decorative images as we feel this information is excessive rather than useful and can hinder the operation of screen readers attempting to provide important content to website users.

Features that enhance website accessibility

We provide content in a variety of different formats in order to make it as accessible as possible, including: High colour contrast between background colours and text to help users who may have visual impairments. A text-only version of website content that removes all images, colour and styling and can be easily read by screen readers. Clear links to change the size of text used throughout the website. Automatic translation of website content into other languages.

Room for improvement

We recognise there in 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.   ​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.