accessibility-auditor

To audit web application accessibility, use the accessibility-auditor to inspect the accessibility tree and test keyboard navigation. It verifies ARIA labeling, focus management, and visible focus indicators across routes to identify gaps in interactive components.

Checking focus management after UI changes requires auditing the running app's accessibility tree. This skill validates that newly added interactive components have proper ARIA labels, semantic structure, and visible focus indicators during keyboard navigation.

Yes, you need a running browser context with the app loaded to test ARIA labeling and accessibility tree structures. The skill performs automated checks and provides manual keyboard navigation guidance directly within the active browser environment.

Yes, you can validate visible focus indicators across different application routes. The skill audits newly added interactive components by inspecting the accessibility tree and verifying that focus visibility and semantic structure are maintained throughout the app.

Accessibility checks for new UI components must cover ARIA labeling, keyboard navigation, and focus management. The skill inspects the running app's accessibility tree to verify semantic structure, focus visibility, and proper interactive element labeling.

Inspecting the accessibility tree identifies keyboard navigation gaps by validating semantic structure and focus management. The skill uses automated checks and manual keyboard navigation guidance to detect missing ARIA labels and invisible focus indicators in the running app.