Close countries panel

Select country

For solutions in a specific country please visit our local website

​​It is of utmost importance that all Nets products and services are easy to use for everybody.

Nets online design system is compliant to WCAG 2.1A+AA+AAA http://www.w3.org/TR/WCAG21/ , meaning we create excellent user experience for all end-users, also for those with, for example color blindness, dyslexia, blindness or partial sight, hearing loss, motor or cognitive disabilities. This includes end-users who use screen readers.

Also, the front-end code for all UI components is semantically correct and WCAG 2.1 A+AA compliant.

 

Guides for creating accessible design solutions:

  • Design for keyboard or speech only use
  • Design with mobile and touchscreen in mind
  • Eliminate time constraints or provide Users enough additional time to allow them to complete their tasks
  • Make large clickable actions
  • Give form fields space
  • Use a linear, logical and consistent layout
  • Break up content with sub-headings or images
  • Keep content short, clear and simple
  • Use plain language
  • Make sure that text is left aligned
  • Make all headers and clickable elements descriptive
  • Describe all images in ALT text and provide subtitles for video
  • Ensure a copywriter has checked all content
  • Ensure the design is accessibility tested and approved (see below)

 


 

Accessibility tests

To ensure that End-users with different types of disabilities find it easy to use the Nets digital solutions, it is important to test the design on multiple test platforms – with and without user involvement, as described below;

 

 

Online tests

Evaluate the design concepts during development via these online test tools:

  • Screen reader check tool
  • Contrast & colour checker
  • LIX validator

 

 

User tests

In order to ensure an intuitive and accessible solution:

  • Include Users with disabilities in target group scope:
    • Motoric
    • Visual
    • Cognitive
    • Hearing   
  • Perform User Tests with disabled Users from the target groups throughout the development process; Observations in conjunction with Think Aloud and interviews
  • Perform a final accessibility audit for WCAG 2.1 A+AA compliance check, before launch
  • Post Launch Test; include disabled Users in the test