Text to Speech: Making Digital Content Accessible to Everyone

What Is Text to Speech and Why Is It Important?

Text to speech, also called speech synthesis, turns written text into audible speech using artificial intelligence. Modern voices sound natural and make content accessible to far more people. That is why the technology is a natural part of modern web design.

The need is large, and the numbers show why:

• The World Health Organization estimates that 1.3 billion people, roughly 1 in 6, live with a significant disability.
• Between 5 and 10 percent of the population has dyslexia (Store norske leksikon).
• 1 in 4 Norwegian students report having a disability (Statistics Norway).

The technology is especially important for:

• People with visual impairments who use screen readers
• People with dyslexia or other reading and writing difficulties
• Users who prefer auditory learning over visual
• People who want to consume content while doing other activities
• Elderly users experiencing age-related vision challenges
• People with cognitive disabilities

Universal design is also a legal requirement in Norway. The regulations on universal design of ICT apply to both public websites and private websites aimed at the general public. The Norwegian Digitalisation Agency's supervisory body (Uu-tilsynet) can order corrections and impose coercive fines. At Mementor we help businesses meet the requirements in a simple way.

Which Requirements Apply in Norway in 2026?

The requirements are split between the private and public sector. Here is the overview:

• Private businesses: websites must meet 35 requirements from WCAG 2.0, and apps must meet 29 requirements. The audio description requirement is exempt.
• Public organizations: must follow 48 of 78 requirements in WCAG 2.1. They must also publish an accessibility statement on uustatus.no.
• Audio description: public organizations must provide audio description for videos published on or after 1 February 2024.
• WCAG 2.2: arrived in October 2023 but is not yet part of Norwegian regulations. Feel free to follow 2.2 anyway, and you are prepared for the next update.

The EU Accessibility Act (EAA) applies in the EU from 28 June 2025. The directive sets requirements for online stores, banking services and e-books in the private sector, among others. Norway has not yet incorporated the directive into Norwegian law, because the EEA process is delayed. If you sell goods or services to customers in the EU, you must follow the requirements regardless.

A new version of the EN 301 549 standard is expected to be adopted during 2026. It ties the requirements closer to the EAA. Always check uutilsynet.no for updated requirements.

Technical Requirements and WCAG Standards

WCAG (Web Content Accessibility Guidelines) are international guidelines for accessible web content. The guidelines build on four principles: perceivable, operable, understandable and robust. Norwegian and European legislation build on this standard.

You can find the complete overview of the WCAG standard at Uutilsynet or explore the interactive WCAG Quick Reference at W3C. When it comes to text-to-speech and screen reader compatibility, the following principles are particularly relevant:

1. Text Alternatives for Non-text Content

All images, graphics, and other visual elements must have descriptive alternative text (alt text) that can be read by screen readers. This is fundamental for visually impaired people to understand the content on a webpage. The requirements include:

• Informative images that convey important content must have descriptive alt text
• Complex diagrams and infographics require detailed descriptions
• Decorative images should be marked as such to avoid unnecessary reading
• Icons and buttons with functionality must have text describing the action
• Images of text should be avoided, but if used, the text must be reproduced in the alt attribute

2. Correct Semantic Structure

Webpages must be coded with proper HTML structure for screen readers to interpret and navigate the content effectively. This means that developers must be careful about how they structure the code:

• Headings must use correct HTML tags (h1-h6) in hierarchical order
• Lists must be marked as ordered or unordered lists
• Tables must have proper headers and relationships defined
• Navigation elements must be clearly marked with nav tags
• Main content must be marked with the main tag
• Page footer and header must use footer and header tags

3. Keyboard Navigation

All functionality must be accessible via keyboard, as many screen reader users navigate without a mouse. This is a fundamental principle for accessibility and requires thoughtful implementation:

• All interactive elements must be reachable with the tab key
• Focus indicators must be clear and have sufficient contrast
• Skip links to main content should be available as the first element
• Tab order must be logical and follow visual order
• Keyboard shortcuts must not collide with screen reader commands
• Modal dialogs must handle focus correctly

Implementing Screen Reader Support

To ensure that webpages work well with screen readers such as JAWS, NVDA, and VoiceOver, developers must follow best practices and test thoroughly throughout the development process. Here are the most important areas to focus on:

WAI-ARIA Implementation

ARIA (Accessible Rich Internet Applications) attributes provide additional information to assistive technology. Proper use of ARIA can significantly improve the user experience for screen reader users, but incorrect use can make things worse. W3C has extensive documentation on WAI-ARIA standards and guidelines. The following principles are important:

• Use role attributes to define the element's function when semantic HTML is not sufficient
• Implement aria-label and aria-describedby for additional context
• Mark dynamic content with aria-live regions for important updates
• Use aria-expanded for elements that can be expanded/collapsed
• Implement aria-current to indicate the current page in navigation
• Avoid overriding semantic HTML with ARIA when not necessary

Testing with Screen Readers

Regular testing is crucial for ensuring quality. Testing should be an integrated part of the development process, not just something done at the end. Here is a systematic approach:

• Test with multiple screen readers (NVDA on Windows, VoiceOver on Mac/iOS, TalkBack on Android)
• Navigate using only the keyboard throughout the entire website
• Check that all information is available and understandable without visual context
• Verify that interactive elements are announced correctly with role and state
• Test with different reading speeds to ensure comprehensibility
• Include actual users with disabilities in the testing process

Practical Examples of Speech Synthesis Solutions

There are many different solutions for text to speech, from built-in system functions to dedicated tools. The choice depends on needs and technical skills. For WordPress websites we have built our own text to speech plugin with natural ElevenLabs voices. The player at the top of this article uses the same solution.

For Webpages and Documents

