Accessibility Statement

1. Our Commitment

StackDaily is built to be usable by as many people as possible, including people who navigate by keyboard, use a screen reader, rely on magnification, or prefer reduced motion. We treat accessibility as part of building the product rather than as a separate exercise, and our internal engineering standard targets WCAG 2.1 Level AA.

2. Conformance Status

StackDaily is partially conformant with WCAG 2.1 Level AA. “Partially conformant” means that some parts of the product do not yet fully meet the standard. We are stating this plainly rather than claiming full conformance, because we have not completed a comprehensive third-party audit and we know of outstanding issues.

This statement is based on our own testing, including automated checks of page structure and interactive controls across the application.

3. What We Currently Support

• Keyboard navigation. Interactive controls are reachable by keyboard, dialogs and drawers close with Esc, and a “Skip to main content” link appears when you first press Tab.
• Visible focus. Focus indicators are shown on interactive elements so you can see where you are on the page.
• Screen reader support. Buttons and icons carry text labels, form fields are associated with labels, dialogs use appropriate roles, and status changes are announced through live regions.
• Reduced motion. If your device is set to reduce motion, we suppress animations and transitions.
• Page structure. Pages use headings and landmark regions so screen reader users can navigate by structure.
• Zoom and resizing. The interface is responsive and supports browser zoom and larger text sizes.

4. Known Limitations

We would rather tell you where the gaps are than let you discover them. As of the date above, we are aware of the following:

• Some icon-only buttons in denser areas of the app — parts of the task list, the habits and notes views — do not yet expose a descriptive name to screen readers.
• A small number of form controls are not yet programmatically associated with a visible label.
• Heading levels skip a step on some screens, which can make navigating by heading less predictable.
• Some elements respond to clicks without an equivalent keyboard interaction.
• Colour contrast has not been comprehensively verified against the 4.5:1 ratio across every surface and theme.
• Rich content — the notes editor and charts — has had less accessibility testing than the rest of the product.
• We have not completed testing with every combination of assistive technology, browser, and operating system.

These are tracked in our engineering backlog and our automated checks now flag them as they are introduced.

5. Feedback and Reporting a Barrier

If something in StackDaily prevents you from doing what you need to do, please tell us — reports from people who actually hit the barrier are the most useful input we get. Email support@stackdaily.ai with the page or feature, what you were trying to do, and the assistive technology and browser you were using, if you know them.

We aim to acknowledge accessibility reports within 5 business days and will tell you what we intend to do and roughly when. If we cannot fix something quickly, we will try to offer a workaround.

6. Alternative Access

If a part of StackDaily is not usable for you, contact us at the address above and we will work with you to provide the information or complete the task another way, including help with account, billing, and data-export requests.

7. Assessment Approach

This statement reflects self-evaluation. We use automated accessibility checks in our development process and review page structure, keyboard operation, and control labelling as part of building features. We have not yet commissioned an independent external audit or formal user testing with assistive technology users; when we do, we will update this page.

8. Changes to This Statement

We will update this statement as we fix known issues and as the product changes. The date at the top reflects the most recent review.

9. Related Policies

See also our Privacy Policy and Terms of Service.