Merge pull request #403 from wpaccessibility/120-readability

add resources to readability

Author: rianrietveld

docs/topics/content/docs.md

@@ -3,7 +3,7 @@ title: Digital documents
 layout: default
 parent: Content and images
 description: Similar accessibility rules apply to both PDFs and HTML documents
-nav_order: 5
+nav_order: 6
 ---
 
 # Digital documents

docs/topics/content/readability.md

@@ -0,0 +1,65 @@
+---
+title: Readability
+layout: default
+parent: Content and images
+description: Make the text scannable and easy to read.
+nav_order: 5
+---
+
+# Readability
+
+Initially, people don’t read on the internet. They scan a page for keywords and only start reading when they find what they are looking for. That’s why it’s important to make the text scannable and easy to read.
+
+Good practice:
+
+- Start with a short summary of the content.
+- Divide the rest of the text in short blocks.
+- Use headings and lists and meaningful link text.
+- Avoid large blocks of text.
+
+## Make text easy to read
+
+Nobody ever complains that a text is too easy to read. Not everyone reads under perfect conditions, and for some readers your language may not be their native language. For most documents, aim for a [Flesch readability score of 60-70](https://yoast.com/flesch-reading-ease-score/). Or aim for the average reading level of a 12-year-old. 
+
+This range isn’t fixed; it depends on your target audience. There are many WordPress plugins that [measure the readability](https://wordpress.org/plugins/tags/readability/) of your text.
+
+## Break your text down
+
+Use [meaningful headings]({{site.baseurl}}/docs/topics/content/headings/), [clear link texts]({{site.baseurl}}/docs/topics/content/links/link-text/), lists, quotes and short paragraphs. This makes text more scannable and easier to read. Important points in the text should stand alone, so don’t hide important information in large text blocks.
+
+## Text style and layout
+
+- Centered or fully justified text is harder to read.
+- Use uppercase carefully. Uppercase obscures the shape of the word and can make it harder to understand. Screen readers will announce some short words as abbreviations.
+- Use italic and bold text carefully, as it interrupts the reading flow. If the information is important, think about making it stand alone.
+- Use enough line-height and a [large enough font-size](https://www.smashingmagazine.com/2011/10/16-pixels-body-copy-anything-less-costly-mistake/).
+- Limit the [content width](https://baymard.com/blog/line-length-readability) to between 50 and 75 characters.
+
+## Resources
+
+{: .resource-h3}
+### WCAG Success Criteria for readability
+
+The Web Content Accessibility Guidelines at level **AA** don't address readability. Decent readability is considered a recommendation. 
+
+However, WCAG 2.2 Level **AAA** has four success criteria for readability: 
+
+- [3.1.3 Unusual Words](https://www.w3.org/WAI/WCAG22/quickref/#unusual-words) (Level AAA).
+- [3.1.4 Abbreviations](https://www.w3.org/WAI/WCAG22/quickref/#abbreviations) (Level AAA).
+- [3.1.5 Reading level](https://www.w3.org/WAI/WCAG22/quickref/#reading-level) (Level AAA).
+- [3.1.6 Pronunciation](https://www.w3.org/WAI/WCAG22/quickref/#pronunciation) (Level AAA).
+
+{: .resource-h3}
+### Related pages in this documentation
+- [No ambiguous link text]({{site.baseurl}}/docs/accessibility-ready/theme-guidelines/no-ambiguous-link-text/) in the Theme guidelines for the WordPress accessibility-ready program.
+- [Design checks for web accessibility]({{site.baseurl}}/docs/testing/design/#readability) in Test for accessibility.
+
+{: .resource-h3}
+### Other resources
+
+- [Writing for Web Accessibility](https://www.w3.org/WAI/tips/writing/) by the W3C.
+- [Writing Accessible Content](https://foxland.fi/writing-accessible-content/) by Sami Keijonen.
+- [Plain Language Is for Everyone, Even Experts](https://www.nngroup.com/articles/plain-language-experts/) by Hoa Loranger.
+- [Dos and don’ts posters on designing for accessibility, designing for people with dyslexia](https://accessibility.blog.gov.uk/2016/09/02/dos-and-donts-on-designing-for-accessibility/) by GOV.UK.
+- [1Up Your Writing with Plain Language](https://www.handcoding.com/presentations/plainwriting/#cover) slides by Ashley Bischoff.
+- [Reading level, accessibility for web writers](https://4syllables.com.au/articles/accessibility-writers-reading/) by 4Syllables.

docs/topics/content/readability/index.md

@@ -24,17 +24,10 @@ Find the documentation for your work role, work field and expertise.
 
 ## New and updated content
 
-In July 2026:
-
-Test for accessibility:
-- [Complete checks against the Web Content Accessibility Guidelines]({{site.baseurl}}/docs/testing/overall/)
-- [Automated accessibility testing]({{site.baseurl}}/docs/testing/automated/)
-- [Content checks for web accessibility]({{site.baseurl}}/docs/testing/content/)
-- [Design checks for web accessibility]({{site.baseurl}}/docs/testing/design/)
-- [Frontend checks for web accessibility]({{site.baseurl}}/docs/testing/code/)
-- [Keyboard navigation testing]({{site.baseurl}}/docs/testing/keyboard/)
-- [Screen reader testing]({{site.baseurl}}/docs/testing/screen-readers/)
-- [WordPress plugins for accessibility testing]({{site.baseurl}}/docs/testing/plugins/)
-
-Standards and best practice:  
-- [Accessibility legislation]({{site.baseurl}}/docs/topics/legislation/)
+In August 2026:
+
+The accessibility-ready program for WordPress:
+- [About the accessibility-ready program]({{site.baseurl}}/docs/accessibility-ready/about-accessibility-ready/).
+
+Standars and best practice:  
+- [Readability]({{site.baseurl}}/docs/topics/content/readability/) in Content and images.