TaggedWorks - Digital Accessibility Firm
Audit & Remediation Protocol

Rigorous, Repeatable Accessibility Engineering

Our 6-stage methodology replaces guesswork with empirical testing, code-level remediation, and verifiable compliance deliverables aligned with global standards.

Operational Architecture

The Six Stages of Digital Accessibility Maturation

From initial baseline scoping to full continuous deployment automation, every phase delivers structured artifacts designed for engineering and compliance rigor.

01

Understand

Discovery, Scope & Environmental Mapping

STAGE 01 / 06

Core Objective:

Establish a clear, statistically sound sampling of user journeys, technical architectures, and regulatory requirements.

Engineering Activities:

  • Audit scope definition across public pages, authenticated states, dynamic modals, and documents.
  • Technical stack review (frontend frameworks, component libraries, state management, design tokens).
  • Applicable standards determination (WCAG 2.1/2.2 AA, Section 508, EN 301 549, PDF/UA).
  • Identification of high-priority conversion funnels (checkout, registration, account administration).

Verified Deliverables & Artifacts:

  • Agreed Audit Scope Specification
  • Representative Template Matrix
  • Testing Device & Browser Matrix

Primary Stakeholders:

TaggedWorks Lead Architect, Client Product Manager, Engineering Lead

02

Evaluate

Automated Sweeps, Manual Code Audit & Assistive Tech

STAGE 02 / 06

Core Objective:

Execute multi-layered empirical testing to uncover all objective and contextual accessibility defects.

Engineering Activities:

  • Automated rule-based discovery passes via axe-core across sampled views.
  • Keyboard-only inspection (tab sequencing, visible focus appearance, bypass links, modal trapping).
  • Screen reader testing across physical setups (NVDA/Firefox, VoiceOver/Safari, TalkBack/Chrome).
  • Responsive zoom and reflow testing up to 400% without 2D scrolling.
  • Accessibility tree (AXTree) inspection and WAI-ARIA 1.2 semantic verification.

Verified Deliverables & Artifacts:

  • Raw Defect Log
  • Screen Recording & Transcription Evidence
  • Calculated Contrast Data

Primary Stakeholders:

TaggedWorks Senior Accessibility Engineers, Client QA Team

03

Prioritize

Defect Triage & Impact-Driven Sprint Mapping

STAGE 03 / 06

Core Objective:

Translate voluminous audit data into actionable, prioritized engineering tickets grouped by root cause.

Engineering Activities:

  • Severity classification (P0 Blocker, P1 High, P2 Medium, P3 Minor) based on real user barrier impact.
  • Component-source mapping: isolating whether defects live in shared design tokens or page-specific markup.
  • Direct ticket integration into client backlog systems (Jira, GitHub Issues, Azure DevOps).
  • Engineering briefing session with core developers to review reproduction steps.

Verified Deliverables & Artifacts:

  • Triaged Engineering Sprint Backlog
  • Root-Cause Component Map
  • Executive Risk Briefing

Primary Stakeholders:

TaggedWorks Technical Lead, Client VP of Engineering, Scrum Master

04

Remediate

Hands-on Code Remediation & Component Hardening

STAGE 04 / 06

Core Objective:

Fix defects directly within the codebase with clean semantic HTML, valid ARIA, and updated tokens.

Engineering Activities:

  • Branching and authoring production-grade Pull Requests against client Git repositories.
  • Hardening shared design system components (dialogs, custom dropdowns, comboboxes, tooltips).
  • Pair-programming and architecture guidance with client frontend engineers.
  • Remediating PDF document tag trees to ISO 14289 (PDF/UA) conformance.

Verified Deliverables & Artifacts:

  • Tested Pull Requests with Rationale
  • Accessible Component Specs
  • Remediated PDF/UA Files

Primary Stakeholders:

TaggedWorks Engineers, Client Frontend Engineers, Design System Team

05

Validate

Retesting, Verification & Evidence Report

STAGE 05 / 06

Core Objective:

Empirically verify that every implemented remediation resolves the barrier without introducing regressions.

Engineering Activities:

  • Rigorous retesting of all resolved tickets in staging and pre-production environments.
  • Full assistive technology validation of remediated user flows.
  • Automated regression test suite execution (axe-core unit tests, Playwright end-to-end assertions).
  • Preparation of official, defensible Accessibility Conformance Reports (ACRs / VPATs).

Verified Deliverables & Artifacts:

  • Verification Sign-Off Report
  • Completed VPAT 2.5 ACR
  • Defect Resolution Summary

Primary Stakeholders:

TaggedWorks QA & Compliance Leads, Client Legal & Procurement Teams

06

Operationalize

CI/CD Guardrails, Governance & Team Enablement

STAGE 06 / 06

Core Objective:

Embed permanent accessibility guardrails and skills into the client development lifecycle.

Engineering Activities:

  • Integrating automated linting and axe-core assertions into Git pre-commit hooks and CI pipelines.
  • Authoring role-based design and engineering coding guidelines.
  • Delivering hands-on accessibility workshops for designers, engineers, and product managers.
  • Establishing scheduled recurring regression audits and continuous compliance monitoring.

Verified Deliverables & Artifacts:

  • CI/CD Accessibility Pipeline Configuration
  • Team Accessibility Playbook
  • Quarterly Health Dashboard

Primary Stakeholders:

TaggedWorks Practice Lead, Client CTO, Engineering Managers

Engagement Readiness

Apply our engineering methodology to your digital ecosystem.

Partner with senior accessibility engineers who resolve defects at the code level rather than handing you unworkable checklists.