Accessibility

Don't treat accessibility as a feature#

When writing, ensure your content works for every user group in your audience, including people living with disabilities.

Aim for WCAG 2.2 AA as the floor, not the ceiling.

Writing for screen readers#

• When using links, make them descriptive. This gives users who use screen readers an idea of where the link will take them before selecting it. For example, "View your statement", not "click here".
• Your buttons should say what they do. "Send ₦5,000", not "Submit" or "Continue" where a specific verb fits.
• Headings should form a real outline. One h1 per page; don't skip levels. Screen-reader users navigate by headings the way sighted users scan.
• Alt texts should focus on what matters to users. Describe the information the image carries, not its appearance. Decorative images should get empty alt text.
• Avoid ALL CAPS and stylised Unicode. Both can be read out letter by letter or skipped entirely.

Writing for low bandwidth and low-end devices#

• Front-load every page and message; assume the bottom may never load.
• Keep transactional SMS and push copy short — they may be the only channel that users get.
• When writing for digital interfaces, don't put essential information only in images.

Writing numbers, codes and references#

• Break long codes into groups: 0803 123 4567, not 08031234567.
• Let people copy reference numbers with one selection, and say so. For example, "Select to copy".

Related guidance#

• Plain language
• Error messages