Accessibility Statement

Bach.ai — operated by Wittelsbach Private Limited — is committed to making this website usable for everyone, including people who rely on assistive technologies. Accessibility is part of how we build, not a box we tick at the end, and we work to keep this site measurably easier to use over time.

1. Conformance target

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA — the standard widely referenced by accessibility law in the EU, UK, US and beyond. These guidelines explain how to make web content more accessible to people with a wide range of disabilities, including visual, motor, auditory, speech and cognitive differences.

This site is substantially conformant with WCAG 2.1 Level AA: it meets the great majority of the success criteria, with a small number of known exceptions listed below that we are actively resolving.

2. Measures we take

Accessibility is designed into the rebuilt site. Concretely, that includes:

• Semantic HTML landmarks — every page is structured with real header, nav, main and footer regions and a logical heading order, so screen readers can announce and navigate the page by structure.
• Skip-to-content link — a “Skip to content” link is the first focusable element on every page, letting keyboard and screen-reader users jump straight past the navigation to the main content.
• Keyboard-operable navigation and dialogs — all interactive elements, menus and dialogs can be reached and operated with the keyboard alone. Dialogs manage focus (focus moves in on open and returns on close) and can be dismissed with the Esc key.
• Visible focus indicators — every focusable element shows a clear, branded focus ring (never outline: none without a replacement), so keyboard users can always see where they are.
• Reduced-motion support — we respect the operating-system prefers-reduced-motion setting. When it is on, scroll reveals, count-ups, parallax and decorative animation are switched off and content is shown in its final, static state.
• Descriptive alternative text — meaningful images carry descriptive alt text, while purely decorative graphics are hidden from assistive technology so they don’t add noise.
• Sufficient colour contrast — body text, headings and interactive controls are chosen to meet the WCAG AA contrast ratios against their backgrounds.
• Responsive, zoomable layout — the layout reflows cleanly from large desktops down to small phones and supports browser zoom up to 200% and text resizing without loss of content or function. We do not disable pinch-to-zoom.
• Generous touch targets — interactive controls are sized to at least 44×44 px (or given an equivalent hit area) so they are comfortable to tap on touch devices and easier to activate with imprecise pointing.
• Tabular figures — on-screen numbers use tabular (monospaced-width) digits so data is easy to scan and compare.

3. Technical approach

The site is built with semantic HTML, CSS and a small amount of progressive-enhancement JavaScript. Core content and navigation do not depend on JavaScript: where scripts add motion or interactivity, the underlying content remains available and readable if those scripts do not run. We rely on native HTML semantics first and add ARIA only where it genuinely improves the experience.

4. Known limitations

We want to be honest about where we fall short. Despite our efforts, you may encounter the following, and work to address each is in progress:

• A few low-contrast micro-labels. Some small uppercase eyebrow and caption labels are rendered at a reduced opacity for visual rhythm and can sit just under our target contrast ratio. We are raising these to meet AA.
• Decorative animated figures. A handful of illustrative, animated diagrams convey their meaning primarily through motion and colour. They are decorative rather than essential, and we are adding clearer static fallbacks and text equivalents.
• Third-party and embedded content. Content served through external providers (such as embedded media) may not always meet the same standard as the rest of the site; we raise issues with those providers when we find them.

None of these prevent access to the core information or actions on this site, and they are tracked for resolution.

5. Feedback and reporting an issue

We welcome your feedback on the accessibility of Bach.ai. If you hit a barrier, or something here is hard to use with your assistive technology, please tell us — your reports directly help us prioritise fixes.

• Email us at info@wittelsbach.ai
• Or reach us through our contact page

When you report an issue, it helps to include the page address, what you were trying to do, and the browser and assistive technology you were using. We aim to acknowledge accessibility reports within five business days. If you need information from this site in an alternative format — for example, a different file format or a plain-text version — let us know and we will provide it.

6. Assessment and review

We assess this site against WCAG 2.1 Level AA through a combination of automated checks, manual keyboard and screen-reader testing, and code review, and we re-check accessibility as part of shipping new pages and features.

Last reviewed: 13 August 2026. This review combined automated WCAG 2.1 AA scanning (axe-core) across representative pages at desktop and mobile widths, layout reflow checks down to 320 CSS pixels, and code review of the landmarks, focus handling and reduced-motion behaviour described above. We update this statement as the site evolves and as we close the limitations listed above.