York SEND Local Offer Accessibility Statement
York SEND Local Offer Accessibility Statement
Technical information about this website’s accessibility
This statement applies to content published on the www.yorksend.org domain.
York SEND Local Offer is committed to making our website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No.2) Accessibility Regulations 2018.
To find out more about how our website meets accessibility guidelines please see:
- accessibility of our online services
- requesting services in an accessible format
- reporting accessibility problems (feedback and contact information)
- how accessible this website is
- compliance status
- non-accessible content
- online services which are not within the scope of accessibility regulations
- what we’re doing to improve accessibility
- preparation of this accessibility statement
Accessibility of our online services
Our website is designed to be used by as many people as possible. The text should be clear and simple to understand. You should be able to:
- zoom in up to 300% without problems
- navigate most of the website using just a keyboard
- use most of our online services with screen reader software
Most of our online services work when scripts, applets or other programmatic objects are turned off, or aren't supported by a device. However, your experience using online services without scripts running may degrade.
Our online services are partially compliant with the latest Web Content Accessibility Guidelines (WCAG). Get details of online services which don't meet accessibility standards, and online services that are not within the scope of accessibility regulations.
Requesting services in an accessible format
If you need information in a different format email: [email protected], and tell us:
- the location of the information (copy and paste the URL/address from your browser address bar)
- your name and email address (so we can respond)
- the format you need (for example, audio CD, braille, British Sign Language (BSL), large print, accessible PDF)
Feedback and contact information
You can report accessibility problems with this website if you find any issues that are not listed on this page, or you think we’re not meeting accessibility regulations. Email: [email protected] in the first instance, so that we can work to resolve the issue. If you contact us with a complaint about the accessibility of our online services, and you’re not happy with our response the Equality Advisory and Support Service may be able to help you.
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.
How accessible this website is
Parts of this website are not fully accessible. For example:
- some occurrences of mark-up languages are not used in a way that fully conforms to their specifications
- some lists or groups of links may not be written semantically
- some form controls may not appear sufficiently distinct from their surroundings
- some text does not have sufficient contrast with its background colour
- some text links refer to anchors that do not exist
- some text content may be written in a way that's too difficult to understand
- some links are not defined in a specific way
- some elements don't identify the purpose of fields programmatically
- some tables that are missing header
- some adjacent links point to the same destination
- some headings on the website do not provide text within the header tag
- some images fail to specify alternative text
- some links fail to explain their purpose
- some interactive components, such as buttons or fields, are not large enough
- at 400% zoom in mobile view it may be difficult to read the content
- keyboard focus is not visible on inactive buttons within the cookie banner
- keyboard focus is not visible on some elements which appear in the website header (or positioned over it)
Compliance status
This website is partially compliant with the Web Content Accessibility Guidelines (WCAG), due to the following non-compliances listed below.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations:
- some instances of inappropriate colour contrast exist, meaning it potentially reduces readability if you have low vision (if not using contrast-enhancing assistive technology) - this relates to success criterion WCAG (AA) 1.4.3
- there may be some form controls that fail to ensure they clearly indicate when they are selected by the keyboard this can cause a bad user experience for users of assisted technologies - this relates to success criterion WCAG 2.2 AAA 2.4.13
- there may be cases where links on the website fail to explain their purpose; It’s important to add additional context to all users especially those with assistive technology who need to better understand what the link does and it’s destination - this relates to success criterion WCAG (A) 2.4.4
- some lists or groups of links may not be written semantically which prevents assistive technologies easily navigating through different items, or past entire groups of links if needed - this relates to success criterion WCAG (A) 1.3.1
- there may be some areas of content that some will find too difficult to understand; content should be written so people with a lower secondary level of education can understand it, if not supplemental content should be provided - this relates to success criterion WCAG 2.0 AAA 3.1.5
- there may be some instances where there's a failure to include alternative text for images inside links, this can prevent users especially ones reliant on-screen readers the ability to determine what the link does - this relates to success criterion WCAG 2.0 A 1.1.1
- there may be some pages that fail to ensure HTML is in a meaningful sequence, content should be experienced in a linear order which is important because not all users can see a page, and may lose important contextual information - this relates to success criterion WCAG 2.0 A 1.3.2
- some pages may fail to contain an appropriate title, The title of the page should briefly describe the contents of this page and also make sense when read out of context by a screen reader for example - this relates to success criterion WCAG 2.0 A 2.4.2
- there may be cases where forms require a redundant entry this is meant to help prevent cases where you may be asked to type in duplicate content twice for example typing the address twice for 2 purposes, this can cause an inferior user experience - this relates to success criterion WCAG 2.2 A 3.3.9
- some drag and drop movements fail to include an accessible alternative; not all users or devices have the ability to use a cursor in a way that would allow drag-and-drop; these users could be denied access to some functionality or content - this relates to success criterion WCAG 2.2 AA 2.5.7
- there may be some cases where users are prevented from animation been able to easily pause or hide animated content, the intent of this success criterion is to avoid distracting users during their interaction with a web page - this relates to success criterion WCAG 2.0 A 2.2.2
- there may be pages with inactivity time limits that could cause data loss, pages that sign users out after a period of inactivity must not cause data loss as this can lead to a poor user journey - this relates to success criterion WCA2.1 AAA 2.2.5
- there may be cases where alternative text is not appropriate, it’s important the alternative text serves the same purpose and presents the same information as the media it describes - this relates to success criterion WCAG 2.0 A 1.1.1
- some links may not be defined in a specific way to be accessed by screen readers, which are used by blind and the partially sighted - this relates to success criterion WCAG (A) 4.1.2
- some text on this website may not sufficiently contrast with its background colour, so that people with moderate visual impairments can read it - this relates to success criterion WCAG (AA) 1.4.3
- there could be occurrences where help isn’t presented consistently, it should be presented in a consistent location within each webpage making it easier for the user - this relates to success criterion WCAG 2.2 A 3.2.6
- some lists are marked up incorrectly which can prevent screen readers accurately reporting the number of items contained in the list - this relates to success criterion WCAG (A) 4.1.1
- there may be cases of 2 adjacent links that point to the same destination, where they shouldn't, this may cause confusion to the user especially if they’re reliant on a screen reader - this relates to success criterion WCAG (A) 1.1.1
- there may be certain cases where links to anchors fail to exist causing a negative user experience - this relates to success criterion WCAG 2.0 A 2.4.1
- some pages don't Identify the purpose of fields programmatically, if done correctly, this allows browsers to help users fill in forms with known information - this relates to success criterion WCAG (AA) 1.3.5
- some failures may occur in allowing users to easily find definitions of unusual words, It’s important users have an easy way to identifying specific definitions of words or phrases used in an unusual or restricted way - this relates to success criterion WCAG 2.0 AAA 3.1.3
- there are cases where an ID attribute has been used more than once on one page, all id attributes on a page must be unique, or accessible technologies used by the page can stop working - this relates to Success Criterion WCAG A, 4.1.1
- there may be cases of adjacent links that haven’t been combined to point to the same destination, this can cause redundant focus stops and duplicate announcements for assistive technologies - this relates to success criterion WCAG (A) 1.1.1
- there are some images that may have been defined as decorative, any image alt tags left blank are considered decorative, and are therefore ignored by assistive technology - this relates to success criterion WCAG 2.0 A 1.1.1
- some headings on the website may fail accessibility as they do not provide text within the Header tag, not been machine-readable makes the title inaccessible to assistive technologies - this relates to success criterion WCAG (A) 1.3.1
- there may be some link text that is directed to more than one different destination, which will create confusion for Screen reader users - this relates to success criterion WCAG (A) 2.4.4
- some pages don’t allow the users to control the visual presentation of text, people with some cognitive, language and learning disabilities and some low vision users cannot perceive the text and/or lose their reading place if the text is presented in a manner that is difficult for them to read - this relates to success criterion WCAG 2.0 AAA 1.4.8
- there are certain pages with interruptions that can’t be postponed or suppressed by the user, from an assisted point of view it’s important to have one point per page to prompt manual verification that users can pause, dismiss, or turn off non‑emergency interruptions - this relates to success criterion WCAG 2.0 AAA 2.2.4
- there may be cases where links in a new tab or window where the destination is not explained, this can be disorientating for novice web users, and the visually impaired - this relates to success criterion WCAG (AAA) 3.2.5
- there may be some interactive components on a page, such as buttons or fields, which are not large enough to be easily used by people with motor impairments - this relates to success criterion WCAG (AAA) 2.5.5
- there may be some cases where a legend is not present for all field sets, this will then fail to explain its contents and can lead to confusion for all users - this relates to success criterion WCAG (A) 1.3.1
Where downloads (in PDF, and other file formats) do not meet accessibility standards we plan to fix or replace them, either when they are next reviewed, or as part of our ongoing programme of review work, whichever is sooner.
Online services not within the scope of the accessibility regulations
Parts of our online services are exempt from accessibility standards:
- the accessibility regulations do not require us to 'fix' downloads if they were published before 23 September 2018 (if they’re not essential to providing services); we will not edit downloads that are supplied to us by other organisations or members of the public to make them accessible
- we do not plan to add captions to live video streams, because live video is exempt from meeting the accessibility regulations, as are pre-recorded audio and videos published before 23 September 2020
- maps are exempt from accessibility regulations, but we're working to provide essential information in accessible ways; email us about requesting services in an accessible format. We don’t yet have a way of presenting geographical information (maps and site plans etc.) in a fully accessible format. However, as new technologies emerge, we'll review our online services
Accessibility exemptions in our work with third-parties
We brief suppliers on our requirement to meet accessibility regulations; while some elements remain beyond our control, we aim to procure services with accessible outcomes in mind, and to highlight potential improvements suppliers need to consider.
Software linked from our website, which is under the control of our suppliers, may not be accessible if our contract with them does not cover accessible development of 'out of the box' functionality. However, we aim to work with suppliers whose products are as accessible as possible, when contracts are reviewed/renewed. If we create content hosted on external platforms (for example, national databases, social media, video-hosting or survey platforms) we endeavour to ensure the content we upload meets accessibility requirements, and is configured in the most accessible way the platform allows. However, we're not responsible for the accessibility of third-party platforms.
What we’re doing to improve accessibility
We’re committed to being a fair and inclusive website, and we're passionate about providing accessible services, ensuring they’re properly designed and coded, so more people can use them, more easily, regardless of their hardware, software, language, location, or ability.
Preparation of this accessibility statement
This statement was prepared on 30 May 2023 and last reviewed in November 2025.
Our online services are currently being (and will continue to be) reviewed for compliance with WCAG standards by City of York Council's Web Services Team, who carry out manual checks, alongside weekly automated sample testing which (together with usage data) informs and prioritise our actions for improving accessibility across online services.
Online services are re-assessed for accessibility whenever a major modification is undertaken; 'page content' is checked every time it is updated. Our current estimate is that further accessibility fixes to address non-accessible content on this site, will be undertaken during 2026.
