oncokb-html-accessibility-reference

Audit healthcare interfaces for accessibility barriers using WCAG-aligned evaluation domains.

Updated Aug 31, 2026
One-click install
npx skills add https://github.com/oncokb/oncokb-skills --skill oncokb-html-accessibility-reference-oncokb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: oncokb-html-accessibility-reference
Source: https://github.com/oncokb/oncokb-skills/tree/main/skills/oncokb-html-accessibility
Command: npx skills add https://github.com/oncokb/oncokb-skills --skill oncokb-html-accessibility-reference-oncokb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Healthcare and clinical interfaces often ship with accessibility barriers that create legal, ethical, and patient-safety risks, especially when built rapidly or with AI assistance. This Skill provides a structured, repeatable audit framework to identify, classify, and escalate accessibility issues before release. ## Core Features & Use Cases - Eight-Domain Audit Framework: Evaluate interfaces across perceivable content, keyboard operability, language clarity, semantic structure, forms, status feedback, motion safety, and cognitive load, aligned with WCAG 2.2, Section 508, and NHS guidance. - Severity Classification: Assign Critical, High, Medium, or Low severity based on real user impact, with clear escalation thresholds for expert review. - Healthcare-Specific Guidance: A reference guide translates standards into clinical considerations, such as color-only alert indicators or screen-reader-blocking data tables. - Use Case: A design team reviewing an AI-generated patient portal prototype walks through key tasks, documents observable issues like missing form labels and low-contrast status badges, assigns severity, and flags patient-facing blockers for expert accessibility review. ## Quick Start Audit this patient dashboard prototype for accessibility issues and report findings with severity levels and remediation guidance.

Frequently Asked Questions about oncokb-html-accessibility-reference

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

FAQPage Schema
How do I audit a healthcare interface for accessibility?▼

Define the audit scope, identify primary user roles such as clinicians or patients, then walk through realistic tasks end-to-end. Evaluate findings across eight domains covering perception, keyboard operation, language, semantics, forms, feedback, motion, and cognitive load, then assign severity to each issue.

What accessibility standards does this audit framework cover?▼

The framework aligns with WCAG 2.2 principles, U.S. Section 508 requirements, and NHS digital service accessibility practices. These standards are abstracted into actionable audit steps rather than formal compliance checklists.

Can this audit replace formal accessibility compliance testing?▼

No, this audit is evaluative, not certifying. It complements but does not replace formal compliance testing or assistive technology testing, and it explicitly defines escalation thresholds for expert review.

How are accessibility issue severity levels assigned?▼

Severity reflects real user impact: Critical blocks access or introduces safety risk, High is a major barrier without workaround, Medium is a partial barrier, and Low is a minor issue. The reference guide provides clinical considerations to inform each rating.

When should accessibility issues be escalated to experts?▼

Escalate when issues affect patient-facing experiences, involve clinical decision-making, create legal or regulatory exposure, or when assistive technology compatibility is uncertain. Multiple clustered high-severity issues also warrant escalation.