liveBook · Manning

Reading level

As explained in Architecting Accessibility

Reading level is an estimate of the educational reading ability required to understand written content.

Reading level estimates the educational reading ability needed to understand content. For web apps, match wording to the audience and prefer simple, concise language. Difficult wording can create barriers for non-native speakers and people with cognitive, learning, or language limitations, and can slow experienced users who do not know domain-specific terms. WCAG 2.2 Success Criterion 3.1.5 recommends a simpler alternative when content requires abilities beyond lower-secondary education. section 4.1

<span style="font-size:16px">Coffee as a service</span>
<br>
We provide an API that affords coffee re-orders with decaying typing
speed. The API typically serves calls within a 2-min mark, but this is
not always guaranteed, especially if there's a surge in API calls. 

Compare the jargon-heavy coffee API description with the clearer version: the latter expands API, defines latency, and uses direct wording. section 4.1

How Architecting Accessibility covers it

How deep it goes
Treats reading level as audience fit, recommending simpler phrasing and an alternative above lower-secondary ability.
Examples
Contrasts a jargon-heavy coffee API description with clearer wording that expands API and defines latency.
What you can do after
Apply it by simplifying wording, explaining unfamiliar terms, and providing an easier alternative when needed.
How it connects
Connects reading level with plain language, technical jargon, and WCAG 2.2 Success Criterion 3.1.5.

Also explained in

Compare how 2 books explain reading level →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecting Accessibility. The section links point to the parts of the book it draws on.