Serving Sa11y Locally in Drupal: Reliability Over Convenience

import TOCInline from '@theme/TOCInline'; The biggest takeaway: serving Sa11y CSS/JS locally in Drupal gives you more predictable accessibility checks, especially when external asset delivery is unreliable or restricted. TL;DR — 30 second version Local Sa11y assets improve reliability in locked-down/CSP-heavy environments The trade-off: you own the maintenance burden for upstream updates "Stable loading" beats "latest by default" for editorial accessibility workflows CSP-heavy environments are a strong signal to prefer local libraries from day one Why I Built It I wanted a safer accessibility integration path for Drupal sites that run in locked-down environments, strict CSP setups, or government networks where third-party asset delivery can fail silently. Accessibility tooling is only useful when it is consistently available; if your script host blips, your QA confidence drops with it. The Solution The practical pattern is simple: download Sa11y assets, ship them with your module/theme