2013 articles with this tag
Keeping scrolling smooth by avoiding expensive work in scroll handlers and layout reads. Where most projects go wrong The usual mistakes: Heavy work inside scro...
How browsers split pages into layers that the GPU can move and blend without redrawing everything. Why does it matter? Animating the right properties keeps moti...
Collecting Core Web Vitals from real users in JavaScript, including attribution data that points at the cause. At a glance Library Google publishes a web-vitals...
Running Lighthouse automatically on each build so performance and accessibility regressions are caught before release. What is at stake Performance work decays...
WCAG 2.2 requirements that sign-in should not depend on remembering or transcribing information. The key figures Success Criterion 3.3.8 requires an alternative...
How visible the keyboard focus indicator is, including its size and contrast against the background. Where most projects go wrong The usual mistakes: outline: n...
The WCAG requirement that content stays usable when users increase line height, letter spacing and word spacing. Why does it matter? People with dyslexia and lo...
Making map-based content usable for people who cannot see or interact with an interactive map. At a glance Text alternatives addresses and directions can be pro...
Video and audio players whose controls work with keyboards and screen readers and that support captions. What is at stake Custom players frequently lose the acc...
Labeling embedded frames so assistive technology users know what each one contains. The key figures Title attribute gives an iframe an accessible name Hidden fr...
Making inline SVG graphics work for screen reader users, whether they are decorative or meaningful. Where most projects go wrong The usual mistakes: Icon-only b...
Input methods such as switches, head pointers and sip-and-puff devices used by people with limited mobility. Why does it matter? These devices usually work thro...
Showing 1,956 of 2,013