Modern browsers and operating systems have built-in support for reading aloud that is continuously improving. The most commonly used solutions include:

• Windows: Narrator (built-in) and NVDA (free, open source)
• macOS/iOS: VoiceOver (built-in with extensive functionality)
• Android: TalkBack (built-in) and Voice Access
• Chrome/Edge: Built-in reading functions and extensions
• JAWS: Professional screen reader with advanced features
• Audio and Braille displays for combined auditory and tactile feedback

For Specialized Needs

Tibi (formerly the Norwegian Library of Talking Books and Braille) is the library for you who have difficulty reading visual text due to disability or illness. They have developed specially adapted solutions for Norwegian users, and their speech synthesizers are optimized for Norwegian language and dialects:

• Clara reads Bokmål with an Eastern Norwegian tone
• Hulda reads Nynorsk with a Western Norwegian tone
• William reads English study literature
• Tibi has around 100,000 borrowers, and the service is free for everyone with borrowing rights

Common Challenges and Solutions

Implementing good screen reader support comes with several technical and design challenges. Here are the most common problems and how they can be solved:

Challenge 1: Complex Interactive Elements

Modern web applications often use JavaScript-based components that can be difficult for screen readers to interpret. Particularly challenging are custom-developed components that don't follow established patterns.

Solution: Use progressive enhancement and ensure that basic functionality works without JavaScript. Implement ARIA attributes correctly for dynamic elements. Test thoroughly with actual screen readers, not just automated tools. Consider using established component libraries that have good accessibility support built in.

Challenge 2: PDF Documents

PDF files are often problematic for screen readers if they are not properly tagged. Many PDFs are essentially images of text, completely inaccessible to assistive technology.

Solution: Use tools like Adobe Acrobat Pro to ensure that PDFs are semantically correctly tagged. Add heading structure, alternative text for images, and correct reading order. Always consider offering HTML alternatives for important documents. For forms, use interactive PDF fields that are accessible.

Challenge 3: Multimedia Content

Videos and audio clips require special adaptation to be accessible. This goes beyond just captioning and includes several aspects.

Solution:

• Provide captions for all video with audio, synchronized and accurate
• Create transcriptions for pure audio clips that can be read with a screen reader
• Provide audio description if you are a public organization. The requirement applies to video published on or after 1 February 2024
• Ensure that video players are accessible with keyboard controls
• Provide the ability to adjust playback speed
• Avoid autoplay that can disrupt screen reader use

Challenge 4: Multilingual Content

Screen readers need to know which language is being used for correct pronunciation. Incorrect language settings can make content incomprehensible.

Solution: Use the lang attribute consistently both at the document level and for text in languages other than the main language. For example: <span lang="en">“Hello world”</span> in a Norwegian document. This ensures that the screen reader switches to the correct voice and pronunciation.

Challenge 5: Dynamic Content and Single Page Applications

Modern frameworks like React, Vue, and Angular create challenges for screen readers when content changes dynamically without page loading.

Solution: Implement ARIA live regions for important updates. Handle focus correctly during route changes. Use announcements to inform about state changes. Test thoroughly with screen readers throughout the entire user journey.

The Future of Text-to-Speech Technology

Artificial intelligence is driving the development. The voices get more natural every year, and support for Norwegian keeps improving. These are the most important trends going forward:

• More natural voices that are difficult to distinguish from human speech
• Better handling of Norwegian dialects and unique expressions
• Smarter context understanding for more precise reading of abbreviations and numbers
• Integration with new platforms and devices, including IoT
• Real-time translation combined with speech synthesis
• Personalized voices tailored to individual preferences

The National Library of Norway has developed NB-Whisper, a Norwegian model that turns speech into text. National initiatives like this ensure that Norwegian-speaking users get solutions as good as English-speaking ones. Accessible content also comes with a bonus: the structure that helps screen readers also helps AI models understand and cite your content. That is the core of AEO optimization.

Best Practices for Implementation

Successful implementation of text-to-speech support requires a complete approach. Here are concrete steps to get started:

1. Start with Basic Accessibility

• Conduct an accessibility audit of existing content
• Implement semantic HTML as a foundation
• Add missing alt texts to all informative images
• Check and correct the heading hierarchy
• Ensure sufficient color contrast (at least 4.5:1 for normal text)

2. Test Continuously

• Integrate accessibility testing in CI/CD pipeline
• Use automated tools like axe or WAVE
• Conduct manual tests with screen readers
• Include users with disabilities in user testing
• Document and follow up on found problems systematically

3. Build Competence in the Organization

• Arrange workshops on universal design
• Share knowledge and experiences across teams
• Establish guidelines and checklists
• Ensure that all new employees receive training
• Stay updated on new requirements and best practices

How Mementor Can Help You

We help you from assessment to finished solution, without complicating the process.

• Accessibility review: we test your website against the WCAG requirements and give you a concrete list of what needs fixing.
• Development that follows the requirements: we build websites and web solutions with semantic HTML, keyboard navigation and screen reader support from the start.
• Text to speech on your website: our WordPress plugin reads your posts aloud with natural voices.
• Ongoing maintenance: with a Service Level Agreement (SLA) we keep your website updated as the requirements change.

Frequently Asked Questions

Conclusion

Text-to-speech technology is no longer a luxury but a necessity for creating an inclusive digital society. By following WCAG guidelines and implementing thoughtful solutions for screen reader support, businesses can ensure that their digital content is accessible to all users, regardless of ability.

Universal design is about more than legal requirements. It is about giving everyone equal opportunities to participate in the digital society. When we design for those with the greatest needs, we create better solutions for everyone.

Start with small steps: check that your images have good alt text, test your website with a screen reader, and gradually build up competence in the organization. Every improvement, no matter how small, makes a difference for someone.