In part three of this series on Making Learning Accessible, we take a look at what you need to do to make your web content accessible. Today’s post focuses on the tools used for content delivery and what to do if you’re not a software/web developer.
Do you manage your own content through someone else’s software?Awesome, start with UC Berkely’s ten tips on web accessibility here. Your goal is two-fold:
How do I make sure my software is accessible?First, ask. Check with your helpdesk, IT team, site administrator, or the vendor to see if the software meets Section 508 accessibility requirements. If you are the Site Administrator, see if your vendor has a Voluntary Product Accessibility Template (VPAT) completed for the release of the software you use. The VPAT requires the vendor to explain what parts of the software don’t meet Section 508 requirements, what workarounds exist, and if they are working on a fix.
If you can’t get a clear answer, you can do some testing on your own. There are tons of free resources and tools out there to help. A good place to start is to run an accessibility scan of your site. There are lots of free accessibility scanners available that will give results for free like this open source accessibility scanner. You input your URL, run the scan and will receive a report with any issues that can be corrected technically. Some of the items the scan will check for include:
Hi, I'm Root a student at United Theological Seminary training to be an Interreligious Chaplain.