Effective date: [EFFECTIVE_DATE] · Last updated: [EFFECTIVE_DATE]
[LEGAL_ENTITY_NAME] (“Synapse AI,” “we,” “us”) wants everyone to be able to plan, run and deliver work with Synapse AI, including people who use assistive technologies. This statement explains our accessibility goal, the steps we take to reach it, the limitations we know about and how to contact us if you run into a barrier.
1. Our Commitment
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. WCAG 2.2 is published by the World Wide Web Consortium (W3C) and defines how to make digital content more accessible to people with visual, auditory, motor, speech, cognitive and neurological disabilities.
This is a goal, not a statement of full conformance. Some parts of our website and product do not yet meet every Level AA success criterion. We describe the known gaps in Section 5 and are working to close them.
2. Scope
This statement applies to:
- Our public website at [SITE_DOMAIN], including product, pricing, careers, blog and legal pages.
- The checkout and billing portal used to purchase and manage plans.
- The Synapse AI web application, including tasks, projects, docs, meetings, dashboards and Synapse Copilot.
- The Synapse AI desktop apps for macOS and Windows and the companion apps for iOS and Android.
Content that customers create inside their own workspaces, such as documents, files and project descriptions, is the responsibility of the customer that creates it. Third-party services that connect to Synapse AI are covered by those providers’ own accessibility practices.
3. Measures We Take
3.1 Design
- Our design system defines color pairs that meet WCAG AA contrast ratios: at least 4.5:1 for body text and 3:1 for large text and interface components, on both light and dark backgrounds.
- Our design standards call for visible focus indicators on every interactive element and pointer targets of at least 24 by 24 CSS pixels, the WCAG 2.2 minimum.
- We do not rely on color alone to convey status. Priority, risk and workload indicators also use text labels, icons or patterns.
- Designers review new features against an accessibility checklist before development begins.
3.2 Development
- We use semantic HTML with a logical heading structure and landmark regions, and add WAI-ARIA attributes where native elements are not enough.
- Core workflows, including creating and updating tasks, approving AI suggestions and navigating projects, are designed to work with a keyboard alone.
- Forms have programmatic labels, clear instructions and error messages that identify the field and explain how to fix the problem.
- Layouts support browser zoom and text resizing up to 200% and reflow to a width of 320 CSS pixels.
- Status changes, such as a completed automation run or a newly generated meeting summary, are announced to screen readers without moving focus.
3.3 Testing
- Automated accessibility checks run as part of our development pipeline and flag common issues before code is released.
- We manually test key user journeys with a keyboard, with screen readers on Windows, macOS, iOS and Android, and with operating system zoom and high-contrast settings.
- Accessibility defects are tracked alongside other product defects and prioritized by their impact on users.
3.4 Features that support accessibility
- Meeting Intelligence produces searchable transcripts and written summaries of recorded meetings, which can help participants who are deaf or hard of hearing or who prefer to review content in text.
- Synapse Copilot lets users ask questions about projects and documents in plain language instead of navigating complex views.
- On plans that include Portfolio Analytics & Risk Radar, dashboards support scheduled CSV exports, so chart data can be reviewed in the spreadsheet tools and assistive technologies you already use.
3.5 Our team
Product designers, engineers and support staff receive accessibility training, and we consider accessibility when we select third-party components and vendors.
4. Compatibility
Synapse AI is designed to work with the current versions of major web browsers and the assistive technologies commonly used with them. Our web experiences rely on HTML, CSS, JavaScript and WAI-ARIA. Older browsers and assistive technologies may not support every feature.
5. Known Limitations
Despite our efforts, some content does not yet fully meet our goal. The limitations we know about are:
- Motion on marketing pages: Some website pages use headings that animate letter by letter and continuously scrolling logo strips. These do not yet offer a pause control and may not respect the reduced-motion setting in your operating system. We are adding a pause control and support for that setting.
- Product images: Illustrations of the product interface on our website contain text inside images. Each image has alternative text that summarizes its purpose, but it may not describe every value shown.
- Complex visualizations: The workload heatmap, dependency graph and delivery forecast charts are primarily visual. Summary figures are available as text, and we are building fully accessible table views for these visualizations.
- Drag-and-drop: Some board and planning views rely on drag-and-drop. Keyboard alternatives are available for moving tasks, but not yet for every planning interaction.
- Automated transcripts: Meeting transcripts and summaries are generated automatically and may contain recognition errors, particularly for specialist terminology, overlapping speech or poor audio. They are not a substitute for professional captioning where that is required.
- Third-party content: Embedded payment fields, video meeting platforms and connected integrations are provided by third parties, and their accessibility is outside our direct control.
- PDF documents: Some PDF files we provide, such as order forms and procurement documentation, may not be fully tagged for assistive technologies. Accessible versions are available on request.
6. Feedback and Assistance
If you have difficulty using any part of our website or product, or if you need information in an alternative format, please contact us:
- Accessibility contact: [ACCESSIBILITY_CONTACT]
- Phone: [PHONE_NUMBER]
- Postal mail: [LEGAL_ENTITY_NAME], Attn: Accessibility, [MAILING_ADDRESS]
To help us respond, please tell us the web address or product area involved, what you were trying to do, the problem you encountered and the browser, device and assistive technology you use, if any.
We aim to respond to accessibility feedback within [ACCESSIBILITY_RESPONSE_DAYS] business days. If we cannot resolve the issue right away, we will explain the next steps, provide the information or service you need through an alternative method where possible, and keep you updated on our progress.
If you are applying for a job with us and need a reasonable accommodation during the application or interview process, contact [ACCESSIBILITY_CONTACT]. See our Candidate Privacy Notice for how we handle that information.
7. Escalation
If you are not satisfied with our response, you may write to our legal team at [LEGAL_EMAIL]. We will review your concern and respond in writing.
8. Accessibility Documentation for Customers
Enterprise customers and prospective customers who need accessibility documentation for procurement, such as an Accessibility Conformance Report where available, can request it through their account team or at [ACCESSIBILITY_CONTACT].
9. Assessment and Review of This Statement
This statement is based on a self-assessment by our design and engineering teams that combines automated testing with manual review of key pages and user journeys. It is not a third-party audit or certification.
We review this statement at least once a year and whenever we make significant changes to our website or product. The date at the top of this page shows when it was last updated.