Accessibility at Bloomily

We want everyone to be able to use Bloomily. That means parents, children, school staff, and anyone who uses a screen reader, a keyboard, voice control, zoom, or other tools.

Last updated: September 24, 2026

Our goal

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. This page says where we are, what we are fixing, and when.

What this page covers

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.

What we have done

  • We tested our public pages with testing tools and with a keyboard, and wrote down every problem we found.
  • We made a plan to fix each problem, starting with the pages families use.
  • We fix the pages themselves. We never add an “accessibility overlay” or widget on top.
  • Our tool for school offices shows a clear outline around the control you are on, and we test its colours.
  • In our Android apps, buttons use dark text on orange, so the words are easy to read.

What we are working on

These are our target dates. We will update this page as each one is done.

Our accessibility plan, with target dates
WhenWhat
By December 2026The pages families use: school websites, registration, checkout, forms, sign in, and the family portal. Every question gets a label a screen reader reads out, text gets dark enough to read, every page gets its own title, and you can sign by typing your name.
By December 2026The parent apps on iPhone and Android work with VoiceOver and TalkBack. The check-in tablet gives you more time and warns you before it resets.
By December 2026The same fixes in the staff tools and staff apps, and in our emails and PDF files. Then we do our own full check of all of it.
January 2027An outside accessibility expert tests Bloomily.
February 2027We publish the expert’s reports (called ACRs, or VPATs) for our websites, iPhone apps, and Android apps, and update this page to match.

Need something in another way?

If you cannot use part of Bloomily, or you need a page, form, or file 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, you can also ask your school. We will help them.

Tell us about a problem

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 will answer, and tell you what we will fix and when.

Our standard

We use the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, from the World Wide Web Consortium (W3C).