Accessibility

Accessibility options


Accessibility statement for Surrey County Council

This accessibility statement applies to surreycc.gov.uk

This website is run by Surrey County Council. We are committed to providing an accessible website that is easy to use by anyone, whatever their age, background, access device or level of ability/disability.

This means that:

  • Our pages are written to be clear and easy to understand.
  • The website is organised so you can find what you need.

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 aim to meet the AA level of the Web Content Accessibility Guidelines (WCAG). This is the international standard for accessible websites and content.

How accessible is this website?

Most of our website should be accessible. It should work well when used with access devices such as screen readers, braille readers, as well as smart phones and other devices.

These are the internet browsers that we support on our website.

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

We know some content on this website is not fully accessible and this includes:

  • Most older PDF documents. These are not fully accessible to screen reader software.
  • Live video streams. These do not have captions.
  • Some page content.
  • Some PDF and other document content.

A detailed list of known accessibility issues and how we plan to address them is available further down this statement. We regularly review the site and add further issues to this statement as they are identified.

Reporting accessibility problems with this website

If you need information in a different format to the one that we provide, please email us at contact.centre@surreycc.gov.uk.

If you have difficulty using any part of our website, email us at contact.centre@surreycc.gov.uk and mark your email for the attention of the Web and Digital Services team.

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 about the accessibility of our website, you can contact the Equality Advisory and Support Service (EASS).

Technical information about this website's accessibility

Surrey County 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

HTML is used to format some content.

This fails WCAG 2.1 level A success criterion 1.3.1 (info and relationships). We are working to correct this.

Some element IDs are not unique.

This fails WCAG 2.1 level A success criteria 1.3.1 (info and relationships) and 4.1.1 (parsing). We are working to correct this.

Visible label and accessible name do not match

The links in the navigation crumb trail of some pages, do not match the labels for those links. This may make these links harder to correctly identify and activate for people using assistive technology. This fails WCAG 2.1 level A success criterion 2.5.3 (label in name). We are working to correct this.

Link without a text alternative

Links in the footer of our 'search for a job pages' for Arabic, Urdu, Bengali and Chinese language contact details do not have text alternatives. This fails WCAG 2.1 level A success criteria 2.4.4 (link Purpose - In Context) and 4.1.2 (Name, Role, Value). We are working to correct this.

Text is clipped when resized

The text 'follow us on social media' in the footer of our 'search for a job pages' can be clipped if the page is magnified. This fails WCAG 2.1 level AA criterion 1.4.4 (resize text). We are working to correct this.

Container element is empty

On some category landing pages, there is an empty container element on tiles that contain paragraph text rather than lists. This can be confusing for people using screen readers. This fails WCAG 2.1 level A success criterion 1.3.1 (info and relationships). We are working to address this.

Video captions

Some video captions are auto-generated and are not always accurate. This fails WCAG 2.1 level A success criterion 1.2.2 (captions (pre-recorded)).

PDFs and other documents

Some PDFs and documents may not meet accessibility standards. For example, they may not be structured so they're accessible to a screen reader. This fails WCAG 2.1 level A success criterion 4.1.2 (name, role value).

Currently, all documents are checked with an automated test before being published on the site. This eliminates many common accessibility errors but does not guarantee that documents will be fully accessible.

We manually check and fix:

  • the most-viewed documents (currently, approximately the top 10%).
  • documents that are essential for using our services.
  • documents intended for audiences likely to have accessibility needs.

These documents should be fully accessible.

If you are unable to read a document on our site, please contact us and we will help you. Email us at contact.centre@surreycc.gov.uk and mark your email for the Web and Digital Services team's attention.

See the section on disproportionate burden for further details.

Bus timetables

Our bus timetables are provided as PDFs and will be difficult to read using assistive technology such as screen readers. They fail WCAG 2.1 level A success criteria, 1.3.1 (information and relationships), 1.3.2 (meaningful sequence), 2.4.2 (page titled) and 2.4.3 (focus order). We are working with the supplier of the timetables and expect to provide more accessible timetables this year (2022).

Images

Some of our pages and documents contain complex images such as diagrams, charts, graphs or infographics. Some of these may not be adequately described. This fails WCAG 2.1 level A success criterion 1.1.1 (Non-text Content). We are working to correct this.

