Website content: What’s WCAG got to do with it? #5822
Replies: 2 comments 1 reply
-
Becoming aware of conversations around plain language and accessible content is a great place to start. For example, join the plain language community on Digital.gov. The listserv will give you a place to ask questions and will show you conversations about challenges that others are facing. You'll also be informed of upcoming learning events. |
Beta Was this translation helpful? Give feedback.
-
I do really think that there is value in running text through a tool like Hemingway App Worth noting that this is recommended in the California Design System Also, I really find that Edge's Reader Mode is great. Nobody likes to read their own work aloud, but it is useful to hear it spoken. Having editors hear their work, can give them some experience of how people will be experiencing it with other text to speech tools, too. I think this is a good practice for authors. |
Beta Was this translation helpful? Give feedback.
-
A site with accessible code becomes inaccessible when content is confusing or too complex. Inaccessible content affects everyone, and this includes English language learners, people with disabilities, and assistive technology users. (You can hear more about the needs of screen reader users on our May 2023 monthly call recording.)
Using plain language techniques and conforming to Readable Web Content Accessibility Guidelines (WCAG) can help. Some of the WCAG success criteria related to clear writing include:
USWDS guidance on plain language and content can be found on many pages of our site. Some examples include:
We want to hear from you: How do you ensure plain language on your site? What can USWDS do to support teams working towards more accessible content?
Beta Was this translation helpful? Give feedback.
All reactions