Well documented UX design outlining structure, interaction, navigation patterns and so on will enable developers to bring designs to life. It will help avoid costly retrofits later on in a project.

Overall developers are responsible for technical accessibility where following web and platform standards reinforces best practice and support for users of access technology. While QA are on hand to test the code output, developers should check work day by day. Developers should endeavour to complete the BBC Academy Accessibility for Web Developers course (BBC Internal Link).

Developers should be familiar with the principles and all the standards and guidelines, including those they would expect to be covered by design documents or by other teams such as Media Playout and AV Key Experience. Developers are responsible for implementation and should use a progressive enhancement approach, building from a basic core experience to full functionality. When possible use standard interface controls, as these usually come with accessibility built in. If creating a custom component research how similar standard UI components have accessibility built in and mimic this as far as possible, testing interaction with screen readers and keyboard control.

If editorial colleagues need to add alternatives for non-text content like video or images, ensure that they are able to do so and that these are used correctly.