Accessibility

Our commitment

Bespoke Technologies aims to make Bespoke AI useful to people with varied abilities, devices, assistive technology, and ways of interacting. Accessibility is treated as a product requirement and verification gate, not a decorative finishing step.

Our reference standard is the W3C Web Content Accessibility Guidelines 2.2. We use Level AA as the working target while also applying platform guidance and direct usability evidence.

Current foundations

• Semantic landmarks, ordered headings, named controls, associated field labels, and a skip link on public pages.
• Visible keyboard focus and focus-managed menus, dialogs, sheets, notices, and tooltips.
• At least 44-pixel primary touch targets for buttons and icon controls in the shared design system.
• Light mode by default, an explicit dark appearance setting, semantic colour tokens, and meaning that does not rely on colour alone.
• Polite live regions for changing response activity and urgent announcements reserved for failures that require immediate attention.
• Responsive reflow for narrow mobile layouts and restrained reading measures for long-form public information.
• Reduced-motion contracts for non-essential movement and product states that remain understandable without animation.

AI-generated and user-provided content

Generated responses are presented as structured parts such as text, citations, code, activity, reasoning, and artifacts. The interface supplies names and status semantics around those parts, but the accessibility and accuracy of generated content can still vary.

Uploaded documents, images, audio, video, linked websites, and generated artifacts may not include complete captions, descriptions, headings, language metadata, or accessible reading order. Review and remediate content before publishing or relying on it as an accessible deliverable.

Known limitations

• An independent end-to-end WCAG conformance audit has not yet been recorded.
• Complex generated code, tables, diagrams, images, and third-party embeds may require an alternative description or format.
• Real-time streaming can update frequently. We aim to announce one measured phase, but some assistive-technology combinations may still feel busy.
• Third-party authentication, payment, support, and linked provider pages are governed by their own accessibility practices.
• The product is tested primarily in current browsers; older browsers and uncommon assistive-technology combinations may behave differently.

How we test

The delivery workflow includes component semantics, keyboard behavior, visible focus, mobile reflow, link integrity, and automated accessibility checks. Automated tests cannot establish conformance alone, so representative flows also require manual keyboard and visual review.

Request help or an alternative format

If a page, control, document, or generated artifact is difficult to use, contact us with the route, task, browser or device, assistive technology if relevant, and the format or outcome you need. Do not include passwords, one-time codes, or unnecessary private workspace content.

Use the signed-in Support page or the Bespoke Technologies contact page. We will acknowledge the report, assess a practical workaround, and use it to prioritise remediation.

Changes and version history

A material change to our accessibility commitment or stated limitations receives a new calendar version and preserves the prior statement. Product fixes are recorded in the Changelog.