Legal and financial documents

Some legal and financial documents on our site are provided as records of the original documents and may not be fully accessible. For example, they may not be structured so they're accessible to a screen reader. This does not meet WCAG 2.1 level A success criterion 4.1.2 (name, role value). Please contact us for accessible alternatives.

Draft statement of accounts 2021 to 2022

This PDF may be difficult to read using assistive technology such as screen readers. This fails WCAG 2.1 level A success criteria 1.1.1 (Non-text content), 1.3.1 (information and relationships), 1.3.2 (meaningful sequence), 2.4.3 (focus order), 4.1.2 (name, role value). We are working to correct this.

Statement of accounts pre-2021

Some tables in our statements of accounts prior to 2021, may be difficult to read using assistive technology such as screen readers. They may fail WCAG 2.1 level A success criteria 1.3.1 (information and relationships), 1.3.2 (meaningful sequence). We are investigating how to correct this.

What can I recycle?

Some of the content within our 'what can I recycle?' tool may be difficult to use with some accessibility software. This may fail WCAG 2.1 level success criteria 2.1.1 (keyboard). We are currently investigating how to improve this.

Fair cost of care exercise – SCC supplementary questions for homecare providers

This Excel spreadsheet may be difficult for some people to view and complete, particularly if using accessibility software such as a screen reader. We are currently assessing the file and investigating how to improve it. In the meantime, please contact us at asc.fcofc@surreycc.gov.uk if you need help viewing or using the file.

SCC identity: register or sign in page

The visible label of 'Email' which is not programmatically associated with the relevant form field. This fails WCAG criteria 1.3.1 (Info and relationships). We are working to correct this.

There is a link with the text 'Create an account' and a button with the text 'Sign in' which are styled to look the same. This fails WCAG criteria 1.3.1 (Info and relationships). We are working to correct this.

Autocomplete is set to off on the email and password form fields. This fails WCAG criteria 1.3.5 (Identify input purpose). We are working to correct this.

When the 'Sign in' button gets keyboard focus the text does not have sufficient contrast with the background colour. This fails WCAG criteria 1.4.3 (contrast, minimum). We are working to correct this.

When the 'Create an account' link gets keyboard focus, the white arrow does not have sufficient contrast with the background. This fails WCAG criteria 1.4.11 (non-text contrast). We are working to correct this.

The 'Skip to content' link doesn't take the user's keyboard focus to the main content. This fails WCAG criteria 2.4.1 (bypass blocks). We are working to correct this.

The <html> element does not have a lang attribute. This fails WCAG criteria 3.1.1 (language of page). We are working to correct this.

The error message displayed after submitting the login form without entering information into the form fields does not correctly reflect the name of the fields. This fails WCAG criteria 3.3.1 (error identification). We are working to correct this.

Screen readers do not announce the current status after toggling the 'show password' and 'hide password' button. This fails WCAG criteria 4.1.2 (name, role ,value). We are working to correct this.

SCC identity: create an account page

The visible label of 'Title' is not programmatically associated with the relevant form field. This fails WCAG criteria 1.3.1 (Info and relationships). We are working to correct this.

The form fields collect information about the user but do not specify what autocomplete values to use., and the 'Confirm email' form field has the autocomplete value set to off. This fails WCAG criteria 1.3.5 (Identify input purpose). We are working to correct this.

The contrast between the blue link text and the grey non-link text is not sufficient to differentiate links from text. This fails WCAG criteria 1.4.1 (use of colour). We are working to correct this.

The text on the 'create an account' button does not have sufficient contrast with the background colour. The form fields with grey placeholder text do not have sufficient contrast with their background colours. This fails WCAG criteria 1.4.3 (contrast, minimum). We are working to correct this.

On the 'Create an account' page, the only way to bypass the header and navigation is to use headings. As all the headings on the page use a <h1> tag it is unclear where the main content starts. This fails WCAG criteria 2.4.1 (bypass blocks). We are working to correct this.

The page title doesn't inform the user which website the user is on. This fails WCAG criteria 2.4.2 (page titled). We are working to correct this.

The visible label of the ''I have read, understand and agree to the use of my personal information as described in Surrey County Council's Privacy Policy and agree to Surrey County Council's general Terms and Conditions of use of this website.' checkbox is not included in the accessible name. This fails WCAG criteria 2.5.5 (label in name). We are working to correct this.

