CuraCourseLessons every student can use.
Accessibility depends on us and on the lessons you write. Here’s where we stand, and how to make your lessons work for every student.
Where we are
We design CuraCourse to meet WCAG 2.1 AA, and we provide a VPAT on request. Email us if your school needs one or you want us to look at a specific activity.
Write lessons everyone can follow
- Use clear headings and descriptive link text, so students can find their way around.
- Describe important images in words, and add captions or transcripts to video and audio.
- Give instructions in words, not just color, position, or a screenshot.
- Preview math, code, and uploaded files with the tools your students use, such as a screen reader.
Choose activities with your students in mind
Some activities ask more of students than others. Dragging items into order, drawing on a graph, and typing in a code editor can be hard without a mouse or with a screen reader. Try them yourself with only a keyboard before you assign them, and offer a written response when a student needs another way to answer.
A custom activity is only as accessible as its code, even when CuraAI writes it. Try it with a keyboard and look for missing labels and heavy motion before you publish.
Plan accommodations early
Before a timed exam or graded activity, talk with the student and your school’s accessibility office about timing and how they’ll answer, so a barrier never costs a student points.