Assigned Readings

Each of the project teams have subteams that take a turn introducing one of the class readings as a part of an in-class panel on the kickoff date. Members of the kickoff team typically get started on the reading one class session before the rest of the class. They then participate in a panel in front of the class to answer questions posed by an instructor (acting as moderator) and other classmates. Some of the questions from classmates will be from the list of questions given to the panelists in advance. Students in the class can also ask questions that they think of. The instructors can help field the questions that the panelists deem to be beyond their knowledge of the reading or topic.

Reading 6

Dual track kick-off panels 10/15 by Oof Whites subteam-Y & Oddidos subteam-Y

all students complete readings by 10/18

6a: - Errors readings and panel by Oof Whites subteam-Y

• Destructive Errors & Undo-ing
  • Historically, this was more of "what if you exit your document without saving?" Now that we have auto-save, sometimes companies do it intentionally.
  • What if you swipe left on the love of your life?
  • Tinder+ with undo Button
• Preventing In Progress Errors
  • Some of this is just making things intuitive, some of this is displaying appropriate in line messages
  • Form validation design is a great example.

6b: - Accessibility readings and panel by Oddidos subteam-Y

All of these guidelines are good design principles in general, not just good for accessibility. They look a little long but is mostly bulleted and quite quick to read.

• Overview of web accessibility (so you'll know the four principles and can dive in deeper later!)
• 3.3 - Errare Humana est - continuing on the error theme w/ an accessibility bent
• 1.3 - Present Content in Different Ways
• 1.4 - Separate Background & Foreground (Focused on color) OR 3.1 - Easy to Read (Focused on text)
• 2.4 - Focused on Information Architecture

Questions to pose for each team facilitating discussions:

Errors tables

• Can you think of spaces in your project where it makes sense to purposely take away an undo feature?

• When people are entering data, how might color help you signal good progress and invalid input? If you have users from multiple cultures, are there cues that you can give from colors that work across a wide range of cultures? Should people be able to select their “region” to help influence color palettes?

• choosing passwords are things that people need to re-enter a lot based on seemingly random requirements - how much security do you need for your applications based on how much sensitive data you take and how much of a security hit can you take for tough password or authentication?

• Is it OK to have an AI “autocorrect” and submit information on behalf of a user? If so, in what situations is doing so more palatable / acceptable than other situations?

Accessibility tables

• Projects for UX Design class do not have to be completely accessible / perceptible by all users, but teams are encouraged to consider at least one or two ways that they could improve accessibility. To what degree are your teams’ sketches depending upon media that require additional steps to make accessible / translatable (images, audio, video)?

• In the context of your project, with an eye toward accessibility, introduce a situation when you would need to point to a user error and propose descriptive text that make it clear what went wrong and how to correct it.

• Why do so many designers change text in its presentation to convey information without using the appropriate markup?

• Normally, designers use alt tags and other mechanisms to describe words that are in images, with the power of machine learning on the rise, will this practice become obsolete soon?