UAMS Web Accessibility Publishing Checklist

A quick reference for content management system and calendar editors

Every page matters. Before publishing or updating a UAMS webpage or calendar event, check the items that apply. See the UAMS Web Accessibility Reference Guide for explanations and examples.

Images and Alternative Text

• Meaningful images have accurate, descriptive alternative text.
• Decorative images are marked as decorative.
• Complex images, such as charts and infographics, have text alternatives.
• Important information is not available only within an image.
• Event details and instructions appear as webpage text, not only in a flyer or graphic.

Videos and Audio

• Videos with speech or meaningful audio have accurate captions.
• A transcript is available on the page for audio and video content.
• Important visual information has narration, audio description or another alternative.
• Media titles and descriptions clearly identify the content.
• Media players can be operated with a keyboard.

Links, Forms and Tables

• Link text describes its destination or purpose.
• Downloadable files are identified by type, such as “(PDF).”
• Forms that collect protected health information or personally identifiable information were not built in the CMS. Those forms are created by IT or in Microsoft Forms.
• Form fields have visible labels and clear instructions.
• Required fields and errors are identified in text, not by color alone.
• Error messages explain how to fix the problem.
• Tables are used for data, not page layout.
• Data tables have header rows or columns marked with the CMS table-header tools.
• Tables pasted from Word or Excel were rebuilt, with no merged or split cells.

Keyboard Navigation

• Links, buttons, forms and other controls work without a mouse.
• Keyboard focus is visible and moves in a logical order.
• Visitors can move into and out of interactive elements without getting trapped.
• Important actions don’t require a mouse.

Publishing tip: Use Tab, Shift + Tab, Enter and the space bar to check navigation and controls. If something doesn’t work with a keyboard, report it to Web Services.

Documents and Readability

• Information is published as webpage text whenever practical.
• Required PDFs and other downloadable documents have been checked for accessibility.
• Content uses clear, plain language.
• Headings use the built-in styles in a logical order.
• Lists use real list formatting.
• Body text is left-aligned, not fully justified.
• Text and important visual elements meet contrast requirements (4.5:1 for normal text, 3:1 for large text and interface elements).
• Information is not communicated through color alone.
• Text can be enlarged to 200%, and the page works at 400% zoom without scrolling sideways.

Accessibility Review

• I reviewed the content with Blackboard Ally for Websites.
• I addressed issues within my editing permissions.
• I completed a manual review for issues automated tools may miss.
• I rechecked the content after making corrections.
• I reported unresolved issues to Web Services.

Before You Publish

Can everyone find, understand and use the information I have provided? If you identify a barrier, correct it before publishing or contact UAMS Web Services.

Need Help?

• UAMS Web Accessibility Knowledge Base
• For detailed guidance, see the UAMS Web Accessibility Reference Guide.