26517ISO 26517 Revision CheckerDIS edition 1 · stage 40.60

Home / The record / Clause 9: Accessible UA for a mobile application

ISO/IEC/IEEE DIS 26517, Clause 9 · Headings only

9 Accessible UA for a mobile application

Clause 9 makes accessibility a property of the help itself, with a specific duty to give a text description of an image.

What this clause covers

The public contents gives accessibility its own clause, which is a stronger signal than a sentence inside the design clause. It has a general statement and one specific subclause on the text description of an image. That specific duty is the most concrete accessibility requirement visible in the public record, and it lands on the illustrations and screenshots that clause 7.4 already brings into the help. The general subclause is likely to carry the wider expectation: the help must be perceivable, operable and understandable with the assistive technology people actually use. The draft does not name a test method in the free preview, and this site does not invent one. Our preparation uses WCAG 2.2 AA as a working benchmark, labelled as ours, not as a claim about the draft.

The headings in this clause

What to put in place before publication

  1. Inventory every image, screenshot, icon and video in the help and record whether it carries meaning.
  2. Write a text description for each informative image that says what the image shows and why it matters.
  3. Mark decorative images as decorative, so a screen reader can skip them.
  4. Test the help with a screen reader, large text and a keyboard or switch control, on a real device.
  5. Caption and transcribe video, and check that the player controls are reachable.
  6. Use WCAG 2.2 AA as the working benchmark, and label it as the team's benchmark rather than a requirement of the draft.

Evidence to keep

EvidenceWhat it looks like
Image registerA register of every image with meaning, description and owner
Alt textApproved text descriptions, reviewed with the image
TestingScreen reader, large text and switch access test records on real devices
MediaCaptions and transcripts for every video in the help
BenchmarkA note that names WCAG 2.2 AA as our benchmark, not a draft requirement

The test a reviewer runs

  • Does every informative image have a text description that reads as a sentence?
  • Is the description about the meaning, not the file name or the colours?
  • Can a screen reader user reach the help, read it and dismiss it?
  • Is the help still usable at the largest text size the platform allows?
  • Does every video have captions and a transcript?

Where teams usually fall short

  • Alt text is a file name such as screen1.png, or a duplicate of the caption.
  • The help is tested with a screen reader on a desktop browser only.
  • A video is published with no captions because it was made for a social channel.

What happens next

At FDIS, read clause 9 in full and replace the working benchmark with the published expectation where the text is more specific. Keep the WCAG note, because a benchmark is still useful beside a requirement.

Source

ISO Online Browsing Platform, free preview of ISO/IEC/IEEE DIS 26517 https://www.iso.org/obp/ui#iso:std:iso-iec-ieee:26517:dis:ed-1:v1:en read 21 October 2026

ISO/IEC/IEEE DIS 26517, standard record 87297 https://www.iso.org/standard/87297.html read 21 October 2026

W3C Web Content Accessibility Guidelines 2.2 https://www.w3.org/WAI/standards-guidelines/wcag/ read 21 October 2026

The rules this is built from

Read from the real rules, not invented.

This page is read from the public record for clause 9: the heading in the free contents, and where public, the text the preview carries.

  • 80 headings and defined terms
  • 12 dated stages behind the draft
  • 26514:2022 named as the normative reference
  • Check any line yourself
Nothing here is guessed while you wait. Each answer is written from the public record and points to the exact page it came from. Record updated 21 October 2026