At VerifyEd, accessibility is fundamental.

We want our platforms to be fully inclusive and we know that accessibility improves the experience for everyone. From early in the design process right through to product development, we consider accessibility at every step of the way.

Currently, we're serving accessibility needs with these techniques:

✏️ Design Checks

Early in the feature ideation process, we consider how we can make it inclusive. This includes:

• exploring how the feature will be used, and on which devices;
• ensuring the application can be used in its entirety on even the smallest screens, right down to 320px;
• standardising the font-sizes and typefaces used to ensure they are readable, for example:
  • the default font-size throughout the application is 16px;
  • ensuring any elements that are necessary for normal usage of the application have a contrast of at least 4.5:1, meeting WCAG AA standards for contrast. To check contrast, we use WebAim, Google Lighthouse, Chrome's developer tools, Figma plugins and our experienced eyes;
  • we primarily use Roboto in our application (which is a sans-serif typeface), and this makes our application easier to read.

👀 Designing for the colour-blind

1 in 12 men and 1 in 200 women suffer from some form of colour-blindness. There are three types of colour-blindness:

• Protanopia is a red weakness
• Deuteranopia is a green weakness
• Tritanopia is a blue/yellow weakness

In extreme cases (1 in 33,000 people), someone may have monochromacy, where they cannot see colour.

Therefore, we think of these people when designing our app and experience.

For example, when developing our analytics feature we added a toggle which would change the colour scheme to one which has more contrast and should allow those impacted by colour-blindness to understand the data visualisations we offer.

VerifyEd analytics with default colours

VerifyEd analytics with an alternate colour scheme which is more understandable for those with colour-blindness

We use icons and text to indicate the context of data. For example, if data increases or decreases between a time-period the user will see an up or down icon, while if there is no change there will be a horizontal arrow.

Icons and text help convey context about the data we show