When viewing the page at 200% and 400% and navigating the page using only a keyboard, the focus styling of the burger icon is not obvious. This fails WCAG criteria 2.4.7 (focus visible). We are working to correct this.

The <html> element does not have a lang attribute. This fails WCAG criteria 3.1.1 (language of page). We are working to correct this.

This title form field is mandatory but there is no label or instruction to indicate this. This fails WCAG criteria 3.3.2 (labels or instructions). We are working to correct this.

There is no accessible name on the hamburger icon button. When opening and closing the burger menu, screen readers do not announce the status update. This fails WCAG criteria 4.1.2 (name, role value). We are working to correct this.

SCC identity: we have sent you a text message page

There is a link with the text 'Resend Code' and a button with the text 'Confirm and Sign in' which are styled to look the same. This fails WCAG criteria 1.3.1 (Info and relationships). We are working to correct this.

The 'Skip to content' link doesn't take the user to the main content. This fails WCAG criteria 2.4.1 (bypass blocks). We are working to correct this.

The <html> element does not have a lang attribute. This fails WCAG criteria 3.1.1 (language of page). We are working to correct this.

SCC identity: completing your account setup page

The 'Skip to content' link doesn't take the user to the main content. This fails WCAG criteria 2.4.1 (bypass blocks). We are working to correct this.

The <html> element does not have a lang attribute. This fails WCAG criteria 3.1.1 (language of page). We are working to correct this.

Error messages displayed after clicking submit are not announced to screen reader users. This fails WCAG criteria 4.1.3 (status message). We are working to correct this.

All van permit application pages

Page titles within the van permit application process do not accurately reflect the content of the pages. This fails WCAG criteria 2.4.2 (page titled). We plan to correct this by October 2022.

Van permit terms and conditions page

The link 'Apply for a van and trailer permit' doesn't look like a link. This fails WCAG criteria 1.3.1 (Info and relationships). We plan to correct this by October 2022.

Some of the content is not contained in semantic text markup. This fails WCAG criteria 1.3.1 (Info and relationships). We plan to correct this by October 2022.

The contrast between the blue link text and the grey non-link text is not sufficient to differentiate links from text. This fails WCAG criteria 1.4.1 (use of colour). We plan to correct this by October 2022.

There is insufficient contrast between the blue text 'Send to a friend' and 'Top' and the background colour. There is insufficient contrast between the white text 'rate this page' and 'confirm' and the green background. When the 'Sign in' button gets keyboard focus the text does not have sufficient contrast with the background colour. This fails WCAG criteria 1.4.3 (contrast, minimum). We plan to correct this by October 2022.

When receiving keyboard focus the search and headphone icons do not have sufficient contrast with the background. This fails WCAG criteria 1.4.11 (non-text contrast). We plan to correct this by October 2022.

The page times out after a short period of time without warning the user or allowing the user to turn off, adjust or extend the timeout. This fails WCAG criteria 2.2.1 (timing adjustable). We plan to correct this by October 2022.

There is no way to bypass the header content. This fails WCAG criteria 2.4.1 (bypass blocks). We plan to correct this by October 2022.

When using the keyboard to navigate, the tab order of the page is unpredictable. This fails WCAG criteria 2.4.3 (focus order). We plan to correct this by October 2022.

The accessible name of the headphones link in the header is not meaningful. This fails WCAG criteria 2.4.6 (headings and labels). We plan to correct this by October 2022.

The focus styling on the feedback button is barely visible. This fails WCAG criteria 2.4.7 (focus visible). We plan to correct this by October 2022.

The page reloads but no error message is displayed when submitting the form without checking the 'I have read, understand and agree to the use of my personal information' checkbox. This fails WCAG criteria 3.3.1 (error identification). We plan to correct this by October 2022.

Van permit: application form

The radio buttons for 'Permit for hire vehicle' and 'Permit for personal vehicle' have a visible question of 'Choose a vehicle permit type'. The question is not programmatically associated to the radio buttons. This fails WCAG criteria 1.3.1 (Info and relationships). We plan to correct this by October 2022.

The form fields collect information about the user but do not specify what autocomplete values to use. This fails WCAG criteria 1.3.5 (Identify input purpose). We plan to correct this by October 2022.

