Draft. This is a self-assessment against the code and the rendered pages, not a third-party audit. Anything marked like this still needs to be filled in, and every "Supports" below is our own reading until an audit confirms it.
Accessibility conformance report (VPAT)
Dabbled for Schools · Last updated September 22, 2026
Product
Dabbled for Schools, the web application at edtech.dabbled.ai: the pages a teacher or administrator uses to describe, build, manage and share small educational apps, the class join flow a student uses, and the public library. Version: [release identifier].
Scope note. The apps that teachers and students generate are their own content, produced by an AI model from their description, and are out of scope of this report. Their accessibility varies with what was asked for. The generation instructions ask for keyboard-operable, readable pages, but we do not certify the result.
Standard and method
Assessed against WCAG 2.1 Level AA (which Section 508 incorporates). Method: review of the source and of the rendered pages in Chrome, with keyboard-only operation and reduced-motion settings; no assistive-technology user testing yet. [Commission an audit, and test with at least one screen reader, before removing the draft notice.]
Terms
- Supports — the functionality meets the criterion.
- Partially supports — some functionality does not.
- Does not support — most functionality does not.
- Not evaluated — not yet assessed.
Report
| Criterion | Level | Remarks |
|---|---|---|
| 1.1.1 Non-text content | Partially supports | Decorative marks and orbs are hidden from assistive technology. App preview images carry the app's title as alternative text. Emoji used as icons in headings are not all hidden. |
| 1.3.1 Info and relationships | Supports | Forms use labelled controls; the build-progress strip is an ordered list with the current step marked aria-current="step"; tables are tables. |
| 1.4.1 Use of colour | Supports | Progress is shown with a tick, a number and a label, not colour alone; the cancel action is red and also named. |
| 1.4.3 Contrast (minimum) | Not evaluated | Body text is dark on light and light on dark; muted text has not been measured against the 4.5:1 ratio. [measure] |
| 1.4.10 Reflow | Supports | Layouts are fluid; two-column pages stack on narrow viewports. |
| 2.1.1 Keyboard | Supports | Every control is a native button, link, input or select; there are no custom widgets that need pointer input. |
| 2.2.2 Pause, stop, hide | Supports | The only moving content is the working indicator while a build runs; it honours the operating system's reduced-motion setting and stops. |
| 2.3.1 Three flashes | Supports | Nothing flashes. |
| 2.4.2 Page titled | Partially supports | Pages carry the application title; not every route sets its own. [per-route titles] |
| 2.4.4 Link purpose | Supports | Links are named for where they go; icon-only controls carry an aria-label. |
| 2.4.7 Focus visible | Supports | Browser focus rings are not suppressed. |
| 3.3.1 Error identification | Supports | Errors are shown in text beside the control or action they belong to, never by colour alone. |
| 3.3.2 Labels or instructions | Supports | Every input has a visible label; optional fields say so. |
| 4.1.2 Name, role, value | Supports | Native controls throughout; the one composite (the progress strip) exposes its state through standard attributes. |
| 4.1.3 Status messages | Supports | The build's progress and the "draft saved" note are live regions. |
[Complete the remaining WCAG 2.1 AA criteria, and add the Section 508 chapters (functional performance criteria, support documentation) in the standard VPAT layout, once the audit has been done.]
Feedback
If something here does not work with the assistive technology you use, tell us at [accessibility contact address] and we will fix it or find you a way round it.
See also: Privacy Policy · Terms of Service