sdcorejs-review-accessibility-angular-portal

To audit Angular portal accessibility for WCAG compliance, run Lighthouse, pa11y, and axe baseline probes alongside Angular-specific focus and ARIA checks. This validates keyboard navigation, screen reader support, and CDK focus management patterns across routed pages.

Testing CDK focus management and ARIA attributes in Angular requires verifying focus trapping, focus monitoring, and aria-live announcements for async toasts. Use axe and Lighthouse probes to detect missing aria-describedby and aria-invalid associations in dynamic disclosure widgets.

Validating keyboard navigation and screen reader behavior in Angular routed pages involves auditing RouterOutlet focus on navigation and SdTable keyboard interactions. Run pa11y and axe probes to confirm heading structure and portal action button usability for assistive tech users.

You can run Lighthouse and pa11y probes on Angular portal routes to catch accessibility regressions after adding screens, workflows, modals, or forms. These tools map WCAG success criteria and detect missing aria-live regions for async errors.

Axe CLI detects missing aria-live and aria-invalid associations in Angular forms by running baseline accessibility probes. It identifies incomplete ARIA mappings for dynamic disclosure widgets and validates focus-visible behavior for portal interactions.

Run an accessibility regression check on an Angular portal application after adding new screens, workflows, modals, forms, or routed navigation. This ensures keyboard users and screen reader users can navigate tables, dialogs, and routed pages without encountering new gaps.