Iso 24495 5 by @gazmagik · Skillet

skill by

Iso 24495 5

Provisional sector-specific Plain Language standard for document design (based on ISO/WD 24495-5, under development). Applied when structuring complex documents so readers can find and navigate content through layout, visual hierarchy, and navigation aids.

Follow @gazmagik

Permissions

Just instructions. No commands, network, or file access.

Files

SKILL.md

iso-24495-5

Provisional sector-specific Plain Language standard for document design (based on ISO/WD 24495-5, under development). Applied when structuring complex documents so readers can find and navigate content through layout, visual hierarchy, and navigation aids.

metadata.version: 0.6.1
metadata.iso-standard: ISO/WD 24495-5
metadata.iso-status: working-draft

ISO/WD 24495-5 - Plain Language (Document Design) [PROVISIONAL DRAFT]

Provisional status: ISO 24495-5 is a Working Draft (ISO/WD 24495-5) and is not yet published. This skill is original guidance based on the draft's public scope and established information design practice. It does not reproduce ISO text. Expect revision when the standard is published.

Extends ISO 24495-1:2023 for the structural design of complex documents: reports, specifications, guides, contracts presented as documents, and long-form technical or health information. Design works together with linguistic cues to help readers find and navigate a document's structure and content.

Design for readers who are not looking at the page. The intended readers include everyone who uses the document. Some see it, some hear it through a screen reader, and some read it by touch.

A listener has no visual hierarchy. Their structure is the heading tree, the link text and the reading order. Every rule below is written to hold when the document is heard.

Scope & Execution Boundaries

Thinking Block Exemption:
- Internal layout planning and structural reasoning within thinking blocks (<thought>, <thinking>) are 100% exempt from these constraints.
- Plan freely within thinking blocks. Apply document design rules strictly to final user-facing documents.

8 files · 46 KB7 KB

Install

It’s free, and every skill you add syncs into every AI tool on your computer, instantly.

Get the Skillet appor

npx skilletmd add @gazmagik/iso-24495-5 -y

Version history

Log in to claim @gazmagik

Visual Hierarchy Limits:
- Use at most 3 heading levels below the document title. Flatten deeper nesting into lists or tables.
- Make headings state the section's message or task, not just its topic ("Install the dependencies" rather than "Dependencies").
Navigation Aids:
- Add a table of contents or link list to any document with 6 or more sections.
- Keep heading wording identical between the table of contents and the section it points to.
Chunking & White Space:
- Present one idea per visual chunk (paragraph, list, table, or callout). Separate chunks with blank lines.
- Never run two unrelated topics together in one paragraph or one table.
Choosing the Right Structure:
- Comparisons: Use a table when readers must compare 2 or more items across shared attributes.
- Sequences: Use a numbered list for steps that must happen in order.
- Options and collections: Use a bulleted list for unordered sets of 3 or more items.
- Warnings and conditions: Use a distinct callout (e.g. blockquote or bold lead-in) so readers cannot miss them.
Consistent Visual Signalling:
- Give each visual device (bold, italics, blockquotes, code formatting, icons) one meaning per document and apply it consistently.
- Never use the same device for two different meanings, or two devices for the same meaning.
- Never let a visual device carry meaning on its own. Bold, colour, an icon and a position on the page are all silent to a listener. State the meaning in words as well. "Required fields are marked in red" fails; "Required fields are marked with the word required" works.
Reaching Readers Who Cannot See the Page:
- Link text names its destination. A screen reader can list every link in a document, read aloud without the sentence around it. "Click here" and a bare web address tell that reader nothing.
- Every image that carries meaning has alternative text describing what it shows, not what it is. An image that carries no meaning is decorative and may say so.
- Tables carry a header row, because a listener hears each cell announced against its column name.
- The reading order is the document order. A sidebar or a floating callout only makes sense out of sequence, so give each one its own heading in the flow.

❌ Not aligned (Buried in Prose):

The Basic plan costs £5 per month and includes 10 GB of storage but no
priority support, whereas the Pro plan is £15 per month with 100 GB and
priority support, and the Team plan, at £40 per month, offers 1 TB,
priority support, and audit logs.

✅ ISO 24495-5 (Draft) Aligned:

Choose a plan based on storage and support needs:

Plan Price / month Storage Priority support Audit logs
Basic £5 10 GB No No
Pro £15 100 GB Yes No
Team £40 1 TB Yes Yes