WCAG accessibility audit for Angular applications

Angular's change detection system automatically updates the DOM when component data changes. These updates are not wrapped in aria-live regions and do not trigger announcements. A notification counter that updates, a data table that refreshes, a status message that appears: all of this is invisible to screen readers without explicit aria-live implementation.

Angular Material components (mat-select, mat-autocomplete, mat-datepicker, mat-table) have incomplete ARIA support. mat-select does not always announce the selected option. mat-datepicker has complex keyboard navigation not conforming to APG patterns. mat-autocomplete does not correctly handle aria-activedescendant. These gaps are documented in the project's GitHub issues but persist in stable versions.

Angular's router performs client-side navigations that change content without reload. Screen readers do not detect the page change. Focus remains on the clicked link instead of moving to the new content. The page title is not always updated via Title service. The blind user does not know the navigation worked or what content is now displayed.

The *ngIf and *ngFor directives physically add and remove DOM elements. If the focused element is destroyed by *ngIf, focus returns to the top of the document. This problem is frequent in conditional forms (showing a field based on a selection), dynamic lists (deleting an item), and tab interfaces built with *ngIf instead of CSS.