Last updated October 21, 2026
Accessibility statement
I built this site to be welcoming and easy to use for as many people as I can, including people who use a screen reader, magnification, voice control, a keyboard, or a switch. I’m always learning, so if something doesn’t work for you, please let me know.
My goal
I designed and built this site to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, and to go further where I can.
This is my own assessment. The site hasn’t had an independent audit yet.
Make it yours
The Display button at the top of every page lets you change how the site looks. Your choices are remembered on your device.
- Theme: System, Light, or Dark.
- Vibe: five color and type styles. Breton, Garden, Asawa, Lavender, and Terminal.
- High contrast: stronger colors and borders.
The site also follows your device settings for dark mode, increased contrast, reduced motion, and Windows contrast themes.
What’s built in
- Zoom and text size: pages work at up to 400% zoom and on small phones. Layouts reflow to one column, with no sideways scrolling and no words split across lines.
- Color contrast: in every vibe, main text has a contrast ratio of at least 9.6:1, above the 7:1 Level AAA bar. Secondary text and links are at least 6.3:1. Selected options are marked with a checkmark, not color alone.
- Keyboard: everything works with a keyboard, with a clear focus outline. A “Skip to content” link comes first. Dialogs keep focus inside while open, and return it to the button that opened them.
- Screen readers: pages use real headings, landmarks, lists, and tables. Charts are built as tables. Images have text alternatives, and decorative images are hidden.
- Motion: animations are small, and they’re reduced or turned off when your device asks for less motion.
- Video: the A11ykit walkthrough has no sound. It comes with a written description and a download link.
- Plain language: I write instructions that don’t depend on seeing the screen.
- Resume: available as a web page and as a tagged PDF.
Known limitations
- Screenshots of design work: many case study images show Figma files with small text. Each has a text alternative that describes what matters, and many have an Enlarge button. Some fine details aren’t described.
- YouTube video: the Turtle Graphics video in “Who am I?” comes from YouTube, so its player and captions are YouTube’s.
- Terminal vibe: its monospace font is wider than the others and can be harder to read for some people. You can switch vibes anytime in Display.
How I test
- Keyboard only, from the first link to the last control on every page.
- Zoom up to 400%, and widths from small phones to very large monitors.
- Every vibe, in light and dark, with high contrast on and off, and with reduced motion.
- Color contrast for every vibe, checked against WCAG ratios.
- Automated checks across every page and vibe for layout problems, like words splitting at large text sizes.
The site is built with HTML, CSS, and JavaScript, using WAI-ARIA only where native HTML doesn’t cover a pattern.
Feedback
If something on this site gets in your way, I want to know. Tell me the page, what you were trying to do, and what you use, like your browser or assistive technology.
The form opens with Accessibility already chosen. Your name is optional, and you can include your browser and display details to help me find the problem.