Accessibility Statement

Bramante Biologics Corporation sells reagents to laboratories, and a laboratory is staffed by whoever is good at the work. Some of those people use a screen reader, a keyboard and no mouse, speech recognition, a large-text setting, or a screen magnifier. A price you cannot read is not a published price, and a cart you cannot reach with a keyboard is not a store. So this is a functional requirement here, not a compliance exercise.

We target the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, published by the World Wide Web Consortium. That is the same standard referenced by Section 508 of the US Rehabilitation Act, by the Americans with Disabilities Act in practice, and by the European Accessibility Act, so it is also the standard most institutional and federal purchasing offices ask us about.

We do not claim full conformance with WCAG 2.2 Level AA today, and this statement is not a Voluntary Product Accessibility Template. We are describing what we have actually built and tested. Section III below lists the specific things we know fall short. If you need a completed VPAT or an Accessibility Conformance Report for a procurement file, write to us and we will tell you honestly what we can attest to and by when.

This statement covers bramantebio.com: the catalog, product pages, search, the cart and checkout flow up to the point it hands off to Stripe, your account pages, the support and documentation pages, and these legal pages.

Three things it does not cover, and we would rather say so than let you assume:

• Stripe Checkout. Payment happens on a page Stripe hosts and controls. Its accessibility is theirs, and Stripe publishes its own conformance information. If you hit a barrier at the payment step, tell us anyway: we can take your order by email or against a purchase order instead, and we will pass the report on.
• LabKick, our laboratory software at app.bramantebio.com. It is a separate application on a separate release cycle and is not assessed here.
• Our PDFs. Certificates of Analysis, datasheets, and Safety Data Sheets are generated documents. See Section III: they are the largest known gap on this list.

Everything below is a barrier we know about and have not fixed. Each one names the WCAG success criterion it fails, so an accessibility reviewer can check our work rather than take our word for it.

• There is no way to skip past the header.Tab into any page and you walk the whole header before you reach the content: the utility links, the menu button, the wordmark, the products menu, the primary navigation, search, account, and cart. Twelve stops, on every page, every time. WCAG 2.4.1 Bypass Blocks asks for a way around a block of content that repeats. The “Skip to main content” link that provides it is built and is waiting to be switched on site-wide. In the meantime a screen reader can jump straight to the main landmark or to the first heading, which most of them offer as a shortcut key.
• Generated PDFs are untagged. Our Certificates of Analysis, datasheets, and SDS documents are produced programmatically and carry no document structure: no headings, no table markup, no reading order. A screen reader gets a flat wall of text, and the tables in particular will not read correctly. This fails WCAG 1.3.1 Info and Relationships. If you need the contents of any of these documents in an accessible form, email us and we will send the same data as plain text or as an accessible web page, usually the same business day. We are working on tagged output.
• Two text colours are below the contrast minimum. Our muted grey measures 4.26:1 against the paper background and 4.11:1 against the warm one, and the amber we use for made-to-order and backorder status measures 4.34:1. WCAG 1.4.3 Contrast (Minimum) requires 4.5:1 at these sizes. The muted grey carries explanatory paragraphs, table captions, and form hints, so it is by count the largest failure on the site. Both are single colour-token changes, both are specified, and both are in progress. Our other status colours already pass: blue at 9.19:1, red at 7.37:1, green at 7.07:1.
• A few controls have no spoken name. The catalog sort dropdown, the dropdown on the report-an-order-issue form, and one checkbox on the account terms form are visually labelled but not programmatically labelled, so a screen reader announces them only by their type. Elsewhere on the same forms we use a shared labelled field, and these are the ones that predate it. They fail WCAG 4.1.2 Name, Role, Value. Fixes are written up and queued.
• Some links inside paragraphs are distinguished by colour alone. Where a link sits in a sentence without an underline, colour is the only cue, which fails WCAG 1.4.1 Use of Color for anyone who cannot distinguish it. Our automated checks flag this on the account pages, on the panel body copy and the alert lines, including the mailto links there. Buttons and standalone links are not affected. The fix is an underline on inline links in body copy and is queued.
• Four controls are smaller than 24 by 24 pixels. The dialog close button, the remove button on a cart line, the cancel control on the order-issue form, and our small icon buttons all sit under the 24 pixel square that WCAG 2.5.8 Target Size (Minimum) asks for. On phones and tablets our layout already enlarges them, so this is a pointer-on-desktop problem, and it is a fix of a minimum size plus padding on four rules. Escape closes any dialog without aiming at anything, but that is a workaround, not a fix.
• The pack-size selector does not respond to arrow keys. It presents itself to assistive tech as a radio group, and a radio group is supposed to move between its options with the arrow keys. Ours moves with Tab instead. Every pack size is still reachable and selectable from the keyboard, so this is a wrong keyboard convention rather than a blocked purchase. It fails WCAG 4.1.2 Name, Role, Value.
• Text fields show focus faintly.Tab onto a text box, a dropdown, or a comment box and the only change is the colour of its border: our stylesheet suppresses the browser’s own focus ring on those three and does not replace it. Links and buttons do get a proper outline. On a long form a border tint is easy to lose, so this is a weak pass on WCAG 2.4.7 Focus Visible at best. The fix gives fields the same outline the buttons already have, and is queued with the contrast change.
• Quick order by SKU reports its errors silently. Type a catalog number it does not recognise and the reason appears beside that line without being announced, so a screen reader user learns nothing happened only by going back through the rows. The same check on a product page does announce. This fails WCAG 4.1.3 Status Messages.
• The Products menu in the header uses the wrong markup. It announces itself to a screen reader as an application menu when it is a panel of ordinary links, and it points at a container by a name that container does not use. Every link in it is reachable, and the same links are on the products page without the menu, but the announcement is wrong. This fails WCAG 4.1.2 Name, Role, Value.
• We have not completed a full manual audit. We run automated checks, and automated checks find perhaps a third of real problems. We have not yet done a full keyboard-only and screen-reader pass over every page, and we have not had the site reviewed by an independent auditor. Until we have, treat this list as incomplete by definition.

