In addition to accessibility for UI design, content should be accessible to everyone. Universality may be a lofty goal. But if as many people as possible can enjoy our products and services, it's necessary that we develop universally accessible, inclusive content.
Universal design, accessibility, and inclusion is a big deal. So these guidelines are not definitive. Consider them the beginning of a work that will always be in progress. Read the Web Content Accessibility Guidelines (WCAG) for more on this subject.
People who have visual impairment or difficulties reading use screen readers to understand what's written on our webpage or app. We can optimise their experience by keeping these guidelines in mind when we develop content.
Read what you've written out loud to listen to how a screen reader might read it.
Write descriptive calls-to-action (CTA) and links so that people can a hint of what happens when they click the CTA or link.
Use commas and periods for long sentences. Screen readers will pause at punctuation and this may make long sentences easier to understand.
Avoid using directional words like left, right, up, down, above, and below. It will be difficult for blind and visually impaired people to find the item you are referencing.
Tell developers which of your headings are tagged H1, H2, and so on. This way, screen readers can read the page structure better through a hierarchy of content.
Make sure that abbreviations are formatted correctly so that screen readers can interpret them properly. And if you use all CAPS for regular words, screen readers might interpret them as acronyms and read them out letter-by-letter.