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

