Creating accessible environments for disabled people

Technology includes things like:

• Computer hardware and software
• Applications (including mobile apps)
• Business systems (such as client record databases)
• Assistive devices or accessibility software

Here are some steps we can take to embed access into technology:

• Technology should be usable for all regardless of access requirements. Apps, software and business systems should conform to Level A and AA criteria as set out in the Web Content Accessibility Guidelines (WCAG). We aspire to achieve AAA conformance where possible. This supports accessibility for a wider range of users.
• Some users may need to access technology via a range of solutions. This may be voice control, keyboard-only control, screen readers or non-standard keyboard or mouse design. Software, applications, and systems should be compatible with these.
• We should test technology with a range of access solutions before the technology is launched for employees or service users. This includes solutions built into devices that people may be using. For example, VoiceOver on iPhones and Narrator on Windows devices.
• We should also conduct testing periodically. This ensures technology stays compatible with access solutions after updates or changes to design or function. It's also important to note that:
  • The access needs of different users will differ. It can include using technology with sensory loss, limited dexterity, or via vocal command only. Some users may have dual access needs. We should consider solutions that support individuals with a combination of access requirements.
  • We should provide staff with appropriate access solutions. These may be available within the organisation. But we may need to order them as part of reasonable adjustments for an employee or through the Access to Work scheme.
  • It's important that interactions between individual systems or technologies are also accessibility tested. This ensures there are no incompatibility issues when using access solutions.
• Documents from any technology (such as forms generated by a system) should be accessible for all. We should test such documents with a range of access solutions.
• Where a technology is not adequately accessible, we must make a robust plan. This will set out how we deal with accessibility barriers and make reasonable adjustments.