accessibility-check

Assess edtech product accessibility against WCAG 2.1 AA, Section 508, and UDL.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/savvides/edtechfounderstack --skill accessibility-check-savvides
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-check
Source: https://github.com/savvides/edtechfounderstack/tree/main/skills/accessibility-check
Command: npx skills add https://github.com/savvides/edtechfounderstack --skill accessibility-check-savvides

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many edtech products fail enterprise and district procurement reviews because they lack clear accessibility documentation, prioritized remediation, and alignment with pedagogical frameworks; this Skill helps founders identify legal and procurement blockers and close gaps before pilots or sales meetings. It translates WCAG 2.1 AA, Section 508 expectations, VPAT requirements, and UDL principles into actionable recommendations targeted to common edtech product types.

Core Features & Use Cases

  • Prioritized WCAG checklist: Focuses on the critical procurement blockers first (keyboard navigation, screen reader compatibility, color contrast) then high-priority and important items based on product type.
  • VPAT and procurement guidance: Explains what a VPAT is, when you need one, how to create one, and cost/third-party audit considerations.
  • UDL alignment & AI concerns: Evaluates pedagogical accessibility (UDL) and flags AI-specific risks like bias, transparency, explainability, override capability, and consent when AI-generated content is present.
  • Use Case: Founders preparing for higher education or K‑12 procurement run this Skill to produce a remediation roadmap, VPAT plan, and tools checklist ahead of pilots or enterprise demos.

Quick Start

Run accessibility-check, answer the guided product questions one at a time, and receive a prioritized WCAG 2.1 AA remediation plan, VPAT guidance, and UDL recommendations.

Frequently Asked Questions about accessibility-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prepare my edtech product for WCAG 2.1 AA procurement checks?

A WCAG 2.1 AA accessibility check evaluates edtech products against critical procurement blockers like keyboard navigation, screen reader compatibility, and color contrast. It generates a prioritized remediation plan and VPAT guidance to ensure compliance before enterprise pilots.

What is a VPAT and when do I need one for Section 508 compliance?

A VPAT documents Section 508 compliance for edtech procurement. You need a VPAT during K-12 and higher education procurement reviews to transparently report accessibility conformance, identify gaps, and avoid procurement blockers before enterprise sales meetings.

How do I create an accessibility remediation plan for a web application?

Create an accessibility remediation plan by evaluating your web application against WCAG 2.1 AA requirements. Prioritize critical procurement blockers first, apply tooling recommendations, and develop a staged action plan suitable for internal remediation or third-party audits.

Does my AI-generated content platform need specific accessibility testing for UDL alignment?

AI-generated content platforms require specific accessibility testing for UDL alignment to flag AI-specific risks like bias, transparency, explainability, override capability, and consent. Evaluating pedagogical accessibility ensures educational technology meets diverse learning needs.

Can I use this accessibility check for mobile apps and content platforms during pilot preparation?

You can use this accessibility check for mobile apps and content platforms during pilot preparation. It applies to various educational technology products including web apps, desktop software, content platforms, and APIs to identify procurement blockers and remediation priorities.