guide
WAD on Gatsby: complete compliance checklist
Implementing WAD compliance on Gatsby means addressing the platform's specific failure modes (image plugin alt prop omission, route announcements) while applying EU Web Accessibility Directive success criteria across content, code, and editorial workflow.
WAD in 60 seconds
The EU Web Accessibility Directive (Directive (EU) 2016/2102) requires public-sector bodies in all EU member states to make their websites and mobile apps accessible per EN 301 549, with mandatory accessibility statements and a complaints mechanism — operative since September 2018 for new sites and September 2020 for all sites.
Gatsby accessibility — what you are starting with
Gatsby is a static-site React framework. SSG output is fast and accessible at the markup level if components are written semantically.
WAD setup checklist for Gatsby
1. Use semantic React: Native elements first.
Common WAD failures on Gatsby
• Image plugin alt prop omission
• Route announcements
Putting it together
Combine WAD's Level AA requirements with Gatsby's native tooling. Bake accessibility into your component library and editorial workflow; instrument axe-core in CI for regression.
FAQ
Frequently asked questions
Cited answers. Sourced. Updated as standards and case law change.
Is Gatsby WAD-compliant out of the box?
Gatsby is in maintenance mode under Netlify. New projects often prefer Next.js or Nuxt.
What is the easiest path to WAD compliance on Gatsby?
Start with the platform's most-accessible default theme (where applicable), audit each installed plugin/extension/module, train content authors on alt text and heading hierarchy, and instrument axe-core in your CI pipeline.
Is Gatsby still maintained for accessibility?
Gatsby is in maintenance mode under Netlify. New projects often prefer Next.js or Nuxt.
Stop guessing. Get the audit a Fortune 500 a11y team would have written.
Free audit on your live URL. No sign-up. IAAP-format report. Ready in hours.
founders@accessivepath.com · +977 9851094056