Keyboard use
Navigation, links, form controls, disclosure widgets, and copy buttons are designed to work without requiring a mouse.
The OER Promptbook aims to meet WCAG 2.2 Level AA where this project controls the experience and to make the site usable across devices, input methods, and assistive technologies.
Found a barrier? Please report it so I can review it.
I aim to build and maintain the Promptbook in alignment with Web Content Accessibility Guidelines (WCAG) 2.2 Level AA.
This is an accessibility goal, not a claim that every page or third-party service has been formally certified. Accessibility work is ongoing, and human testing remains important.
Last updated: September 2026.
Navigation, links, form controls, disclosure widgets, and copy buttons are designed to work without requiring a mouse.
Keyboard focus is styled so the active control or link is easier to locate as you move through a page.
Pages use headings, landmarks, labels, instructions, and status messages to provide meaningful structure for assistive technology.
Text and controls are designed with strong contrast, readable sizing, and layouts that do not depend on color alone to communicate meaning.
Layouts are designed to reflow on smaller screens and at increased text or browser zoom rather than requiring a fixed desktop view.
The shared site styles respect reduced-motion preferences and avoid relying on motion to understand or use the content.
The Promptbook links to or uses services maintained by other providers, including GitHub Pages, Google services, Padlet, AI tools, and external OER websites. Their accessibility features and barriers are controlled by those providers.
If a third-party service creates a barrier, I still welcome the report. It may help me improve instructions, offer a different path, or reconsider how that service is used in the Promptbook.
If you encounter an accessibility barrier in The OER Promptbook, please email karencrozer@gmail.com.
If possible, include the page or link, what you were trying to do, and any browser, device, or assistive technology details that would help reproduce the problem. You do not need to disclose a disability or diagnosis.
Automated checking can catch some problems, but it cannot establish complete accessibility on its own. The project will continue to use source review, keyboard testing, responsive testing, and assistive-technology feedback as the site evolves.