#  Use Content Patterns that Support Accessibility 

 



 ##  

  expand\_more  

 
  

 

Good content structure improves access for everyone. Whether users are scanning visually, reading with a screen reader, or navigating by keyboard, clear formatting makes content easier to follow.



 

##  Why it matters 

 



 

**Structure:** Content built with real headings, lists, and spacing is easier to read and navigate.

**Consistency:** Avoiding workarounds like empty paragraphs improves maintainability across editors and teams.

**Accessibility:** Assistive technologies depend on semantic formatting to provide the right reading experience.



 



      ![Illustration of simple document outlines with structured headings, bullet points, and consistent spacing.](/sites/g/files/omnuum631/files/styles/hwp_1_1__480x480/public/2025-12/images_content_1.png?itok=jXvnK3cd) 

 

 

  

 



 

 

 

##  How to do it 

- **Use real headings, not visual styling.**
    
    Don’t bold or enlarge text to mimic headings.
    
    Use H2 for main sections, H3 for sub-sections, and keep the order consistent.
- **Write lists as lists.**
    
    Use the bullet or numbered list tool in the text editor.
    
    Do not use hyphens or asterisks as alternatives to bullets or numbers. These are not recognized by screen readers.
- **Avoid using empty paragraphs or spacing tricks.**
    
    Don’t press return multiple times to create space.
    
    Use spacing built into components or layouts, or add a Horizontal Rule component to separate sections when needed.



 

##  Accessibility tips 

- Always preview content in both the editor and on the published page. Look for skipped headings, broken list formatting, or unexpected spacing.
- Ask yourself: Would this structure still make sense if all the styling disappeared?
- When pasting from Word or Google Docs, clear formatting before editing to avoid hidden styles.



 

##  Resources 

[Harvard Digital Accessibility Services: Content Formatting](https://accessibility.huit.harvard.edu/content)

[W3C WAI: Writing for Web Accessibility](https://www.w3.org/WAI/tips/writing/)



 

 



 

 See also:- [ Accessibility ](/how-guides-topics/accessibility)
- [ Content Clarity ](/how-guides-topics/content-clarity)
- [ How-To Guides ](/page-categories/how-guides)