HW5: Accessibility & Inclusivity
CS302, Spring 2025

Your class will be uniquely filled with students who are all different. We want our courses to be accessible to all students taking them. In this homework you will dig more into accessibility and inclusivity and audit your course/past iterations of your course to find areas to improve.

Audit #1: Accessibility/Keyboard test of Website

This audit will check your website for accessibility issues, like those faced by students using a screen reader or just a keyboard with no mouse.

Pick a page to audit

If your website has been audited recently or uses the [berkeley-class-site][berkeley-class-site] template, you might want to pick a different page to audit. You can pick any page on your website, but it is recommended to pick the homepage or a page that has a lot of content.

[berkeley-class-site]:

Step 1: Send HTML of homepage through validator https://validator.w3.org/

Step 2: Automated audit with the aXe Dev Tools * Install the aXe DevTools browser extension (just the free version) * Run through the automated audit of 1 page of your course website. * Optional: You may want to try the “Linter” static analysis tool aXe Linter

Step 3: Keyboard testing Guide

On the responses document, write up results for each step. Be sure to mention any:

There should be 1 writeup per step per course. See if you can fix any of these issues this semester. (Definitely aim to get the top issues fixed by the course starts this summer if you are teaching a class.)

Audit #2: Content of One Piece of Content Per Teammate

This audit will check your content for inclusivity.

First, to familiarize yourself with inclusivity on content, read (no need to comment):

For each p, pick a different piece of content on the scale of a homework assignment, lab assignment, lecture, textbook chapter, exam, etc, where you can find at least one thing to change to make it more inclusive and accessible. Write up on the responses document what you would change and why you are changing it.

Audit #3: Inclusivity of Syllabus

Now that each of you have learned about accessibility and inclusivity, work as a team to carefully go through your syllabus and audit the wording. Imagine how different students would read and what their reactions would be (low confidence students, high confidence students, those with lots of programming experience, those with little experience, etc).

Find a few things to improve about your syllabus and write it up as a team in the responses document.

Required listening/Reading

Rubric (Do this for full credit)