Worked sample · printable PDF
ACC-04 · Co-design with partners
Run a structured co-design cycle with consented partners; show how their feedback changed the design.
Specialty centers · Assistive & Accessible AI
Free education and therapies briefs about designing for the person the default model was not built for. Students run a consented co-design cycle and show how partner feedback changed the work, and they document where a mainstream tool fails a named need with evidence. ACC-04 and ACC-01 have single-brief PDFs; every brief is in the bank PDF; the other ten are full on the page. No account. No student data leaves your school.
Partner consent and do-no-harm
Documented, specific, revocable consent before any partner testing. No fake partners. No medical advice, diagnosis, or therapy delivery — students evaluate tools; licensed professionals own clinical decisions. If partners cannot be secured under school rules, the brief becomes a protocol and desk review, not a fabricated study.
How to run one
Worked sample · printable PDF
Run a structured co-design cycle with consented partners; show how their feedback changed the design.
Featured · printable PDF
Document where a mainstream AI tool fails for a named disability-related need — with evidence, not anecdote alone.
Evaluate an AI-assisted AAC workflow for rate vs. authorship; propose safeguards for voice and agency.
Test a reading-support tool against a learning goal; measure support vs. doing the work for the student.
Build or evaluate a planning scaffold; test whether it reduces load or adds compliance theater.
Measure ASR error across dialects/accents using public data or consented samples; propose mitigation.
Evaluate an AI feature under keyboard-only / switch access constraints; file bugs as first-class deliverables.
Score auto-captions for a classroom video set; define an acceptance bar before publishing.
Write the educator guidance for using AI supports without violating plan accommodations or privacy.
Adapt a brief for a specialized setting; price accessibility work as core, not a margin afterthought.
Replace demo scripts with tasks users actually need; report completion, errors, and abandonment.
Kill a feature that tests poorly; write the memo explaining why shipping would be unethical.
Six-dimension rubric
Scope unclear? Standards language off? Tell us here — you do not have to leave an email.