Draft for review
This Accessibility Statement is a draft prepared for internal review and does not constitute a final, legally binding commitment. It is based on code-level observations and has not been verified by a formal accessibility audit. The content may change after review and before launch.
Commitment to accessibility
TODO: legal company name placeholder (“we”, “us”, “our”) is committed to making AutoStitch accessible to the widest possible audience, including people with disabilities. We aim to provide an inclusive experience and are working toward improving the accessibility of our service on an ongoing basis.
Current accessibility goals
We are working toward conformance with the Web Content Accessibility Guidelines (WCAG). No specific WCAG version or conformance level has been formally adopted at this time.
TODO: Confirm WCAG target version and conformance level after product and legal review.
Supported accessibility features
Based on a code-level review, the following accessibility practices are currently observed in AutoStitch. These observations do not guarantee full coverage across every feature or page.
Semantic HTML and ARIA
The application uses semantic HTML elements and ARIA attributes, including aria-label usage, to convey meaning and structure to assistive technologies. Role attributes are used for interactive elements where technically feasible.
Keyboard navigation
Keyboard navigation is supported in parts of the application. Tabindex attributes are used to manage focus order, and focus management has been observed in authentication flows, status indicators, modals, and form elements.
Images and alternative text
Alt attributes are provided for images, where technically feasible, to support users who rely on screen readers or other assistive technologies.
Visual design and contrast
The application uses a dark theme with high-contrast white text on dark backgrounds. The Inter font family and responsive font sizing are used to support readability across device sizes.
Known limitations
We are aware of the following limitations and are working to address them where technically feasible. This list is not exhaustive and may be updated as we identify additional areas for improvement.
- No formal WCAG compliance audit has been conducted. The observations above are based on code-level review only.
- No automated accessibility testing infrastructure has been detected or implemented at this time.
- No skip-to-content links are currently provided. Users who rely on keyboard navigation may need to tab through navigation elements to reach main content.
- Focus trap behavior in modals may need further verification to ensure that keyboard users are not unintentionally trapped or that focus is properly returned when modals close.
- Not all features have been verified for full keyboard accessibility. Some interactive elements, such as drag-and-drop reordering, may not be fully operable via keyboard alone.
- Screen reader compatibility has not been formally tested across all pages and workflows.
Feedback and contact
We welcome your feedback on the accessibility of AutoStitch. If you encounter an accessibility barrier or have suggestions for improvement, please contact us:
TODO: accessibility/support email placeholder
TODO: legal company name placeholder
TODO: legal mailing address placeholder
When contacting us about an accessibility issue, it is helpful to include the page or feature where you experienced the issue, a description of the problem, and the assistive technology you were using (if applicable).
Response timeline
TODO: define response timeline after product and legal review. We aim to acknowledge accessibility feedback within a reasonable timeframe and to provide updates on any actions taken.
Ongoing improvements
We are committed to continuously improving the accessibility of AutoStitch. Our ongoing efforts include:
- Reviewing and improving keyboard navigation across all features
- Evaluating automated accessibility testing tools for integration into our workflow
- Monitoring for accessibility issues reported by users
- Working toward a formal accessibility audit when feasible
- Training our team on accessible design and development practices
Changes to this statement
We may update this Accessibility Statement from time to time to reflect changes in our accessibility practices, features, or legal requirements. When we make material changes, we will update the “Last updated” date at the top of this page.