ustwoLogo written in handwriting styleSkip to content

ustwo Accessibility Help

This website has been designed to work for everyone.

Our website has been tested internally against WCAG Level 2.2 AA.

You should be able to operate it with the input device of your choice (keyboard, mouse, touchpad, game controller, brain/computer interface, etc), and understand it using whatever output device you prefer (screen, braille display, screen reader, etc)

You should also be able to:

  • Change colours, contrast levels and fonts using browser or device settings
  • Zoom in up to 400% without the text spilling off the screen
  • Reduce motion support and better control video content

If you cannot – then we have let you down, and we are sorry. We love talking to our users. We would love to talk to you – and make it up to you!

Please consider contacting us to report the issue at info@ustwo.com.


There are a few known improvements in the pipeline:

  • Offset outlines for buttons
  • Improvements to reduced motion including handling fade-in text
  • Image transitions for our product packages
  • Tabbing behaviour when navigating between links

ustwo's Accessibility principles

We achieved this by following the ustwo Accessibility principles:

  1. Level-up your gear Just use the tools. There is a wealth of accessibility testing tools (contrast checkers, checklists, simulators). Use them to ensure your work meets basic accessibility standards.

  2. Enjoy the patterns An accessible design pattern is a repeatable solution that solves a common accessibility problem. We are a team of highly original and unique creative minds – but we're not the first to need form validation, or a tooltip.

  3. Think beyond touch Most users are happy with touchscreens and trackpads. But it is essential we think beyond mice and touch. Using our keyboards allows us to determine if our work is perceivable, operable, understandable, and robust.

  4. Close your eyes If it's usable with a keyboard, there’s a good chance it’ll work nicely with a screenreader. But we won’t know this unless we try it ourselves. Everyone on the project should learn how to use at least one screen reader – and use it!

  5. Party party (test) party! Testing the application for accessibility is not just the tester's responsibility. We get our teams together and huddle around the work. If our diverse teams can use it on all the phones, in all the browsers, and with all the input and output devices… then what we've created is truly usable