Accessibility

Our WCAG 2.1 AA commitment, what is in place, and the gaps we know about.

What we are aiming for

A quiz is no use if a student in the room cannot take it. We aim to meet WCAG 2.1 Level AA, and we treat a failure against it as a bug rather than a feature request.

What is in place

• Every interactive control can be reached and operated from a keyboard, and the focus outline is left visible rather than styled away.
• Buttons that show only an icon carry a text label for screen readers.
• Answer feedback never relies on colour alone — a correct or incorrect option carries an icon and words as well as a green or red background.
• Text meets the 4.5:1 contrast ratio against its background, and page text can be enlarged without the layout breaking.
• Tap targets on phones are at least 44 by 44 pixels.
• The quiz screen is built to fit a phone without scrolling to reach the answer buttons.

Known gaps

We would rather list these than let you discover them mid-lesson.

• Hotspot questions ask a student to tap a point on an image. There is no keyboard equivalent yet. If you have a student who cannot use a pointer, avoid that question type for now.
• The rich text editor used for writing quizzes and posts is a third-party component and its toolbar is not fully keyboard navigable.
• Some marketing pages animate as you scroll. These respect a reduced-motion preference where the browser reports one, but coverage is not complete.

Tell us

If something blocks you or a student, write to support@eduquizzy.com and say what you were trying to do and what got in the way. Accessibility reports go to the front of the queue, and we will tell you honestly whether a fix is days or months away.