SC 1.3.1 Info and Relationships (Level A)

Content should be structured semantically. This section seemingly has a heading to describe the section's meaning; however, it wasn't formatted as a heading and so there's no semantic relationship between the heading and body text. As a consequence, screen reader users might not be able to access this content because they don't see its heading listed while navigating by headings.

In general, the visual cues made available to sighted users should also be available to visually impaired ones. This paragraph succeeds the previous one and is visually separated by a blank line. To screen readers, this separation should be conveyed through the use of separate paragraphs (automatically done by the rich text editor when pressing Enter) rather than entering line breaks by pressing Shift+Enter.

The rich text editor avoids a lot of problems for content editors automatically as it inserts semantically-appropriate HTML tags for bold and italic formatting, unordered and ordered lists, links, paragraphs, headings, etc.

SC 1.3.3 Sensory Characteristics (Level A)

Consider the following instruction:

To save an article, press the button on the left hand side

Following it requires a sensory ability: being able to perceive spacial location in this case. Instead, in case of referring to interactive element like a link or button, make use of the element's accessible name. In the rich text editor, the button on the left hand side would be the "Save" button.

SC 1.4.1 Use of Color (Level A)

Information shouldn't be conveyed by color alone. Consider the following list of mushrooms and the accompanying legend identifying some entries on the list as poisonous:

  • Amanita virosa
  • Boletus edulis
  • Collybia nuda

Legend: red = poisonous; green = edible

Without being able to perceive color, important information isn't accessible.

For content authored via the rich text editor, this kind of problem can't occur provided the regular user interface is used and colors aren't added manually like I did for the sake of this example via the "Source" view.

SC 1.4.5 Images of Text (Level A)

Text should be presented as actual text rather than in image form.

image

Text that's part of an image is often partially inaccessible, or fully, if there's no text alternative. For example, settings like increasing or decreasing the browser's default font size don't directly apply to images.

SC 2.4.2 Page Titled (Level A)

A page must have a meaningful title describing the content. A title in this context refers to the information displayed in the browser tab.

For editorial content, the title of an article, recipe, etc. will be used to set the page title. The name of the website (e.g. "Dole") is commonly included to make identifying the tab easier. This is done automatically.

Links should identify their purpose through the link text.

A link with the text click here doesn't do that.

This makes navigation by links harder for screen reader users, especially if multiple elements on the page use the same insufficient link text.

A good link text sets expectations for what the user can expect once they navigated to the link's target. On WCAG 2.2's Understanding Docs for SC 2.4.4 Link Purpose (In Context), you can learn more details.

SC 2.4.6 Headings and Labels (Level AA)

Screen reader users can get a sense of a page's contents by accessing lists of landmarks, headings, form controls, and links. These lists are both informative with regards to what a page contains and also very commonly used to navigate around a page. This makes it important to use headings to describe sections of content and to clearly label interactive elements to describe their purpose.

SC 3.1.2 Language of Parts (Level AA)

Text content in a different language that isn't marked as such with the "lang" attribute will be announced in the document language.

  • without "lang" attribute:

    Eine Liste von giftigen und essbaren Pilzen.

  • with "lang" attribute set to "de":

    Eine Liste von giftigen und essbaren Pilzen.

(Unfortunately, the rich text editor does not currently provide means to set the "lang" attribute on content)