This accessibility statement applies to content published on the payment system Pay360 (https://ip.e-paycapita.com/)
This website is run by The Access Group and Dorset 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 250% without the text spilling off the screen
- navigate most of the website using just a keyboard
- 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 aren’t fully accessible:
Feedback and contact information
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille, please email [email protected]. We will consider your request within 3 working days and get back to you.
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 the requirements of the accessibility regulations please email [email protected]
Enforcement procedure
The Equality and Human Rights Commission (EHRC) is responsible for enforcing 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
Dorset 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
The website has been tested against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard.
This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed below.
Non-compliance with the accessibility regulations
The content listed below is non-accessible for the following reasons.
1.3.5 Identify Input Purpose
Some form fields, such as address and postcode inputs, are missing programmatic identifiers. This means browsers and assistive technologies cannot help users autofill these fields, which may make completing forms harder for some users.
The Access Group have advised that for security reasons, the autocomplete attribute is set to “off” and they do not plan to fix this item.
1.3.1 Info and Relationships
Certain page content is not wrapped in ARIA landmarks (such as <main> or <header>). This can make navigation harder for users of assistive technologies like screen readers.
1.3.1 Info and Relationships
Some table headers are missing valid scope attributes, which means assistive technologies cannot determine whether the header applies to a row or column. This can make navigating tables harder for screen reader users.
1.3.1 Info and Relationships
Some lists include elements that are not <li> tags as direct children (e.g., <p> tags inside <ul> or <ol>). This can cause screen readers to misreport the number of items in a list, making navigation harder for users.
1.3.1 Info and Relationships
There is a skipped heading level from a heading one to a heading three on some of the help pages.
1.4.10 Reflow
There is currently an issue on the payment summary table which means some words in the header and some payment descriptions overlap each other on certain devices such as a tablet. We hope to have this fixed by mid-December 2025.
Disproportionate burden
At this time we have not made any disproportionate burden claims.
What we’re doing to improve accessibility
We have raised these issues with the Access Group, the supplier of this platform and are waiting for a timeframe for fixes.
Preparation of this accessibility statement
This statement was prepared on 24 November 2025.
This website was last tested on 24 November 2025 by Dorset Council's Content Design team. A mix of automated tests and manual checks were used to test the site.