Free first call
What you need, and whether an audit is the right start.
Eastbourne and remote · Public sector, charities and business
Automated checks miss
Automated checks miss
most of the problems.
A scanner gives you a score and a clean conscience. It cannot tell you that the form is unusable with a keyboard or that the screen reader announces nothing. That part needs a person.
- 2022trading since
- UKregistered company
- WCAG2.2 AA
- Youown the code
What we do
Four services, with the code transferred
Audits combine automated and manual testing. No audit is a certification, and compliance stays the client's duty.
Websites and web applications
Sites and applications built so accessibility is designed in rather than retrofitted.
See the programAccessibility audits
Audits against WCAG 2.2 AA using automated tools plus manual testing with assistive technology.
See the programRemediation and statements
Fixing the issues found, and drafting the accessibility statement that has to be published.
See the programHandover and maintenance
Documentation and training so your team can publish without reintroducing barriers.
See the program
How it works
How we work
Test with real assistive technology, fix in the code, write honest statements, and transfer the repository.
Manual testing, always
Automated tools alone miss most barriers.
Fixed in code
Not hidden behind an overlay widget.
Code transfers to you
Repository and documentation on payment.
Working together
Ways to work with us
Fixed fee per phase or per audit. No audit is a certification, and compliance remains your organisation's duty.
Accessibility audit
Automated plus manual testing on your key journeys.
- Key journeys tested, not a sample
- Keyboard and screen reader testing
- Failures mapped to WCAG criteria
- Ranked by impact on users
- Plain report your developers can act on
Build or rebuild
A site built with accessibility designed in.
- Contrast and structure settled at design
- Tested throughout, not at the end
- Repository transferred on payment
- Documentation handed over
- No lock-in created
Remediation & statement
Fix the findings and publish an honest statement.
- Blocking issues fixed first
- Fixed in code, not with an overlay
- Retested with the same tools
- Statement drafted honestly
- Remaining gaps listed with a plan
Every engagement is quoted after a free consultation. No subscription.
How we work
An honest position on accessibility
JAD Codes Ltd is a private limited company registered in England and Wales under company number 13842672, incorporated in January 2022, with its registered office at 17 Freeman Thomas Place, Eastbourne, East Sussex BN22 0DQ.
Three things we will not pretend. An audit reports the pages we tested on the day we tested them — content changes, plugins and embedded media introduce new barriers, so it is not a certification and nobody can issue one. Automated tools find only a minority of real problems, which is why we test with a keyboard and a screen reader. And the legal duty stays with you: public sector bodies must meet the relevant WCAG level so far as reasonably practicable and publish an accessibility statement under the 2018 Regulations, and private organisations have duties under the Equality Act — we can draft and advise technically, but we give no legal advice and cannot assume the obligation.
Frequently asked
The questions we get most
Can you certify our site as accessible?
No, and nobody can. There is no certification scheme behind WCAG. An audit tells you what failed on the pages tested on the day, which is useful and genuinely different from a guarantee.
We ran a scanner and scored well. Is that enough?
Usually not. Automated tools catch a minority of real barriers and cannot tell whether a form is completable with a keyboard or whether a screen reader announces anything useful. That part needs manual testing.
What about those accessibility overlay widgets?
We do not recommend them. They sit on top of the problem rather than fixing it, disabled users widely report that they make things worse, and they have featured in legal claims rather than preventing them.
Do we have to publish an accessibility statement?
Public sector bodies do, under the 2018 Regulations, and it must be accurate — a statement claiming full compliance on a site with known failures is worse than one listing them with a plan. We draft it; publishing it remains yours.
Do we own the code?
Yes, on payment, with full repository access and documentation. Ask any developer this before signing.
Will this protect us from a claim?
We give no legal advice and cannot promise that. Fixing real barriers and publishing an honest statement is the substantive thing you can do; the legal position is a question for your own advisers.
Not sure where your site stands?
A free first call, including an honest answer about whether you need an audit yet.