Dispatch
CSS scroll animations silently blinded a developer's own accessibility scanner
A solo builder running a weekly accessibility monitoring service found their scanner reporting zero violations on their own site — incorrectly — after they added CSS scroll-driven animations. Elements below the fold never entered their animated end state during the headless scan, so roughly half the page was never evaluated, and the tool reported clean rather than reporting incomplete. Single-source practitioner report, but it names a real failure mode for anyone shipping scroll-driven animations alongside automated a11y or visual-regression checks: absence of violations is not evidence of coverage.
Source
↳ Follow the thread