1. Conformance target
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, and we take the Americans with Disabilities Act (ADA) and Section 508 standards into account when designing new features. We describe our status as partially conformant: most of the product meets the standard, and the areas that do not are listed below rather than omitted.
2. Measures we take
- Semantic HTML with landmark regions, real headings, and labelled form controls.
- Accessible component primitives (dialogs, menus, tabs, selects) that manage focus, keyboard interaction, and ARIA roles for us.
- Full keyboard operability for primary flows, with a visible focus indicator on interactive elements.
- Color choices reviewed for contrast, in both light and dark themes; color is never the only way information is conveyed.
- Text that resizes and reflows on zoom and on small viewports, without loss of content or functionality.
- Meaningful alternative text for informative images, and empty alternative text for decorative ones.
- Accessibility considered during design and review of new features, rather than retrofitted.
3. Known limitations
We would rather name these than imply full conformance. We are actively working on:
- Data tables and charts — dense analytics views and charts may not expose complete information to screen readers. Every chart is backed by data that can be exported to CSV as an accessible alternative.
- Drag-and-drop interactions — some ordering interactions are pointer-oriented; keyboard-accessible equivalents are being added.
- Third-party content — embedded payment and authentication flows are rendered by our providers, and their accessibility is outside our direct control.
- Customer-generated content — documents, notes, and files uploaded by customers are not controlled by us and may not be accessible.
4. Compatibility
The Service is designed to work with recent versions of Chrome, Edge, Firefox, and Safari, used with current versions of screen readers such as NVDA, JAWS, and VoiceOver. It may not work reliably on browsers older than two major versions.
5. Feedback and assistance
If you encounter a barrier, or need information in an alternative format, contact accessibility@businessmanagementai.com. Please include the page or feature, what you were trying to do, and the browser and assistive technology you were using.
We aim to acknowledge accessibility feedback within 3 business days and to provide a remediation plan or a workaround within 10 business days. Feedback about a barrier is treated as a defect report, not a feature request.
6. Assessment approach
We self-evaluate using a combination of automated tooling and manual keyboard and screen reader testing. We have not commissioned a third-party audit; this statement will be updated with the results if we do.