Skip to article frontmatterSkip to article content
Site not loading correctly?

This may be due to an incorrect BASE_URL configuration. See the MyST Documentation for reference.

Here we discuss accessibility best practices when sharing code snippets, Jupyter Notebooks, and MATLAB Live Scripts. We also discuss some considerations for software used in class.

Code Snippets

When sharing code snippets, make sure the code is shared in a plain-text format. Avoid screenshots of code because screen readers cannot read text inside images.

Include comments in the code to explain what the code does and why, and to provide context. This is a good practice not just for accessibility, as it helps students understand the code better.

Jupyter Notebooks and MATLAB Live Scripts

Here’s a checklist to make Jupyter Notebooks and MATLAB Live Scripts accessible:

Software Use in Class

The current requirement focuses on web content and mobile apps, and it does not directly apply to traditional software. If your class uses software that is not web-based or mobile, you are not required to make the software itself accessible under this requirement.

However, the general ADA requirements still apply. Hence, if a student requests an accommodation related to software use through CDA, you should work with the CDA to ensure the student can access the software and participate in class effectively.

If you post any instructions, guides, or other materials (such as code snippets and notebooks) that are related to the use of software on the course website, you do need to ensure those posted materials are accessible, even if the software itself may not be accessible.