Which screen readers do you test with?

NVDA, JAWS, VoiceOver (macOS and iOS) and TalkBack (Android). We agree with you which combinations matter most for your audience.

Do you test apps and internal systems too?

Yes. We test native and hybrid apps, web apps and complex internal systems, not only public websites.

Can you test in Hebrew?

Yes. We test Hebrew, English and mixed RTL/LTR content, which is where many reading-order issues appear.

Screen Reader and Assistive Technology Accessibility Testing

Web access for everyone regardless of disability.

The short answer: assistive technology testing means our experts use your website, app or system the way people with disabilities do: with screen readers such as NVDA, JAWS, VoiceOver and TalkBack, with only a keyboard, with screen magnification and with voice control. It finds the barriers automated scanners miss, and every finding comes with a clear fix.

An automated scan can tell you a button has no label. It cannot tell you that a blind customer gets stuck halfway through checkout. For 9+ years, that second kind of finding has been the core of our work.

What we test with

Screen readers

NVDA and JAWS on Windows, VoiceOver on macOS and iOS, TalkBack on Android. In Hebrew and English, including mixed right-to-left and left-to-right content.

Keyboard only

Every action without a mouse: visible focus, logical tab order, skip links, menus, dialogs and custom widgets.

Magnification and zoom

Browser zoom up to 400%, system magnifiers and large text settings, checking that nothing is cut off or overlaps.

Voice control

Voice Control on iOS and macOS and Windows Voice Access, checking that visible labels match what users say.

What we look at

Key user journeys: sign up, log in, search, forms, purchase, booking and contact.
Structure: headings, landmarks, page titles and language.
Controls: buttons, links, menus, tabs, accordions, carousels and modals.
Forms: labels, instructions, error messages and how they are announced.
Dynamic content: live updates, loading states, notifications.
Media: captions, transcripts, alt text quality.

What you receive

A report organized by page or screen, with each issue’s location, the affected WCAG criterion, who it affects and how to fix it.
Short screen recordings for the issues that are hard to describe.
A priority order, so your team fixes the blockers first.
A retest after the fixes, and a summary you can use for your accessibility statement.

Who this is for

Teams launching a new site, app or major feature.
Organizations that have run automated scans and want to know what real users experience.
Product teams preparing for WCAG 2.2 AA, IS 5568 or EN 301 549.
Complex systems: portals, dashboards and internal tools.

How it works

Scope: we agree on the pages, screens and journeys to test.
Testing: our experts test manually with each assistive technology.
Report and walkthrough: we go over the findings with your team.
Retest: we confirm the fixes work with real assistive technology.

Want the full picture first? See our website accessibility testing service, or read about the accessibility process.

Talk to our team

Tell us what you need tested and we will suggest a scope that fits. Contact us.

Frequently asked questions

Scanners detect only part of the issues. Whether a flow actually works with a screen reader or a keyboard can only be confirmed by testing it.

4 Stages to taking care of the website accessibility

Checking the website accessibility following country regulation.

We start by first verifying the laws and regulations of each client’s country are in regulation. Then we make a complete website check of the WCAG guidelines. We consider your organization services, size and resources, the nature of your business and the impact accessibility would have on your organization.

Fixing The Unsuitable Accessibility That We Found On The Website

After checking all the regulations and requirements, we move to fix the unsuitable issues and bugs on your website that may hinder our workflow or affect the process.

Making an additional check With Assistive Technologies

In the third stage, we make use of Assistive technology (AT) is any device, software, or equipment used to maintain or enhance the functional capabilities of people with disabilities. Common tools include an alternative keyboard or mouse, screen magnifier, screen reader, and voice recognition software.

Writing a full and detailed accessibility declaration

After we have resolved all the issues and bugs and fulfilled all your requirements by regulations, we then write an accessibility declaration statement with your internal organizational policies, your accessibility goals, and your commitment to providing a fully accessible website to serve and work with people who have disabilities.