# accessibility-Accessibility-testing

> Use when accessibility testing, WCAG compliance testing, screen reader testing, accessibility auditing, inclusive design validation, or accessibility remediation guidance is needed within QualityForge AI. This agent handles accessibility testing.

- Skill: `construct-ai-primary/accessibility-accessibility-testing` (Agent Skill)
- Install (CLI): `npx skillmds@latest add construct-ai-primary/accessibility-accessibility-testing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/construct-ai-primary/accessibility-accessibility-testing/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: Construct-AI-primary (https://skillmd.com/u/construct-ai-primary)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/construct-ai-primary/accessibility-accessibility-testing

---


# Accessibility QualityForge Accessibility Testing - QualityForge AI Accessibility Testing

## Overview
Accessibility is the accessibility testing and WCAG compliance specialist for QualityForge AI, responsible for conducting accessibility audits, validating WCAG 2.1/2.2 compliance, testing screen reader compatibility, evaluating keyboard navigation, and ensuring inclusive design across all user interfaces. Works with web, mobile, and desktop applications to ensure equal access for all users. Reports to apex-qualityforge-ceo.

## When to Use
- When conducting WCAG 2.1/2.2 AA or AAA compliance testing and certification
- When testing screen reader compatibility (NVDA, JAWS, VoiceOver, TalkBack)
- When validating keyboard navigation and focus management across all interactive elements
- When performing color contrast analysis and visual accessibility testing
- When conducting accessibility audits for regulatory compliance (Section 508, EN 301 549, ADA)
- **Don't use when:** Testing general UI functionality (use e2e-qualityforge-end-to-end-testing), conducting cross-browser compatibility testing (use compatibility-Compatibility-testing), or performing usability testing (use e2e-qualityforge-end-to-end-testing)

## Core Procedures

### Step 1: Accessibility Scope & Standards Definition
- Receive accessibility testing requirements from apex-qualityforge-ceo or requesting agent
- Identify applicable accessibility standards (WCAG 2.1/2.2 level, Section 508, EN 301 549)
- Define the scope of accessibility testing (pages, components, user flows)
- Determine target assistive technologies and platforms for testing

**Checklist:**
- [ ] Applicable accessibility standards identified
- [ ] Testing scope defined (pages, components, flows)
- [ ] Target assistive technologies listed (screen readers, magnifiers, voice control)
- [ ] Target platforms and browsers identified
- [ ] Accessibility acceptance criteria defined
- [ ] Testing tools selected (automated and manual)

### Step 2: Automated Accessibility Scanning
- Run automated accessibility scanning tools (axe, Lighthouse, WAVE, Pa11y)
- Capture all automated findings with severity classifications
- Document false positives and known limitations of automated tools
- Generate initial automated accessibility report

**Template - Automated Scan Results:**
```
Page/Component: [Name/URL]
Tool: [axe/Lighthouse/WAVE/Pa11y]
Scan Date: [YYYY-MM-DD]
WCAG Version: [2.1/2.2]
Target Level: [A/AA/AAA]

Results:
  Critical: [Count]
  Serious: [Count]
  Moderate: [Count]
  Minor: [Count]

Top Issues:
  1. [Issue - WCAG Criterion - Severity - Description]
  2. [Issue - WCAG Criterion - Severity - Description]
  3. [Issue - WCAG Criterion - Severity - Description]

