Accessible Assessment Flow Specification Brief
Structure an exhaustive UI/UX design brief for building WCAG 2.2 AAA compliant digital grading and submission workflows.
Deploy this template when modernizing student submission and educator feedback interfaces across multi-device learning environments. It ensures all interaction states meet strict pedagogical and assistive technology standards.
Role: Principal Accessibility Architect and EdTech UX Strategist
Context
- Learning platform: {{learning_platform_name}}
- Assessment formats: {{assessment_type_scope}}
- Assistive tooling support: {{assistive_tech_requirements}}
- Educator grading pain points: {{educator_workflow_bottlenecks}}
- Student UX stress factors: {{student_anxiety_friction_points}}
- Accessibility standard: {{compliance_target_level}}
Task
Author a definitive UI/UX design brief for end-to-end assignment submission and grading workflows on {{learning_platform_name}}, removing cognitive overload and ensuring complete accessibility compliance across diverse learner and instructor abilities.
Method
- Deconstruct the submission sequence to systematically eliminate triggers identified in {{student_anxiety_friction_points}}.
- Formulate high-efficiency grading canvas layouts addressing {{educator_workflow_bottlenecks}} with split-screen rubric alignment.
- Map keyboard navigation trees, logical focus shifts, and skip-link targets across multi-file upload zones.
- Design inline validation, drag-and-drop alternatives, and persistent save indicators for low-bandwidth scenarios.
- Audit proposed color palettes, typography scale, and touch targets against {{compliance_target_level}} specifications.
- Detail screen reader announcement strings (ARIA live regions) for dynamic grading updates and deadline countdowns.
- Formulate multimodal feedback mechanisms (audio annotations, rubrics, structured text) suitable for {{assistive_tech_requirements}}.
- Synthesize UI component patterns across desktop, tablet, and mobile breakpoints for {{assessment_type_scope}}.
Constraints
- MUST guarantee full keyboard operability without trapping focus on interactive submission components.
- MUST NOT rely solely on color or shape to convey grading status, overdue warnings, or validation errors.
- All dynamic DOM changes must specify ARIA live announcements for {{assistive_tech_requirements}}.
- Keep total word count of the generated brief between 800 and 1200 words.
Output format
Format the deliverable under the following mandatory headings:
- Workflow Blueprint (Student Submission vs. Educator Grading)
- Accessibility & Assistive Tech Implementation Matrix
- Form Input, Upload Canvas & Rubric Interaction Specs
- Non-Visual UX: ARIA Architecture & Screen Reader Sequences
- Stress-Reduction UI Patterns & Safety Nets
- Usability Testing & Audit Checklist
Self-review
- Does the brief explicitly address {{compliance_target_level}} criteria for every interactive element?
- Are solutions provided for each of the {{educator_workflow_bottlenecks}}?
- Are fallback patterns defined for assistive technologies lacking mouse simulation?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.