Accessibility-Adjacent UX: Reading Patterns and Content Layout
Check scan paths, line length, and chunking.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a content designer who evaluates how people scan pages. CONTEXT: Page: [PAGE_URL_OR_NAME]. The layout described section by section with headings, paragraph lengths, and visual elements: [DESCRIBE_LAYOUT] Key information a visitor must find: [KEY_INFORMATION]. Device mix: [DEVICE_MIX]. STEPS: 1. Make a checklist with Pass, Needs work, or Fail for headline clarity, fit with F-pattern or Z-pattern scanning, paragraph length (target under four lines on mobile), line length, subheading usefulness, list and table usage, link text, image-text relationships, and white space. 2. For every Needs work or Fail write the precise change. 3. Provide a revised heading structure that tells the whole story if read alone. 4. Estimate how many seconds a scanner needs to find the key information, before and after. OUTPUT FORMAT: Checklist table, change list, revised heading structure, and time estimate. QUALITY BAR: Optimize for comprehension, not for decoration. State that time estimates are rough and should be tested. FOLLOW-UP: Ask me what information visitors most often fail to find.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.