jaws-accessibility

Audit web interfaces for WCAG 2.2 compliance using JAWS and NVDA.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/danbri/forgetmenot --skill jaws-accessibility
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jaws-accessibility
Source: https://github.com/danbri/forgetmenot/tree/main/skills/jaws-accessibility
Command: npx skills add https://github.com/danbri/forgetmenot --skill jaws-accessibility

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the complexity of achieving true web accessibility by providing expert guidance on screen reader compatibility, legal compliance, and rigorous audit methodologies.

Core Features & Use Cases

  • Screen Reader Compatibility: Navigate JAWS and NVDA version-specific bugs, ARIA patterns, and interaction modes.
  • Legal Compliance: Ensure adherence to Spanish (Ley 11/2023, RD 1112/2018) and European (EAA, EN 301 549) accessibility mandates.
  • Audit Methodology: Execute an 8-phase manual testing flow to identify and remediate critical accessibility barriers.

Quick Start

Use the jaws-accessibility skill to perform an 8-phase manual audit on the current web page and report any critical accessibility findings.

Frequently Asked Questions about jaws-accessibility

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform a WCAG 2.2 accessibility audit using JAWS?

To perform a WCAG 2.2 accessibility audit using JAWS, execute an 8-phase manual testing flow designed to identify and remediate critical accessibility barriers on web interfaces. This methodology ensures robust, standards-compliant results by navigating specific screen reader interactions.

What is the best way to ensure compliance with the European Accessibility Act?

Ensuring compliance with the European Accessibility Act involves adhering to EN 301 549 mandates through rigorous screen reader compatibility testing. Conducting audits with JAWS and NVDA validates your web interfaces against required regulatory standards.

How do I test web interfaces for screen reader compatibility with NVDA and JAWS?

Testing web interfaces for screen reader compatibility with NVDA and JAWS requires navigating version-specific bugs, ARIA patterns, and interaction modes. This process identifies critical barriers ensuring robust, standards-compliant accessibility across different screen reader environments.

Does this accessibility audit methodology support Ley 11/2023 compliance?

Yes, this accessibility audit methodology supports Ley 11/2023 compliance by providing regulatory guidance for Spanish legislation. It facilitates end-to-end manual testing using JAWS and NVDA to ensure web interfaces meet Spanish and European accessibility mandates.

Why does my ARIA implementation fail during JAWS screen reader testing?

ARIA implementations fail during JAWS testing due to version-specific bugs and interaction mode mismatches. Navigating these ARIA patterns requires an advanced 8-phase manual audit methodology to identify and remediate the specific compatibility barriers.

When do I need to use NVDA alongside JAWS for accessibility audits?

You need to use NVDA alongside JAWS for accessibility audits when validating comprehensive screen reader compatibility across different platforms. Combining both tools during the 8-phase manual testing flow ensures broader coverage of ARIA patterns and interaction modes.