Unformatted lists—A reader who is blind will not perceive the visual cues that help a sighted reader understand that a set of items should be considered as a group. When a person who is blind and using a screen reader comes across an accessible list, they will hear something similar to “list, 8 items”. This helps orient the user to the fact that they are entering a list, and how long this list is. If this information is not available, it may be confusing as to why there is a random string of words in the middle of a document (Example: “apple orange banana”). By using either the ordered or unordered list type in Froala, the accessibility reader will be able to identify this as a list.

Table captions—Much like headings serve to organize text, captions function as titles for tables, guiding users through complex information. For users utilizing screen readers, captions are announced, enabling them to understand the table's context and decide its relevance to their needs. Without captions, users might struggle to locate or interpret the purpose of tables, leading to a disjointed and frustrating experience.

Sequential headings—Properly structured headings are crucial for outlining the organization of content, enabling both sighted users and those using assistive technologies to grasp the hierarchy and flow of information. Web browsers, plug-ins, and assistive technologies can use them to provide in-page navigation. Headings should always be designed to be hierarchical in nature, with H1 being at the top (limited to one per page) and H2s nested underneath. In Simple Syllabus we restrict the use of H1 and H2s in documents as these are only available at the template level.

Table headers—Associating table data with headers through the <th> tag allows screen readers to announce these headers, providing context as users navigate through a table. This association is vital for understanding the content within each column, making tables accessible by giving users a clear understanding of the data presented. Without these headers, users are left to interpret tabular data linearly, which can be confusing and inefficient. By adding a table header, context is given to the user on what the values in a particular column are about.

Color contrast—The legibility of text against its background is critical for all users, particularly for those with vision impairments. Ensuring sufficient contrast between text and background colors aids in readability.. To meet WCAG standards a certain ratio is required between the background color and the text on a specific page. For example, yellow text on a light pink background likely would not have enough contrast.

Image alt text—For users who cannot see images, alternative text descriptions play a crucial role in conveying the content and function of images. This descriptive text allows screen readers to verbalize what the image depicts, ensuring content is fully accessible. Images should always have an alternative text description so that users who can't see an image can get a verbal description of what the image encapsulates. The Simple Syllabus accessibility Checker will audit all images in a syllabus for alt text. The alt tag can be assigned to an image by clicking on the image and selecting the "T" icon in the Froala editor.

Empty headings—Empty headings disrupt screen readers and can hinder user understanding of content structure. Headings are crucial for users relying on screen readers to assist with clear navigation through documents.

Heading max length (< 120 characters)—Limiting heading length to 120 characters ensures brevity and clarity, facilitating easier navigation and comprehension for users of screen readers. Concise headings help maintain focus and provide clear, straightforward navigation cues, contributing to a more accessible and user-friendly document structure.