There is insufficient contrast between the blue text 'Send to a friend' and 'Top' and the background colour. There is insufficient contrast between the white text 'rate this page', 'Find address' and 'Submit' and the background colour. There is insufficient contrast between text and background colours when hovering over links in the A to Z and links in the footer. There is insufficient contrast between grey placeholder text in form fields and the background colour. This fails WCAG criteria 1.4.3 (contrast, minimum). We plan to correct this by October 2022.

There is no way to bypass the header content. This fails WCAG criteria 2.4.1 (bypass blocks). We plan to correct this by October 2022.

The visible label 'Feedback' is not included in the accessible name 'Please rate this page'. This fails WCAG criteria 2.5.3 (label in name). We plan to correct this by October 2022.

Adult Learning page

The link with the text 'Advanced search' and the button with the text 'Search' are styled to look the same. This fails WCAG criteria 1.3.1 (Info and relationships). We are working to correct this.

When opening and closing the burger menu, screen readers do not announce the status update. This fails WCAG criteria 4.1.2 (name, role value). We are working to correct this.

Jobs page

When clicking on the 'Skip to content' link if, using only a keyboard focus is taken to the 'Find out more' link and bypasses the job search bar. This fails WCAG criteria 2.4.1 (bypass blocks). We plan to correct this by October 2022.

Surrey Matters page

There is no focus styling on the banner link. This fails WCAG criteria 2.4.7 (focus visible). We plan to correct this by October 2022.

There are six instances of <p> tags nested inside <span> tags. This fails WCAG criteria 4.1.1 (parsing). We plan to correct this by October 2022.

Schools admissions page

When tabbing down the page the 'Chat with me' button gets keyboard focus when tabbing between the links 'Directory of Surrey schools' and 'Late primary, infant or junior applications'. This fails WCAG criteria 2.4.3 (focus order). We are working to correct this.

Apply for a place at primary, infant or junior school page

When viewing the page at 400%, it is not possible to view all the content in the table. This fails WCAG criteria 1.4.3 (contrast, minimum).

Category landing pages (such as Libraries, School admissions, and Waste and Recycling)

Where boxes with links appear side by side with boxes with non-link text it is hard to identify the links as colour alone is used to distinguish the links. This fails WCAG criteria 1.4.1 (use of colour). We plan to correct this by October 2022.

All pages: Feedback button/pop-up

When viewing the page at 400%, the 'Don't show again' button is not visible and cannot be accessed. This fails WCAG criteria 1.4.10 (reflow). We are discussing this issue with our supplier.

No error messages are displayed when submitting the form without entering any information into the form fields. This fails WCAG criteria 3.3.1 (error identification). We are discussing this issue with our supplier.

The button (<button>) element contains multiple div (<div>) elements inside of it. This fails WCAG criteria 4.1.1 (parsing). We are discussing this issue with our supplier.

All pages on www.surreycc.gov.uk

There is a style (<style>) element within the main body content. This fails WCAG criteria 4.1.1 (parsing). We plan to correct this by October 2022.

All pages with drop-down menus in the navigation

It is not possible to dismiss the main dropdown navigation when you hover over it. This fails WCAG criteria 1.4.13 (content on hover or focus). We are investigating this issue.

It is not possible to interact with any of the dropdown navigations when using only a keyboard. This fails WCAG criteria 2.1.1 (keyboard). We plan to correct this by October 2022.

Search page

When viewing the page at 200% and 400% zoom, the filter changes into a dropdown which cannot be accessed when using only a keyboard. This fails WCAG criteria 2.1.1 (keyboard). We are discussing this issue with our supplier.

After tabbing down the search results the 'search more' button can only be reached by tabbing through all the filters and search help content first. This fails WCAG criteria 2.4.3 (focus order). We are discussing this issue with our supplier.

Keyboard focus becomes lost for around 5 keyboard tabs after tabbing away from the last search result item and before tabbing to filters and search help content. This fails WCAG criteria 2.4.7 (focus visible). We are discussing this issue with our supplier.

Registering a birth: appointment bookings

The label for the terms and conditions checkbox does not have full context. Users may not understand what they are confirming. This fails WCAG A criterion 3.3.2 (labels or instructions). Our supplier is working to correct this by 29 August 2022.

