Accessibility

When we build content in Vega, we strive to create content which is usable and accessible for all users. This means that we need to understand that there are those who are differently-abled, who may have issues accessing and manipulating content in the same way as others.

Criteria that can affect how someone perceives content on a website must consider individuals with disabilities in any of the following ways:

  • Visual acuity, ranging from difficulties in differentiating colors on a page to full blindness
  • Hearing impairment, which must be taken into account when using any sound on a page.
  • Other physical limitations, such as the ability to move a pointing device.

For this reason, Vega follows a “universal design” approach. Content in Vega must be accessible for the widest possible audience, and provide options for those who may not be able to use standard methods.

Best Practices

One of the main things we think about when approaching a website is usability. This applies to all users. If we make our sites easily accessible by differently-abled users, this will translate into a positive user experience for all users.

Whenever possible, Vega follows the Web Content Accessibility Guidelines (WCAG) version 2.0 and 2.1.

Predictable Content

When web pages appear, they should be rendered in predictable ways. For instance, if a component receives focus, it should not instantiate a change of context until a user makes a specific action. Similarly, most components, such as toggles, should not immediately change the context of the application. For more information, view the WCAG guidelines.

Readability

Wherever possible use simple language that is easy to read and understand.

Typography

In Vega, we use the Inter font because of its ease of reading, and its professional look.

Color Contrast

It is important to use clear enough contrast so that readers with sight disabilities, such as color-blindness can adequately discern differences in content. The color contrast ratio in most cases should be at least 4.5:1, except for large text, which can have a 3:1 ratio. For more information, view the WCAG guidelines.

Keyboard Accessibility

Not all users are able to use a pointing device. In fact many users of a wide range of abilities prefer to use a keyboard to navigate a website. For this reason, Vega has attempted to make navigation fully accessible through the user of the keyboard, where users can tab through content.

Support for Assistive Technology

Vega provides support for the following technologies:

  • Screen Readers
  • Speech Recognition software
  • Alternative Keyboards
  • Readability Tools

Avoid overly decorative animations

Any animations on the page should be specifically to assist using the site, and not for decorative purposes. It’s especially important to avoid any flashing content, especially that which may cause seizures in some users.