Prepare accessible text
Last updated: September 8, 2026 · 4 min read
Review text appearance, structure, language, and reading order together.
Large, legible type is only one part of accessible text. Heading roles, list structure, and link purpose also matter.
Follow these steps
- 1
Assign heading and body styles
PropertiesStyleParagraph style
Use a heading-role style for main headings, a subheading-role style beneath them, and Body for explanatory paragraphs. Increasing the size alone does not create a heading. Naming a custom style Heading does not assign that role either; use an existing role-bearing style.
A main heading should precede its subheading. Keep headings and long body content in separate text blocks when they serve different purposes.
- 2
Aim for readable size
PropertiesTypography
Creavim recommends 16 or above in the editor. Check small portions inside mixed-size text and text scaled from a corner. Preflight offers a size fix where applicable; separately styled portions may need to be selected and corrected inside the text.
The current check uses 16 px, which is not the same unit as 16 print points. Smaller text produces a readability recommendation; that finding alone does not block publishing.
- 3
Check text against its background
PropertiesStyle
Review text color against the actual background, including any underlying image. Transparency and effects can change the result. Follow contrast findings and visual-review prompts in Preflight.
- 4
Use actual lists and descriptive links
PropertiesParagraph
Create lists with the bullet or numbered-list control. Typing • or 1. manually does not provide the same structure. Write link text that explains its destination, and use Letter spacing instead of inserting spaces between letters.
- 5
Mark a different text language
PropertiesAccessible publishing
Select the text block and click Accessible publishing in Properties. In the popover, use Text language only when the text differs from the catalog language. For example, mark an English slogan in a Turkish catalog as English.
This does not translate the text. It helps screen readers pronounce it correctly. Professional translation of the full catalog is a separate workflow.
- 6
Review reading order
LayersReading order
With accessible mode enabled, open Reading order in Layers. Check that headings, subheadings, and their content follow a meaningful sequence. Adjust order values when needed and avoid assigning the same value to several blocks.
- 7
Finish with checks and reading
EditorPreflight
Review findings about size, heading structure, styles, language, contrast, and overflow. After making corrections, read the accessible version and try navigating its headings, lists, and links. Check the PDF separately if you are producing one.
Result
The meaning and reading sequence of the text are prepared alongside its appearance. Complete the final review on the whole accessible publication.