26517ISO 26517 Revision CheckerDIS edition 1 · stage 40.60

Home / The record / Clause 3: Terms and definitions

ISO/IEC/IEEE DIS 26517, Clause 3 · Public text

3 Terms and definitions

Nine terms fix the vocabulary for the draft, from coach mark to user experience, and eight abbreviations cover AI, AR, CSS, FAQ, GUI, JSON, STE and UI.

What this clause covers

The vocabulary is small and deliberate. User assistance is wider than a help page: it includes principles, design techniques and solutions. A coach mark is a small pop-up laid over the interface, not a tooltip in a web page. An icon is a screen graphic that stands for a function. Minimalism is not brevity for its own sake; it is critical information plus the least extra information needed to be complete. Responsive design is about adaptation to the device layout. Context of use brings in users, tasks, equipment and the physical and social setting. The abbreviations show the technical range of the draft: AI, AR, CSS, JSON, STE and UI all appear in the mobile help conversation.

The headings in this clause

What to put in place before publication

  1. Put the nine terms and eight abbreviations into the house style guide with the same meaning as the draft.
  2. Write a short usage note for user assistance, user experience and user interface so the team stops using them as synonyms.
  3. Decide how you will name gestures and controls in help content, and keep that list beside the glossary.
  4. Check translated glossaries for a matching term, not a literal translation.
  5. Review the glossary when the published edition appears, because defined terms can change between a draft and publication.

Evidence to keep

EvidenceWhat it looks like
GlossaryA glossary entry for each defined term, with the draft as its source
UsageA usage note that separates UA, UX and UI in the style guide
TranslationThe approved term list shared with translators
CurrencyThe glossary review date and the edition it was checked against

The test a reviewer runs

  • Does the style guide use user assistance in the same sense as the draft?
  • Is a coach mark distinguished from a tooltip, a banner and a modal?
  • Do the translated terms match the approved glossary?
  • Are minimalism and brevity used as if they meant the same thing?

Where teams usually fall short

  • The team uses help, documentation and user assistance interchangeably.
  • A coach mark is called a tooltip in the design file, so the build and the text diverge.
  • The glossary is copied from a web style guide and never checked against the draft.

What happens next

Re-read clause 3 when the FDIS appears. A changed definition can change the reading of every clause that uses the term, so update the glossary before the pages or the templates.

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

The rules this is built from

Read from the real rules, not invented.

This page is read from the public record for clause 3: 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