Web Accessibility

The organization Wed Accessibility In Mind (Web AIM) has a lot of resources and information on website accessibility (click on this sentence to see their website).

This website is run by WordPress. I am doing my best to make it as accessible as possible. This is a learning experience for me, and I want to see what is possible with this platform for someone who is only slightly “tech savvy.” I welcome comments on how this site, and others like it, can be made more inclusive.

A few things I have tried to do here:

-Sans serif

My department has many debates about this, mainly because on of our masters students is now in design school and thinks we are all pompous for loving serifs (those little lines on letters) so much. As historical and impressive as they make look, fonts with serifs (like Times New Roman) are more difficult for people to read. Fonts without (SANS) serifs (like Arial) are easier to read.

-No information conveyed through typeface, color, etc.

-Images carry explanations of what the image is

-Hyperlinks are explained

-When PDFs are posted, they are accessible. More on what this means is at this link on PDF Accessibility Overview. Currently, in order to make it so that a PDF is screen-reader friendly and has all of these great features, you neeed Adobe Pro. If you are posting PDFs for a course or as any part of a university project, it is incumbent upon your institution to make these PDFs accessible and you should not have to pay for it out of pocket. Keep in mind that if you are scanning a chapter from a physical book, the scan will not be accessible until you run it through Scan & OCR. Sadly, accessible PDFs are not born–they are made.