Skip to content
Joe Tries

Accessibility

Last updated July 14, 2026

Joe Tries should work for everyone, including people who use screen readers, keyboard navigation, screen magnification, or other assistive technology. We treat accessibility as part of building the site, not an afterthought, and this page is our honest read on where we stand and how to reach us if something gets in your way.

The standard we aim for

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, the standard most widely referenced for websites in the United States. These guidelines organize accessibility around four ideas: content should be perceivable, operable, understandable, and robust across different devices and assistive technologies.

Where we stand today

Joe Tries is partially conformant with WCAG 2.1 Level AA. Partially conformant means most of the site meets the standard, but some content or features may not yet. We say this plainly because claiming full conformance we have not verified would be misleading.

What we have built in so far:

  • A skip-to-content link so keyboard users can jump past the navigation.
  • Semantic headings, landmarks, and real table markup with header scopes on the catalog and compare pages, so screen readers can announce structure correctly.
  • Descriptive labels on interactive controls, including filters, compare actions, and buy links.
  • Text alternatives on meaningful product images.
  • Support for your browser and system dark mode and text-size preferences.
  • Color choices checked for contrast against the AA thresholds.

Known limitations

We are still improving in these areas, and we mention them so you know they are on our list rather than overlooked:

  • The home builder is a rich interactive tool, and some of its controls have not been fully tested with every screen reader and keyboard-only path.
  • A small number of older product images may have generic or missing text descriptions while we finish reviewing the catalog.
  • The shareable home cards are images, so the information they show is also always available as text on the same page.

If you hit a barrier that is not listed here, telling us about it genuinely helps, and we treat those reports as priorities.

How we check

We test with a mix of automated accessibility checks during development and manual review, including keyboard-only navigation and screen reader spot checks. This is an ongoing process, not a one-time audit, and new pages are reviewed as we ship them.

Tell us about a barrier

If any part of Joe Tries is hard to use with your assistive technology, or you cannot get to information or a feature you need, please email joe@joetries.com. Tell us the page, what you were trying to do, and the assistive technology or browser you were using, and we will get back to you. We aim to respond within five business days, and if we cannot fix something quickly we will try to get you the information another way in the meantime.

Related pages

For how we verify product data, see how we check. For how we handle your data, see our privacy policy.