Accessibility Statement

1. Our Commitment

DailySobrietyReflections.com is meant to be usable by everyone, including people who use screen readers, keyboard-only navigation, voice control, or other assistive technology. We're a small, independently run site, but accessibility is something we actively work on, not an afterthought.

2. Conformance Target

We target WCAG 2.1 Level AA. We have not commissioned a formal third-party audit, and we do not claim full conformance — some parts of the site fall short in ways we describe honestly below. What follows is a real account of where things stand, not a promise of perfection.

3. Steps We've Taken

• Every text/background color pairing used for body text has been checked against the WCAG contrast formula and meets or exceeds 4.5:1 (our advertisement labels were found to fail this and have been corrected).
• A visible focus indicator (:focus-visible) is applied sitewide so keyboard users can always see which element is focused, instead of relying on a browser default that's easy to lose track of.
• A skip-to-content link is present at the very start of every page, so keyboard and screen reader users can bypass the navigation and jump straight to the main content.
• Every image on the site has descriptive alt text, or an empty alt where the image is purely decorative.
• Heading levels follow a single, logical order on every page (one H1, no skipped levels) so screen reader users can navigate by heading.
• A prefers-reduced-motion media query is honored sitewide — if your system is set to reduce motion, our animations and transitions are shortened accordingly.
• Form fields (including the contact form) have visible labels, and status messages use ARIA live regions so screen reader users are told when a message sends successfully or fails.

4. Known Limitations

We'd rather tell you where this site currently falls short than imply everything is solved:

• We have not yet completed testing with real screen reader software (e.g. NVDA, JAWS, VoiceOver) across every page — testing so far has focused on code-level checks (contrast math, DOM structure, ARIA attributes), not full assistive-technology walkthroughs.
• Some decorative flourishes (icons, emoji) may not be marked up perfectly consistently across every page yet; we're working through these systematically rather than page-by-page.
• We have not yet run this site through a live PageSpeed/Lighthouse accessibility audit on production; the checks described above were performed against the site's source code.

5. Feedback & Contact

If you use assistive technology and run into a barrier anywhere on this site, please tell us. Use our contact form and select "I found a bug or issue" — describe the page and what happened, and we'll look into it. We do not publish a direct email address to prevent spam, but every message submitted through the contact form is received and reviewed by the site owner.

6. Ongoing Work

Accessibility isn't a one-time checklist for us — this statement will be updated as we test further and make improvements. If you'd like to know what's changed, the "Updated" date at the top of this page reflects the most recent revision.