Assignment 2 practice site
This site contains five screens of a ticket purchase flow for a fictional theatre. The markup, styles,
and scripts contain a set of accessibility failures. Your job is to find them,
map them to WCAG 2.2, rank them, and repair some of them. See the assignment page for the full details of how to complete this assignment.
The flow
- Events listing
- Event detail
- Seat selection
- Checkout
- Confirmation
Working on a copy
Before you start, clone the assignment repository.
You will submit your repairs as a patch file generated from the initial repo state. The
assignment page
has instructions on how to do this.
Every page is plain HTML with no build step, so opening each HTML file in a browser is enough to see your changes.
Running the automated checkers needs one more step. Serve the folder at a localhost
address first, because browsers block extensions such as axe DevTools from reading pages opened
straight from disk. The assignment page
gives the commands.
Notes
- Audit the five screens listed above. This page is not one of them, and neither is
the banner at the top of each page that says "Course exercise".
- About half of the issues announce themselves in a screen reader's speech output, a handful
more turn up when you operate the page from the keyboard or fill in the form, and
the rest are only visible in the CSS, the DOM, or an automated checker's report.
Expect to read the source as part of this assignment, which is a normal part of auditing.
- Some problems conform to WCAG but still create usability issues. Those belong in the
second list of your analysis, not in the list of findings mapped to WCAG.
- This assignment does not tell you the total number of accessibility issues. Find as many as you can!
Start the flow