The other half of an honest statement. These are things we have built deliberately and checked:

• Nothing important is behind a sign-in. Every price, specification, lead time, and stock status is on a public page. You never need an account to see what something costs or to buy it, so no accessibility barrier in our sign-in flow can stand between you and a price.
• Every page is reachable from a keyboard. Nothing on the site needs a mouse: every link, button, field, and pack-size option is reachable and operable by Tab and Enter alone. Links and buttons show a visible focus outline. Dialogs and the cart drawer keep the keyboard inside them, close on Escape, and return focus to the control that opened them.
• Form fields are labelled with text.Not with a placeholder that disappears the moment you type. Where a page repeats a label, a shipping address and a billing address both asking for “City,” the field says which one it belongs to. Errors are written as what to do next, are attached to the field they belong to, and are announced rather than only shown. Three controls still fall short of this: see Section III.
• Results that arrive late are announced. A form submitting, an order lookup returning, an address saving, a sign-in link being sent: each one says what happened instead of changing the screen silently. Adding to the cart opens the cart panel and moves the keyboard into it, so the result is read rather than assumed.
• Illustrations describe the product, not the drawing. Our product figures are drawn rather than photographed. Their text alternatives give the product name, catalog number, and key spec, which is the information the picture carries. Purely decorative art is hidden from assistive tech instead of narrated.
• Specifications are real tables. Spec tables, shipping rates, and order lines use table markup with proper header cells, so a screen reader can read a value together with what it is a value of.
• Text reflows and scales. Layouts are built to hold together down to 320 pixels wide, which is also what 400 percent zoom on a laptop looks like. Wide specification tables get their own horizontal scroller rather than squeezing a column of prose into an unreadable ribbon.
• Motion respects your system setting. Every animation that moves on its own, the scrolling strip and the animated transcript on the software page, stops if your operating system is set to reduce motion. What is left are short fades on hover and on opening a panel. Nothing flashes, nothing auto-plays audio or video, and there is no video or audio on the site at all.
• Nothing times out while you are reading. No page expires, no form clears itself, and your cart does not empty because you took a while. Two exceptions, both credentials: an emailed sign-in link lasts fifteen minutes, and a signed-in session lasts thirty days. You can request a fresh link as many times as you need, and browsing and buying never require one.

Automated checks with axe-core and pa11y run against our pages, and we fix what they find. Alongside that we test by hand: navigating with the keyboard alone, and reading pages with VoiceOver on macOS.

We have not tested with JAWS, NVDA, Dragon, or TalkBack, and we have not had an independent audit. We are telling you which tools our claims rest on so you can weigh them accordingly. If you use assistive technology we have not tried and something on the site behaves oddly, your report is genuinely more useful to us than another automated scan.

If any part of this site blocks you, please tell us. You do not need to know which guideline it breaks or to describe it in accessibility terms. “I cannot get to the Add to cart button with my keyboard” is a perfect report.

Email is the fastest way, and it reaches the same small team that builds the site:

It helps if you can tell us the page address, what you were trying to do, and what assistive technology or browser you were using. If you cannot, send what you have and we will work it out.

What we commit to:

• A reply from a person within two business days, not an auto-acknowledgement.
• An answer that says either what we fixed, or when we will fix it, or that we cannot and why. We would rather tell you no than leave a report open indefinitely.
• A way to get the thing done in the meantime. If a barrier stands between you and an order, a document, or a lot record, we will place the order, pull the document, or read you the record by email or by phone. That path is always available and is not a lesser service.

If you are not satisfied with our response, say so in a reply. It reaches the founders, because on a team this size it already did.

Prepared by Bramante Biologics Corporation on the basis of our own review of bramantebio.com, self-assessed and not independently verified. Last reviewed July 30, 2026.

We review it whenever we change something on this page’s lists, and at least twice a year regardless. A statement that has not been touched in three years tells you nothing about the site it describes, so the date above is part of the content.