The following checkpoints are based on the W3C’s Web Content Accessibility Guidelines (WCAG) 2.1, but are not a substitute for the WCAG specification. They were created to assist the UGA community, including web designers, developers, content creators, and people making procurement decisions. Our intent in creating them is to present accessibility information in a way that is easier to understand and directly applicable to the UGA audience.Many of the items included in the checkpoints apply to a full range of technologies, including web pages, digital documents (e.g., Word, Google Docs, PDF), and eLC pages. Other items apply only to a subset of these technologies. The checkpoints are organized with this in mind.
Within each section, the checkpoints are roughly organized by impact, combined with ease of implementation. The most critical checkpoints that are also easiest to fix appear near the top of each list.
For a working checklist that can be used for manually evaluating web pages, websites, or web applications for accessibility, see the UGA Web Accessibility Checklist.
Checkpoints for web pages, documents, and eLC pages
- Headings: Do headings form an outline of the page content?
- Lists: Are lists used to identify all content that can be described as a list of something?
- Images: Do images have alt text?
- Tables: Are tables used solely for presenting data, and are column and row headers identified?
- Color contrast: Does the interface have sufficient contrast between text and background colors?
- Visual characteristics: Have you avoided using color or other visual characteristics as the sole means of communicating information?
- Links and buttons: Are links and buttons used appropriately and labeled correctly?
- Forms: Do form fields have appropriately coded labels, prompts, and accessible error messages?
- Time limits: Do pages with time limits include mechanisms for adjusting those limits?
- Language: Has the language of the web page or document been defined?
Checkpoints for web pages and documents only
Checkpoints for web pages only
- Keyboard accessibility: Can all menus, links, buttons, and other controls be operated by keyboard?
- Page regions: Are common regions of the web page properly identified in the code?
- ARIA: Do rich, dynamic web interfaces include proper ARIA markup?
- Popups: Are pop-ups such as menus, dialogs, and tooltips accessible?
- Flashing and flickering: Have you avoided content that flashes at a rate that might trigger seizures?
- Auto-updating content: Do auto-updating features have mechanisms to pause or stop them?
- Enlarged text: Does the content scale well when text is enlarged?
- Mobile devices: Is content accessible on mobile devices?
- Predictability: Have you avoided controls that automatically trigger a change in context?
- Finding content: Does the website have consistent navigation with multiple ways of finding content?
- Code validation: Is the web page coded using valid HTML?
Checkpoints for audio and video
- Captions: Does recorded video have captions for people who are unable to hear the audio?
- Audio description: Does recorded video include audio description for critical visual content?
- Transcripts: Does recorded audio have a transcript?
- Live captions: Are captions available for live meetings, classes, and events?
Getting help
If you have questions or need assistance, the Digital Accessibility Services Hub (DASH) is available to support colleges, schools, and administrative units as they build sustainable accessibility practices.
- Contact DASH at [email protected] for consultations, training, or technical assistance.
Accessibility is a shared responsibility, and every step you take makes UGA’s digital environment more inclusive.