Good Markup Resources
Practical references for building accessible interfaces with native HTML.
Module 08: Build the Accessible Version
A non-linear documentation index for concepts, standards, and methods used across the semester.
Practical references for building accessible interfaces with native HTML.
Module 08: Build the Accessible Version
A quality standard for digital experiences: people with disabilities should be able to perceive, understand, navigate, and complete tasks with comparable independence.
Used in Module 01 - Accessible According to Whom?
Designing with disability perspectives from the start improves outcomes for many users, not only edge cases.
Expanded guidance will be added when we reach this topic.
The Web Content Accessibility Guidelines provide testable success criteria used internationally to evaluate conformance.
Used in Module 01 - Accessible According to Whom?
POUR (Perceivable, Operable, Understandable, Robust) is a practical map for organizing accessibility investigations.
Used in Module 01 - Accessible According to Whom?
Legal and institutional requirements define accountability, obligations, and risk for accessibility decisions.
Used in Module 01 - Accessible According to Whom?
How color choices and contrast ratios affect readability and information access.
Expanded guidance will be added when we reach this topic.
Readable type, spacing, and responsive reflow are critical to sustained comprehension.
Expanded guidance will be added when we reach this topic.
Writing text alternatives that communicate the purpose and meaning of non-text content.
Expanded guidance will be added when we reach this topic.
Making time-based media understandable and navigable through captions, transcripts, and structure.
Expanded guidance will be added when we reach this topic.
Ensuring all core functionality works without a mouse.
Expanded guidance will be added when we reach this topic.
Visible, predictable focus behavior supports navigation confidence and task completion.
Expanded guidance will be added when we reach this topic.
Labels, instructions, and error handling determine whether forms are actually usable.
Expanded guidance will be added when we reach this topic.
Mobile interaction patterns must remain perceivable and operable across device contexts.
Expanded guidance will be added when we reach this topic.
Document structure and native semantics are foundational for robust accessibility.
Expanded guidance will be added when we reach this topic.
How assistive technology users perceive structure, controls, announcements, and link purpose.
Expanded guidance will be added when we reach this topic.
ARIA can improve custom UI semantics when native HTML cannot represent interaction patterns.
Expanded guidance will be added when we reach this topic.
UConn's central guide to university-supported accessibility tools, assistive technologies, browser testing tools, coding guidance, and validators.
Free, open-source screen reader for Windows. This course uses NVDA as the primary Windows screen-reader testing path.
Screen reader built into macOS and other Apple devices. Use it in Module 05 to test page structure, controls, and state announcements without relying on visual layout alone.
Commercial Windows screen reader. It is useful to know about, but it is not the required class path.
Browser bookmarklets that make hidden accessibility information visible, including headings, landmarks, labels, descriptions, and ARIA information.
Practical tools and methods available throughout this course for testing, investigation, and evidence.
A durable workflow for investigating accessibility that synthesizes the course without turning testing into a checklist fetish.
Reduce unnecessary interpretation and memory demands. See the Module 06 reference entries for clear content, predictable interaction, and repetition.
Give people time and control over motion. See the Module 06 reference entries for timing, moving content, safety, and reduced motion.
AI can assist accessibility work; its claims and proposed corrections need verification.
Session 15 — How Do You Know the Fix Worked?
Automated results support investigation; they leave conditions requiring judgment and manual testing.
Session 14 — What Can the Tool Actually Tell You?
A structured evaluation process combining standards mapping, manual testing, and prioritization.
Expanded guidance will be added when we reach this topic.
Let users turn off, adjust, or extend unnecessary content-imposed time limits.
Module 06
Let users control moving, blinking, scrolling, and auto-updating information.
Module 06
Treat flashing as a safety risk. Use static representations for teaching.
Module 06
Reduce nonessential slide, zoom, and parallax effects that may cause physical discomfort.
Module 06
Focus and input should let users explore without surprising changes of context.
Module 06
Use familiar words, meaningful hierarchy, and instructions whose action is easy to find.
Module 06
Reuse information from the same process, preserve progress, and make the current state and next action clear.
Module 06
Classify the claim before proposing a fix. How do you know?
Module 06