WCAG 2.1 AA–Aligned Checklist for Drupal Content Editors

Plain Language & Readability

Drupal Editor Guidance

These best practices support overall accessibility, across numerous WCAG Success Criteria:

• Write clearly and concisely.
• Use simple, familiar words instead of complex or bureaucratic phrasing.
• Keep sentences and paragraphs short:
  • one idea per sentence
  • one broader idea per paragraph
• Spell out acronyms and abbreviations on first use.
• Avoid jargon, internal process language, slang, and culturally specific idioms.
• Maintain a Grade 10 reading level or lower whenever possible.
• Use readability tools (e.g., Hemingway) to assess complexity.
• Use consistent terminology across the site.
• Use headings and lists to break up long or complex content.
• Avoid unnecessary repetition, hyperbole, or unsupported claims.

Relevant WCAG 2.1 AA Success Criteria

• 3.1.1 Language of Page (A)
• 3.1.2 Language of Parts (AA)
• 2.4.6 Headings and Labels (AA)
• (3.1.3 Unusual Words and 3.1.4 Abbreviations are AAA, best practice)

Inclusive, Non-Sensory Instructions

Drupal Editor Guidance

• Do not refer to content by position, color, shape, or sound.
  • example: “above,” “below,” “on the right,” “the green button”
• Refer to content by name or function instead.
  • example: “Select Submit application.”
• Assume content may be read:
  • on different screen sizes
  • in a different visual order
  • using assistive technology

Relevant WCAG 2.1 AA Success Criteria

• 1.3.3 Sensory Characteristics (A)
• 1.3.1 Info and Relationships (A)

Images & Alt Text

Drupal Editor Guidance

• Provide alt text for all meaningful images when uploading them in Drupal.
• Describe the purpose or meaning of the image.
  • example: “Students studying in a library.”
• Leave alt text empty for purely decorative images (if permitted).
• Do not:
  • repeat nearby text in alt text
  • use “image of” or “photo of”

Relevant WCAG 2.1 AA Success Criteria

• 1.1.1 Non-text Content (A)

Headings & Page Structure

Drupal Editor Guidance

• Use Drupal’s Format dropdown to apply real headings.
• Do not bold or enlarge text to mimic headings.
• Follow proper hierarchy:
  • tage title = H1 (handled automatically by Drupal)
  • section headings start at H2
• Do not skip heading levels.
• Ensure each heading clearly describes the content that follows.

Relevant WCAG 2.1 AA Success Criteria

• 1.3.1 Info and Relationships (A)
• 2.4.6 Headings and Labels (AA)

Links

Drupal Editor Guidance

• Write descriptive, meaningful link text:
  • ❌ “click here”
  • ✅ “view course requirements”
• Ensure links make sense when read on their own.
• Indicate file types for non-HTML links. (not required but recommended)
  • example: “download the policy [PDF]”
• Avoid excessive links that interrupt reading.
• Use Drupal’s link tool instead of pasting raw URLs when possible.

Relevant WCAG 2.1 AA Success Criteria

• 2.4.4 Link Purpose (In Context) (AA)

Documents & PDFs

Drupal Editor Guidance

• Use HTML pages instead of PDFs whenever possible.
• If PDFs are necessary:
  • confirm they are accessible (tagged, searchable, logical reading order)
  • clearly label links as PDFs
• Avoid uploading scanned documents unless accessibility remediation is complete.

Relevant WCAG 2.1 AA Success Criteria

• 1.3.1 Info and Relationships (A)
• 2.4.5 Multiple Ways (AA)
• various criteria including: 1.1.1, 1.3.1, and 4.1.2

Page Titles, URLs & Metadata

Drupal Editor Guidance

• Ensure every page has a unique, descriptive title.
• Avoid unexplained acronyms in titles.
• Use clear, keyword-based URL aliases:
  • 3–5 words
  • hyphens instead of underscores
• Write unique meta descriptions (not required by WCAG but an SEO best practice):
  • 150–160 characters
  • accurately describing page content

Relevant WCAG 2.1 AA Success Criteria

• 2.4.2 Page Titled (A)

Additional Content-Level Accessibility Checks

Drupal Editor Guidance

• Do not rely on color alone to convey meaning.
  • ❌ “required fields are in red”
  • ✅ “required fields are marked with an asterisk (*)”
• Do not embed critical text inside images.
• Ensure instructions are clear without relying on:
  • memory
  • timing
  • prior context
• Check content by:
  • zooming to 200%
  • viewing on mobile
  • scanning headings and links only

Relevant WCAG 2.1 AA Success Criteria

• 1.4.1 Use of Color (A)
• 1.4.3 Contrast (Minimum) (AA)
• 1.4.4 Resize Text (AA)
• 3.3.2 Labels or Instructions (A)