Your team stops shipping
the same findings.
Role-based accessibility training for developers, QA and UX. Your team works through the components that fail most often, with a keyboard and a screen reader, and leaves knowing how to check their own work.
Train your team Why the same issues come back
after every release
An audit is a snapshot. It catches what is in the product on the day we test it. The next sprint adds a modal, a filter panel and a data table, and the next audit finds them.
The habit behind a finding survives the fix
We test the views and flows in scope. The component your team builds next week is not one of them. When the same developer makes the same decision about a custom dropdown, it lands in the next report.
Automated scans leave the hard calls to your team
An automated scan flags a missing label. It can't tell whether the label it finds makes sense, or where focus went when the dialog closed. Someone on your team needs to know what to press and what to listen for.
How a training session runs
We find out what keeps breaking
You tell us the roles in the room, the stack, and the problems your team hits more than once. If you already have an audit, we read it first.
We build the programme around that
We pick exercises that match the problems you named. If data tables are the problem, the whole session can be data tables.
We run the workshop
We explain, demonstrate with a screen reader, then hand the exercise over. Your team does the work, on their own machines. Remote or on-site.
Your team keeps the material
Slides, references and the exercise files stay with your team, so the next hire can be walked through the same examples.
Three ways to run accessibility training
One role, in depth
A session for developers, for UX, or for QA, spent on the decisions that role makes every day.
The whole product team
Designers, developers and testers in one room. Shared fundamentals first, then the parts each role owns, so accessibility stops falling through the handoffs.
One problem, in detail
Already working on accessibility and stuck on something specific? The session can be built around it: data tables, focus management in a single-page app, or one component type such as the combobox.
An audit tells your team what is broken this quarter. Training is what keeps the next release from adding to the list. Run the audit first and we build the session around what it found, with exercises aimed at the kinds of failure your team shipped.
What to settle before booking accessibility training
How long does accessibility training take?
Accessibility training runs from four hours to three days, depending on the track and how much of it is hands-on. A single role goes further in one day than a mixed room does in two, because everyone runs the same exercise. When time runs short, we cut topics and keep the practice.
How much does accessibility training cost?
Each accessibility training gets one fixed quote, set by the track, the audience and the number of days we agree up front. A four-hour session for designers and three days for the whole product team are two separate quotes.
How many people can attend the training?
Usually your whole team. Everyone needs hands-on time with the exercises and a screen reader, so we agree the group size with you when we plan the session.
Do participants get a certificate?
Yes. Each participant can receive a certificate of completion for the training they attended.
Is this a WCAG course?
The training covers WCAG 2.2 AA through the decisions your team makes while building. Knowing that 2.4.7 exists doesn't tell a developer what to do about a focus ring, so we teach the decision first, then point at the criterion that governs it.
Does the European Accessibility Act require accessibility training?
Not for product teams. The European Accessibility Act mentions training only in recital 20, which isn't binding and is about staff knowing how to use accessible products and services. What the law requires is the result: a service that meets the accessibility requirements. Public bodies are different: the Web Accessibility Directive asks member states to promote training for public-sector staff (Article 7(4)).
Is the training suitable for beginners?
Yes. We can start at semantic HTML, or assume your team already reads WCAG and spend the day on focus management and live regions instead. Tell us which and we'll set the level before the session.
Can the training run remotely or on-site?
Both work. Remote suits the developer and QA tracks, because everyone tests on their own machine with their own screen reader, which is how they will work afterwards. On-site is easier for a mixed-role workshop.
What happens after the training?
After the training, your team keeps the slides, reference links and exercise files. Remediation support answers the questions that come up later, in Slack, Teams or Google Chat, and an audit tells you whether the habits stuck.
Unlock your full potential
You have a product to build. You don't have time to become a WCAG expert. Let us handle the technicalities so your team can get back to what they do best.
Discuss Your Project