Digital accessibility audit of ReadSpeaker webReader

Executive summary

The Readspeaker tool was evaluated between 1 and 18 november 2024 and re-tested between 1 and 15 april 2025. The re-test showed that all issues found during the initial audit in November 2024 were resolved. The evaluation was conducted using the WCAG-EM methodology. The purpose of this report is to identify the necessary improvements to enhance the accessibility of this digital product.

The Evaluation Result

The assessment SC
Compliant 55
Not compliant 0
Total 55

From the auditor

We would like to take a moment to commend the team for their excellent work in enhancing the accessibility of this tool. The improvements made demonstrate a strong commitment to inclusive design and user experience, and they represent a significant step forward in ensuring the tool is usable by a wider range of individuals. Your efforts are clearly reflected in the positive outcomes of this audit, and we congratulate the team on this achievement.

Evaluated by:
Julia T and Julia F van Proper Access
Commissioned by:
ReadSpeaker
Software by:
ReadSpeaker
Date:
15 april 2025
Methodology:
WCAG-EM
Standard:
WCAG 2.2 and EN 301 549
Target level:
WCAG 2.2, Level AA
Scope of the audit

In scope:

  • All screens of the ReadSpeaker webReader tool
  • Not the website where the tool is placed
Accessibility support baseline
  • Mozilla Firefox, version 137
  • Google Chrome, version 134
  • Apple Safari, version 18
  • NVDA screen reader in combination with Firefox
  • VoiceOver screen reader in combination with Safari
  • Common browsers and assistive technologies
Technologies used in webReader
  • HTML
  • CSS
  • JavaScript
About this audit

Reading Guide

This report is structured around the webReader tool content, allowing you to address accessibility issues screen by screen. This approach facilitates a more efficient workflow. Each identified issue includes examples, but these are not exhaustive. It is crucial to check for similar issues throughout the webReader tool.

Standard Used

This evaluation assessed the webReader's compliance with WCAG 2.2 Levels A and AA, the international standard for digital accessibility. WCAG (Web Content Accessibility Guidelines) is also included in the European standard EN 301 549. This report provides concise descriptions of the success criteria. For detailed information, refer to the WCAG documentation and in Swedish Webbriktlinjer.

Evaluation Methodology

This evaluation employed the WCAG-EM research methodology developed by W3C. The evaluation process involved:

  • Defining the scope
  • Identifying technologies used
  • Creating a sample
  • Evaluating the sample
  • Describing identified issues

The evaluation was primarily manual, with automated tools like axe-core and Chrome Developer Tools used for specific criteria.

Important Considerations

This report is a valuable tool for improving webReader's accessibility. However, it's essential to acknowledge its limitations:

  • Sample-Based Evaluation: The sample-based approach may not uncover all accessibility issues.
  • Falsification Principle: The evaluation focuses on identifying non-compliance rather than confirming complete compliance.
  • Evolving Insights: Interpretations of the WCAG standard can evolve, leading to potential variations in future evaluations.
  • Potential for New Issues: Addressing one accessibility issue might inadvertently introduce another.

Regular evaluations are crucial for maintaining and improving webReader tool's accessibility.

Priority in Solving Issues

When determining the priority of the issues mentioned in this report, you can follow one of the common approaches:

Level of Success Criteria

  • Level A of WCAG 2.1 → Priority 1
  • Level AA of WCAG 2.2 → Priority 2
  • The five new criteria in WCAG 2.2 are not yet part of EN 301 546 → Priority 3

Most Critical Issues

Keyboard accessibility: If an element is not accessible via the keyboard, it is also inaccessible to visitors using screen readers and fails other success criteria beyond vision-related ones.

Knoledge of your audience

You know your target audience best and can prioritize resolving identified issues based on the needs of the people who use your tool.

Sample
  • Lees voor widget

    Click on the the “Lees voor” button to open the player.

  • Lees voor pop-up player

    Click on the “Lees voor” button. See the lower right corner of the page.

  • Pop-up “Instellingen”

    Click on the menu button with three horizontal lines. Select “Instellingen”.

  • Pop-up “Tekstversie”

    Click on the menu button with three horizontal lines. Next, select “Tekstversie”.

  • Pop-up “Pagina maskeren”

    Click on the menu button with three horizontal lines. Next, select “Pagina maskeren”.

  • Pop-up “Download mp3”

    Click on the menu button with three horizontal lines. Next, choose “Download mp3”.

  • Pop-up “Hulp bij vertaling”

    Click on the menu button with three horizontal lines. Next, select “Hulp bij vertaling”.

  • Pop-up “Help”

    Click on the menu button with three horizontal lines. Next, select “Hulp”.

  • Vergroot tekst functionality (Enlarge text)

    Click on the menu button with three horizontal lines. Select “Vergroot tekst”. Press “Lees voor”.

  • Klik en lees voor functionality (Click and read)

    Click on the menu button with three horizontal lines. Select “Klik en lees voor”. Press “Lees voor”.

  • Selected text menu

    Select any text on the page to see this functionality.

  • Pop-up “Woordenboek” (selected text)

    Select any text on the page and click on “Woordenbook”.

  • Pop-up “Vertalen” (selected text)

    Select any text on the page and click on “Vertalen”.