99dots Accessibility Statement

1. Our Commitment to Digital Accessibility and Inclusion

SnackSafe Inc. believes that access to technology is a matter of equity, and we design 99dots so that people of all abilities can use it effectively. We are committed to providing a digital experience that is perceivable, operable, understandable, and robust for the widest possible range of users, including people who are blind or have low vision, people who are deaf or hard of hearing, people with limited mobility or motor differences, people with cognitive or learning differences, and people who use assistive technologies such as screen readers, screen magnifiers, voice control, alternative input devices, and keyboard-only navigation.

Accessibility is not a one-time project for us; it is an ongoing commitment that informs how we plan, design, build, test, and ship the Service. We treat accessibility as a core part of product quality rather than an optional enhancement, and we hold ourselves accountable to continuous improvement as standards, technologies, and user needs evolve.

2. Our Conformance Target

We design and build 99dots to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, the standard published by the World Wide Web Consortium (W3C) and widely recognized as the benchmark for accessible digital experiences. WCAG defines success criteria organized around four principles, requiring that content be perceivable, operable, understandable, and robust, and we use these criteria as the practical measure of our work.

In addition to WCAG 2.1 Level AA, we actively track and work toward the newer WCAG 2.2 Level AA success criteria, and we incorporate 2.2 requirements into our design system and testing as we advance. Our aim is to meet these standards across the core, frequently used areas of the Service, and to close gaps in less central or newer areas over time through our regular release and audit process.

3. Accessibility-First by Design

Accessibility is built into 99dots from the start, not bolted on afterward. It is embedded in our design system and shared component library, so that the building blocks used across the Service carry accessible behavior by default and improvements to a single component propagate consistently everywhere that component is used.

In practice, this means we build on semantic HTML and meaningful document structure, using headings, landmarks, lists, and native controls so that assistive technologies can convey the layout and purpose of each page. We design color and contrast to meet or exceed WCAG AA thresholds for text and meaningful interface elements, and we do not rely on color alone to communicate information. We provide clearly visible focus states so that people navigating by keyboard can always see where they are, and we support full keyboard operability so that interactive features can be reached and used without a mouse.

We use ARIA (Accessible Rich Internet Applications) attributes deliberately and only where native semantics are insufficient, following the principle that correct native markup is preferable to added ARIA. We respect user preferences for reduced motion, limiting or removing non-essential animation for people who indicate that preference at the system level. We build responsive layouts that adapt to different screen sizes and orientations, and that remain usable when text is resized or the page is zoomed, so that content reflows without loss of information or functionality.

4. How We Test

We combine automated and manual testing throughout development. Automated accessibility checks, including tools such as axe and Lighthouse, are integrated into our development workflow so that many common issues are surfaced early, before features reach users. We treat automated results as a first line of defense rather than a complete measure of accessibility.

Because automated tools cannot detect every barrier, we also perform manual audits of our interfaces, including keyboard-only testing to confirm that all interactive functionality can be reached and operated without a pointing device, and review of focus order, labeling, error handling, and state changes. We test with assistive technologies, including screen readers such as VoiceOver on macOS and iOS, NVDA and JAWS on Windows, to evaluate the real experience of navigating and completing tasks with these tools. Findings from this testing feed directly into our backlog and our prioritization of fixes.

5. Ongoing Effort and Continuous Improvement

Accessibility is reviewed as part of our regular release process, so that new and changed features are evaluated against our accessibility standards before and as they ship, and so that regressions can be identified and addressed. We also conduct periodic audits of the Service as a whole to assess conformance more comprehensively and to guide longer-term improvements.

As the underlying guidelines advance, as assistive technologies change, and as we receive feedback from users, we update our design system, components, and testing practices accordingly. We view accessibility as an ongoing responsibility, and we are committed to making measurable progress over time rather than treating conformance as a fixed or finished state.

6. A Candid Note on Limitations

We want to be transparent that, despite our efforts, some parts of 99dots may not yet fully conform to WCAG 2.1 Level AA. Certain third-party or embedded components, integrations, and content that we do not fully control, and newly shipped features that have not yet completed our full accessibility review, may contain accessibility gaps at a given point in time.

Where we identify such issues, we prioritize remediation based on severity and user impact, and we work to bring affected areas into conformance through our regular release and audit cycles. If you encounter a barrier that prevents you from using any part of the Service, we want to hear about it, and we will work with you to provide the information or functionality you need while we address the underlying issue.

7. How to Give Feedback or Request Assistance

We welcome your feedback on the accessibility of 99dots, and we treat accessibility reports as a priority. If you experience any difficulty accessing or using the Service, if you encounter a barrier, or if you would like to request assistance completing a task, please contact us by email at support@99dots.ai or by phone at (415) 510-9335.

To help us respond effectively, it is useful (though not required) to include a description of the problem, the page or feature involved, the browser and any assistive technology you were using, and how we can reach you. We aim to acknowledge accessibility requests and respond within a few business days, and to work with you toward a resolution or a suitable alternative.

8. Requesting an Accessible Alternative, Alternative Format, or Reasonable Accommodation

If any content or functionality within 99dots is not accessible to you, you may request the information in an alternative format or ask for a reasonable accommodation, and we will make good-faith efforts to provide the content or an equivalent alternative in a way that meets your needs. This may include providing information in a different format, offering an alternative method of completing a task, or assisting you directly.

To make such a request, please contact us at support@99dots.ai or (415) 510-9335, and describe the content or task involved and the format or accommodation that would work best for you. We will respond within a few business days and work with you to find a workable solution.

9. Formal Conformance Status Statement

The term "conformance status" describes how closely a digital product meets a given accessibility standard. SnackSafe Inc. designs and builds 99dots to conform to WCAG 2.1 Level AA and works toward WCAG 2.2 Level AA. At this time, 99dots is partially conformant with WCAG 2.1 Level AA, meaning that we aim for and work toward full conformance and that most of the Service meets the standard, while some parts may not yet fully conform for the reasons described in our note on limitations.

This statement reflects our current good-faith assessment and commitment. It is not a claim of certified or independently audited full compliance with WCAG 2.1 Level AA, WCAG 2.2 Level AA, or any other standard or legal requirement, and nothing in this statement should be read as a warranty or guarantee of conformance. We are committed to ongoing improvement and to addressing accessibility issues as they are identified.

10. Standards and References We Follow

Our accessibility work is guided principally by the Web Content Accessibility Guidelines (WCAG) 2.1 and 2.2 at Level AA, published by the World Wide Web Consortium (W3C) through its Web Accessibility Initiative (WAI). We also draw on related W3C guidance, including the WAI-ARIA specification for accessible rich internet applications and the associated authoring practices, and we consider recognized accessibility standards and expectations, such as those reflected in EN 301 549 and the principles underlying the U.S. Americans with Disabilities Act, as context for our efforts.

References to these standards are provided to explain the framework we use in our work. They do not constitute a claim of certification or legal compliance, and they are subject to the conformance status and limitations described above.

11. About This Statement and Its Date

This Accessibility Statement is provided by SnackSafe Inc., a Delaware corporation with a registered address at 251 Little Falls Drive, Wilmington, DE 19808, USA, and applies to the 99dots service and website at 99dots.ai. You can reach us regarding accessibility by email at support@99dots.ai or by phone at (415) 510-9335.

This statement was last updated on July 24, 2026. We review and revise it periodically to reflect changes in the Service, our practices, and applicable standards, and any updates will be posted here with a revised date.