Accessibility at Bloomily

Our goal is to meet WCAG 2.1 Level AA across our websites and our apps. WCAG is the main set of rules for making websites and apps work for people with disabilities. Where the newer WCAG 2.2 adds something easy, we do that too.

We are not there yet. Our reports below say, rule by rule, where we are.

We tested Bloomily ourselves against WCAG 2.1 Level A and AA. We wrote what we found in three reports, called Accessibility Conformance Reports (ACRs). They use the VPAT 2.5 form, WCAG edition.

Each report names the version it describes, the date, and how we tested. For each rule it says Supports, Partially Supports, Does Not Support, or Not Applicable, and why.

• Bloomily on the web

  School websites, registration and checkout, forms, payment links, sign in, the family portal, and the tools schools use.

  Our websites as they were on September 27, 2026.

  Of the 50 rules at Level A and AA: 38 Supports, 10 Partially Supports, 2 Not Applicable.

  Read the web report (ACR)

• Bloomily for iPhone and iPad

  The family app, Bloomily Center, and Bloomily Kiosk.

  App Store versions 1.7.47, 3.0.85, and 2.0.18, as they were on September 27, 2026.

  Of the 50 rules at Level A and AA: 26 Supports, 11 Partially Supports, 4 Does Not Support, 9 Not Applicable.

  Read the iPhone and iPad report (ACR)

• Bloomily for Android

  The family app, Bloomily Center, and Bloomily Kiosk.

  Google Play versions 1.0.62 and 1.0.21, as they were on September 27, 2026.

  Of the 50 rules at Level A and AA: 31 Supports, 5 Partially Supports, 5 Does Not Support, 9 Not Applicable.

  Read the Android report (ACR)

This page covers the software Bloomily builds:

• school websites and program pages made with Bloomily
• sign up, registration, and checkout
• the family portal, forms, and payment links
• the parent apps, the check-in tablet, and the staff apps
• the tools schools use to run their programs
• the emails and files Bloomily sends

Each school adds its own words, photos, videos, and files. The school is in charge of those. Schools can add a description to each picture on their website, so screen readers can read it out.

• We tested our websites and apps with testing tools, with a keyboard, and with the checks built into iPhone and Android. We wrote down every problem we found.
• We fixed problems in order, starting with the pages families use. Our reports list what is still open.
• We fix the pages themselves. We never add an “accessibility overlay” or widget on top.
• On the pages families use, every field and button shows a clear outline when you reach it with a keyboard.
• You can sign a form by typing your name, and upload a file with a keyboard.
• The check-in tablet warns you before it resets, and gives you more time.
• In the parent apps on iPhone and Android, buttons and photos have names for VoiceOver and TalkBack.
• Orange buttons use dark text, so the words are easy to read.
• A school can set the language its website is written in, so screen readers know it.
• We wrote down accessibility rules that every change to Bloomily must follow. Automatic checks catch many new problems before a change goes live.

Our reports say where something does not fully work yet. We keep fixing, starting with what families use. Each report describes the versions and the date it names. We have shipped more fixes since then, and the reports do not show them yet. We update the reports and this page each time we test again.

If you cannot use part of Bloomily, or you need one of our pages or files in another format, tell us. For example: large print, a plain text copy, or a form you can fill out without a mouse. We will get it to you.

If it is a form or file from your school, please ask your school. Each school is in charge of its own forms and files. If you write to us about one, we will pass your request to the school and help them with what Bloomily can do.

Email accessibility@bloomily.app. Please tell us:

• the page or screen
• what you were trying to do
• what happened
• the device, browser, and any tools you use (for example, a screen reader)

We send a first reply within 2 business days. If something stops you from finishing a task, we will tell you another way to do it while we work on a fix, if there is one.

We use the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, from the World Wide Web Consortium (W3C). Our reports also list the WCAG 2.2 rules, for information.