Finish this sentence: “A learner wants to ___, but ___ gets in the way.” Make the task specific enough to demonstrate in two minutes. Avoid assuming that every learner has a recent phone, unlimited data, perfect vision, or a quiet room.

• Can the main task be completed with a keyboard?
• Is essential information available without relying on color or audio alone?
• Are labels, instructions, and feedback understandable?
• What happens on a slow connection, small screen, or shared device?
• What evidence shows that the learner can do something useful after using the tool?

Choose the checks relevant to your project and describe the limits of your testing. Do not claim universal accessibility from a single test.

Introduce the learner and barrier. Show the original difficulty. Demonstrate the core task with your tool. Explain what you built during the event, credit dependencies, and name one limitation or next step. Use made-up learner data.

Use the Discussions tab to find teammates or ask general event questions. Contact the organizers through the contact link for private event questions. Your team can combine teaching insight, research, design, and coding; no particular platform is required.