Skip to content

accessibility.md

Latest commit

 

History

History
33 lines (21 loc) · 1.62 KB

accessibility.md

File metadata and controls

33 lines (21 loc) · 1.62 KB
Raw

Accessibility

This document highlights how we have secured universal accessibility on our web page, and what we have based our choices on.

Accessibility Standards

We have taken the Web Content Accessibility Guidelines (WCAG) into consideration when trying to improve the accessibility of our webpage.

The WCGA is "built" on four pillars:

  • Perceivable:
    • How is the content presented to the user.
  • Operable:
    • User interaction.
  • Understandable:
    • Clearness and predictability
  • Robust:
    • Contents work across multiple technologies, including assistive tools.

Implementation

Testing tools

We have used variuos tools for testing the different aspects of accessibility on our page. The tools we have used are WAVE, Axe Development Tools and Google LightHouse. These tools help check and improve web accessibility in a complete and easy way. They help identify issues like missing alt text, contrast errors, ARIA usage, and WCAG compliance, while providing actionable insights to enhance user experience and ensure inclusive design.

Labels and Classnames

During the development process we have keept focus on descriptive classnames/id's for components. Where this has not been sufficient we have added ARIA-labels to ensure high accessibility. We have also implemented ARIA-live alerts to improve accessibility for users with assistive technologies.

Contrasts

Using the different web extention tools we got feedback on where we needed to improve the contrasts on our web page. This includes all hover-effects and toggles on drop-down menues. We have ensured that all our text have a strong enough contrast to the background.