Target

The site targets WCAG 2.1 Level A and AA. That is a target, not a conformance claim: conformance requires evaluation against every success criterion, including manual testing this site has not yet undergone (see Current limitations below). What follows describes the real, verifiable mechanisms in place today.

15Automated coverage

12 templates, both themes.

@axe-core/playwright runs an automated wcag2a/wcag2aa/wcag21a/wcag21aa scan against every route below, in light and dark mode, with reduced motion emulated so entrance animations can't be sampled mid-transition. Any violation fails CI.

/home
/projectsprojects index
/projects/abakada-toolkitcase study
/blogblog index
/blog/why-abakada-org-means-everything-to-meblog post
/contactcontact
/colophoncolophon
/resumeresume
/accessibilityaccessibility statement
/engineering-logengineering log
/apiapi docs
/statusstatus

That is 12 routes × 2 themes = 24 scans, run on every push.

CI gate

Lighthouse CI asserts the accessibility category at a minimum score of 0.90, at error level (build-breaking), across both a desktop and a mobile budget run, on every push. A regression fails the build before it ships; it does not get to production and get noticed later.

16Current limitations

What this doesn't cover yet.

  • No manual screen-reader testing has been performed yet (VoiceOver, NVDA, or JAWS).
  • Automated scanning covers 12 representative templates, not every route on the site. Legal pages, /about, and /sitemap itself are not in the automated suite.
  • Axe-core catches a meaningful but partial subset of WCAG success criteria: contrast math, ARIA validity, and accessible-name computation. It does not evaluate meaningful reading order, keyboard-trap edge cases beyond its rule set, or gesture alternatives; those need a human.
  • Third-party embedded content (none currently on the site) would not be covered by this statement if added later without a corresponding audit update.
17Report an issue

Found something that doesn't work?

Automated coverage catches a lot; it doesn't catch everything. If something on ramonloganjr.com is hard to use with assistive technology, email hello@ramonloganjr.com or use the contact form. Real reports move faster than any audit.

Accessibility Statement · Ramon Logan Jr.