The labels for form fields are not sufficiently contextual. This may present a barrier for some users. This fails WCAG A criterion 3.3.2 (labels or instructions). Our supplier is working to correct this by 29 August 2022.

H1 headings are not sufficiently distinct. Users may not understand where they are in the journey. This fails WCAG AA criterion 2.4.6 (headings and labels). Our supplier is working to correct this by 29 August 2022.

The label for confirming details check box does not have full context. Users may not understand what they are confirming. This fails WCAG A criterion 3.3.2 (labels or instructions). Our supplier is working to correct this by 29 August 2022.

Radio button focus is not set correctly. This fails WCAG A criterion 2.4.7 (focus visible). Our supplier is working to correct this by 29 August 2022.

There is inconsistent wording on page and form fields. This may make it difficult for users to correctly complete the form. This fails WCAG A criterion 3.3.2 (labels or instructions). Our supplier is working to correct this by 29 August 2022.

Tabbing between radio buttons, the read description is not sufficient and may cause confusion for users. This fails WCAG A criterion 3.3.2 (labels or instructions). Our supplier is working to correct this by 29 August 2022.

Disproportionate burden

The accessibility regulations do not require us to fix accessibility issues if doing so would be a disproportionate burden (where fixing an issue would cost a lot but provide minimal or no benefit and would affect our ability to provide our services).

PDFs and other documents

We've assessed that it would be a disproportionate burden to make all PDFs and documents published on our websites fully accessible.

Most of our documents are rarely viewed (in many cases, less than 50 times a year from a population of 1.1 million people) and so users with disabilities or impairments are unlikely to be negatively impacted. For this reason, we don't believe the cost to fully fix all documents is justified.

For the majority of our documents, we have committed to ensuring they pass an automated accessibility check. This will eliminate many common accessibility issues but will not necessarily ensure that the document is fully accessible.

For our most-viewed documents (approximately, the top 10%), documents that are essential for using our services, and documents intended for audience likely to have accessibility needs, we are committed to manually checking them and making sure they are fully accessible.

If you are unable to read a document on our site, please contact us and we will help you. Email us at contact.centre@surreycc.gov.uk and mark your email for the Web and Digital Services team's attention.

We will continue to investigate cost-effective ways of improving the accessibility of all our documents.

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

PDFs and other documents

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.

The accessibility regulations also do not require us to fix PDFs or other documents provided by third-parties that we have no control over.

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.

Supplementary Information Forms (School Directory/School Admissions)

We are legally required to offer these documents on our site, but each document is owned by their respective school. The accessibility regulations do not require us to make third-party content (content created by other organisations) accessible. Please contact the schools directly for alternative formats.

Maps

Maps are excluded from the accessibility regulations as long as any essential navigational information they provide is available.

How we test this website

We use an automated tool, Siteimprove accessibility checker, to check the accessibility of our website every five days. We also use to Siteimprove to assess the accessibility of most PDFs prior to publication on our site. We routinely carry out manual checks on a proportion of our pages and documents to identify issues that can't be detected automatically.

We are testing:

  • our main website platform, available at www.surreycc.gov.uk
  • these services based on a different technical platform but 'skinned' to look like our website:
    • adult learning course finder
    • adult social care portal
    • blue badge portal
    • councillors and committees
    • crisis fund
    • family information directory
    • find my nearest
    • free bus pass applications
    • GIS maps
    • highway defect reporting
    • highway insurance claims
    • identity and authentication
    • library catalogue
    • payments
    • petitions
    • planning register
    • registration bookings
    • rights of way reporting
    • school admission appeals
    • schools directory
    • street light fault reporting
    • student fare card applications
    • Surrey history centre archives catalogue
    • real time traffic and travel
    • waste permit applications
    • other online forms

What we're doing to improve accessibility

We aim to fix any issues that are identified by our testing as soon as possible. If a prompt fix is not possible, we will plan a longer term solution to address the issue.

We have a programme of work in place to address the accessibility of our PDFs and documents. We have allocated new staff specifically for this programme.

We have increased the training and support available to our staff to help them create accessible content.

About this statement

This statement was prepared on 23 September 2019. It is reviewed every three months and was last updated on 16 August 2022.


In this section