To save this webpage as a printable checklist, follow the instructions in your web browser to print it.
Google Slides
Google doesn’t provide tagging features that support document accessibility. To address this, Aims recently implemented Grackle for Google. Grackle is a new tool available for everyone using Google Apps to help you make your Google Sheets accessible. Grackle works as an “overlay tool” with Google Sheets to support the accessibility of content.
When you run Grackle Docs it scans your Sheet for many types of accessibility barriers. Along with Grackle, use the following checklist to create a more accessible Google Sheets.
- ___ File format: Google Slides saves files in a web format. Users can export files as .pptx or PDF files. Create accessible PDFs or other file formats of your presentation.
- ___ Document language: Set the primary language: File > Options > Language.
- ___ Slide title: Since Google Slides does not use headings, use a slide title instead. Every slide should have a unique title. Assistive technology users such as screen readers need to be able to navigate by slide title.
- ___ Themes and master slide layouts: A theme defines the overall look and feel of a presentation, including colors, fonts and background styles. Master slide layouts are the predefined templates that determine how content is arranged on each slide, and they are incorporated within a theme. It's crucial to use existing themes as these can provide structure that is recognized by assistive technologies. Manually inserting elements outside the slide master may lead to screen readers not identifying key information on a slide.
- ___ Reading order: Accessible themes have pre-designed slide layouts. The reading order should be understandable by both a sighted person and a person with low vision or blindness using a screen reader.
- ___ Headings: Use built-in heading styles (Heading 1, Heading 2, etc.) within each slide to ensure that headings are descriptive and concise. Organize headings in a logical order; avoid skipping levels (e.g., from 1 to 3).
- ___ Links: Use meaningful descriptive link text that clearly indicates the link destination. Links need to be visually distinct from surrounding text (e.g., underlined and in a different color). Avoid generic phrases like “click here” or “learn more.” People who use screen readers may scan a list of links to learn about the content.
- ___ Tables: Avoid tables and instead use paragraphs with headings. If you must use data tables, avoid fixed width tables and use table headers. Ensure that tables don't contain split cells, merged cells, or nested tables.
- ___ Lists: Make content easier to read by providing visual structure and highlighting key points using lists.
- ___ Slides on a timer: Avoid these because they can restrict users from reading everything before a slide advances.
- ___ Text boxes are inaccessible: Avoid using text boxes. Screen readers may ignore text in text boxes.
- ___ Font and font size: An accessible font supports the reading speed of anyone reading a slide, including people who are blind, have low vision or a reading disability. Use a clear, simple font like Arial, Calibri or Times New Roman. Use a body text font size of 18 points or larger and provide for sufficient white space. Avoid using ALL CAPS, italics or underlining for large blocks of text.
- ___ Line spacing: Use adequate line spacing (e.g., 1.15 or 1.5).
- ___ Paragraph spacing: Use to separate paragraphs; avoid using multiple spaces or tabs for indentation.
- ___ Color: Do not rely on color alone to convey important information.
- ___ Color contrast: Use high color contrast between the foreground and background colors.
- ___ Use a color contrast analyzer tool to ensure WCAG 2.1 Level AA sufficient contrast:
- ___ Images: Provide clear and concise descriptive alternative text ("alt text") for all meaningful images (best practice is 120 characters or less). Provide long text descriptions for infographics. No alt text for decorative images.
- ___ Images: Nest images in line with the text so screen readers will identify an image and read its alt text.
- ___ Charts and graphs: Position these inline with the text. Must have a long text description.
- ___ Animations and slide transitions: Keep these short and to a minimum. Avoid using any flashing objects.
- ___ Grackle for Google: An accessibility checker for Google Apps that simplifies the process of making presentations accessible to all users. Has automated checks and guided corrections.
- ___ Aims has purchased Grackle for Google to create accessible resources for Google apps. This includes Docs, Slides and Sheets. Here are video instructions for how to enable Grackle from within each Google app.
- ___ Manual testing: After using this checklist to update the Google Slides file, I have done manual testing for keyboard navigation, and with a screen reader (if I have been trained to use NVDA for PC, or VoiceOver for Mac).