PLECK lesson 101 · suggested week 21, day 1
Audit barriers instead of labeling a game accessible
Objective. Describe specific tested features and limitations.
Godot Engine Standard desktop editor 4.7.2-stable, GDScript (Godot 4), Compatibility renderer. Headless Godot 4.7.2.stable.official.ed1daf0bf passed 106 assertions on the supplied scaffolds, including malformed JSON saves. Audio used the Dummy driver and a synthetic WAV, not a speaker. The visual editor, browser export, and signed-in submission were not tested. The desk still does not run a student's own upload.
About 55 minutes. The due date is chosen by a parent.
Text, focus, motion, privacy and evidence-based claims
Suggested pace: Recall and predict 5 min; Read instruction and scaffold 12 min; Build or design the assigned artifact 25 min; Run acceptance tests 8 min; Explain and checkpoint 5 min.
Materials: Paper and pencil or a private text document, Local course folder and prior checkpoint, No paid assets or public account required.
Comes after VGC-L100.
Accessibility is a set of concrete design decisions, not a decorative badge. Audit your game for keyboard control, readable text, non-color cues, sound alternatives, pause and motion settings. For each feature write a test and a remaining limitation. A game can improve without claiming it serves every player. Do not ask a tester to disclose a diagnosis. Let people choose settings without justification and accept text-based explanations instead of mandatory recordings.
Worked example
A barrier audit might test whether Tab can reach Restart. The result is a specific supported capability, not a claim that every assistive technology is supported.
Audit barriers instead of labeling a game accessible — evidence task
- 1. Create a six-feature barrier audit with one test per feature.
- 2. Choose the two highest-impact fixes.
Deliverable. Accessibility audit and prioritized fixes.
Acceptance checks
- VGC-L101-T1. Claims describe tested behavior rather than universal compliance.
- VGC-L101-T2. No test asks for health or identity information.
Understanding question. Why is “fully accessible” too broad without evidence?
Submit readable text or photos/scans of each numbered design page. Audio explanation may supplement a diagram or text, not replace requested artifacts.
If this is still shaky. Test one barrier at a time: keyboard only, muted audio, reduced motion and enlarged text. Keep a checklist of actual results. Start with the first assigned task and re-run its acceptance test before adding the remaining feature.
Optional extra. Let a willing tester choose a comfort setting before the test without asking why they need it. Document one changed parameter, your prediction, and the observed effect; optional, not required for completion.
Turn in a typed answer, a JPEG, PNG, or WebP photo, a PDF scan, or an MP3, WAV, M4A, MP4, or WebM file up to 4 MB. A parent can log paper. One https address is stored as text and is not opened or run. Zip and code files are refused.
- Your first 2D game
Free public tutorial; no account; external asset download is optional, not used by this course.
· Opening this link does not submit the lesson. - Exporting for the Web
Free public documentation. Local editor play is the required alternative to web export.
· Opening this link does not submit the lesson.
This is a preview. A parent assigns the lesson and chooses the due date after the student is enrolled. The answer key is not on this page.