Digital accessibility training
Training for teams and experts
WHY TRAIN THE TEAM
Skills break down barriers
An audit tells you what to fix, but it is your team that writes the code, designs the components and publishes the content. If the development criteria are not clear to the people who handle day-to-day operations, the same issues may come up again. With AccessiBit training, your people gain skills, checks and accountability.
- Development3/3 sessionsSemantics, keyboard, components
- 2Design1/2 sessionsContrast, focus, reflow
- 3Content0/2 sessionsAlt text, documents
- 4Governance0/1 sessionProcesses, reviews, statement
Different skills for different roles
Each track starts from the responsibilities of the role and brings criteria and examples straight into the projects your team works on every day.
Build components and interactions that keep their semantics, navigation and compatibility with assistive technologies.
Semantic HTML and the accessibility tree
What a component actually exposes to assistive technology, and why name, role and state matter more than the markup you can see.
Keyboard, focus and custom components
Full keyboard navigation, focus that is visible and never obscured, and handling dialogs, menus and content that changes after load.
Forms, errors and status messages
Labels, instructions, error prevention and error announcement — the point where the most conversion flows are lost.
Design readable, usable interfaces that account for contrast, focus, zoom, reflow and interaction states.
Contrast, sizing and target areas
Contrast ratios for text and components, minimum target sizes, and why colour on its own is never enough to carry meaning.
Reflow, zoom and spacing
What happens to a layout when someone zooms, changes spacing or works in a narrow window — and how to design one that holds.
States, focus and components
Visible, consistent states for focus, error and selection, and components designed so the accessible name matches the visible label.
Produce text, images, documents and media that keep their information and structure across different ways of accessing them.
Alt text written for its purpose
When an image needs describing, when it should stay decorative, and how to write an alternative that serves the purpose the content is there for.
Structure, headings and links
Headings that reflect the real structure, lists and tables used for what they are, and links that still make sense out of context.
Accessible documents
Word, PDF and presentations: reading order, styles, tables and tags — the parts that decide whether assistive technology can read a document at all.
Bring accessibility criteria, responsibilities and checks into workflows, reviews and publishing processes.
Obligations, standards and guidelines
What the laws say, what the standards say and what the guidelines say: three separate layers that are routinely collapsed into one.
From finding to backlog
How a finding becomes a backlog item with context, impact, priority and an owner — and why, without that last one, it does not get fixed.
Statement, monitoring and regressions
An accessibility statement built on evidence, known issues, an improvement plan, and the checks that stop barriers coming back.
HOW IT RUNS
How a training track comes together
Step 1 — We start from your context
We look at roles, skills, processes and the results of any audits to see where training can have the greatest impact.
Step 2 — We build the programme
We choose modules, examples and exercises based on the team's real work, avoiding generic tracks.
Step 3 — We work on your cases
Sessions alternate principles, examples and hands-on exercises on components, content and flows close to everyday work.
Step 4 — Materials and follow-up
Checklists, materials and practical guidance help the team apply what it has learned after the training too.
FAQ
Frequently asked questions
Contact us
Leave us your details
One of our consultants will contact you as soon as possible