Accessibility Statement
How accessible this website is, what we know isn't working, and how to tell us if you hit a problem.
Last updated: DATE
⚑ Draft — and this one cannot be completed yet
An accessibility statement is a factual report of testing that has been done. No testing has been done on this site yet, so the honest sections below say so. Do not replace “not yet tested” with a compliance claim until an audit has actually been carried out — an inaccurate accessibility statement is worse than none, because disabled users rely on it to decide whether to bother.
This statement applies to DOMAIN.
We want as many people as possible to be able to use this website. A lot of the people who need us are older, or have a learning disability, a visual impairment or a cognitive difference. If the website doesn't work for them, it isn't doing its job.
What we have done so far
The site has been built with accessibility in mind from the start:
- Body text is set at 18px rather than the more common 16px, with generous line spacing
- Colour contrast was checked at design stage, and the primary button colour was darkened specifically to meet the AA contrast threshold
- Every page has a skip link, one main heading, and a logical heading structure
- All interactive elements have a visible focus outline
- Accordions and menus are built to work with a keyboard
- Motion is reduced automatically if your device asks for that
- Images carry descriptive alternative text
How accessible this website is
NOT YET TESTED. We have built to the Web Content Accessibility Guidelines version 2.2 level AA, but we have not yet had the site independently audited or tested with assistive technology. Until we have, we cannot honestly tell you it is compliant, so we are not going to.
Testing planned before launch: automated scanning of every page template, a full keyboard-only pass, a screen reader pass on the enquiry and referral forms, and a check at 200% zoom on a small screen.
Known issues
TO BE COMPLETED AFTER TESTING. List each known problem, the WCAG criterion it fails, and when you expect to fix it. Being specific here is what makes a statement credible.
Two things we already know need attention:
- The website platform has no tablet breakpoint of its own, so intermediate screen sizes are handled with custom code that needs verifying on real devices
- The embedded enquiry form is provided by a third party, and we do not fully control its markup
Easy read and other formats
We support people with learning disabilities, so this matters more here than on most websites.
DECIDE AND STATE what is available — easy read versions of key pages, large print, audio, or information in another language. If nothing is available yet, say what someone should do instead, and who will help them.
If you need something on this site in a different format, contact us and we will do our best to provide it. CONTACT ROUTE AND RESPONSE TIME
Tell us if you hit a problem
If you find something that doesn't work, or you can't get at information you need, please tell us. It genuinely helps — we can't fix what we don't know about.
ACCESSIBILITY CONTACT — email and phone
We will acknowledge what you tell us and let you know what we are going to do about it. TIMESCALE
If you are not happy with our response
The Equality Act 2010 requires service providers to make reasonable adjustments for disabled people. If you contact us with a complaint about accessibility and you are not satisfied with how we respond, you can use our complaints process.
The Equality Advisory and Support Service can also give free advice: equalityadvisoryservice.com, 0808 800 0082.
Technical information
Bellus Care & Support is committed to making this website accessible in accordance with the Equality Act 2010.
AFTER TESTING, state the compliance status here in the standard form: fully compliant, partially compliant with WCAG 2.2 AA, or not compliant — and if partially, list the exemptions and the reasons.
Statement prepared on DATE. Last reviewed on DATE. Testing carried out by WHO.
Before this page can be published
- Run the accessibility audit set out in the blueprint
- Fix what it finds, or list it honestly under Known issues with a date
- Decide what easy-read and alternative formats will actually be offered
- Nominate an accessibility contact who will respond