Accessibility Statement

Last updated: October 30, 2026

Our commitment

The Smart Prepper is built for a wide audience — beginners, families, apartment residents, homeowners, commuters, outdoor enthusiasts, seniors, people with accessibility needs, and pet owners. That range is the point: preparedness advice that only works for one type of household is not preparedness advice at all. We design every page with accessibility in mind because the people who need preparedness guidance most are sometimes the people who face the most barriers online.

Standards we target

We aim to meet WCAG 2.2 Level AA, the standard referenced by the Americans with Disabilities Act and Section 508 guidelines. This includes:

• Perceivable. Text contrast meets AA ratios against backgrounds. Images have descriptive alt text or are marked decorative when not informational. Content is readable without color alone.
• Operable. All navigation, links, forms, and interactive tools are usable with a keyboard. A skip-to-content link is present on every page. Focus states are visible. No content traps keyboard users.
• Understandable. Language is plain and direct. Forms have labels and instructions. Error messages are specific, not generic. Input errors are identified and corrected with guidance.
• Robust. Pages use semantic HTML — proper headings, landmarks, lists, and table structures — so they work with screen readers and assistive technology.

What we have implemented

• A skip link at the top of every page to bypass navigation.
• Keyboard-accessible navigation with a desktop mega menu and mobile accordion that open and close with the keyboard.
• Labeled form inputs with associated labels and required-field indicators.
• Reduced-motion support: animations and hover effects respect the user's prefers-reduced-motion setting.
• Responsive design from 320px upward — no horizontal overflow on small screens.
• Sticky elements that do not cover text, disclosures, or controls. Dismissible promotional notices.
• No autoplay, flashing warnings, forced notification prompts, or repeated blocking popups.

Known limitations

We test across breakpoints (320px, 375px, 768px, 1024px, and large desktop) and with keyboard navigation, but we are a small team and may miss issues. Some interactive tools rely on browser local storage, which may behave differently across assistive technology. If you encounter a barrier, please report it — we prioritize fixing accessibility issues that block access to core content or tools.

How to report an issue or request help

If you find an accessibility barrier — a control you cannot reach with a keyboard, a contrast problem, a missing label, or content a screen reader cannot parse — tell us. Use our contact page and include the page URL and a brief description. We will review it and work on a fix. If you need a guide or checklist in an alternative format, let us know and we will do our best to accommodate.

Ongoing effort

Accessibility is a practice, not a checkbox. We review pages as we publish them, run manual keyboard and screen-reader checks alongside automated testing, and improve as we learn. If something is not working for you, that is a bug we want to fix — not a limitation we expect you to live with.