Workshop accessibility category: Perceivable

[wes-brooks]

WCAG guidelines in this category:

• Provide text alternatives for non-text content.
• Provide captions and other alternatives for multimedia.
• Create content that can be presented in different ways, including by assistive technologies, without losing meaning.
• Make it easier for users to see and hear content.

[wes-brooks]

Items to address in this category:

• Images with no alternative text description
• Text tables are hard to read and generally don't offer an alternative text description
• Inline math with MathJax takes focus when tabbing through controls
• Color blind friendly formatting
• Caption, axis, and label text must be large enough to see

[wes-brooks]

It seems that the <pre> elements used for text output from a code chunk can accept ARIA labels and descriptions that will be read by screen readers. Here are the options:

• Use aria-label You can add an aria-label attribute to provide a concise, descriptive label for the <pre> element.
• Use aria-labelledby If there is a visible label or heading associated with the <pre> element, you can link it using aria-labelledby.
• Use aria-describedby For more detailed descriptions, you can provide additional context using aria-describedby.