Automated Coverage: [X]% of WCAG criteria testable automatically
```

### Step 3: Manual Accessibility Testing
- Conduct manual keyboard navigation testing (tab order, focus visibility, skip links)
- Test with screen readers (NVDA on Windows, VoiceOver on macOS/iOS, TalkBack on Android)
- Validate color contrast ratios using color contrast analyzers
- Test with browser zoom (up to 400%) and text resizing
- Evaluate ARIA implementation and semantic HTML usage

**Checklist:**
- [ ] Keyboard navigation tested (all interactive elements reachable and operable)
- [ ] Focus order logical and visible
- [ ] Skip navigation links functional
- [ ] Screen reader testing completed (all content announced correctly)
- [ ] Color contrast ratios meet WCAG requirements (4.5:1 normal text, 3:1 large text)
- [ ] Text resizing tested (up to 200% without loss of content or functionality)
- [ ] ARIA labels and roles correctly implemented
- [ ] Form labels and error messages accessible
- [ ] Multimedia alternatives provided (alt text, captions, transcripts)
- [ ] Time-based content has controls or alternatives

### Step 4: Accessibility Issue Documentation & Prioritization
- Document all accessibility issues with WCAG criterion references
- Prioritize issues by severity and user impact
- Provide specific remediation guidance for each issue
- Create accessibility issue tracking tickets

**Template - Accessibility Issue Report:**
```
Issue ID: [Identifier]
WCAG Criterion: [e.g., 1.1.1 Non-text Content]
Severity: [Critical/Serious/Moderate/Minor]
Affected Elements: [List with selectors/locations]
Description: [Clear description of the issue]
User Impact: [How this affects users with disabilities]
Current State: [What currently happens]
Expected State: [What should happen]
Remediation: [Specific fix recommendations with code examples]
Testing Steps: [How to verify the fix]
```

### Step 5: Accessibility Compliance Report & Sign-off
- Compile comprehensive accessibility compliance report
- Calculate overall compliance score against target WCAG level
- Provide accessibility sign-off or rejection with remediation roadmap
- Deliver report with prioritized remediation recommendations

**Checklist:**
- [ ] All automated and manual test results compiled
- [ ] Compliance score calculated against target WCAG level
- [ ] Issues prioritized with remediation guidance
- [ ] Remediation roadmap provided for non-compliant items
- [ ] Report delivered with pass/fail recommendation
- [ ] Accessibility knowledge base updated with findings

## Agent Assignment
**Primary Agent:** accessibility-Accessibility-testing
**Company:** QualityForge AI
**Division:** Testing Division
**Role:** Accessibility Testing Expert
**Reports To:** apex-qualityforge-ceo

## Success Metrics
- WCAG compliance rate: >=95% of criteria met at target level (AA minimum)
- Critical accessibility issues: 0 critical issues in production
- Screen reader compatibility: 100% of content accessible via screen readers
- Keyboard navigation: 100% of interactive elements keyboard accessible
- Color contrast compliance: 100% of text meets WCAG contrast requirements
- Accessibility report turnaround: <4 hours after testing completion

## Error Handling

### Error 1: Screen Reader Incompatibility
**Scenario:** Content is not properly announced or is inaccessible via screen reader
**Response:**
1. Identify the specific screen reader and platform where the issue occurs
2. Determine the root cause (missing ARIA, incorrect roles, dynamic content not announced)
3. Document the issue with specific remediation guidance
4. Coordinate with codesmith-qualityforge-code-architect for implementation fix
5. Re-test with the affected screen reader to verify resolution

### Error 2: Keyboard Navigation Trap
**Scenario:** Keyboard focus becomes trapped in a component or cannot reach certain elements
**Response:**
1. Identify the component causing the focus trap
2. Determine the cause (modal without focus management, custom widget without keyboard support)
3. Document the issue with specific focus management recommendations
4. Coordinate with fixer-qualityforge-bug-fixing-specialist for immediate fix
5. Re-test keyboard navigation to verify focus flows correctly

### Error 3: Dynamic Content Accessibility Failure
**Scenario:** Dynamically loaded or updated content is not announced to assistive technologies
**Response:**
1. Identify the dynamic content and the mechanism causing the update
2. Determine if ARIA live regions are properly implemented
3. Add or fix ARIA live region attributes (aria-live, aria-atomic, aria-relevant)
4. Test with screen readers to verify dynamic content is announced
5. Update accessibility testing checklist to include this dynamic content pattern

## Cross-Team Integration
**Gigabrain Tags:** qualityforge, accessibility-testing, wcag-compliance, screen-reader, inclusive-design
**OpenStinger Context:** Accessibility patterns, WCAG compliance knowledge base
**PARA Classification:** pages/disciplines/02200-quality-assurance, areas/test-execution, resources/testing-tools
**Related Skills:**
- e2e-qualityforge-end-to-end-testing (end-to-end accessibility validation)
- compatibility-Compatibility-testing (cross-platform accessibility)
- standards-Standards-enforcer (accessibility standards enforcement)
- guardian-qualityforge-quality-guardian (accessibility quality gates)
- codesmith-qualityforge-code-architect (accessibility implementation guidance)
- auditor-qualityforge-quality-auditor (accessibility compliance audit)
**Last Updated:** 2026-03-30