Three schools or three hundred — every one on a single accessible, monitored, fully managed platform, websites and native mobile apps together, while each school keeps its own name, its own look, and its own domain. Thirteen years building for New York schools.
Send us your list of school websites. We'll tell you which ones fail accessibility, which are broken on phones, and what it would take to fix all of them.
One alert.
Every school. Instantly.
Every school keeps its own look. The notice is one shared entry — edit it once and all of them are correct.
The Department of Justice's 2024 rule requires web content and mobile applications of state and local government entities, including public school districts, to conform to WCAG 2.1 Level AA. Compliance was due April 2026 for districts serving populations of 50,000 or more, and is due April 2027 for smaller districts and special district governments.
Most school-site vendors treat accessibility as a statement page. It is now a technical specification, it explicitly covers your apps as well as your sites, and it applies to every one of your schools — including the ones your district office doesn't manage.
See where your schools standSome schools are on a vendor. Some are on a CMS a parent volunteer set up. One hasn't been updated since the principal who had the password retired. The district is responsible for all of them and has visibility into none of them.
A website contract per school, an app vendor per school, a renewal date per school, a support queue per school — and no purchasing leverage in any of them. The district pays retail over and over.
An accessibility complaint, a compromised site, a missed closure notice, a wrong translation on an emergency alert — none of those land on the school. They land on you.
This is where district website projects usually fall apart: the district wants one platform, and every principal hears "our school is about to look like everyone else's." On our platform they don't have to.
Each themed with about fifty design tokens. Different structure, different typography, different color — two schools on the same platform can look nothing alike.
Their web address doesn't change. Their email doesn't change. We never touch their name servers.
The people who update the site today keep updating it. Nobody has to route a lunch menu change through the district office.
A high school can run forms and photo galleries; an elementary school can turn off what it doesn't use. Content and navigation are theirs.
What the district gets is not uniformity. It's a floor — every school accessible, fast, backed up, monitored and current — under one contract.
Post a closure, a delay, or an emergency notice once. It appears in the alert bar on every school's website and app, ahead of that school's own notices. One edit updates all of them; one delete clears all of them.
Publish the district calendar once — holidays, professional development days, testing windows, half-days — and it merges chronologically into every school's calendar, labeled as a district date. Parents see one calendar, not two they have to reconcile.
These are shared entries, not copies. When a snow day moves, you change one record and every school is correct. Platforms that fan out copies leave you chasing each school separately to fix one date — and one of them always gets missed.
District notices never overwrite a school's own alerts and events — they sit alongside them, so schools keep their own voice. District-wide push notifications are on our roadmap for this platform.
| Role | Can do |
|---|---|
| District administrator | Publish district-wide alerts and calendar dates; see every school; manage membership and settings |
| School administrator | Everything within their own school — and nothing outside it |
| Staff | Read the private staff area at their school (optional per school) |
| Families and the public | Read the public site. No accounts, ever. |
Most platforms hide the buttons a user shouldn't press. We enforce the boundary at the data layer — a school administrator cannot reach another school's content even with developer tools open. District content is district-writable only.
Every administrative change across every school is written to an append-only audit log: what changed, when, and by whom. When a district asks "who deleted that page?", there is an answer.
Semantic structure, visible keyboard focus, labeled controls, live regions on loading and error states, and contrast-safe color pairs that hold no matter which brand colors a school picks — a principal cannot choose their way into a contrast failure.
The 2024 rule covers mobile applications explicitly. Because our apps and websites are one platform, an accessibility fix ships to both at once. Districts running a website vendor and a separate app vendor have two compliance surfaces and two vendors pointing at each other.
There's an automated check suite built into the platform that runs against your live sites — accessibility basics, page rendering, error states, forms, permissions and data integrity. Not a pre-release test on our machines: a test we can run on your production sites, on the call, and send you the output.
Regressions happen when a school uploads a bad image or publishes an unstructured page. Checks run continuously, and the design system prevents most of the common failures from being possible in the first place.
The stock website-translation widget schools bolt on fails audit — unlabeled dropdown, untitled frames, low-contrast chrome. It is one of the first things a WAVE or axe scan flags, and it is frequently the reason a site that "looks fine" fails. We suppress it entirely and ship our own accessible control.
One control, in each language's own script, with right-to-left support — on every page of every school in the district, including forms and emergency alerts.
For districts with translation obligations under state or federal language-access rules, this is the difference between a compliance line item and a checkbox. No per-school setup, no per-page work, and no additional cost per language.
The reason district website consolidations take two years is content migration — every school is asked to rewrite its own site, and half of them never do. We don't ask them.
Give us the list of school web addresses. We pull the text from each existing site, clean it, and load it into a themed, working site — pages, staff, events, links, contact details. The school reviews it rather than writing it.
Compromised school websites are routine, and a district migration is exactly when malware spreads between properties. Our import takes text and nothing else: every image reference, script, piece of markup and insecure link is stripped before anything is stored. Images are re-uploaded fresh.
Each school gets a private preview link and a checklist. The lift for a school secretary is an afternoon, not a semester.
Each school's existing address keeps working, and we cut over when that school is ready — school by school, not all at once.
Across the district and per school — views, visitors, by day and by month.
Views, visitors, form submissions, last content update and last admin login. That last column is how you find the three schools that have stopped updating — before a parent does.
Totals per school, so nobody is surprised by a limit.
Who has access to what, across every school in the district.
Crashes and performance problems reported by real browsers, grouped so one bug is one row instead of five hundred.
Analytics are first-party and stay in your district's data. Nothing sold, shared, or sent to an ad network — one fewer vendor for your privacy officer to review.
No family accounts. No student information system sync. No rosters, no grades, no attendance. Our platform is not integrated with your SIS and does not receive student records. When a school collects information through a form — a registration, an absence report, a permission slip — that submission is stored under per-school database permissions, visible only to that school's administrators, and exportable or deletable on request.
We will sign your district's data protection agreement and complete your review process.
Authorization is enforced in the database itself. There is no middle tier holding credentials for every school.
Family attachments land in a private area nobody can read, are checked byte-by-byte against their declared type and screened for active content before release. Administrators download through links that expire in sixty seconds.
Rate limiting, bot challenge, server-side validation, and spam scoring that flags rather than deletes. A suspicious registration still appears in the school's dashboard.
Of the entire platform, plus per-school exports. A single school can be restored without touching any of the others.
Of every administrative change across the district — enough to answer "what changed and who changed it," and enough to put it back.
Exportable on request, in a documented format. No hostage clause, no per-export fee.
Every row here is something we will demonstrate live on a briefing call.
| Every school buying separately | One district platform | |
|---|---|---|
| Contracts | One per school, plus app and forms vendors | One |
| Renewal dates | Scattered across the year | One |
| Accessibility | Unknown per school; unverified | WCAG 2.1 AA by construction, checked against live sites |
| Mobile apps | A separate vendor, or none | Included and branded per school |
| Emergency alerts | Called or emailed school by school | Published once, live everywhere |
| District calendar | Re-entered by every school secretary | One entry, merged into every school's calendar |
| Translation | Per-school widget, often failing audit | 36 languages, accessible, everywhere |
| Oversight | None | One dashboard: traffic, activity, storage, errors, admins |
| Backups | Per school, if any | Nightly, off-site, plus per-school restore |
| Who's responsible when a site breaks | Ambiguous | Us |
| Migration | Each school rewrites its own site | We import from the sites you already have |
| Cost | Retail, once per school | Per school, declining with size |
Scroll the table sideways on a small screen.
Weeks 1–2
We scan every school site you have and deliver the report. You pick the pilot schools. Procurement and the DPA run in parallel.
Weeks 3–4
Two or three schools go live end to end — imported, themed, reviewed, cut over. These become the internal proof that wins the remaining principals.
Weeks 5–10
Schools go live in batches of five to eight — as many waves as your district needs. Each school gets a preview link, a review checklist and a 30-minute training session. District alerts and calendar switch on with the first wave.
Week 11 onward
Full dashboard, monitoring and one support queue. Remaining schools join on their own timetable — nothing is blocked on the slowest school.
Provide the list of school websites, name one project contact, and approve the design direction. That's it. We don't run a change-management program on your staff.
500+ school websites and apps built — including branded school apps live in the App Store and Google Play, many of them for New York City public schools. This is not a roadmap. It is work we have been shipping and operating for years.
Live sites, right now — including Manhattan HS District, a multi-school district running on this platform today. Click any of them; that is faster than anything we could tell you.
The per-school rate declines as the district grows. Every school in a district plan gets the full platform — there is no cut-down tier.
Small
Full platform per school, consolidated billing.
Network
Adds district-wide alerts and the shared calendar.
District
Adds the district dashboard and a named account contact.
Large
Let's talk. Phased rollout, custom terms, procurement support.
Website and branded mobile app per school
All content sections and forms
Each school's own domain
36 languages and WCAG 2.1 AA
Nightly backups and monitoring
District alerts and shared calendar
The district dashboard
Content migration from your old sites
Training and support
One purchase order, one renewal date, one invoice. We complete district vendor onboarding, insurance and data-privacy paperwork as part of the contract — not as a change order.
Send us the list of your school websites. Within two weeks you'll have a report showing which schools fail WCAG 2.1 AA, which are broken or slow on phones, which have dead links and stale content — plus one school rebuilt on our platform so you can see the difference.
Send your list of school websites
We scan every one of them
You get the report and a sample rebuild
On the next page choose "The Digital School Package (Web/App)" and paste your list of school websites — and your number of schools — into the details box.
Thirty minutes with your comms, technology and procurement people in the room. We'll run our accessibility checks against your live school sites while you watch, and answer the data-privacy questions on the call.
Book a district briefingSend it over. We respond to district procurement regularly — and we'll tell you honestly if we're not a fit.
The single-school platform has its own page, including a free 48-hour site rebuild.
See the school platform