-
Notifications
You must be signed in to change notification settings - Fork 271
Persona names
On this page:
We want to have a wide range of roles and situations. The table below helps manage that.
Notes:
-
Use the same "persona" throughout this page where relevant. That is, if one persona can do multiple quotes, then don't create separate personas for those quotes.
-
We do not want to overlap with the other roles in Stories of Web Users: online shopper, online student, reporter (below), accountant at insurance company (below), middle school student (below), retiree (below), supermarket assistant (below).
Below currently adds: comic, gamer, parent, teacher, artist, politician, school playground aid
quote activity |
role |
|
any (tablet on wheelchair) |
Comic with cerebral palsy who uses a wheelchair: |
### 1.3.4 Orientation (Level AA) |
many (typing address) |
supermarket assistant – existing story |
### 1.3.5 Identify Input Purpose (AA) |
many (website nav) |
Gamer with language processing disability: |
### 1.3.6 Identify Purpose (AAA) |
many (reading) |
Parent with low vision – 20/500: |
### 1.4.10 Reflow (AA) |
many (order form) |
retiree – existing story |
### 1.4.11 Non-Text Contrast (AA) |
many (reading) |
student; retiree – existing stories |
### 1.4.12 Text Spacing (AA) |
any (popup) |
Teacher with low vision who uses screen magnification software: |
### 1.4.13 Content on Hover or Focus (AA) |
mail app, spreadsheet |
reporter – existing story |
### 2.1.4 Character Key Shortcuts (A) |
employee benefits |
School playground aide with cognitive disabilities: |
### 2.2.6 Timeouts (AAA) |
online tax app |
Artist with vestibular disorder: |
### 2.3.3 Animation from Interactions (AAA) |
many (motion actuation) |
Comic with cerebral palsy who uses a wheelchair: |
### 2.4.1 Motion Actuation (A) |
zoom map |
Comic with cerebral palsy who has limited movement in fingers: |
### 2.5.1 Pointer Gestures (A) |
mute, end call, web conferencing |
Politician with motor disabilities and low vision: |
### 2.5.2 Pointer Cancellation (A) |
many (send button) |
reporter – existing story |
### 2.5.3 Label in Name (A) |
many (small buttons, Cancel, Submit) |
retiree – existing story |
### 2.5.5 Target Size (AAA) |
any |
reporter – existing story |
### 2.5.6 Concurrent Input Mechanisms (AAA) |
scheduling conference call & meetings |
accountant – existing story |
### 4.1.3 Status Messages (AA) |
- Purpose and Parameters (some "Requirements Analysis")
- Some of the SCs relate to personas that we already have in Stories of Web Users. Some do not.
- If a relevant persona exists in Stories, it would be good to use that name and link to it.
- We might create additional personas in the future. It would be better not to change names later. Therefore, if we do not have a relevant persona in Stories, it would be better not to use a name at all.
- It's a bit awkward to use names for some and not for others. (e.g., Persona name / no name)
Use roles not names.
- Where we don't have an existing persona, change "person" to a role. For example:
change:
Person with limited movement in fingers:
Problem: "I can't move my fingers like that. I need another way to zoom in the map."
to:
Delivery driver with limited movement in fingers:
Problem: "I can't move my fingers like that. I need another way to zoom in the map."
- Where we have an existing persona, delete the name and start with the role. For example:
change:
Yun, retiree with low contrast sensitivity:
to:
Retiree with low contrast sensitivity:
Pro: All will be consistent.
Pro: Role is probably more humanizing/relate-able than just a name in this case where we're using just a short bit with limited context (versus personas used throughout a design project).
Con: Roles might change later when we work on all personas big picture and make sure we have good coverage of different roles, regional names, sexes, etc.
- Take off all names and roles.
Con: Boring. Less relate-able. Not persona-like. - Add just names (not roles) for those we don't have.
Con: Role is probably more humanizing/relate-able than just a name in this case where we're using just a short bit with limited context..
Con: Roles might change later when we work on all personas big picture and make sure we have good coverage of different issues. - Add names and roles for those we don't have.
Con: Names and roles might change later when we work on all personas big picture and make sure we have good coverage of different regional names, sexes, etc.