Use Case in Software Testing: How to Turn One Into Test Cases
Every path through a use case becomes at least one test case. A worked bank-transfer example shows the test table, and ISTQB's 2023 and 2025 syllabus changes explain…
Accessibility Testing Services: Manual, Screen Reader, WCAG
Vervali tests accessibility with people and assistive technology: automated scans, manual expert review, keyboard and focus, NVDA, JAWS, VoiceOver and TalkBack on real hardware, plus the same pass on mobile, inside the development cycle. Facing an ADA deadline or a VPAT request? See our ADA and Section 508 compliance testing (WCAG 2.2 AA).
150+ clients
450+ projects
275+ engineers
15+ years
ISO/IEC 17025:2017Accredited testing laboratory
CMMI Maturity Level 3The process is written down and repeats
ISO 9001:2015Quality management
ISO/IEC 27001Information security
What Accessibility Testing Covers
Automated scans find mechanical defects. Manual, keyboard and screen-reader testing proves whether people can complete the journeys that matter.
Automated Scanning
Fast, wide, and incomplete. Contrast, missing names, empty buttons. It cannot tell you whether alternative text is useful. We run a scan so the cheap defects are not billed as expert hours. We do not sell the scan as the audit.
Manual Expert Review
The criteria a scanner cannot evaluate: whether alternative text describes the image, whether headings make a document, whether an error can be understood, whether a custom widget matches its role. That is most of the work a user would actually fail, and it is where the quote is spent.
Assistive Technology
NVDA, JAWS, VoiceOver and TalkBack on real hardware. Not a simulation in a browser pane. The pass is whether a person can complete the task, not whether a tool reported zero issues.
Keyboard and Focus
Can a person reach every control, see where they are, and finish without a mouse. Focus order is the failure users hit first. It is its own pass, not an add-on to a scan.
Mobile Apps
The same manual and assistive-technology pass on iOS and Android, including TalkBack and VoiceOver. Web and app can be one engagement when they share templates. They are not the same test. Mobile is named in the quote so it is not a surprise after kickoff.
Need a screen-reader pass, not a scanner PDF?
Testing Inside the Development Cycle
Prevent accessibility debt before release: review designs early, fix shared components once, and keep critical checks in regression.
Design Reviews
Before anything is built, so a contrast or focus mistake is not copied onto two hundred pages. A Figma pass is cheaper than a production retest.
Component Libraries
A fix lands once, in the button, the form, the modal. That is how a product stays accessible after the first audit.
Accessibility in Regression
Accessibility checks on the same journeys that already make money, plus a definition of done that includes it. A ticket is not closed on a visual pass alone. Billed monthly if the product will still ship next quarter.
Tools and What They Miss
Scanners clear the mechanical layer quickly. Expert review covers the meaning, behaviour and task completion that tools cannot judge.
What the Scanner Catches
We name the scanner in the design: axe, WAVE or Lighthouse are typical first passes. They are good at contrast, missing names and empty buttons. That is the cheap layer. It is not the audit.
What a Person Still Has to Judge
Whether alternative text is meaningful, whether headings make sense, whether an error is understandable, whether a custom widget behaves as its role promises. A widget overlay is not a test. A PDF of scanner output is not a report a developer can act on.
Related reading: accessibility testing services in 2026, is my website ADA compliant, and ADA compliance for billing and payment portals.
Case Studies
Public-sector procurement and release testing where manual, keyboard and screen-reader evidence mattered more than a clean scan.
United States · public-sector HR software · web
Before: a federal procurement needed evidence the product could be used with a keyboard and a screen reader, and a scanner PDF was not that evidence. Vervali ran manual and assistive-technology testing across a large URL set, then retested. After: the product was ready to answer that procurement question.
Manual and screen readerLarge URL setRetest includedWeb application testing · accessibility add-on
On the same journeys already in a web test: keyboard and a screen reader, not a full-site audit. That add-on is quoted once we know how many templates those flows use.
Same flows as the web testQuoted as an add-onEngagement Models
Choose a one-off audit, remediation support or ongoing release coverage. Paid work follows templates and flows, with typical rates of $25 to $49 per hour.
One-Off Audit
Pages and flows you name, manual plus assistive technology, a report developers can act on. Suits a release or a procurement question.
Remediation Support
Sit with your developers on the ordered fixes. Retest is named in the quote. Suits a team that will change the code this month.
Ongoing in the Cycle
Design, components, regression. Billed monthly. Suits a product that will still ship next quarter. Ask for this shape in the call.
Frequently Asked Questions
There is not one. A scanner is the fastest first pass and misses most of what a keyboard or screen-reader user fails. NVDA, JAWS, VoiceOver and TalkBack on real hardware, plus a person, are the test. The best tool is the one that does not pretend alternative text quality can be scored automatically. We name the scanner in the design. We do not sell an overlay as a test.
Scan for the cheap defects, then walk the money paths with a keyboard, then with a screen reader on real hardware. Check focus order, names, errors and custom widgets. A free 10-page WCAG 2.2 AA spot audit, report in three business days, is how Vervali starts that look. A full site is sampled by templates, not by promising every URL.
Yes. VoiceOver on iOS and TalkBack on Android, plus keyboard-equivalent focus where the platform has it. Web and app can share an engagement when they share flows. They do not share a single scan. Mobile is named in the quote so it is not a surprise after kickoff. Device coverage for the rest of the app sits on mobile application testing.
WCAG is the technical standard: success criteria you can test. ADA is civil-rights law. Title II now points at WCAG 2.1 AA, while Title III is enforced through litigation with no named web rule. We test against WCAG 2.2 AA with assistive technology, so one set of findings answers both. For which law applies, the deadlines, VPAT and Section 508, see our ADA and Section 508 compliance testing.
Yes, on a monthly retainer: design reviews, component library checks, accessibility in regression, and a definition of done that includes it. It is not bundled silently into a one-off audit. A one-off audit still exists for a release or a procurement. Ask for the ongoing retainer on the call if the product will still ship next quarter, and we scope it around your release cadence.
Email Us
Call Us
