惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

F
Full Disclosure
Stack Overflow Blog
Stack Overflow Blog
H
Help Net Security
Microsoft Azure Blog
Microsoft Azure Blog
The GitHub Blog
The GitHub Blog
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
Recorded Future
Recorded Future
Y
Y Combinator Blog
Cloudbric
Cloudbric
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
S
Schneier on Security
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
C
Cybersecurity and Infrastructure Security Agency CISA
TaoSecurity Blog
TaoSecurity Blog
Security Latest
Security Latest
N
News and Events Feed by Topic
Hacker News - Newest:
Hacker News - Newest: "LLM"
D
DataBreaches.Net
Security Archives - TechRepublic
Security Archives - TechRepublic
H
Hacker News: Front Page
C
Cisco Blogs
L
LangChain Blog
aimingoo的专栏
aimingoo的专栏
Recent Commits to openclaw:main
Recent Commits to openclaw:main
V
Vulnerabilities – Threatpost
L
LINUX DO - 最新话题
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
Google Online Security Blog
Google Online Security Blog
D
Darknet – Hacking Tools, Hacker News & Cyber Security
A
About on SuperTechFans
www.infosecurity-magazine.com
www.infosecurity-magazine.com
Jina AI
Jina AI
C
CXSECURITY Database RSS Feed - CXSecurity.com
Schneier on Security
Schneier on Security
T
Tenable Blog
N
News and Events Feed by Topic
W
WeLiveSecurity
有赞技术团队
有赞技术团队
AI
AI
爱范儿
爱范儿
大猫的无限游戏
大猫的无限游戏
Latest news
Latest news
T
The Blog of Author Tim Ferriss
S
Security Affairs
Know Your Adversary
Know Your Adversary
Simon Willison's Weblog
Simon Willison's Weblog
G
GRAHAM CLULEY
Google DeepMind News
Google DeepMind News
The Cloudflare Blog

TetraLogical Blog

Designing for people with reading disabilities - TetraLogical Designing for people who are D/deaf - TetraLogical Designing accessible documents - TetraLogical Introduction to creating accessible documents - TetraLogical Inclusive user research: vulnerable people - TetraLogical Designing for people who are blind - TetraLogical Designing for people with low vision - TetraLogical Meet the team: Niamh Madden - TetraLogical Designing for people with anxiety - TetraLogical Designing for people with disabilities - TetraLogical Accessible building blocks for the web videos - TetraLogical Common accessibility misconceptions - TetraLogical Common misconceptions about testing accessibility - TetraLogical Common misconceptions about implementing accessibility - TetraLogical Common misconceptions about WCAG - TetraLogical Common misconceptions about disability - TetraLogical Meet the team: Grace Snow - TetraLogical Sustainable accessibility in complex organisations: strategic foundations - TetraLogical Sustainable accessibility in complex organisations: organisational realities - TetraLogical Sustainable accessibility in complex organisations: external factors - TetraLogical Common misconceptions about screen readers - TetraLogical Guide to the Inclusive Design Principles - TetraLogical Meet the team: Ian Lloyd - TetraLogical Annotating designs using common language - TetraLogical Meet the team: Catriona Morrison - TetraLogical Championing inclusive language - TetraLogical Press release: TetraLogical launches accessible self-led training courses to help digital teams build confidence in accessibility - TetraLogical Why inclusive products are green products - TetraLogical Accessible Recruitment - TetraLogical Accessibility and the agentic web - TetraLogical Meet the team: Craig Abbott - TetraLogical Foundations: types of assistive technology and adaptive strategies - TetraLogical European Accessibility Act (EAA) FAQ - TetraLogical Screen reader HTML support tables - TetraLogical Interview with Lola Odelola - TetraLogical Understanding EN 17161 Design for All - TetraLogical Inclusive user research: building rapport - TetraLogical Foundations: Keyboard accessibility - TetraLogical Can generative AI write contextual text descriptions? - TetraLogical Understanding the European Accessibility Act (EAA) - TetraLogical Meet Josh: a sportsman who has spinal muscular atrophy - TetraLogical Meet Jonathan: a photographer who has ADHD - TetraLogical Foundations: grouping forms with `<fieldset>` and `<legend>` - TetraLogical XR Accessibility: for people with moving disabilities - TetraLogical Meet Andre: a music producer and blind screen reader user - TetraLogical Foundations: types of disability - TetraLogical Meet Lauren: a film editor who has ADHD - TetraLogical Meet Steve: a photographer who is deaf and low vision - TetraLogical Foundations: form validation and error messages - TetraLogical Meet Hasmukh: a blind cricketer and screen reader user - TetraLogical XR Accessibility: for people with hearing disabilities - TetraLogical XR Accessibility: for people with thinking disabilities - TetraLogical XR Accessibility: for people with seeing disabilities - TetraLogical Introduction to XR Accessibility - TetraLogical Foundations: labelling text fields with input and label - TetraLogical Design patterns and WCAG - TetraLogical Does WCAG 2.2 apply to native apps - TetraLogical Why are my live regions not working? - TetraLogical Building a culture of accessibility - TetraLogical When to use tabindex= Accessibility foundations - TetraLogical Meet the team: Demelza Feltham - TetraLogical Can generative AI help write accessible code? - TetraLogical Meet the team: Steve Faulkner - TetraLogical Meet the team: Gez Lemon - TetraLogical Keyboard accessibility myths and WCAG - TetraLogical Amendment to the Public Sector Accessibility Regulations - TetraLogical What Considerations for TV user interface accessibility - TetraLogical Meet the team: Alistair Duggin - TetraLogical Sticky content: focus in view - TetraLogical The only accessibility specialist in the room - TetraLogical Meet the team: Ian Pouncey - TetraLogical Meet the team: Dean Holden - TetraLogical Meeting WCAG Level AAA - TetraLogical Foundations: accessible names and descriptions - TetraLogical Inclusive XR: accessible augmented reality experiences - TetraLogical Foundations: pointer gestures - TetraLogical Meet the team: Graeme Coleman - TetraLogical Adding sign language to videos - TetraLogical Foundations: introduction to WAI-ARIA - TetraLogical Meet the team: Joe Lamyman - TetraLogical Inclusive XR: accessible 3D experiences - TetraLogical Foundations: visible focus styles - TetraLogical Foundations: target sizes - TetraLogical Meet the team: Henny Swan - TetraLogical Meet the team: Ela Gorla - TetraLogical Foundations: native versus custom components - TetraLogical Foundations: HTML semantics - TetraLogical Accessibility and supporting Internet Explorer - TetraLogical Meet the team: Felicity Miners-Jones - TetraLogical Accessibility and QR codes - TetraLogical Inclusive user research: recruiting participants - TetraLogical Meet the team: Léonie Watson - TetraLogical Android accessibility: roles and TalkBack - TetraLogical Accessible design systems - TetraLogical Meet the team: Patrick H. Lauke - TetraLogical Inclusive user research: analysing findings - TetraLogical How to write user stories for accessibility - TetraLogical Triaging WCAG 2.1 Level AAA - TetraLogical
Research insight: accessibility of images - TetraLogical
2022-07-21 · via TetraLogical Blog

