School District Website and App Accessibility

It depends on total population, and the measure is specific. For an independent school district, the rule takes total population from the Census Bureau's most recent Small Area Income and Poverty Estimates (SAIPE). A school system or department that is part of a larger government - a city system, a statewide system - uses that government's population instead, which often places it on the earlier date. Any special district government is on the later date regardless of the population it serves, so a career center or vocational district organized as a special district generally has the longer runway. One caution worth passing to your business office: SAIPE figures are republished every year, so a district sitting close to the 50,000 line should confirm its current number rather than rely on a figure quoted in a policy template. The dates themselves are in the banner at the top of this page.

Everything the district makes available to the public digitally. Public websites and every web-based tool reachable from them - enrollment portals, lunch payment, transportation lookups, board agenda systems, learning platforms you expose to families, forms. Native mobile apps on iOS and Android, including a district app built by a vendor. Downloadable documents, which in practice means PDFs, and PDFs are where most districts' exposure actually sits. Video and multimedia, including captions. Maps and dashboards if you publish them. The inventory step matters more in a district than almost anywhere else, because the real list is always longer than the one the technology office is holding - individual school sites, department microsites, and vendor-hosted tools that nobody logged as district web content.

Mostly no, and this is the single most expensive misreading of the rule we see in board policy. The exception covers preexisting conventional electronic documents - word processing, presentation, PDF and spreadsheet files available before the compliance date - but it expressly does not apply to documents people still use to apply for or access services. In a district that excludes almost everything that matters: enrollment packets, registration and consent forms, free and reduced lunch applications, handbooks, calendars, special education notices, board policies families are directed to read. If a family needs the document to do something, it is in scope whatever date it was posted.

Five in total, and they are narrower than they sound. Archived web content, which must meet all four conditions - created before the compliance date or reproducing older physical media, kept only for reference, research or recordkeeping, held in a special archive area, and unchanged since archiving. Preexisting conventional electronic documents, with the service-access carve-out above. Content posted by third parties who are not acting for the district and have no contractual, licensing or other arrangement with it - which does not cover a vendor platform you contracted for. Individualized password-protected documents about a specific person, property or account - a student's own records behind a login. And social media posts made before the compliance date. The ADA's underlying effective-communication and reasonable-modification duties still apply to excepted content.

Only in very limited circumstances, and it is not the escape hatch board policy templates make it sound like. Under the rule a conforming alternate version is permitted where a technical or legal limitation genuinely prevents the content being made accessible. Maintaining an inaccessible main page alongside a separate accessible one is not the intended arrangement, and a district that leans on it broadly is building a second site it has to keep in sync forever. We will tell you honestly which of your assets are candidates and which are simply unremediated.

Both, on iOS and Android, and mobile is a different discipline rather than the same checklist re-run. Testing covers key user flows, navigation and controls, forms, content presentation and touch target sizing, screen-reader compatibility with VoiceOver and TalkBack, keyboard and switch access where applicable, and behaviour under the platform settings people actually use - Dynamic Type and larger text, reduce motion, increased contrast. We also report whether each issue is specific to the app, shared with your web platform, or inherited from a third-party SDK, because those three have completely different owners and fix costs - and in a district the app is usually a vendor's.

The district carries the obligation for what it makes available to the public, which is why board policy increasingly tells districts to put explicit WCAG 2.1 Level AA language into technology vendor contracts. Practically, an audit has to say which defects sit in your own content and configuration - the part your staff can fix - and which sit in a platform vendor's code, where no amount of district remediation budget will close them. For those we give you the documented workaround and the specific thing to escalate to the vendor, so your procurement office has something concrete to hold them to. For our own work we provide the conformance documentation and accessibility reporting those contract clauses ask for.

Yes, and for most districts it is the highest-value part of the engagement. An assessment that produces a report and no capability leaves you buying another assessment next year, while the people who create content keep creating the next backlog. Accessibility training covers practical WCAG application rather than theory, how to read automated tool output and what it structurally cannot detect, manual testing techniques your own staff can run, review workflows for pages and documents, accessible authoring in the tools your team already uses - the CMS, Word, PowerPoint, Google Workspace - and the governance and QA steps that keep new content conformant. It is built for the people who actually publish: technology directors and their teams, curriculum developers and instructional staff, communications staff, and campus-level content authors. Live sessions, with materials you keep and can re-run for new starters.

It is part of what the roadmap addresses, yes. The rule's underlying transparency expectation, and most board policy written against it, asks districts to implement and publicize a process by which users can report accessibility concerns about web content or a mobile app - usually surfaced through a published accessibility statement - with something behind it that actually goes somewhere. In the assessment we review the accessibility statement and reporting route you have today, and the remediation roadmap includes recommendations for tracking and communicating outstanding items: what is still open, who owns it, and when it is expected to close. A reporting link that reaches an unmonitored inbox is worse than none, because it creates a record of notice with no record of response.

The ADA Title II rule adopts WCAG 2.1 Level AA, and that is the standard your board policy and your compliance date are written against. We test and report against 2.1 AA for that reason, and we can additionally map findings to WCAG 2.2 AA where a district wants it - 2.2 is effectively a superset, adding nine success criteria and obsoleting one, so content conforming to 2.2 AA also satisfies 2.1 AA. Where federal funding or federal procurement is involved we also map to Section 508, which is a WCAG 2.0 AA obligation and applies today rather than on a future date.

Usually on a vehicle you already hold, which is the fastest route past procurement. Taika is a BuyBoard and TIPS awarded vendor, a GSA Schedule holder and a NASPO ValuePoint contract holder, registered in SAM.gov with an active Unique Entity Identifier, and a veteran-owned small business. For districts spending federal award money, that also means we are set up for procurement governed by the Uniform Guidance at 2 CFR Part 200, including the competitive-selection requirements at 2 CFR 200.318-200.320. If your district needs a formal solicitation response instead, we can meet standard RFP submission requirements.

Sometimes, and the test is the same one your business office already applies: the activity has to be allowable under the program it is charged to, traceable to the plan, and supplemental rather than something the district already owes every family. Accessibility of Title I parent and family engagement materials is a credible fit; the district's general obligation to make its website accessible is not a Title I expense. We write quotes with line items a business office can code and budget-justification language your monitor can follow, and we will say where we think a cost does not belong on a program line.

No, and be wary of anyone who says otherwise. There is no such thing as being 'ADA certified' - no such certification exists. An audit documents conformance against a named technical standard at a point in time, which is what a board, a state monitor or a complainant can actually act on. Whether your district carries a particular legal obligation, and what its exposure is, is a determination for your counsel. We give you an accurate technical picture; we will not tell you that you are safe.

It lands on the same documents far more often than either side expects, and districts usually buy the two from different vendors with different quality processes. An enrollment packet translated into six languages and left untagged in all six has solved half the problem six times over - and the inaccessible version is the one a parent using a screen reader receives. Because this sits inside a language company operating since 2009, one vendor covers both: Title VI language access and disability access on the same page, the same PDF, the same video, with consistent terminology across the spoken, written and translated versions.