Create Accessible Content with Velir’s WCAG 2.2 Guide

Content is often the first thing a user encounters, and it shapes how they experience a website. If headings are misused, if alt text is missing, or if links are vague, users relying on assistive technology are immediately at a disadvantage.

Creating accessible content isn’t just best practice; it’s a responsibility. Every piece of content we publish shapes how people experience the web. When accessibility is overlooked, we are excluding people from being able to engage with our work.

That’s why Velir has created a WCAG 2.2 A & AA Checklist for Content Authors. It’s a practical resource designed to give authors not just rules, but real examples and guidance they can use every day.

Why Accessibility Starts with Content

Accessibility is often thought of as a developer’s responsibility, but content authors have just as much impact. The words we choose, the way we structure information, and how we label media and links, all influence whether users can understand and interact with our content.

It’s easy to think about accessibility as screen readers, color contrast, or ARIA labels. But at its core, accessibility is about ensuring information is perceivable, understandable, and usable by everyone. And that begins with content.

• A heading structure that flows logically helps screen reader users scan content just as quickly as visual readers.
• Alt text for images conveys meaning that would otherwise be indiscernible.
• Descriptive links (“Read our annual report”) are far more helpful than vague ones (“Click here”).
• Captions and transcripts for media mean no one is excluded.

When authors implement these practices into their workflow, accessibility becomes part of the content’s DNA, not an afterthought at the end of development.

What’s in the Checklist

The checklist provides clear, actionable steps organized into key areas:

• Text Content – Guidance on plain language, semantic markup, headings, and page titles.
• Links – How to write descriptive, non-duplicated link text.
• Images – Best practices for alt text, decorative images, and avoiding text in images.
• Audio/Video – Requirements for captions, transcripts, and audio descriptions.
• Content Structure – Using proper lists, tables, and spacing for readability.
• Cognitive Accessibility – Techniques like summaries and shorter paragraphs.
• Touch & Focus (WCAG 2.2) – Avoiding hidden or hard-to-activate interactions.
• Other Considerations – Addressing flashing content, target sizes, and motion.
• CMS Training – Practical tips for Drupal and Sitecore authors, including editor features and accessibility preview tools.

Each recommendation is tied directly to the relevant WCAG 2.2 success criteria, so content teams can understand not only what to do but also why it matters.

How Authors Can Use It

The goal of this checklist is twofold:

1. Training resource – For onboarding new authors into accessibility best practices.
2. Reference guide – Something to revisit when publishing new pages or reviewing existing content.

If content excludes, then it isn’t delivering its full value. By integrating accessibility from the start, we not only meet compliance requirements but also create digital experiences that are usable, trustworthy, and equitable.

Quick Wins for Content Authors to Improve Accessibility

Here are seven quick wins every author can apply today:

1. Use clear, plain language
   Avoid jargon, acronyms, and overly complex phrasing. If you must use an acronym, spell it out the first time. Clear writing helps everyone, especially readers with cognitive or language processing differences.
2. Structure pages with proper headings
   Headings should follow a logical order (H1, then H2, H3, etc.). Never skip levels or use bold text in place of headings. Screen reader users rely on this structure to navigate quickly.
3. Write descriptive links
   Instead of “Click here” or “Read more,” use link text that tells people exactly where they’re going, like “Download our annual report.” This helps users with screen readers and makes scanning easier for everyone.
4. Add alt text to images
   Every meaningful image needs alternative text that conveys its purpose. Keep it concise (about 140 characters). For decorative images, use empty alt text (alt=""). Avoid embedding text inside images when possible.
5. Provide captions and transcripts
   Video and audio content must have captions or transcripts. They’re critical for people who are Deaf or hard of hearing, and they help anyone who prefers reading over listening.
6. Break up long paragraphs
   Dense blocks of text are difficult to follow. Use headings, lists, and short paragraphs to make content more digestible. Summaries at the top of longer pages help readers scan and decide what’s important.
7. Make interactive elements easy to use
   Buttons and links should be large enough to tap on mobile devices and shouldn’t require long presses or hidden gestures.