Build the Accessible Version
What does good accessible markup look like when you build it from the beginning?
Much of the course so far has focused on finding, explaining, and verifying accessibility problems. This module turns toward implementation.
There is no new lecture this week. Instead, you will work through hands-on accessibility exercises and use the resources below as references for writing stronger markup.
Session 16: Practice and Studio
Tuesday, October 27, 2026. No new lecture today. Use class time to begin Challenge 08, review for Quiz 2, revisit course material, or ask questions. This is open work time for accessibility practice and catching up.
Challenge 08: Build It Right
Individual Challenge · 10 points
Complete all a11yphant challenges and submit completion evidence through HuskyCT.
Because Quiz 2 is this week, Challenge 08 is due next week: by end of day Tuesday, November 3, 2026. Submit through HuskyCT.
Good Markup Resources
Start with native HTML when it already provides the semantics and behavior you need.
- Semantic HTML MDN explains how headings, landmarks, lists, buttons, links, and forms provide useful structure and native behavior.
- Forms and labels W3C WAI covers <label>, fieldset and legend, accessible names, instructions, validation, and error feedback.
- Buttons and links Links go somewhere; buttons do something: use native <a href> and <button> elements for their intended purposes.
- Images and alternative text Use the W3C WAI decision tree to choose appropriate alt text, including empty alt text for decorative images.
- Keyboard and focus MDN explains keyboard operability, visible focus, logical focus order, and why native controls help.
- ARIA: read this first W3C explains the responsibilities that come with ARIA: No ARIA is better than bad ARIA.
Quiz 2
Thursday, October 29, 2026
Quiz 2 is completed at home through HuskyCT. There is no in-person class meeting Thursday. HuskyCT is the authoritative location for Quiz 2.
Final Project
Final Project released October 29.