~/talk

Testing for accessibility in Angular 1 and 2

Talkat Angular Connect 2016 · 2016-09-27..09-28· [angular, accessibility]
links:none on file
slides:none on file

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

  1. 0:00Start
  2. 3:21reach and operate all of the controls in your application
  3. 4:20add support for accessibility through coverage in your unit tests
  4. 12:09creating a custom checkbox
  5. 17:15write an integration test
  6. 26:41mocking keyboard events in unit-tests
  7. 31:33provide a component accessibility contract using unit tests
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.