Last updated: August 26, 2026
I want jeffcalaway.com to be useful and welcoming to as many people as possible. Accessibility shouldn’t be something added after the “real” work is finished. It should be part of how the site is designed, written, built, and maintained from the beginning.
My approach
My goal is to make accessibility the default rather than an afterthought. That means choosing accessible patterns when I build shared components, writing content with different readers in mind, and fixing problems at their source so improvements carry across the site.
I use established web accessibility guidance, including the Web Content Accessibility Guidelines (WCAG), to inform decisions. I’m not claiming that every page currently meets every guideline or that the site is perfectly accessible. Accessibility is ongoing work, and real experiences matter more than a checklist.
What the site currently does
The site currently includes a number of accessibility features and practices:
- Semantic structure: Pages use headings, landmarks, lists, buttons, links, forms, and other HTML elements according to their intended purpose whenever practical.
- Skip links: Keyboard users can skip directly to the main content, navigation menu, or footer.
- Keyboard access: Navigation, search, tabs, menus, dialogs, pagination, and other interactive controls are designed to work without a mouse.
- Visible focus: Interactive elements display a visible focus indicator so keyboard users can tell where they are on the page.
- Accessible names and status updates: Icon-only controls have text labels for assistive technology, and changing search information is announced where appropriate.
- Readable, responsive layouts: Content adapts across screen sizes and is designed to remain readable on phones, tablets, and larger displays.
- Motion preferences: Several animated features reduce or remove motion when a visitor has enabled the reduced-motion preference on their device.
- Text alternatives: Meaningful images and media can include descriptive text, while decorative visuals are kept from adding unnecessary noise for screen readers.
- Automated and manual review: Accessibility checks are part of development, and components are reviewed with keyboard and assistive-technology needs in mind. Automated tools help, but they can’t find every problem.
Where the site may fall short
This is a personal site maintained by one person. My available time and energy are limited, so some accessibility issues may take longer to find and fix than I’d like. Older content, third-party services, embedded media, or unusual combinations of browsers and assistive technology may also behave in ways I haven’t caught yet.
That’s context, not an excuse to ignore a barrier. If something is keeping you from using the site, I want to know about it and I’ll do my best to address it. I simply ask for a little grace if a complete fix takes time.
What I intend to keep improving
As the site grows, I intend to:
- Keep accessibility requirements in shared components and design decisions
- Test important interactions with a keyboard and accessibility tools
- Improve color contrast, focus behavior, labels, and error messages when issues are found
- Add or improve alternative text, captions, transcripts, and other content alternatives where they’re needed
- Review new content for clear headings, meaningful link text, and easy-to-understand language
- Revisit older pages and components instead of treating accessibility as a one-time project
Third-party content
Some pages may link to or use services I don’t control. I can’t guarantee the accessibility of another website or platform, but I’ll try to choose accessible options and provide alternatives when that’s practical.
Feedback and accessibility requests
If you find an accessibility problem, need content in another format, or have an idea that would make the site easier to use, email support@jeffcalaway.com.
It’s helpful if you include:
- The page or feature you were using
- What happened and what you expected to happen
- Your browser, device, or assistive technology, if you’re comfortable sharing it
- The kind of alternative or adjustment that would help
You don’t need to explain or prove a disability to ask for help. Please don’t include private or sensitive information in your first message. I’ll review requests in good faith and respond as soon as I reasonably can.