Heading levels should be organized hierarchically, just as in a topic outline. The page title in Canvas is always automatically coded as Heading 1. Heading 2 is used for all subtopics on the page, Heading 3 for sub-subtopics, and so on.
Lists should be formatted using the Canvas Rich Content Editor (RCE) so that it can be read as a list by a screen reader.
Using hyphens, asterisks, or other non-semantic characters may create the appearance of a list, but lists created without formatting tools will not be recognized as a list by assistive technology.
Keep in mind that depending on the content, some list styles are more appropriate than others. For instance, if you are providing instructions that must be followed in order, you should choose an ordered list style. If the list data isn’t sequential, you should use an unordered list style.
*You may not be able to see the list icon if your browser window is too small. You can expand the editor menu by clicking on the overflow menu (three vertical dots).
When making links on canvas, link text should be unique within a page. Canvas allows users to make two kinds of links: external links, which lead to web content outside of canvas, and course links, which allow you to link to a variety of course content, pages, quizzes, assignments, and discussions.
When writing captions for tables, avoid generic captions (e.g. “Data Table”). Instead, concisely summarize and contextualize the content. If the table is referred to in the text, assure that the table is consistently being referred to by its caption. You can provide an additional text summary of the table if needed.
Remembering that screen readers will read left to right and top to bottom, choose whether you will have headers across the top or left side of your table (or both). Be sure to set the scope of the header to properly associate the cells with their header(s).
Before leaving the page, click on the accessibility checker icon below the text editor. This will walk you through any issues and how to resolve them.
Using color can help convey information, but many users cannot benefit from the use of color due to visual impairment or color blindness. All users benefit from color contrast that makes information easy to read.
Be specific and concise. Consider the purpose of using the image and the context it is being presented in. Note: Alt text exceeding 120 characters will be flagged by the Accessibility Checker, but there is no hard limit.
Don’t start your description with “An image of…”. The screen reader will tell the user that an image is being described.
For complex images, provide a brief summary and describe the contents more fully in the text.
For icons, describe the purpose of the icon rather than its shape (e.g. Describe the magnifying glass icon for searching as “Search” rather than “magnifying glass”).
Non-English words will be read with the default English pronunciation is they are not marked with the language attribute. For many languages, the result is incomprehensible and inaccessible for students using assistive technology. To see and hear what this looks like, watch the following video demo of a screen reader reading various Asian languages in which the characters are not read correctly without the proper language attribute.
Language issues can be remedied by accessing the HTML layer of the page and updating the language attribute on any non-English text.