Accessibility Compliance (WCAG 2.2 AA) in Complex Enterprise Web Apps

Focus Not Obscured (Minimum) requires that a focused element is not entirely hidden by author-created content — a direct challenge to sticky headers and floating action bars, which routinely cover the focused row in a long table. Dragging Movements requires a single-pointer alternative to any drag interaction, so kanban boards and reorderable lists need keyboard and menu-driven equivalents.

Target Size (Minimum) sets a 24 by 24 CSS pixel floor with spacing exceptions, which affects icon-dense toolbars. Consistent Help and Redundant Entry address multi-step workflows, requiring stable help placement and avoiding re-asking for information the user already supplied in the same process.

Automated scanning catches roughly a third of issues — contrast, missing names, invalid ARIA. The rest requires structured manual testing: full keyboard traversal of every flow, screen reader passes with at least two combinations, 200% zoom and 400% reflow checks, and reduced-motion verification.

Component-level testing scales better than page-level auditing. Certify each primitive against its ARIA authoring pattern once, then test composition and flow logic at the page level. This keeps the audit surface proportional to the design system rather than to the number of screens.

Conformance decays without enforcement. Add axe checks to component tests, block merges on new violations, and record keyboard traversal snapshots for critical flows. Maintain an accessibility conformance report and update it per release rather than reconstructing it during a procurement cycle.

Assign ownership. When accessibility belongs to everyone, it belongs to no one; a named owner per surface with a quarterly review keeps the standard from drifting as teams rotate.