Skip to main content

Accessibility by role

Accessibility is everyone's responsibility

Accessibility isn’t just the job of designers and developers; it’s everyone’s responsibility. Each person in a multidisciplinary team plays a role in creating a product that’s usable by all people, including those with disabilities.

At every stage of a project accessibility must be a priority and each team member should know how to contribute to a more inclusive experience.

For those working on Turas applications, we’ve outlined specific accessibility considerations for different roles within the team.

How your role can contribute to accessibility:

  • content creators: Write content that is clear, easy to follow, and works well with screen readers
  • designers: Create layouts and interactions that are easy for everyone to use
  • developers: Build accessible code that supports all input methods and devices
  • procurement teams: Choose tools and services that meet accessibility standards
  • product owners: Set accessibility as a priority and support teams to deliver it
  • testers: Use both automated and manual checks to find and fix accessibility issues
  • user researchers: Involve people with access needs in research and help teams design based on real user experiences

Key Accessibility Principles

  • embed accessibility from start to finish, integrating it into the planning, design, development, and testing phases
  • define the "definition of done" for accessibility, ensuring all features meet the required standards before release
  • set measurable goals to ensure accessibility is tracked and achieved (WCAG 2.2 AA compliance for example)
  • work together across roles to create a consistent and accessible experience
  • view accessibility as an ongoing process not a one-off checklist. The focus should always be on continuous improvement

Getting in touch

If you can’t find your role or you think we’ve missed anything, you can get in touch to help us to improve this guidance.

Was this page helpful?