a11y-expert

To audit web UI for WCAG 2.2 AA compliance, you review UI semantics, keyboard behavior, focus management, labeling, ARIA usage, and user-impacted states against baseline criteria. This produces actionable findings separating automation from human judgment, including concrete remediation and verification steps.

Fixing keyboard navigation and focus management requires prioritizing native HTML patterns and using ARIA only when native semantics are insufficient. You provide concrete, engineering-focused changes for focus order, visibility, and keyboard interaction to ensure correct accessible names, roles, and states.

Implementing accessible form validation involves engineering-focused changes for semantics, labels, and error handling mapped to WCAG 2.2 AA considerations. You identify issues by user impact first, then apply concrete code-level remediation to ensure forms are usable for keyboard and screen reader users.

You need ARIA attributes for custom interactive components like dialogs, menus, tabs, and accordions only when native HTML semantics are insufficient. Prioritize native HTML patterns to avoid patching broken structure, ensuring correct accessible names, roles, and states for screen reader users.

Verify web accessibility fixes by combining automated checks with manual keyboard walkthroughs, focus order and visibility review, screen-reader-oriented naming checks, zoom and reflow spot checks, and reduced-motion and contrast validation to ensure usability for low-vision and motion-sensitive users.

This accessibility audit approach works for dynamic content and media components by reviewing interactive elements against WCAG 2.2 AA baseline criteria. It applies to pages and interactive components including forms, dialogs, menus, tabs, accordions, custom selects, and media to ensure correct accessible behavior.