Accessibility Statement

Last reviewed November 20, 2026

I want everyone to be able to use this website, including people who use screen readers, magnifiers, voice control or a keyboard instead of a mouse. That goes for the sites I build for clients, too. Towns, nonprofits and small businesses serve everyone, and their websites should as well.

The standard I follow

I design and build to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. These are the internationally recognized guidelines for making websites usable by people with disabilities, and they are the standard the U.S. Department of Justice has adopted for state and local government websites.

Accessibility is ongoing work, not a one-time checkbox. I check new pages as I build them, and I fix problems as soon as I find them.

What this site does

  • A “Skip to content” link and a main content landmark so keyboard and screen reader users can jump past the menu
  • A clear heading structure, with one main heading on each page and headings in order
  • Descriptions for images that carry meaning, so screen readers can describe them
  • Keyboard access to menus, buttons, links and forms, with links that say where they go
  • Labeled form fields, with clear messages when something needs fixing
  • Readable text and color contrast, with text that can be enlarged without breaking the layout
  • Reduced motion: if your device is set to reduce motion, hover and scroll effects are turned off
  • Mobile-friendly layouts that work on phones, tablets and large screens
  • Translation into other languages with the language menu at the top of every page
  • Plain language, written for real people instead of industry jargon

How I check

I use a mix of automated tools and hands-on testing: the Accessibility Checker plugin for WordPress, color contrast checks, and moving through each page with only a keyboard. Automated tools catch a lot, but not everything, which is why the hands-on part matters.

Where I’m still improving

  • Reviewing older blog posts and PDFs, which were written before my current checks
  • Making sure embedded content from other services, such as maps, videos and social media posts, has titles and works with a keyboard

Some content comes from other companies, such as Google Maps, YouTube, Facebook and payment pages. I choose accessible options where I can, but I can’t fully control how those services work.

Need help or found a problem?

If anything on this site is hard to use, please tell me. I’ll help you get the information you need another way, and I’ll work on fixing the problem. I aim to reply within 2 business days.

It helps to include the page address and a short description of what went wrong, but any message is welcome.

For my clients

Every site I build follows the same standard. If you run a town or other public agency, ask me about accessibility reviews of your existing pages and documents, and about your own accessibility statement.

Scroll to Top