Accessibility statement for Prenly

Accessibility statement for Prenly

Introduction

At Textalk, we work to ensure that our platform is as accessible as possible for all users. This accessibility statement describes which parts of the platform do not meet accessibility requirements, as well as how we work to identify and correct accessibility issues.

The statement covers the platform itself, for example:

• The web application https://thisis.prenly.com/

• The iOS application Prenly (https://apps.apple.com/us/app/prenly/id6736682103)

• The Android application Prenly (https://play.google.com/store/apps/details?id=com.prenly.thisis)

Platform and customer adaptations

The platform strives to follow applicable European accessibility standards, but some parts do not yet fully meet the requirements. Customers can for example customise the platform according to their brand colours, which may affect accessibility. Another example is alt text: the platform enables alt text, but customers are responsible for providing it.

We offer guidelines and support to help customers maintain or improve accessibility in their customised versions of the platform.

Digital accessibility status

Technical details and testing

The technical foundation of the platform has been tested against:

• WCAG 2.1 levels A and AA

• EN 301 549 (relevant for the European Accessibility Act, EAA)

Test methods

• Automated tests using axe DevTools, Lighthouse, and Wave Evaluation Tool on the web application

• Manual keyboard navigation testing – all platforms

• Manual contrast testing – all platforms

• Manual testing with screen readers – focus on the web application, partial testing with VoiceOver and Voice Control on iOS

Limitations

Accessibility issues may occur in:

• Customer colour choices and layout modifications

• Customer-provided content (e.g., images without alt text, non-descriptive link texts, videos without captions, advertising material, text that is not easy to read)

• Features, integrated systems, or third-party components outside our direct control (e.g., consent dialogs, login systems, embedded web views)

• Mobile applications that are not running the latest version.

Planned improvements

We continuously work to improve the accessibility of the platform’s core functionality. Ongoing or planned measures include:

Improvements for screen readers in the web application

• Support for system settings for dark/light mode (Android and iOS)

• Support for system settings for larger text sizes (Android)

• The next major review is planned for 1 November 2026 or in connection with major updates.

Content that is not fully accessible

Applies to Web, iOS, and Android

Views with images of entire newspaper pages

Some views contain images of full newspaper pages. According to guidelines, text should be presented as real text, not images. These images are used only as a visual representation. All text that customers define as editorial content is available in a simplified reading mode when the publication is opened.

Heading levels in replica mode

Replica mode lacks a main H1 heading, which affects structure and semantics for screen readers. However, this is not deemed to impact understanding of the content in reading mode.

Error message during login

When an incorrect password is entered, the message “Incorrect login details” is shown. It is not fully descriptive according to accessibility requirements, but more detailed information is not provided for security reasons.

Archive page and pagination

More publications load automatically as the user scrolls, by design. Pagination would not improve usability due to archive sizes (sometimes 100+ years). Publications are displayed in chronological order, and filtering and date/title search are available.

Podcasts

Some customers include podcasts; these are presented without transcripts, meaning the content is only accessible via audio. Article audio may also be used, however this content usually matches the written text.

Links on the start page

Some components use links (for example to multiple issues, archives, or podcasts) which rely solely on colour to indicate link functionality.

Applies to iOS and Android

Archive page – search field

The search field is a native component that lacks a visible “Search” button and therefore has no visible text label indicating a voice command. However, the search functionality works with common generic Voice control prompts such as “enter that”, and there is a Search button in the keyboard navigation.

Applies to iOS

External keyboards

Some assistive functionality is switched off due to a large number of previously reported crashes on iPads connected to external keyboards. Switching off these functions has improved stability and lowered the amount of crashes significantly.

Applies to Android

Article reading mode

There is no button to enter article reading mode when viewing a PDF/replica. Keyboard-only navigation cannot access reading mode.

Applies to Web

Screen readers with Mozilla Firefox

Article boxes cannot be opened to access the reading mode when using Firefox in combination with a screen reader. This works with other browsers.

Screen readers in zoomed-in mode

At browser zoom levels above 115%, the screen reader menu option becomes hidden.

“Skip to content”

There are currently no “Skip to content” links.

Missing screen reader notification in search filtering

When search results are filtered in narrow browser views, the filter panel covers the results. Applying filters updates the search results in the background, but no notification is provided to screen reader users. When the filter panel is closed and the updated results are shown, the change is still not announced.

Report issues and contact details

If you discover additional accessibility issues or want to provide feedback, please contact us:

• Email: hello@prenly.com

• Phone: +46 31-388 47 40

If you are not satisfied with our response, you may contact the Swedish Post and Telecom Authority (PTS). More information: https://www.pts.se/digital-inkludering

Review and Updates

This statement is updated at least once per year or in connection with major changes.

Last updated: October 2025