Design & UX Skill
Accessibility Compliance
Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns…
$15
Screen Reader Testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS.
A practical, command-level playbook for testing your web app with real screen readers including VoiceOver, NVDA, and JAWS, so you validate accessibility the way disabled users actually experience it. It covers the full assistive-technology chain from browser to accessibility tree to spoken output, with concrete fixes for the most common breakages like unlabeled icon buttons, silent dynamic content, and unannounced form errors. You move from guessing to verifying across the screen readers that cover the vast majority of real users.
$15 one-time
Add to a kit → Prices include 20% VAT. · Forged on real agency work · one-time, no lock-in
- Type Skill
- Category Design & UX
- Delivery Email · instant
- License One-time
Inside the run · no black box
See the actual work before you buy it.
An accessibility audit that never ran a real screen reader is a guess. NVDA, VoiceOver, and JAWS walk the page element by element, and divergent behavior gets triaged, not dismissed.
- Sets the coverage matrix first: minimum NVDA plus Firefox on Windows and VoiceOver plus Safari on macOS and iOS; comprehensive runs add JAWS, TalkBack and Narrator to cover roughly 90 percent of real usage.
- Walks page structure with each reader's own navigation keys: page title announced on load, all landmarks reachable, heading levels logical when browsed through the rotor or the elements list.
- Tests every interactive element against the announcement order of role, name, state and description: an icon-only button with no accessible name is a broken chain and gets an aria-label fix on the spot.
- Runs the form script: labels read together with inputs, required fields announced, an invalid submission moves focus to the error and the message is spoken through role=alert and aria-describedby.
- Validates dynamic content: aria-live regions announce updates, modals trap focus on open and return it to the trigger on close, and SPA route changes move focus to the new page heading.
- Cross-checks results between at least 2 screen readers, because identical ARIA can behave differently in NVDA Browse Mode versus JAWS Forms Mode; divergence is triaged as platform variance with a documented workaround, not a random failure.
One power source. 6 lines out.
screen-reader-testing · core
core active · 6 lines
- ✓ validate aria implementa…
Validate ARIA implementations against actual screen reader output
- ✓ debug why an icon button
Debug why an icon button announces nothing to VoiceOver
- ✓ test modal focus trapping
Test modal focus trapping and focus return on close
- ✓ verify form labels, requ…
Verify form labels, required fields, and error announcements
- ✓ confirm live regions ann…
Confirm live regions announce dynamic content correctly
- ✓ cross-test the same flow
Cross-test the same flow on NVDA and JAWS for platform variance
Yours to keep.
Drag time forward. Watch what stays.
Forever
That's what owning means.
The rented stack
ai writing tool: subscription
expired · access lostanalytics suite: subscription
expired · access lostdesign platform: subscription
expired · access lost(nothing left)
Your forge
-
Ship interfaces that work for assistive technology, not just visual users
license: perpetual -
Catch focus-management bugs that make modals invisible to screen readers
license: perpetual -
Resolve the role-name-state announcement gaps before users hit them
license: perpetual -
Distinguish real bugs from screen-reader platform variance with confidence
license: perpetual
subscriptions expire · deeds don't
Everything in the box.
Pick a piece up. Watch it work.
Essential command references for VoiceOver, NVDA, JAWS, and TalkBack
6 parts · one working system · ships instantly by email
This wasn't forged for everyone.
- Not for you if you'd rather rent a tool than own one.
- Not for you if you want someone else to run your stack.
- Not for you if you're happy guessing.
For front-end developers and QA engineers who need to prove screen reader compatibility with real assistive technology, not simulators.
then this was forged for you.Works with
Universal by design: these run in any AI. Delivered in the open Agent Skills + MCP format (native in Claude); ChatGPT, Gemini, Cursor and Copilot adapt the same files their own way.
- Claude Native format
- ChatGPT Adapts via open standards
- Gemini Adapts via open standards
- Cursor Adapts via open standards
- Copilot Adapts via open standards
Catch what's on your mind.
the air is clear. nothing between you and the forge.
catch a spark: the forge will answer
-
I only have a Mac, can I still test NVDA and JAWS coverage?
The playbook gives per-screen-reader command references and checklists for all of them, but NVDA and JAWS run on Windows, so cross-testing needs a Windows machine or VM. VoiceOver coverage on macOS works right away.
-
Why isn't an automated scanner like axe or Lighthouse enough?
Scanners check markup; this validates the full chain from browser to accessibility tree to spoken output, the way disabled users actually experience the page. That catches what scanners miss: silent live regions, modals that trap focus without returning it, and form errors that are never announced.
-
Does passing these tests certify my site as WCAG compliant?
No. It proves screen reader behavior with real assistive technology and gives before-and-after HTML fixes, but WCAG conformance also covers contrast, motion, and timing, areas outside screen readers. A formal audit is a separate exercise.
-
How is it delivered?
By email right after purchase: ready to run, downloaded instantly, no setup wait.
-
One-time or subscription?
A one-time purchase; no subscription or hidden fees. VAT (20%) is included.
-
Can I get a refund?
As a digital product, it can’t be refunded once downloaded. That’s why we show exactly what’s inside and who it’s for, right here.