Accessibility Statement for Essex County Council
This accessibility statement applies to the Essex County Council website. It also includes web tools needed to complete tasks and user journeys located at:
This website is run by Essex County 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 colours, contrast levels and fonts
- zoom in up to 400% 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
We know some parts of this website are not fully accessible:
Perceivable
Some images and icons have missing or incorrect alternative text so do not read out on a screen reader.
Some headings do not look like headings and some text that look like headings are not.
Some pages have multiple heading 1 tags and some heading levels are skipped.
Some links and buttons are used incorrectly.
Lists are not always used correctly, in the contents each item is a list, and some menus are a combination of two lists, some lists have incorrect aria roles, and, on some forms, an unordered list is used when it should be ordered.
On the bus lane payments website there are no page landmarks making it difficult to navigate for assistive technology users.
Tables are used to format content on the bus lane payments website making it difficult for some users to understand the purpose of the content.
On some form inputs there are no autocomplete values making it difficult for some users to fill in the forms.
Some text has low contrast and is difficult to read.
When increasing font-size to 200% some text is difficult to read or obscured.
When zooming in, some text and content Is obscured or difficult to read. This occurs on:
- the school admissions application form
- bus lane payments
Inputs have low contrast making them difficult to see when paying bus lane fines.
Adding text spacing can obscure content on the bus lane payments page.
Operable
Some elements cannot be controlled with a keyboard including the YouTube embedded videos.
On some of our forms there is no option to adjust timings.
The bus lane payments page has no option to skip to page content.
On the bus lane payments page the page titles are not clear of the page content.
On some of our forms the page titles are not clear of the page content.
The focus order on some of our forms and our feedback mechanism is not always logical.
The purpose of some links is ambiguous to the user.
Some headings or labels do not clearly describe the purpose of the page or section.
Some items on our form and feedback mechanism and bus payments page have focus styles that cannot be or are impossible to see.
Understandable
On some forms choosing an address or selecting an appointment time creates a change of context.
Navigation on the bus lane payments website is not always consistent.
Some links that are identified differently go to the same destination.
When entering details on the bus lane payments website some inputs do not have clear error identification.
Some inputs do not provide clear suggestions for overcoming errors.
Robust
In many places the correct markup is not used correctly. This may have an effect on users who use assistive technology or want to change the website layout or style to improve their experience. This occurs on:
- school applications form
On some pages the correct name role or value is not assigned, this could affect users of assistive technologies or require said technologies to provide information about states, properties, and values etc. This occurs on the:
- school applications form
Feedback and contact information
Contact our Service Transformation Team to request a different format. This could be an accessible PDF, large print, easy read, audio recording or braille.
Email: Accessibility@essex.gov.uk
We’ll consider your request and get back to you within 20 working days.
Reporting accessibility problems with this website
We’re always looking to improve the accessibility of this website. Contact the Service Transformation Team if you find any problems not listed on this page.
Email: Accessibility@essex.gov.uk
We'll consider your request and get back to you within 20 working days.
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.
Technical information about this website’s accessibility
Essex 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.
Compliance status
This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
Essex County Council website
Perceivable
Some PDF images have missing alternative text. This makes it difficult for users of assistive technologies to understand the purpose of the image. This fails WCAG 2.1 success criterion 1.1.1 (Non-text content). We plan to make sure all images have the correct alternative text. At this current time we have no fixed resolution date.
Operable
When navigating with a keyboard, focus styles on YouTube are hard to see or not visible. This fails WCAG 2.1 success criterion 2.4.7 (Focus Visible). We plan to address this issue. At this current time we have no fixed resolution date.
When using a mobile iPhone device with a keyboard, YouTube videos can not be accessed with a keyboard. This fails WCAG 2.1 success criterion 2.1.1 (Keyboard). We plan to address this issue. At this current time we have no fixed resolution date.
Booking Lab: Registration Appointments
Perceivable
Asterisks are used for required fields, but instructions on the purpose of this is not provided. Some form fields communicate multiple labels making it difficult for assistive technology users to understand the purpose of the fields. Some pages have multiple heading level h1s making it difficult to understand the page structure. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).
Some fields are marked with an asterisk (*) but this is the only visual cue for required fields. This fails WCAG 2.2 success criterion 1.3.3 (Sensory Characteristics).
Colour is the only visual clue to identify some links and keyboard focus indicators. Users with visual impairments will be unable to access information that is presented only in color. This fails WCAG 2.2 success criterion 1.4.1 (Use of Color).
Some text has low contrast making it difficult for some users to see. This fails WCAG 2.2 success criterion 1.4.3 (Contrast (Minimum)).
Increasing font size to 200% causes some combo box options to become truncated making content difficult to read. This fails WCAG 2.2 success criterion 1.4.4 (Resize (Text).
Increasing magnification to 400% causes some combo box options to become truncated making the content difficult to read. This fails WCAG 2.2 success criterion 1.4.10 (Reflow).
Some non-text contrasts are low making it hard to identify elements that can be interacted with or acted on. This fails WCAG 2.2 success criterion 1.4.11 (Non-text contrast).
Operable
Not all functionality is operable with a keyboard, meaning keyboard only users cannot interact with them. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard).
On an iOS mobile device, some combo boxes can cause keyboard users to become trapped within the top section of the page. This fails WCAG 2.2 success criterion 2.1.2 (Keyboard Trap).
There is a time limit for inactivity, but there is no warning message or option allowing the user to turn off, adjust or extend the time limit. This fails WCAG 2.2 success criterion 2.2.1 (Timing Adjustable).
Some webpages have the same title, and some page titles are not descriptive of its purpose. This may make it difficult for users to orient themselves and find the right content. This fails WCAG 2.2 success criterion 2.4.2 (Page Titled).
Non-interactive content is reachable with a keyboard, but this content cannot be interacted with or acted on. On an iOS and Android mobile device, the keyboard focus does not always follow a logical order which can cause difficulty understanding what element will receive keyboard focus. This fails WCAG 2.2 success criterion 2.4.3 (Focus order).
There are some links with ambiguous text so users may not be able to identify where a link takes them. This fails WCAG 2.2 success criterion 2.4.4 (Link Purpose (In Context)).
The location of the keyboard is not always visually obvious so keyboard only users will not know where they are on a webpage. This fails WCAG 2.2 success criterion 2.4.7 (Focus Visible).
On an iOS mobile device, the element which has keyboard focus is not always visible or partially visible making it difficult for keyboard users to understand what element has keyboard focus. This fails WCAG 2.2 success criterion 2.4.11 (Focus Not Obscured (Minimum)).
In some instances, the visible label is not included in the accessible name making it difficult for users of assistive technologies to interact with certain elements. This fails WCAG 2.2 success criterion 2.5.3 (Label in name).
Understandable
Some buttons which have the same functionality are labelled differently making it difficult for some users to identify where to navigate. This fails WCAG 2.2 success criterion 3.2.4 (Consistent Identification).
Sole form fields do not provide clear errors to users or even identify the field which has an error. This will make it difficult for some users to complete the form. This fails WCAG 2.2 success criterion 3.3.1 (Error Identification).
There is no indication some form fields are required making some forms difficult to complete. This fails WCAG 2.2 success criterion 3.3.2 (Labels or Instructions).
Some error messages do not provide appropriate suggestions making it difficult to resolve errors. This fails WCAG 2.2 success criterion 3.3.3 (Error Suggestion).
Robust
For some content which can be expanded and collapsed, selected and unselected, the state is not communicated to assistive technology users. Some interactive elements have not been given a name or role or have been given an incorrect name making it difficult for assistive technology users to interact with as the purpose is not clear. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).
Some status messages are not presented to screen reader users making some functionality difficult to interact with. This fails WCAG 2.2 success criterion 4.1.3 (Status Messages).
Booking Lab: Registration Ceremonies
Perceivable
The image in the banner landmark does not have alternative text. This fails WCAG 2.2 success criterion 1.1.1 (Non-text Content).
Asterisks are used for required fields, but instructions on the purpose of this is not provided and required fields are not communicated to screen reader users. Some form fields communicate multiple labels making it difficult for assistive technology users to understand the purpose of the fields. Some pages have multiple heading level h1s making it difficult to understand the page structure. On the Terms and Conditions pdf, there is content that does not behave like a heading but has been marked up as a heading. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).
Some fields are marked with an asterisk (*) but this is the only visual cue for required fields. This fails WCAG 2.2 success criterion 1.3.3 (Sensory Characteristics).
Colour is the only visual clue to identify some keyboard focus indicators. Users with visual impairments will be unable to access information that is presented only in color. This fails WCAG 2.2 success criterion 1.4.1 (Use of Color).
Some text has low contrast making it difficult for some users to see. This fails WCAG 2.2 success criterion 1.4.3 (Contrast (Minimum)).
Increasing font size to 200% causes some combo box options to become truncated making content difficult to read. This fails WCAG 2.2 success criterion 1.4.4 (Resize (Text).
Increasing magnification to 400% causes some combo box options to become truncated making the content difficult to read. On the Terms and Conditions pdf, users are required to scroll horizontally and vertically at 400% magnification. This fails WCAG 2.2 success criterion 1.4.10 (Reflow).
Some non-text contrasts are low making it hard to identify elements that can be interacted with or acted on. This fails WCAG 2.2 success criterion 1.4.11 (Non-text contrast).
Operable
Not all functionality is operable with a keyboard, meaning keyboard only users cannot interact with them. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard).
On an iOS mobile device, some combo boxes can cause keyboard users to become trapped within the top section of the page. This fails WCAG 2.2 success criterion 2.1.2 (Keyboard Trap).
There is a time limit for inactivity, but there is no warning message or option allowing the user to turn off, adjust or extend the time limit. This fails WCAG 2.2 success criterion 2.2.1 (Timing Adjustable).
Some webpages have the same title, and some page titles are not descriptive of its purpose. This may make it difficult for users to orient themselves and find the right content. This fails WCAG 2.2 success criterion 2.4.2 (Page Titled).
On an iOS and Android mobile device, the keyboard focus does not always follow a logical order which can cause difficulty understanding what element will receive keyboard focus. This fails WCAG 2.2 success criterion 2.4.3 (Focus order).
There are some links with ambiguous text so users may not be able to identify where a link takes them. This fails WCAG 2.2 success criterion 2.4.4 (Link Purpose (In Context)).
The location of the keyboard is not always visually obvious so keyboard only users will not know where they are on a webpage. This fails WCAG 2.2 success criterion 2.4.7 (Focus Visible).
On an iOS device, the element which has keyboard focus is not always visible or partially visible making it difficult for keyboard users to understand what element has keyboard focus. This fails WCAG 2.2 success criterion 2.4.11 (Focus Not Obscured (Minimum)).
In some instances, the visible label is not included in the accessible name making it difficult for users of assistive technologies to interact with certain elements. This fails WCAG 2.2 success criterion 2.5.3 (Label in name).
Understandable
Some form fields do not provide clear errors to users or even identify the field which has an error. This will make it difficult for some users to complete the form. This fails WCAG 2.2 success criterion 3.3.1 (Error Identification).
There is no indication some form fields are required making some forms difficult to complete. This fails WCAG 2.2 success criterion 3.3.2 (Labels or Instructions).
Some error messages do not provide appropriate suggestions making it difficult to resolve errors. This fails WCAG 2.2 success criterion 3.3.3 (Error Suggestion).
Robust
For some content which can be expanded and collapsed, selected and unselected, the state is not communicated to assistive technology users. Some interactive elements have not been given a name or role or have been given an incorrect name making it difficult for assistive technology users to interact with as the purpose is not clear. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).
Some status messages are not presented to screen reader users making some functionality difficult to interact with. This fails WCAG 2.2 success criterion 4.1.3 (Status Messages).
Booking Lab: Ceremony Portal
Perceivable
The image in the banner landmark does not have alternative text. This fails WCAG 2.2 success criterion 1.1.1 (Non-text Content).
Some form fields communicate multiple labels making it difficult for assistive technology users to understand the purpose of the fields. Asterisks are used for required fields, but this is not communicated to screen reader users. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).
Colour is the only visual clue to identify some keyboard focus indicators. Users with visual impairments will be unable to access information that is presented only in color. This fails WCAG 2.2 success criterion 1.4.1 (Use of Color).
Some text has low contrast making it difficult for some users to see. This fails WCAG 2.2 success criterion 1.4.3 (Contrast (Minimum)).
Some date fields with date picker calendars do not increase when the font size is increased to 200%. This fails WCAG 2.2 success criterion 1.4.4 (Resize (Text).
Increasing magnification to 400% requires users to scroll horizontally and vertically to view some content on the ‘Give Notice’ page. This fails WCAG 2.2 success criterion 1.4.10 (Reflow).
Some non-text contrasts are low making it hard to identify elements that can be interacted with or acted on. This fails WCAG 2.2 success criterion 1.4.11 (Non-text contrast).
When additional content is made available on hover, the additional content disappears meaning users are unable to hover over this content. This fails WCAG 2.2 success criterion 1.4.13 (Content on hover or focus).
Operable
Not all functionality is operable with a keyboard, meaning keyboard only users cannot interact with them. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard).
On an iOS mobile device, some combo boxes can cause keyboard users to become trapped within the top section of the page. This fails WCAG 2.2 success criterion 2.1.2 (Keyboard Trap).
There is no option to skip repeated content meaning keyboard users a required to tab through the repeated content. This fails WCAG 2.2 success criterion 2.4.1 (Bypass Blocks).
Some webpages have the same title, and some page titles are not descriptive of its purpose. This may make it difficult for users to orient themselves and find the right content. This fails WCAG 2.2 success criterion 2.4.2 (Page Titled).
There are some links with ambiguous text so users may not be able to identify where a link takes them. This fails WCAG 2.2 success criterion 2.4.4 (Link Purpose (In Context)).
The location of the keyboard is not always visually obvious so keyboard only users will not know where they are on a webpage. This fails WCAG 2.2 success criterion 2.4.7 (Focus Visible).
On an iOS device, the element which has keyboard focus is not always visible or partially visible making it difficult for keyboard users to understand what element has keyboard focus. This fails WCAG 2.2 success criterion 2.4.11 (Focus Not Obscured (Minimum)).
In some instances, the visible label is not included in the accessible name making it difficult for users of assistive technologies to interact with certain elements. This fails WCAG 2.2 success criterion 2.5.3 (Label in name).
Understandable
Some form fields do not provide clear errors to users or even identify the field which has an error. This will make it difficult for some users to complete the form. This fails WCAG 2.2 success criterion 3.3.1 (Error Identification).
On the ‘Login’ page, there is a form field missing a label, instead placeholder text has been used but this is not an appropriate label. There is no indication some form fields are required making some forms difficult to complete. This fails WCAG 2.2 success criterion 3.3.2 (Labels or Instructions).
Some error messages do not provide appropriate suggestions making it difficult to resolve errors. This fails WCAG 2.2 success criterion 3.3.3 (Error Suggestion).
Robust
For some content which can be expanded and collapsed, selected and unselected, the state is not communicated to assistive technology users. Some interactive elements have not been given a name or role or have been given an incorrect name making it difficult for assistive technology users to interact with as the purpose is not clear. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).
Some status messages are not presented to screen reader users making some functionality difficult to interact with. This fails WCAG 2.2 success criterion 4.1.3 (Status Messages).
Granicus Forms
Perceivable
We build and host our forms using a third-party product.
The vendor states that ‘citizen facing products are being updated to ensure they meet all required elements of the accessibility directive that require implementation in the EN 301 549 mandate.’
The use of links, lists and roles is not correct. This fails WCAG 2.1 success criterion 1.3.1 (Info & Relationships).
Some forms do not include autocomplete values. This fails WCAG 2.1 success criterion 1.3.5 (Identify input purpose).
When increasing font-size to 200% some options become unavailable or difficult to interact with. This fails WCAG 2.1 success criterion 1.4.4 (Resize Text).
When zooming in to up to 400% some content and functionality becomes obscured. This fails WCAG 2.1 success criterion 1.4.10 (Reflow).
Operable
Some form functions such as date pickers and collapsible rows does not work with a keyboard. This fails WCAG 2.1 success criterion 2.1.1 (Keyboard).
Some forms have a timeout with no option to extend the form duration and some form messages disappear before the user has time to read them. This fails WCAG 2.1 success criterion 2.2.1 (Timing Adjustable).
When using a keyboard to complete the form the focus order is not always logical. This fails WCAG 2.1 success criterion 2.4.3 (Focus Order).
Some links have ambiguous text making it difficult to identify the destination of the link. This fails WCAG 2.1 success criterion (Link purpose (in Context)).
When using a keyboard focus styles are not always visible. This fails WCAG 2.1 success criterion 2.4.7 (Focus Visible).
Understandable
When selecting an address, there is a change of focus without warning. This fails WCAG 2.1 success criterion 3.2.2 (On Input).
Robust
The forms include invalid HTML and HTML attributes as well as incorrectly implemented CSS. This fails WCAG 2.1 success criterion 4.1.1 (Parsing).
Some form inputs do not have connected labels. Some form elements are in tables. This makes it difficult for users of assistive technologies to interact with. This fails WCAG 2.1 success criterion 4.1.2 (Name, Role, Value).
Some role attributes are not correct. Some form values contain prior information given to the user. This fails WCAG 2.1 success criterion 4.1.2 (Name, Role, Value).
Bus lane payments
Perceivable
Some images have no or inadequate alt text. This fails WCAG 2.1 success criterion 1.1.1 (Non-text contrast).
There are multiple level 1 headings, and some heading levels are skipped, there are no page landmarks or regions and lists and tables are used incorrectly. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).
Some form fields do not have autocomplete attributes making it difficult for some users to complete the form. This fails WCAG 2.1 success criterion 1.3.5 (Identify input purpose).
Some heading text falls below a 4.5:1 contrast ratio. This fails WCAG 2.1 success criterion 1.4.3 (Contrast (Minimum)).
Some font is obscured or overlapped on the menu and navigation when font-size is increased making it difficult to read. This fails WCAG 2.1 success criterion 1.4.4 (Resize Text).
When zooming in, the page does not reflow making it impossible to view some of the page content. This fails WCAG 2.1 success criterion 1.4.10 (Reflow).
Inputs have low contrast below the required 3:1 contrast ratio making it difficult to see. This fails WCAG 2.1 success criterion 1.4.11 (Non-text Contrast).
When increasing text-spacing some text in the menu becomes obscured. This fails WCAG 2.1 success criterion 1.4.12 (Text Spacing).
Operable
DixerIT accessibility features cannot be operated with a keyboard. This fails WCAG 2.1 success criterion 2.1.1 (Keyboard).
There is no way to adjust any timings used on forms. This fails WCAG 2.1 success criterion 2.2.1 (Timing Adjustable).
There is no option to bypass blocks such as the menu or navigation making it difficult for keyboard only users to access content. This fails WCAG 2.1 success criterion 2.4.1 (Bypass blocks).
The homepage title is not descriptive of the purpose of the page. This could be confusing for some users who rely on a screen reader. This fails WCAG 2.1 success criterion 2.4.2 (Page Titled).
The focus order when filling out the appeals form is illogical and does not move to the start of the next form section when it is loaded. This fails WCAG 2.1 success criterion 2.4.3 (Focus Order).
Headings and labels do not clearly describe the topic or purpose of the content. Making it difficult for some user to identify or find the right content they require. This fails WCAG 2.1 success criterion 2.4.6 (Headings and Labels).
There are no focus styles on many of the interactive elements. This makes it difficult for Keyboard only users to navigate through the website. This fails WCAG 2.1 success criterion 2.4.7 (Focus Visible).
Understandable
When making an appeal the navigation changes making it potentially confusing for some users. This fails WCAG 2.1 success criterion 3.2.3 (Consistent Navigation).
Some links that got to the same destination are labelled differently making it difficult for some users to identify where to navigate. This fails WCAG 2.1 success criterion 3.2.4 (Consistent Identification).
When submitting a form some inputs are not identified clearly. This fails WCAG 2.1 success criterion 3.3.1 (Error identification).
When entering information in to inputs not all required inputs provide clear error suggestions. This fails WCAG 2.1 success criterion 3.3.3 (Error Suggestion).
Direct debit mandate PTX form
Operable
Expanding the Direct Debit Guarantee cannot be operated with a keyboard. This fails WCAG 2.1 success criterion 2.1.1 (Keyboard).
When using a keyboard, focus styles on some fields and buttons are not always visible. This fails WCAG 2.1 success criterion 2.4.7 (Focus Visible).
Expanding the Direct Debit Guarantee is not accessible using screen reader. This fails WCAG 2.1 success criterion 3.3.1
Perceivable
When increasing font-size to 200% some options become unavailable or difficult to interact with. This fails WCAG 2.1 success criterion 1.4.4 (Resize Text).
Some text falls below a 4.5:1 contrast ratio. This fails WCAG 2.1 success criterion 1.4.3 (Contrast (Minimum)).
Some images have no or inadequate alt text. This fails WCAG 2.1 success criterion 1.1.1 (Non-text contrast).
Robust
Some form fields do not have connected labels. This fails WCAG 2.1 success criterion 4.1.2 (Name, Role, Value).
Some presentational attributes are used instead of CSS styling. Some form labels refers to a non-existent element id. So element ids are not unique. This fails WCAG 2.1 success criterion 4.1.2 (Name, Role, Value).
Fostering contact form
This form has been tested on multiple mobile devices without encountering any issues.
Due to the variety of screen resolutions' and user's settings, we cannot guarantee that the page will display correctly.
Content that’s not within the scope of the accessibility regulations
PDFs and other documents
Some of Essex County Council’s older PDFs do not meet accessibility standards.
We're working towards making as many PDFs as possible meet WCAG 2.1 AA accessibility standards.
The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 unless they're essential to providing our services.
We are prioritizing PDFs as they often:
- contain information on how users can access our service
- are most frequently downloaded
- have information that has a statutory requirement
We have developed training and guidance for document creators to make accessible documents.
Our plan is to ensure that all essential PDFs meet accessibility regulations by 1st December 2025.
Live video
We do not plan to add captions to live video streams. This is because live video is exempt from meeting the accessibility regulations.
What we’re doing to improve accessibility
We are currently working with internal teams and external suppliers to improve accessibility on essex.gov.uk and its connected services.
We will continue to monitor accessibility using automated and manual checks.
Preparation of this accessibility statement
This statement was prepared on 26 June 2019. It was last reviewed on 19 May 2023.
The www.essex.gov.uk part of this website was tested on 19 May 2023, carried out by Essex County Council. Other elements were last tested on 16 June 2021. The test was carried out by the Central Data and Digital Office.
The website was tested using Windows 10 Pro, iPhone device, Android device, Google Chrome, Firefox, NVDA, and Axe testing software on a range of pages and user journeys. This included:
- Home
- News
- Search
- Accessibility statement
- Contact us
- Jobs and Apprenticeships
- Libraries
- Adult social care and health
- Blue Badge
- Trading Standards for consumers
- Admissions (Schools)
- Secondary school places
- Admissions booklet, policies and forms (Schools)
- School terms and holidays
- Admissions common application form (Schools)
Updated 20 November 2024