Building accessible websites for diverse users

Your website needs to give people access to the same information across different abilities, devices and browsing conditions. Design choices, development decisions and ongoing updates all affect whether visitors can use the experience you intended.

When should accessibility shape our website design?

Accessibility should shape your website design from the outset, with designers and developers resolving visual ambitions and technical requirements together before designs are approved.

Read more

Which access needs should our website design cover?

Your website design should cover different input methods, visual access, reading speeds and viewing conditions, including temporary or situational access needs.

Read more

When should we use custom website controls?

Use native browser controls where they fit the interaction, and choose custom controls only when you explicitly provide for the keyboard operation and screen-reader compatibility they replace.

Read more

When should we use accessibility overlays on our website?

Do not rely on an accessibility overlay to remedy underlying barriers or establish compliance; address accessibility in your website's structure and code.

Read more

Which website accessibility tasks should we give AI?

Give AI repetitive accessibility coding tasks and context-aware alternative text drafting, while keeping people responsible for accuracy and users' experience.

Read more

What browsing conditions should our website support?

Your website should support varied browsers, devices, connection speeds and JavaScript availability, rather than treating one browsing setup as representative of all visitors.

Read more

When should we update our website for accessibility?

Review and update your website's accessibility as technology and the site change, using redesign or redevelopment where needed and continuing maintenance after launch.

Read more