Skip to content

Accessibility Statement

Last updated:

Berine Metabolic builds this site for adults who live with diabetes and prediabetes. Many of them have reduced vision from diabetic retinopathy, or less feeling and control in their hands from peripheral neuropathy. We build the site so it works for them, and this page says what that means in practice.

If something on this site is hard for you to use, or you need this content in another format, write to support@berine.io. We reply within 2–3 business days. Our reply tells you what we will change and when.

1. What this statement covers

This statement covers the pages Berine builds on berine.io: the public pages, the blog, the inquiry form on the work-with-us page, the sign-in and account pages, and the course area.

1.1 Paying for the course

When course enrollment is open, you pay on a page that Stripe hosts. Berine does not control that page. If something on it stops you from paying, write to support@berine.io and tell us what went wrong.

2. Our standard

We build to Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. Every change to the site runs the checks described in §5 before it can ship. The gaps we know about are listed in §4.

3. What we have built

3.1 Reading

  • Body text is 16 pixels. Labels, captions, form labels, footer links and table text are 14 pixels.
  • Text sizes on the public pages follow your browser’s default font size. If you raise that default, the whole page scales with it.
  • You can zoom the browser to 200% and the page still fits the window. Nothing scrolls sideways.
  • On the public pages, our automated check finds no text below a contrast ratio of 4.5 to 1 against its background, or 3 to 1 for large text. It cannot measure some text. See §4.

3.2 Keyboard and touch

  • Every page starts with a “Skip to content” link. It is the first thing the Tab key reaches, and it jumps past the header.
  • On the public pages, the Tab key reaches every link, button and form field. In a row of tabs, the arrow keys move from tab to tab.
  • The control that has keyboard focus shows a 2 pixel outline.
  • Buttons and standalone links are at least 24 by 24 pixels. Links inside a sentence follow the text size.
  • Course activities that let you drag items also work with the keyboard. You pick an item up with a button and place it with a button.

3.3 Screen readers and forms

  • Each page has one main heading and marks the header, main content and footer as landmarks, so a screen reader can jump between them.
  • Buttons, menus and form controls have names that a screen reader reads out.
  • Images that carry information have a text description. Decorative images have an empty one, so screen readers skip them.
  • Form fields have labels. When a field has an error, the error text appears next to the field, and screen readers read it out. This includes each step of the inquiry form.

3.4 Motion and media

  • If your device asks for reduced motion, the site turns off entrance animations and decorative motion.
  • Audio and video never start on their own.
  • Course videos have captions and a written transcript.
  • No lesson or activity has a time limit. You can pause, replay and resume at any time.
  • The course home and each module page show your progress.

3.5 Layout

  • Every public page has the same header with a link home at the top, and the same footer with the Terms, Privacy and Accessibility links at the bottom. The page-not-found page has a shorter header and footer, in the same places.

4. What is not right yet

  • Some dates, category tags, credits, index numbers and small print on the home, About, course, blog and work-with-us pages are 11 to 13 pixels.
  • On each blog post, the Blog link above the title is 21 pixels tall.
  • The illustration of the course app on the course page shows text as small as 8 pixels. It is a picture, and screen readers skip it.
  • On the Terms and Privacy pages, table text is 14 pixels on screens wider than 768 pixels.
  • Our automated contrast check cannot measure text that sits on a gradient, a picture or a layered background. We have not checked that text another way.
  • Course videos have no audio description of what is on screen.
  • A few decorative effects on the public pages use the graphics processor. If your device cannot run them, a still image shows instead.
  • We have not tested with VoiceOver on Apple devices.

5. How we test

  • axe-core checks the WCAG 2.1 AA rules, including text contrast, on every component in our test suite. Every change runs these checks, and a failure blocks the change.
  • We measure the public pages in a real browser at phone and desktop widths: text size, text contrast, the skip link, keyboard reach, focus order and outlines, zoom, control size and reduced motion. The last full pass was 2026-09-24.
  • We test the course area with the NVDA screen reader on Windows. The last pass was 2026-09-21.

6. Tell us about a barrier

Write to support@berine.io. We reply within 2–3 business days. Our reply tells you what we will change and when. It helps if you tell us:

  • The address of the page.
  • What you were trying to do.
  • What went wrong.
  • The browser, device and assistive technology you use, if you know them.

7. The law

This statement supports our duties under the Americans with Disabilities Act (ADA). The European Accessibility Act does not apply to us today, because its microenterprise exemption covers us. We use WCAG 2.2 AA as our working standard either way.

8. Updates to this statement

We review this statement at least once a year. We also update it when the site changes, when we find a new gap, or when the contact route changes. The “Last updated” date at the top shows the most recent revision.