Accessibility

Why should we care?

About 4% of the population has some form of colour-blindness. One in 12 men and 1 in 200 women are colour-blind and face daily challenges with websites, apps, and games.

Why is it important?

It's the law. WCAG 2.0 was added as part of the Equality Act 2010 (UK). For more information please see the Web Content Accessibility Guidelines (WCAG) website.

Rule of 8

To make sure I uphold the principles, I have further defined how I aim to meet the AA standards of WCAG. As well as upholding our my own principle of design, develop, and deliver, I have created 8 rules for accessibility that can be easily followed.

Accessibility rules

Colour contrast

The elements used in our applications must provide visual affordances by passing the WCAG 2.0 AA standard for contrast ratio between text and background.

Typography

Use 16px as our body font and 14px for tabular data representation to ensure that the user can see all information without scrolling. Headings, body copy, and caption sizes use a combination of size, weight, and colour to ensure they’re distinct enough but related to help with reading.

Layout and hierarchy

Create a clear hierarchy of importance by ensuring that items on screen are positioned relative to their importance. Group items in proximity to one another to help those who have low vision or trouble focusing on the screen.

Keyboard access

Every interactive component must have a visible focus state that allows users to navigate using the keyboard or other tool.

Data visualisation

Ensure the data visualisation used is appropriate and data and variables are clearly labelled. Provide context with a brief description of the data visualisation. Ensure there is sufficient contrast between graph colours so users with colour-blindness can distinguish the colours.

Tone of voice

Be clear and avoid jargon where possible.

Credible

We write clearly and don't use misleading language or confusing terminology. We can be trusted because we understand what we write about. We make our users feel confident about using our products.

Considerate

We recognise that our users have a variety of needs and make sure that all users can do their best work with our products. We use simple language with no idioms or colloquialisms. We don’t talk down to people, and we don’t assume they know too much. We make our users feel supported and accomplished while they're using our products.

Conversational

To write the way we talk so our users feel like we’re addressing them personally. To say as much as is needed to users in as few words as possible – without sounding terse. By using natural language, with no slang or excessive jargon. To make our users feel like we're working with them.

Forms

Form fields must be labelled and have clearly-defined boundaries and outlines so that people with cognitive disabilities know the size and location of the click target. Danger states must be highly visible and use multiple cues like colour, icons, bold font, heavy border or outline, and helpful text to make sure users don’t overlook this critical information.

Language

To find the best language font to convey the language correctly, making it easier for global users.