Edition
1
A new standard. No earlier edition of 26517 exists, and no certificate is replaced.
Public headings
80
Every clause, subclause and defined term in the free ISO preview, mapped on one page.
Stage today
40.60
Close of voting on 25 June 2026. The DIS ballot has closed; the FDIS is next.
Planning date
14 Sep 2027
An estimate from the stage, not an ISO announcement. The basis is on every page.
Free · no account · nothing sent
Where does your mobile help stand?
Six questions · a reading, three headings and a dated plan
What the check reads
Your answers are read against the public structure of the draft, not against a requirement text that is not public. It looks at the planning, the help forms you ship, the owner, the testing, accessibility and translation.
What it will not do
It will not certify you, score your compliance or predict the publication date. The reading is a planning device: it names the three headings to read first and the evidence to start collecting.
If you want the whole register
The kit turns the same reading into 80 rows with an owner, a status and a due date, plus a board brief. See what is in the kit.
The public record
What the draft fixes today
Edition 1, no predecessor
26517 does not revise 26514 or any other published 2651x standard. It is the mobile member of the family, and 26514:2022 is its only normative reference.
Contents at heading level
The free preview lists clause 1 to clause 9 and Annex A. The shape is planning, design, development, evaluation and accessibility, with seven disclosure techniques in the annex.
Scope, terms and dates
The scope, nine defined terms, eight abbreviations and the full life cycle to stage 40.60 are public. That is enough to plan the work; it is not enough to quote a requirement.
| Clause | Title in the public contents | Status on this site |
|---|---|---|
1 | Scope | Public text |
2 | Normative references | Public text |
3 | Terms and definitions | Public text |
4 | User assistance planning and analysis | Headings only |
5 | Design principles | Headings only |
6 | Designing content | Headings only |
7 | Developing content | Headings only |
8 | Evaluating UA design and content | Headings only |
9 | Accessible UA for a mobile application | Headings only |
A | Examples of progressive disclosure techniques | Headings only |
The table is the record. Each row links to a page that states what it covers, what to prepare and what a reviewer will ask. Full text is public for clauses 1 to 3; the rest is structure only.
The honest part
What this site will not pretend to know
The draft wording of clauses 4 to 9
The free preview stops after clause 3. The wording of the planning, design, development, evaluation and accessibility clauses is behind the paywall, so this site does not state it. What it does instead is read the public headings, the scope and the terms, and write down the preparation that any team can start now.
The four C principles
Clause 5.3 is named in the public contents as the four C principles. The four elements are not in the free preview. This site names the principle and refuses to fill the letters from memory. When the text is public, the page will carry the real list.
What the draft asks of a mobile team
Four jobs, in the order the contents gives them
Plan and analyse
Write the help plan, name first time and expert audiences, analyse the business use case and record the mobile context: platform, screen, physical setting and security.
Design the form
Choose between a first run tour, overlays, coach marks, guided help, embedded help, a help app, video, a chatbot, support by email, social channels or AI.
Develop the content
Write for a small screen, agree a gesture vocabulary, single source the variants, standardise screenshots and video, and prepare the content for translation.
Evaluate and include
Set testing goals and measures, test on real devices, and make the help accessible, starting with a text description for every image that carries meaning.
Free and paid
What you get, and what it costs
Readiness kit
USD 149
One payment. No subscription, no account.
- The register: one row for each of the 80 headings and defined terms
- The evidence list and the reviewer questions
- A dated plan from now to the planning date
- A board brief and a method note
- PDF, CSV and XLSX, downloaded from the return page
Change watch
USD 19 a month
Cancel any time from the Stripe receipt.
- An email when the ISO stage or a dated checkpoint changes
- An email when the free preview or this record changes
- The diff, with the field, the old value and the new one
- No marketing, no newsletter
Questions
Straight answers
Is ISO/IEC/IEEE 26517 published?
Not yet. The ISO record lists it as a Draft International Standard at stage 40.60, close of voting, which was reached on 25 June 2026. The next public stages are approval for registration as an FDIS, the FDIS ballot, and publication.
When will ISO/IEC/IEEE 26517 be published?
ISO has not announced a date. The planning date on this site is 14 September 2027, an estimate 330 days from the build date and about fifteen months after the close of the DIS ballot. The stage record, not the estimate, is what this site treats as fact.
Is 26517 a revision of 26514?
No. 26517 is edition 1 of a new standard and it does not replace any published 2651x standard. Clause 2 names ISO/IEC/IEEE 26514:2022 as its single normative reference, so 26514 remains the published design and development standard and 26517 adds the mobile setting.
Who is the draft written for?
The scope addresses anyone who designs, develops or evaluates user assistance for a mobile application. In practice that is the product owner, the UX content designer or technical communicator, the mobile engineering lead and the person who tests the help. It also matters to a team that acquires help from an agency.
What is in the USD 149 kit?
The readiness register with one row for each of the 80 headings and defined terms, the evidence list, a dated plan to the planning date, and a board brief, as PDF, CSV and XLSX. One payment, no subscription. A labelled specimen is free.
What does the USD 19 a-month watch do?
It emails you when the ISO stage, the dates, the free preview or this record changes. The refresh script re-reads the ISO record and the preview, compares them with the record and sends the diff. It does not send marketing.
Why is some clause text missing from the free record?
The free ISO preview carries the contents, the scope, the normative reference, the terms and the bibliography. The requirement wording of clauses 4 to 9 and Annex A is behind the paywall. This site does not invent it, and every page for those clauses says so.
The rules this is built from
Read from the real rules, not invented.
Every line points to the public ISO page or the free preview it came from, so you can check it yourself.
- 80 headings and defined terms
- 12 dated stages behind the draft
- 26514:2022 named as the normative reference
- Check any line yourself