Accessibility Statement

I try to keep this site usable for as many people as possible - different devices, different abilities, different assistive tech. Nothing fancy; the basics done properly.

What that means in practice:

• Pages are written and structured to be readable without jargon or unnecessary chrome.
• The site works on phones, tablets, and desktops without a separate mobile version.
• Layouts, headings, and links are built so screen readers and keyboard navigation just work.

What I do to keep it that way

• Follow WCAG 2.1 as a baseline.
• Test the site with keyboard-only navigation before pushing changes.
• Treat accessibility regressions as bugs, not nice-to-haves.

Where it falls short

• Forms get tweaked from time to time and may have temporary rough edges.
• Older PDFs linked from blog posts aren't always tagged for screen readers.
• Embedded third-party content (videos, widgets) is only as accessible as the provider makes it.

Found something broken?

Email me. The more specific, the faster I can fix it - useful details are:

• What you ran into.
• The URL where it happened.
• Your device, OS, browser, and any assistive tech you were using.

Thanks - these reports genuinely help.