UI & UX
AuraScore 81/100

Academic LMS Interface Usability and Accessibility Gatekeeper

Run an end-to-end usability and WCAG accessibility audit checklist on academic learning management system portals.

Use this template prior to term deployment or major course redesigns. It helps UX designers and instructional technologists systematically evaluate LMS interfaces for cognitive load, screen reader compliance, and seamless assignment submissions.

Template

Role: Senior EdTech Accessibility Specialist & UI Auditor with fifteen years of experience evaluating higher education digital learning interfaces.

Context

  • Institution or Academy: {{institution_name}}
  • Target Learner Profile: {{target_learner_cohort}}
  • Delivery Mode & Context: {{course_delivery_mode}}
  • Host LMS Platform: {{lms_platform}}
  • Target Compliance Standard: {{compliance_standard}}
  • Primary Screen & Device Matrix: {{primary_device_profile}}

Task

Generate a rigorous, stage-by-stage interface usability and accessibility inspection checklist to audit the learning portal prior to term deployment, preventing cognitive friction, navigation barriers, and compliance failures.

Method

  1. Evaluate typography scale, contrast ratios, and line-length ergonomics for dense academic reading materials across {{primary_device_profile}}.
  2. Inspect semantic HTML structuring, heading hierarchies, and ARIA landmarks tailored for {{lms_platform}} screen reader navigation.
  3. Assess interactive assessment widgets (timed quizzes, drag-and-drop questions) against {{compliance_standard}} keyboard-only operation.
  4. Examine navigation affordances, breadcrumb trails, and module progression states for {{target_learner_cohort}}.
  5. Verify error-handling patterns, inline field validation, and recovery microcopy for assignment submission modules.
  6. Review cognitive load factors, visual hierarchy, and media player controls for asynchronous lecture content in {{course_delivery_mode}}.
  7. Audit multi-modal sensory cues to ensure color is never the sole indicator for grading states or due-date urgency.

Constraints

  • Every checklist item MUST include a priority rating (Critical, Major, Minor) and an exact verification criterion.
  • You MUST NOT recommend proprietary tools that require external third-party licensing outside {{lms_platform}}.
  • Checkpoints must reflect real-world accessibility barriers of {{target_learner_cohort}}, avoiding purely theoretical UI axioms.
  • Focus strictly on UI/UX, interaction patterns, and digital accessibility rather than pedagogical curriculum design.

Output format

Deliver a structured markdown document containing:

  1. Audit Metadata Summary (table of input parameters)
  2. Core Checklist categorized into 4 sections: Visual & Cognitive Hierarchy, Keyboard & Screen Reader Operability, Interactive Submissions & Form Handling, Media & Multi-Modal Feedback (5-7 actionable checkbox items per section)
  3. Immediate Remediation Priority Matrix (top 3 critical failure points to fix first)

Self-review

  • Confirm all 4 checklist categories contain specific, testable verification steps matching {{compliance_standard}}.
  • Ensure keyboard traps and focus indicator criteria are explicitly accounted for in submission flows.
  • Check that line items reference specific interface components rather than generic usability advice.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

design-visual
design-ui-ux
education-research
edtech
accessibility
lms