Accessibility

Target

New and changed public interfaces target WCAG 2.2 AA. Public pages are scanned automatically for accessibility issues in both light and dark mode; automated tests are necessary but not sufficient, so key flows are also checked by hand. This is a target we work toward, not a statement of formal conformance or the result of an external audit.

Keyboard use

• Every interactive control works with a keyboard
• Every page starts with a "Skip to content" link
• A clearly visible focus outline
• The search dialog supports arrow keys, Enter and Esc, and returns focus when it closes
• Confirmation dialogs use the browser's native dialog, which keeps focus inside, closes with Esc and returns focus to the control that opened it

Structure and labels

• Semantic headings with one main heading per page
• Every form field has a label
• The current page and selected items are indicated by more than color alone

The course feedback form

• Rating scales use native radio buttons that work with the arrow keys, and every option has a full accessible name (for example "5 Strongly agree")
• Each option is at least 48 pixels tall; a selected option is marked by a check mark as well as a fill, not by color alone
• The progress bar for the required questions has a text label and matching accessibility attributes; when a submit is blocked the items to fix are listed in an alert right above the submit button with "Go fix it" links, fields show live status next to them (announced to screen readers), and the session code is checked as you type
• The privacy notice shows three key points by default and expands to the full text, so no important promise is hidden
• At phone width there is no horizontal scrolling, and the eleven recommendation options wrap into two rows
• On the instructor's "Feedback QR code for the projector" page the QR code has alternative text, the countdown only notifies screen readers at one minute left and at the end, full screen and the print layout work from the keyboard, and reduced-motion settings are respected

Motion and responsive layout

• Your system’s reduced-motion setting is respected
• No horizontal scrolling at phone widths
• Controls on phones have comfortable touch targets

Reporting a problem

If something is not usable, tell your instructor, including the page address and the assistive technology you use.