Accessibility Statement
Effective: May 30, 2026 · Last reviewed: October 2, 2026
How Burna AI makes burna.ai usable by people with disabilities: our WCAG 2.2 Level AA target and current status, the measures we take, the limitations we know of, and how to report a barrier.
Effective Date
Effective date: May 30, 2026. Last reviewed: October 2, 2026.
Our Commitment
Burna AI is committed to making burna.ai and the Burna AI platform usable by everyone, including people with disabilities. We treat accessibility as a requirement for every page, component and feature we release.
The people who use burna.ai include clinicians, investigators, research coordinators and nurses, sponsor and CRO safety teams, and people taking part in clinical studies, and their families, who come here to read about Healthnotes. Some have temporary or permanent disabilities, some use assistive technology, and many read our pages under stress, fatigue or limited time. We design with that reality in mind.
Conformance status
This statement covers the burna.ai website, including the Healthnotes pages at burna.ai/healthnotes. The Burna AI platform at app.burna.ai is built with the same component library and design rules. Customers who need accessibility information about the platform can write to [email protected].
burna.ai is designed to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA, published by the World Wide Web Consortium (W3C). WCAG 2.2 is the most recent version of the guidelines published as a W3C Recommendation.
Current status: partially conformant with WCAG 2.2 Level AA. Partially conformant means that some parts of the content do not fully conform to the standard. Burna AI made this assessment itself, against the design rules and automated checks described below. The parts known not to conform are listed under Known limitations, and we update this statement as they are fixed.
Standards referenced
Burna AI takes the following standards and laws into account. Where they differ, we aim to meet the most stringent requirement that applies in a user's jurisdiction.
- WCAG 2.2 Level AA, W3C.
- Americans with Disabilities Act (ADA), Title III, United States.
- Section 508 of the Rehabilitation Act (Revised 508 Standards), United States federal procurement.
- EN 301 549, accessibility requirements for ICT products and services, European Union.
- Accessibility for Ontarians with Disabilities Act (AODA), Ontario, Canada.
- Equality Act 2010, Great Britain, and Disability Discrimination Act 1995, Northern Ireland.
- Disability Discrimination Act 1992, Australia.
Measures taken
Burna AI takes the following measures across burna.ai. They reflect our standing design and engineering practice.
- Color contrast. Our design rules set the WCAG 2.2 AA ratios as the minimum: 4.5:1 for normal text, and 3:1 for large text and for the visual parts of controls and graphics.
- Semantic structure. Pages are built from semantic HTML (headings, lists, landmark regions, and native buttons and links) so assistive technology can convey how each page is organized.
- Bypassing navigation. Pages across the public site mark their main content as a landmark region, so screen reader users can move straight to it. The Burna Learn pages at burna.ai/learn also offer a skip-to-content link.
- Keyboard operation and focus. Menus, dialogs, tabs and other interactive components come from our shared component library, which is built on open-source primitives that provide keyboard operation, focus management and ARIA roles. Buttons and form fields from that library show a visible focus ring when you reach them with a keyboard.
- Text alternatives. Images that carry information are given text alternatives, and decorative images are hidden from assistive technology.
- Forms. Form fields have a label that assistive technology announces. Most show that label on screen; the search box and the newsletter sign-up show placeholder text and carry their label for assistive technology. Fields built with our shared field component are tied to their label and to their error message, and errors are stated in text, not by color alone.
- Motion. Our design rules require animation to respect the reduced-motion setting in your operating system, and require every new animation to be checked with that setting turned on before it ships.
- Appearance. A theme control on the site switches between light and dark appearance, and your browser remembers the choice.
- Resizing. Layouts are responsive and sized in relative units, so pages adapt when you zoom the browser or enlarge text.
- Language. burna.ai is published in English, and every page declares English as its language so screen readers pronounce it correctly.
Compatibility
burna.ai is built to web standards so that it works with current versions of Google Chrome, Microsoft Edge, Mozilla Firefox and Apple Safari, on Windows, macOS, iOS, Android and Linux, and with assistive technologies that follow those standards, including:
- Screen readers: JAWS, NVDA, Apple VoiceOver and Google TalkBack.
- Speech recognition: Dragon and Apple Voice Control.
- Screen magnification and browser zoom.
Older browser versions, and assistive technologies that their vendors no longer maintain, may not display every feature correctly.
Testing approach
Burna AI checks accessibility in three ways today.
- Automated lint rules. Our code linter applies accessibility rules to every change in continuous integration, including alternative text on images, valid ARIA attributes and roles, labels tied to form controls, and a declared page language. A change that breaks one of these rules fails the check.
- Tests that use accessible names. Automated interface tests across our products find buttons, links and fields by their accessible role and name, as assistive technology does, so a tested control that loses its name or role fails its test.
- Design rules. Our design rules set the WCAG 2.2 AA contrast minimum and require new animation to be checked with reduced motion turned on before it ships.
Automated checks catch a meaningful share of accessibility issues, but they cannot replace human judgment, especially for content quality, cognitive accessibility and interaction with assistive technology. A full conformance assessment requires manual review with assistive technology.
Known limitations
The limitations below are known as of the Last reviewed date. We update this list as items are found and fixed.
- PDF documents. Some downloadable resources on burna.ai, such as whitepapers and briefs, may not fully conform to PDF/UA. An accessible version of any document is available on request from [email protected].
- Animation. Some animations play automatically. The looping video at the top of the How the engine works page (burna.ai/engine) has no pause control. Turning on your operating system's reduced-motion setting replaces it with a still image, and stops or simplifies the animations built with our shared motion components. A text description of any visualization is available on request.
- Newsletter sign-up. The email field in the site footer does not change its appearance when it receives keyboard focus. The field is labeled for assistive technology.
- Third-party content. The scheduler on the request-a-demo page is provided by Cal.com, and its accessibility is governed by Cal.com. If it creates a barrier for you, email [email protected] and we will arrange the conversation another way.
Feedback
If you encounter an accessibility barrier on burna.ai, or need any content in an alternative format, email [email protected].
When reporting an issue, it helps to include the page URL, a brief description of the problem, the browser and assistive technology you were using, and how you would like us to reply.
Burna AI aims to:
- Acknowledge feedback within 2 business days.
- Fix confirmed accessibility issues within 30 days where technically and operationally feasible, and tell you the expected timeline where it is longer.
Formal complaints
If your feedback is not adequately addressed, you may file a formal complaint with the appropriate regulatory body in your jurisdiction. Filing a complaint does not prevent you from continuing to work with Burna AI on a fix, and you can raise any concern with us directly first. Examples include:
- United States: the U.S. Department of Justice, Civil Rights Division, ADA enforcement.
- European Union: the national authority responsible for accessibility enforcement in your member state.
- Great Britain: the Equality and Human Rights Commission. Northern Ireland: the Equality Commission for Northern Ireland.
- Canada (Ontario): the Accessibility Directorate of Ontario.
- Australia: the Australian Human Rights Commission.
Review and updates
Last reviewed: October 2, 2026.
Burna AI will review this Accessibility Statement after any significant change to the structure, navigation or core functionality of burna.ai, and will update the Last reviewed date each time it does.
Questions about this document go to [email protected].