The standard I follow

I aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. WCAG is the standard the U.S. Department of Justice points to for the Americans with Disabilities Act, and the one most accessibility laws around the world build on.

What I've done

  • Pages can be used with a keyboard alone, with a visible focus ring and a "Skip to content" link.
  • Pages use headings, lists, landmarks, and form labels in the HTML, so assistive technology can find its way around.
  • Images that carry meaning have text descriptions. Decorative images are hidden from assistive technology.
  • Text, form field edges, and focus rings meet WCAG contrast ratios. The layout works at 320 pixels wide and with larger text spacing.
  • Animation is short and plays once. If your device asks for reduced motion, the site turns it off.
  • The contact form has visible labels, says which field needs attention, keeps your message if sending fails, and does not use a CAPTCHA.

How it was tested

Last reviewed . The checks below covered every page at 1440, 390, and 320 pixels wide:

  • Automated scans with axe-core 4.10 (WCAG 2.0, 2.1, and 2.2 A and AA rules), plus a second review with IBM Equal Access and HTML_CodeSniffer.
  • Keyboard-only use in Chromium, including the review gallery, the job list, and the contact form's error and failure states.
  • Contrast measured for every text and control color pair, text-spacing overrides, and reduced motion.
  • An independent AI-assisted review of the code and the rendered pages.

Testing so far used Chromium-based browsers. Safari, Firefox, and screen readers such as VoiceOver and NVDA have not been tested yet.

Known limits

  • The site has not yet been checked with a screen reader. If you use one and something doesn't work, please tell me.
  • Screenshots in the case studies show other products. Each has a text description, but the small text inside the images may not meet contrast rules. The case study text covers what they show.
  • Some links go to sites I don't control, like LinkedIn, GitHub, and Figma. Their accessibility is up to them.

Tell me about a barrier

If something on this site is hard to use, or you need any of it in another format, email me at hello@lyori.com. Tell me the page and what went wrong. I aim to reply within 5 business days and work on a fix.