Accessibility statement.
We're committed to making strongerthanyesterday.com usable by everyone. This statement reflects our current state and the work in progress.
WCAG 2.1 Level AA.
Our goal is conformance with Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. This is the standard most US e-commerce sites target and the standard most assistive technologies expect.
We're not there yet across every surface. The known gaps are listed below.
Audited April 29, 2026.
We performed an accessibility audit covering all major surfaces of the rebuild: the homepage, four catalog pages, four product detail pages, three editorial pages, and two utility pages.
The audit used automated scanning (axe-core 4.10.2) supplemented by manual testing for keyboard navigation, focus management, ARIA implementation, alt-text coverage, heading hierarchy, and color contrast.
Across the 14 pages scanned, automated checks pass at roughly 92% by rule-instance. Two critical-impact violations were identified and fixed in the same release. The remaining issues are documented below as known limitations with a remediation roadmap.
A post-remediation re-scan on April 30 (after the unified-dark conversion shipped) returned zero color-contrast violations across all 14 pages under WCAG 2.0/2.1 AA scope.
What's still open.
The audit identified specific issues we're working to address. We're listing them here so you know what we know.
- Legacy policy pages. Privacy, Terms, Shipping, and Refund policies still bounce to our legacy Shopify storefront. Those pages use a different template and were not part of this audit. Replacing them with locally-hosted accessible versions is a separate workstream.
What's been fixed.
Issues we've remediated since the April 29 audit ran.
- Header landmark wrapper (resolved 2026-04-30). The masthead-plus-nav region now sits inside a
<header role="banner">element on every page. Screen-reader users navigating by landmark can now jump directly to the banner region using the same pattern they use for nav, main, and footer. - Color contrast on quiet utility text (resolved 2026-04-30). Several small brand-color elements (section eyebrows on the catalog and editorial pages, footer attribution text, trust strip on product pages) fell below the WCAG AA 4.5:1 ratio when rendered against the light-background pages we used to ship. The site converted to a unified dark register on April 30, which lifts every brand-color contrast pairing into the AA-passing range. Brass typography on dark now reads at 6.6:1 to 10.3:1, and quiet utility text reads at 4.9:1. The conversion was both a brand decision and an accessibility win.
- Mobile menu in tab order while closed (resolved 2026-04-29). The slide-in mobile menu was hidden visually but its links remained keyboard-focusable. Fixed by replacing the
aria-hiddenpattern with theinertattribute across all surfaces, which removes the menu from both the accessibility tree and the tab order while it's closed. Same fix applied to the cart, wishlist, filter, quick-view, and search panels for consistency. - Mobile X close button (resolved 2026-04-29). On the All Products page and the four product detail pages, the X button in the open mobile menu had no event listener. Clicking it did nothing. Fixed in the same pass; X now correctly closes the menu and restores the hamburger button to its closed state.
How we're fixing it.
We address identified issues on an ongoing basis rather than against fixed dates. The two critical-impact violations from the April 29 audit were fixed in the same commit as this statement. The known limitations above are queued in priority order.
New work added to the rebuild includes accessibility considerations as standard. We re-run the automated audit after every commit that touches shared structure, and a full 14-page re-audit ships quarterly or when a major surface lands.
If you hit a barrier.
If you encounter an accessibility barrier on our site, write to support@strongerthanyesterday.com with "Accessibility" in the subject line.
Tell us what you were trying to do, what got in the way, and what assistive technology you were using if any. We respond directly and address the issue.
Last updated
This statement was last updated .