What the record proves
The ISO page gives edition 1, copyright 2026, 34 pages, and no "previously" or "will be replaced" entry in the life cycle. The IEEE project is an active PAR, not a revision of an existing IEEE standard. The bibliography lists the other 2651x standards, and clause 2 names only 26514:2022 as a normative reference. Taken together, that is a new standard that adds a mobile member to the family.
Why the word revision still appears on this site
The product is a revision checker because the draft itself is moving through revision: committee drafts, a DIS, an FDIS and a published edition. The thing being checked is the text as it changes, not a previous edition of 26517. A team that reads the site as a transition guide for an old 26517 will find nothing to transition from, and the pages say so.
What a team should do first
Check the family, not a predecessor
26514:2022 is the published design and development standard in the family. If the team already follows it, the mobile additions in 26517 are the delta to plan.
Do not wait for a transition notice
There is no certificate to renew and no accreditation body to notify. The trigger for work is the app roadmap, not a transition deadline.
Plan for the published text
The free preview stops after clause 3. The published edition will carry the full wording. Put a reading task in the plan for the day it appears, not for a date that ISO has not announced.
What is not claimed
- No claim that 26517 replaces 26514, 26512, 26513, 26515, 26516 or 26531.
- No claim that a certificate, audit or contract must change because of this draft.
- No claim that the draft is final, or that the published edition will match it word for word.
- No claim that following this site makes a team conform to the standard.
If you already follow 26514
The useful comparison is between the 26514 process you run and the mobile specific headings in this draft. The planning clause asks for a mobile context, the design clause asks for mobile help forms, the development clause asks for small screen writing and translation, and the evaluation clause asks for testing on mobile devices. Those are the places where a 26514 process may need a mobile appendix, a device test plan and an accessibility check.
Source
ISO/IEC/IEEE DIS 26517, standard record 87297
https://www.iso.org/standard/87297.html
Read 21 October 2026. Title, edition 1, 34 pages, stage 40.60 on 2026-06-25, DIS registered 2026-01-23, ballot opened 2026-04-01, committee ISO/IEC JTC 1/SC 7, ICS 35.080 and 35.240.95, CHF 67, abstract, life cycle.
IEEE SA project P26517, IEEE/ISO/IEC Draft International Standard
https://standards.ieee.org/ieee/26517/11226/
Read 21 October 2026. PAR approved 2023-03-30, active PAR, working group 26514_WG, C/S2ESC, IEEE Computer Society, scope and need statement.
ISO/IEC/IEEE 26514:2022, Design and development of information for users
https://www.iso.org/standard/77451.html
Read 21 October 2026. The single normative reference named in clause 2 of the draft. Published edition 1, 2022, 64 pages, stage 60.60.
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