Legal

Accessibility statement

We want every developer to be able to read, search and use this Site, whatever device or assistive technology they use.

Last updated October 10, 2026

Our goal

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We believe the Site is largely conformant, but we have not had a formal third-party audit, so we do not claim full conformance.

What we do

  • Semantic HTML with landmarks, one h1 per page and a logical heading order, and breadcrumbs on inner pages.
  • Everything works with a keyboard, with a visible focus outline.
  • Text and controls meet AA colour-contrast ratios in both the light and dark themes.
  • Animations respect your reduce motion setting, and the layout reflows down to 320 px wide and to 200% zoom.
  • Images have text alternatives (decorative artwork is hidden from screen readers), and form fields have visible labels and announce their status.
  • Code blocks can be copied with one keyboard-accessible button.

How we test

Key pages are checked with automated tools (axe-core and Lighthouse, also in our CI on every change) and by hand with a keyboard and screen-reader spot checks. Automated tools catch only part of the issues, which is why your feedback matters.

Known limitations

  • Comments are provided by Disqus, a third party. We cannot guarantee the accessibility of its widget.
  • Older articles may contain code screenshots or long tables; we are improving them as we update each post.
  • Diagrams come with a text explanation in the article; tell us if one is missing.

Report a barrier

If something on the Site is hard or impossible to use, email contact@laravel-vuejs.space or open a GitHub issue. Tell us the page, what you were trying to do and the browser or assistive technology you use. We aim to reply within 5 working days and to fix confirmed issues promptly, or give you the content in another format meanwhile.