Testing for accessibility in Angular 1 and 2
summary
Shows that accessibility becomes testable in Angular by adding concrete checks: unit tests for labels and aria, integration/end-to-end tests for keyboard focus and color contrast, and CI gates that fail builds on regressions. Uses axe-core (and axe-webdriverjs) injected into browser tests, uses protractor for Angular 2 keyboard flows, and warns that NG aria can introduce problems if misused. Cites 15% of users affected, demos an Angular Material app and a fixed airline site, and reports the approach works but Angular 2 unit keyboard mocks remain immature.
AI-written summary · about
chapters (7)
- 0:00Start
- 3:21reach and operate all of the controls in your application
- 4:20add support for accessibility through coverage in your unit tests
- 12:09creating a custom checkbox
- 17:15write an integration test
- 26:41mocking keyboard events in unit-tests
- 31:33provide a component accessibility contract using unit tests
