Chapter 5: Easy interaction Flashcards

1
Q

What is an interaction failure?

A

When a user goes “I can’t” due to a design dceision

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Is considering the device important?

A

Yes how are people accessing our site and app.

We can consider Assistive Technologies as another device

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is our aim for Easy Interaction?

A

That sites don’t create barriers or sites make barriers easier to overcome

  • Don’t make things that sort of work
  • Create designs that work for people
  • Idealy people can choose how they interact with our site (provide options)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What does captcha stand for?

A

Completely Automated Public Turing Test to Tell Computers and Humans Apart

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

How can we be successful in inteaction design?

A

Follow established pattrns for intereaction

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

How should we approach identifying and describing interactive elements?

A

Visually
Through Code
Through Interaction

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Basic HTML?

A

Use basic HTML codes correctly

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

WAI-ARIA?

A

Identify and describe interactive elements in a way that software can read and present effectively.

Adding attributes to describe our HTML e.g. role=”alert”

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Create a linear process?

A

Linerise code so that interaction easy to recieve

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What’s common problems with with filling out forms

A

Insering feddback not after the element
Labels after form fields or inside elements
Support keyboard interaction
Remember: Mouse/point/click model not tunversally usable

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

How can we support keyboard interaction?

A

Provide a logical tab order
Don’t require point and lick interaction
Hover: Not universally supported
When selecting elements: Preference is for selection than activate
Drag and Drop: provide an alternative
Show which element has focus - (Best practice: use the same state as hover)
Don’t trap keyboard focus

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What to think about when making controls?

A

Minimise fine motor skills needed for interactive elements
Space around controls
Minimise the complexity of the action required

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

How can let users control the operation of the interface?

A

Users can decide whether to open something in anew window “Don’t take action on behalf of users that they can already accomplish themselves”

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

How can we design for contingencies?

A

Using design to minimise to minimise impact of errors and system failures when they can be avoided
Allow users to request more time

How well did you know this?
1
Not at all
2
3
4
5
Perfectly