UX Accessibility and Inclusive Writing 2 — Questions and Answers
Question 1: What is a 'reading level' consideration in accessible UX writing?
- Ensuring only advanced vocabulary is used
- Targeting a reading level appropriate for the broadest audience, typically around 6th–8th grade for general audiences (Correct answer)
- Writing exclusively for PhD-level readers
- Avoiding the use of numbers
Correct answer: Targeting a reading level appropriate for the broadest audience, typically around 6th–8th grade for general audiences
Writing at an appropriate reading level (typically 6th–8th grade for general US audiences) improves comprehension for users with varying literacy levels and cognitive abilities.
Question 2: What is the purpose of ARIA labels in the context of UX writing?
- To style text elements visually
- To provide accessible text descriptions for interactive elements that lack visible text labels (Correct answer)
- To create automated content translations
- To define heading hierarchy
Correct answer: To provide accessible text descriptions for interactive elements that lack visible text labels
ARIA (Accessible Rich Internet Applications) labels provide text descriptions for interactive elements—like icon-only buttons—that screen readers can announce to users.
Question 3: Why should UX writers avoid using color alone to convey meaning?
- Colors are expensive to implement
- Users with color vision deficiencies may not perceive color differences, causing them to miss important information (Correct answer)
- Color confuses translation algorithms
- Color-based meaning violates copyright
Correct answer: Users with color vision deficiencies may not perceive color differences, causing them to miss important information
Approximately 8% of men and 0.5% of women have color vision deficiencies; using only color to indicate meaning (e.g., red = error) excludes these users without additional text or icons.
Question 4: What writing practice improves accessibility for users with cognitive disabilities?
- Using long, complex sentences to demonstrate thoroughness
- Breaking content into short chunks with clear headings, bullet points, and one idea per sentence (Correct answer)
- Avoiding all images and visual aids
- Using technical jargon to be precise
Correct answer: Breaking content into short chunks with clear headings, bullet points, and one idea per sentence
Short sentences, clear headings, bullet points, and single-idea sentences reduce cognitive load and improve comprehension for users with cognitive disabilities and for all users.
Question 5: What is 'person-first language,' and when should it be used?
- Referring to people before describing their job title
- Putting the person before their condition ('person with diabetes' instead of 'diabetic person') (Correct answer)
- Always using first names in product copy
- Leading with user goals before product features
Correct answer: Putting the person before their condition ('person with diabetes' instead of 'diabetic person')
Person-first language emphasizes the person before their condition (e.g., 'person with a disability'), though some communities prefer identity-first language—context and community preference matter.
Question 6: What is the primary accessibility concern with instructions that say 'tap the red button'?
- The word 'tap' is too casual
- It relies on color alone, excluding users with color vision deficiencies (Correct answer)
- The word 'button' is redundant
- It assumes a touchscreen device
Correct answer: It relies on color alone, excluding users with color vision deficiencies
Instructing users to tap 'the red button' relies on color perception, which excludes users with color vision deficiencies who may not distinguish it from other buttons.
UX Accessibility and Inclusive Writing 2
What is a 'reading level' consideration in accessible UX writing?