Posted on by Henny Swan in Testing, User experience

When conducting usability testing with disabled users, we observed how well images performed from both a visual and non-visual perspective when it came to finding and understanding content.

We often think of accessible images as having alt attributes with appropriate text descriptions for people who can not see or understand them.

What gets overlooked is whether the visual content of the image is appropriate to the context of use for people with sight. Equally, if the text description fits in to the flow of adjacent content.

The participants

Six people with disabilities were invited to test a news website on a desktop. Participants included:

The task

Each participant was asked to find an article about disability on the homepage and by using search.

Each article consisted of an image, heading and text presented in that order both visually and in the code. The image was positioned on top as a rectangle, the heading underneath, followed by a date and name of the author, then short text introducing the topic.

In most cases, the heading stretched over two to four lines and was roughly 10 to 17 words. Most, possibly all, of the images were stock photos.

A sketched wireframe of 3 images with a thick squiggly line underneath for a heading and thinner squiggly lines under the headings to indicate text
A wireframe of how the layout of articles appeared on the home page of the test site.

Observations

Relevancy

When the visual content of the image and its text description did not complement the heading it was grouped with, it negatively impacted people's understanding of the page.

For example, when looking for an article about disability, our participant with dyslexia and ADHD didn't read the long headings. Instead they looked at the images for context but couldn't find any about disability:

It's helpful with the imagery for articles but I'm not necessarily sure that pictures actually go with the titles that much. For me images are always helpful to sort of sum up what something is about quite quickly [...] but some of them don't really seem actually relevant.

Our participant who was browsing with speech recognition and had ADHD didn't connect the visual content of the image with the heading and commented:

The picture seems artificial; I guess it's a stock photo.

A selection of stock photos showing real people, paper cutout people, abstract people and hands moving small coloured pieces into patterns
Stockphotos shown on a website where they can be purchased.

Similar issues were experienced by both screen reader users, who said text descriptions of images often did not convey any useful information. As one commented:

The description just says 'diversity', what does that mean? It tells me nothing about that graphic.

Consistency

Both screen reader users commented on the inconsistent quality of text descriptions.

Some text descriptions gave context, for example, "A disabled woman at work" for an article about disability at work. Other text descriptions were just a single word which was not helpful:

A graphic called covid is amusing. What picture is that!

The other screen reader user, mentioned inconsistent text descriptions. They also noticed some images didn't have a text description and commented the experience was "disjointed".

Other images were followed by a caption, so blind participants knew an image was on the page but could not tell what it contained. They found this annoying and made them wonder what content they were missing:

The images on news articles are often not labelled. It just says "getty image istock" or whatever, it doesn't say what the image is a picture of.

Reading order

On the search results page, images preceded the heading it was associated with which caused one of the two blind participants to navigate to the wrong article.

Wondering what the image with a text description "diversity" contained and referred to, he decided to read the related article. Instead of selecting the article title that followed the image, he selected the one that preceded it, and never realised his mistake.

A sketched wireframe of 3 search results showing an image with a thick squiggly line underneath for a heading and thinner squiggly lines under the headings to indicate text, positioned vertically and repeated three times
A wireframe of how the layout of articles appeared on the search results page of the test site.

Research insights

Decorative images do more than just decorate a page, they also provide context, regardless of whether you can see an image or not.

Our key research insights are:

  1. Avoid the use of generic images and stock photos, they can add to confusion rather than add value.
  2. When choosing images, ensure visual content is relevant to the adjacent content such as headings and text. For example, pick an image that has a strong visual connection to key words in a heading.
  3. When writing text descriptions, ensure the editorial describes the image with language that naturally flows with the adjacent content. For example, if the heading is "Disability in the workplace", pick an image that shows someone with a disability at work and a text description that says something like "A woman in a wheelchair gives a presentation in the office".
  4. Use a consistent approach to writing text descriptions to help build comprehension for people who are blind.
  5. Carefully consider where in the content order, an image appears. Images should follow the a heading in the code order. They can be positioned above a heading using CSS as long as visually the image, heading and associated text are grouped together. This can be done using a line to separate each article, or a box.

Next steps

Read more about moderating usability testing sessions, analysing findings and how we can support you with our Agile Usability testing service.