This activity guides students through the evaluation of a website that they have created to see if it is accessible for users with disabilities. Students will simulate a number of different disabilities (e.g. visual impairments, color blindness, auditory impairments, motor impairments) to see if their website is accessible; they will also use automated W3 and WAVE tools to evaluate their sites. Students will consider the needs of users with disabilities by creating a persona and scenario of a user with disabilities interacting with their site. Finally, students will write up recommendations to change their site and implement the changes.

Comments
Although this activity can be used in isolation, it is intended to be part of a series guiding students towards the creation of a front-end of a website. The series (all published as OER) consist of:

a) Needfinding
b) Personas, Scenarios and Storyboards
c) Front-end Website Design and Development
d) Accessibility Evaluation

This presentation introduces Computer Science students to the notion of accessibility: developing software for people with disabilities. This lesson provides a discussion of why accessibility is important (including the legal, societal and ethical benefits) as well as an overview of different types of impairments (visual, auditory, motor, neurological/cognitive) and how developers can make their software accessible to users with those disabilities. This lesson includes videos and links to readings and tutorials for students.

Comments
These slides use Poll Everywhere polls; to use them, create your own Poll Everywhere account and duplicate the polls.

These slides are used to guide a discussion with students introducing them to the notion of public interest technology and coding for the public good. The lesson is intended to spark a discussion with students about different sorts of technology and their societal ramifications.

Comments
Note that these slides use Poll Everywhere polls; to use them, you will need to create your own Poll Everywhere account.

This activity helps student design and develop a front-end of a website, from wireframes through HTML/CSS/Javascript. It includes design questions for students, including the invocation of Ben Schneiderman's eight golden rules for interface design.

Note: this activity assumes prior knowledge of web development. Since this activity is designed for an HCI course, with a focus on interface design, students are not expected to create a back-end for it. This activity can obviously be modified for a full-stack experience.

Comments
Although this activity can be used in isolation, it is intended to be part of a series guiding students towards the creation of a front-end of a website. The series (all published as OER) consist of:

a) Needfinding
b) Personas, Scenarios and Storyboards
c) Front-end Website Design and Development
d) Accessibility Evaluation

This activity guides students through the process needfinding to identify areas of need for their creation of a technology for the "public good." Students will conduct contextual inquiry to identify the needs of their target audience.

Comments
Although this activity can be used in isolation, it is intended to be part of a series guiding students towards the creation of a front-end of a website. The series (all published as OER) consist of:

a) Needfinding
b) Personas, Scenarios and Storyboards
c) Front-end Website Design and Development
d) Accessibility Evaluation

This activity guides students towards the creation of personas, scenarios and storyboards for a product/website that they are creating.

Comments
Although this activity can be used in isolation, it is intended to be part of a series guiding students towards the creation of a front-end of a website. The series (all published as OER) consist of:

a) Needfinding
b) Personas, Scenarios and Storyboards
c) Front-end Website Design and Development
d) Accessibility Evaluation