Have you ever wondered why some websites feel uncomfortable to use – especially when you’re in a hurry, using a small screen, or simply having a rough day? The answer might be that these websites are not accessible.
Accessibility means that products and services, including websites and web applications, are designed so that everyone can use them, including people with disabilities.
In this article, you will learn how to start testing websites for digital accessibility.
Who is accessibility really for?
Ensuring accessibility is not only a legal obligation (arising, among others, from the European Accessibility Act and the related WCAG 2.1 standard) – it is also an opportunity to reach more customers and build the image of a modern, thoughtful organization.
In addition, accessibility benefits all of us. Apart from people with permanent disabilities (visual, auditory, motor, or cognitive), accessible applications also help:
- older adults,
- people who are tired and need simple, intuitive interfaces,
- people with temporary limitations, such as a broken leg, an injured hand, or parents pushing a stroller,
- people using the internet in difficult conditions (e.g., in bright sunlight or noisy environments),
- foreigners for whom the local language is not their native one.
Just as with any other element of the software development process, accessibility should be designed and tested by the project team. For some products or services – such as medical platforms, government systems, or information portals – careful implementation of accessible solutions is particularly important and should be considered a priority.
When should testing start?
In digital accessibility, early testing – already at the mockup and design stages – is essential. It is estimated that up to 70% of accessibility issues can be identified and resolved before development even begins, making them far faster and cheaper to fix than modifying fully built components later on.
Early testing helps capture problems related to:
- element size and spacing,
- navigation between screens,
- text and image contrast,
- or the size and choice of fonts.
This is not easy; it requires domain knowledge, attention to detail, and awareness of assistive technologies your users may rely on.
How to test effectively?
Accessibility testing requires understanding correct HTML structure (semantic HTML), because assistive technologies used when browsing the web, such as screen readers or switch devices, rely heavily on HTML. When the code is clean and semantically correct, users are much more likely to navigate your website without difficulty.
In addition, many user behaviours can be simulated with free or paid testing tools that extend standard code analysis and present results clearly, enabling deeper evaluation.
One of the most popular and widely accessible tools for accessibility testing is Wave.
Wave is a browser extension (Chrome, Firefox, Internet Explorer) that analyses HTML structure, highlights accessibility errors (e.g., heading hierarchy issues, insufficient colour contrast, missing alt text), and also shows properly implemented accessible solutions (such as aria-label). This allows testers to work and learn accessibility at the same time. Interestingly, Wave itself is an accessible tool; it uses both colour and icon markers, and it is fully usable with a screen reader. This means that even testers with disabilities can use it to analyse accessibility.
Accessibility testing techniques
While a full accessibility audit requires deep expert knowledge, you can identify many fundamental issues independently. Remember: automated tools do not replace manual testing or a user-first perspective. The best practice is to continually verify your assumptions using authoritative sources such as the WCAG guidelines or official developer recommendations.
A few simple manual tests you can start with today
Keyboard navigation
(For users with motor disabilities and for screen reader users)
Many people, including screen reader users and people with limited hand mobility, do not use a mouse – they navigate solely with a keyboard.
How to test:
- Put your mouse aside. Test using only the keyboard.
- Use the TAB key to move through all interactive elements (links, buttons, form fields, media controls).
- Check the order. Ensure the navigation flow is logical – typically top-to-bottom, left-to-right. To go backward, use Shift + TAB.
- Check focus visibility. The element in focus must be clearly visible (e.g., highlighted with a border).
- Ensure that once you enter an element (e.g., a form field or modal), you can exit it using the keyboard without reloading the page.
Testing non-text content
(Images, graphics, multimedia)
People who are blind or low-vision use screen readers (e.g., NVDA), which read aloud the content of the page. Creators must ensure all users can access the information on the site.
How to test:
- Check whether each image or graphic (that is not decorative) has an appropriate alt text that conveys its meaning.
- Do not begin alt text with “image of” or “picture” – the screen reader already knows it’s an image. Keep the description concise.
- If the image is purely decorative and conveys no important information (e.g., a separator line), alt=”” should be used so the screen reader skips it.
- For videos, provide alternatives for audio and visual content – closed captions for deaf users and audio description for blind users. A transcript is also a great addition.
Tools to help you begin testing accessibility
You don’t need expensive software. Most tools are free, built into browser DevTools, or available as extensions. Useful browser extensions include.
Silktide (Chrome)
Silktide, like Wave, scans a site’s HTML structure according to the chosen WCAG guidelines (2.0, 2.1, or 2.2).
It is particularly helpful for verifying:
- adequate colour contrast between elements,
- whether content and layouts are readable for users with visual impairments,
- the clarity and structure of longer texts, helping ensure they are understandable for users with cognitive challenges, such as dyslexia.
Headings Map (Chrome)
This extension visualizes the page heading structure, enabling direct navigation to different sections via the generated outline.
Tests should also include screen readers and checking the website across various device types (laptops, tablets, phones with different screen sizes and operating systems).
The most popular screen readers
- NVDA (Windows): A free screen reader. To understand how users experience your website, try installing NVDA and using it on your site. Keep in mind that learning screen reader navigation takes time. Download
- TalkBack (Android): A built-in Android screen reader that enables navigation using gestures and spoken feedback. It lets users read messages, browse apps, and use the web without needing to look at the screen.
- VoiceOver (MacOS / iOS): Apple’s integrated screen reader is available on Macs and iPhones, offering advanced gesture controls, keyboard shortcuts, and support for Braille displays. It provides detailed voice feedback describing everything on the screen and works the same way across computers and mobile devices. VoiceOver is also the most widely used screen reader among blind users.
Testing & QA
Ensure the quality, performance, and security of your software with our testing and test automation services.
Testing&QA offeringDigital accessibility is our shared responsibility
Remember: accessibility is an ongoing process, not a one-time task. Testing alone, or even running a professional audit, is not enough. Issues must be fixed, and since web applications constantly evolve, new features or UI changes may unintentionally break previously accessible components.
Despite these challenges, if you haven’t tested accessibility before, following the steps above will already make your web application more welcoming and inclusive for all users.
If you need additional support, you can consult:
- PFRON guidelines,
- Ministry of Digital Affairs guidance,
- online accessibility checklists,
- accessibility specialists.
Leave a comment