Accessibility checklist: Common issues and best practices

This article outlines a digital accessibility checklist for Finalsite CMS websites, including the most common issues to review and the best practices that resolve them.

πŸ’‘Quick answers

  • What does the checklist cover? Nine areas: alt text, forms and keyboard access, color contrast, headings, link text, documents, video, third-party content and tools, and responsive design.
  • Where should a review start? With an inventory of the site, beginning with high-traffic pages and materials tied to core services such as calendars, registration forms, and board information.
  • Which tool checks content before publishing? The Accessibility Checker in the Composer Content element flags missing alt text, generic link text, heading order, table headers, and manually formatted lists.
  • What color contrast ratios meet WCAG 2.1 Level AA? At least 4.5:1 for standard text and 3:1 for large text and essential interface components.
  • Where are the ADA Title II deadlines listed? In the 2026 ADA WCAG 2.1 Accessibility at Finalsite article.

In this article


What is digital accessibility?

Digital accessibility means designing and maintaining websites, documents, videos, and tools so that people with disabilities can use them as effectively as anyone else. WCAG 2.1 Level AA, the technical standard adopted by the U.S. Department of Justice for ADA Title II, organizes accessibility around four core principles:

  • Perceivable: Content reaches users through more than one sense, such as alt text for images, captions for video, and sufficient color contrast.
  • Operable: Every part of the site works with a keyboard and other input methods, including forms, buttons, and visible focus indicators.
  • Understandable: Content and navigation are clear and predictable, with descriptive link text, logical headings, and plain language.
  • Robust: Content works across browsers, devices, and assistive technologies such as screen readers.

Three questions for every review

Accessibility reviews work best when each page is measured against what families need to do on the site:

  • Can families find what they need?
  • Can they understand what they are reading?
  • Can users complete important tasks without barriers?

The checklist below turns those questions into specific items to review.

Where to begin

A site with years of accumulated content benefits from a phased approach rather than fixing everything at once.

  • Take inventory: List the pages, PDFs, forms, and videos on the site.
  • Understand what exists: Check the Where Used status of files in Resources to find outdated or rarely accessed documents that can be deleted. See Find where resources are used on your site.
  • Prioritize the content families rely on most: Start with current high-traffic pages and materials tied to core services, such as calendars, registration forms, and board information.

Review the accessibility checklist

Work through each item below. Every item lists what to check, the best practices that support it, and where to learn more.

#1 Add alt text to images and non-text content

βœ… Check: Images, graphs, and other non-text content include alt text.

πŸ’‘ Best practices:

  • Describe the purpose of the image rather than its appearance, and skip phrases such as "image of."
  • Include any text that appears in the image.
  • Keep descriptions to about 125 characters or fewer.
  • Mark purely decorative images with the Decorative image option so screen readers skip them.
  • Add alt text in Resources so it follows the image everywhere it is used.
  • Review AI-generated alt text and adjust it to fit how the image is used on the page.

πŸ“š Learn more: Add alt text to images; Best practice: Writing alt-text for images; Manage alt text site-wide: Find, generate, and require alt text.

#2 Make forms and interactive elements keyboard accessible

βœ… Check: Forms, buttons, and other interactive elements are labeled and work with a keyboard and assistive technologies.

πŸ’‘ Best practices:

  • Test pages with a screen reader plugin and navigate with keyboard commands and shortcuts.
  • Label every form field or include instructions within the field, and write error messages that are clear and easy to understand.
  • Keep a visible focus indicator on links, buttons, and form fields, with a contrast ratio of at least 3:1 against adjacent colors.

πŸ“š Learn more: Understanding focus indicators for web accessibility.

#3 Check color contrast

βœ… Check: Text and essential interface components have sufficient color contrast.

πŸ’‘ Best practices:

  • Use a contrast ratio of at least 4.5:1 for standard text and 3:1 for large text and essential interface components.
  • Pair color with text or icons to signal meaning in forms, alerts, and calls to action.
  • Review contrast manually as part of the pre-publish check.

πŸ“š Learn more: WebAIM Contrast Checker; AudioEye Color Contrast Checker; TPGi Colour Contrast Analyser; Tanaguru Contrast-Finder.

#4 Use headings in logical order

βœ… Check: Headings follow a logical sequence, such as H1, then H2, then H3.

πŸ’‘ Best practices:

  • Use one H1 per page. The Page Name field in Page Settings generates it automatically.
  • Move down one heading level at a time so screen reader users can navigate the page like a table of contents.
  • Apply heading styles to create headings instead of bolding text.
  • Add header rows to tables.

πŸ“š Learn more: Structuring pages for accessibility with HTML headings; The Accessibility Checker.

#5 Write descriptive and unique hyperlink text

βœ… Check: Hyperlink text tells users where the link goes without surrounding context, and links to different destinations use different text.

πŸ’‘ Best practices:

  • Describe the destination, such as "Read our Accessibility Policy" or "Academic calendar," instead of "Click here" or "Read more."
  • Test links before publishing so each one opens the intended page.
  • Run the Accessibility Checker to flag generic link text.

πŸ“š Learn more: The Accessibility Checker.

#6 Make documents accessible

βœ… Check: Online documents, including PDFs and Word documents, follow the same accessibility standards as web pages, such as good color contrast, descriptive links, and proper heading structure.

πŸ’‘ Best practices:

  • Present content as a Composer page when possible, since HTML is easier to make accessible and to maintain than a PDF.
  • Review older PDFs, board packets, flyers, and archived materials, which are often created without accessibility in mind.
  • Export from the original application with the "Retain structure tags" setting instead of using "Print to PDF."
  • Set the document Title and Language in the PDF properties.

πŸ“š Learn more: Making accessible PDFs.

#7 Add captions and transcripts to video

βœ… Check: Videos include accurate captions, transcripts, or audio descriptions.

πŸ’‘ Best practices:

  • Add synchronized captions to announcements, welcome videos, board updates, and event recaps.
  • Provide transcripts where appropriate.

πŸ“š Learn more: Making media accessible.

#8 Review third-party content and tools

βœ… Check: Third-party content, plugins, and tools integrated into the site have been reviewed for accessibility compliance so each one supports an accessible experience.

πŸ’‘ Best practices:

  • Review each third-party tool, plugin, and embedded content item added to the site.

#9 Confirm responsive design on all devices

βœ… Check: Site content is accessible on desktop, tablet, and mobile devices.

πŸ’‘ Best practices:

  • Review key pages, including forms and tables, on desktop, tablet, and mobile devices.

πŸ“š Learn more: Preview your page in multiple ways.

Build accessibility into the publishing workflow

Accessibility is an ongoing practice rather than a one-time project. After an initial audit or redesign, the work shifts to the people who add posts, calendar items, staff pages, PDFs, forms, photos, and videos.

  • Train content editors: Share accessibility best practices with everyone who publishes content.
  • Use the Accessibility Checker before publishing: Resolve the issues it flags in the Content element, then complete a manual review of reading order, page layout, and color contrast.
  • Combine automated and human review: Automated checkers are a strong starting point; human review and shared content standards complete the picture.
  • Publish an accessibility statement: A statement communicates the commitment to accessibility and gives users a way to report issues. A sample template is available in 2026 ADA WCAG 2.1 Accessibility at Finalsite.