Accessibility QA / Software Testing

Applause
Accessibility Expert.

I audit enterprise websites and digital services against WCAG 2.2 (A/AA), validate issues on real devices, and ship reports that are grounded in evidence: videos, photos/screenshots, AT output, and the actual DOM/code path.

My work includes auditing, bug discovery, and triage (validating tickets reported by other testers, de-duplicating, and prioritizing what engineering should fix first).

Also used in enterprise contexts: web clauses such as EN 301 549 section 9.2.x, when applicable.

Accessibility audit and QA

Evidence Package

Video • Screenshots • AT Output • Code Signals

NDA-safe content: representative examples only (no client-identifying details).

Audit Output

  • Evidence-based tickets with steps to reproduce, expected vs actual behavior, and verification notes.
  • Artifacts: short videos, annotated screenshots/photos, AT output transcripts, and device/OS/browser matrix.
  • Suggested resolutions that connect UX impact to practical fixes (semantics, ARIA sources, keyboard parity, focus order).
  • Standards mapping (e.g., 2.1.1 Keyboard, 1.1.1 Non-text Content, 4.1.2 Name/Role/Value) + enterprise checklists.

Code + Reality Alignment

Actual Results

I validate behavior as users experience it (devices + AT), then align it with the implementation (DOM, roles, labels, event handling).

Suggested Fix Paths

When possible, I include high-confidence fix directions and what to re-test after the change (to prevent regressions).

Expertise

I write expert summaries for stakeholders, and I triage reports from other testers to keep the issue pipeline clean and actionable.

01 / Findings & Triage (Representative)

WCAG_2_2_AA
5

Sample Findings

Anonymized examples to demonstrate audit method + reporting quality.

3

P2 / High

Blocking interactions for keyboard-only and screen reader users.

A/AA

Compliance Target

Each ticket maps to criteria and includes “how to verify” after fixes.

Interactive Triage

Filter representative findings by severity and track to mirror how I validate and prioritize incoming reports.

F-01 • Keyboard

Primary menu not operable with Enter/Space

P2 / High

Keyboard-only users cannot open account navigation, blocking access to essential pages and actions.

Click to expand: evidence + suggested resolution

Standards Mapping

  • WCAG 2.2 — 2.1.1 Keyboard
  • WCAG 2.2 — 2.1.2 No Keyboard Trap

Evidence & Artifacts

  • Video reproduction (keyboard-only)
  • Steps-to-reproduce with expected vs actual behavior
  • DOM/code signal: interaction wired only to pointer/click

Suggested Resolution

  • Bind Enter/Space to the same action as click (button semantics or key handlers).
  • Move focus into the opened menu and restore focus predictably on close.
  • Re-test on the device/AT matrix (NVDA/VoiceOver + keyboard-only).

F-02 • Screen Reader

Informational images announced as file names / skipped

P2 / High

Screen reader users lose essential context; announcements are non-informative (file paths) or absent.

Click to expand: evidence + suggested resolution

Standards Mapping

  • WCAG 2.2 — 1.1.1 Non-text Content

Evidence & Artifacts

  • AT output transcript (VoiceOver/NVDA)
  • DOM inspection of accessible name sources (alt/ARIA)
  • Screenshots of impacted headers

Suggested Resolution

  • Provide meaningful `alt` for informative images; empty alt only for decorative content.
  • Avoid accidental file-name announcements by setting intentional name sources.

F-03 • Structure

Focusable element exposed to AT without a meaningful name

P2 / High

Assistive Tech announces generic labels, increasing confusion and misnavigation risk for SR users.

Click to expand: evidence + suggested resolution

Standards Mapping

  • WCAG 2.2 — 4.1.2 Name, Role, Value
  • WCAG 2.2 — 2.4.4 Link Purpose

Evidence & Artifacts

  • AT output transcript (announced label)
  • Accessibility tree / HTML snapshot
  • Screenshot of focus ring and tab stop location

Suggested Resolution

  • Ensure interactive elements have a deterministic accessible name (text/aria-label/aria-labelledby).
  • Remove hidden focus traps or make them non-focusable when not user-facing.

F-04 • Visual

Focus indicator too weak on dark theme components

P3 / Medium

Keyboard users can lose track of focus on complex forms, increasing errors and time-to-complete.

Click to expand: evidence + suggested resolution

Standards Mapping

  • WCAG 2.2 — 2.4.7 Focus Visible
  • WCAG 2.2 — 1.4.11 Non-text Contrast

Evidence & Artifacts

  • Screenshots (focused vs unfocused)
  • CSS check (outline/box-shadow values)

Suggested Resolution

  • Increase focus indicator thickness/contrast; don’t remove outlines without a replacement.
  • Verify across background variants and high-contrast/forced colors where applicable.

F-05 • Structure

Heading structure inconsistent across templates

P4 / Low

Screen reader navigation is slower and less predictable; users lose structure and page cues.

Click to expand: evidence + suggested resolution

Standards Mapping

  • WCAG 2.2 — 1.3.1 Info and Relationships

Evidence & Artifacts

  • DOM outline review
  • SR rotor / headings list check

Suggested Resolution

  • Normalize heading levels (single H1; logical nesting).
  • Use landmarks consistently for page regions.