Beta This is new guidance. Complete our quick 5-question survey to help us improve it.
Accessibility for developers: an introduction
You must build your service in a way that makes it accessible to everyone who needs it. If it isn’t, you may be in breach of the Equality Act 2010.
As a technical member of your team, you need to design and build interfaces that meet government accessibility requirements. To help you do this, you should:
- help identify possible accessibility issues in content and design, and feed them back to your designer or content designer before implementing it in code
- meet the success criteria of the WCAG 2.0 design principles that relate to implementing accessible code
- test for accessibility on a regular basis - and each time you build a new feature
- make sure your service works with assistive technologies - like screen readers and speech recognition software
- help your team plan for its accessibility audit - and fix any issues it identifies
Learn more about making your service accessible.
Implementing accessible code
You should help your team identify any possible accessibility issues in content or design before implementing in code.
When implementing your code, you should:
Add content to your source file in a logical order.
Add CSS and make sure you have not introduced any barriers.
Test your code for accessibility issues.
Case studies and resources
You may find the following resources useful:
- HTML: a good basis for accessibility - a Mozilla guide on using HTML to improve accessibility
- WAI-ARIA basics - a Mozilla guide on using WAI-ARIA to improve accessibility
- Page structure concepts - a W3 tutorial on using HTML and WAI-ARIA to improve navigation and orientation
- Forms concepts - a W3 tutorial on making accessible forms
- Tables concepts - a W3 tutorial on making accessible tables
- Writing CSS with accessibility in mind - using CSS to improve accessibility
Get in touch with the accessibility community directly to:
- discuss how to build accessible service and meet accessibility requirements
- share ideas across government
- find support from teams that have worked on similar services or faced similar challenges
You may also find the following guides useful:
- Published by:
- Accessibility community
- Last update:
Guidance first published