We strive to provide accessible content for the disabled while still providing rich media (images, video, etc.), and typographical representations that go beyond ASCII. In accordance with SJSU's ATI Task Force, the COE webmaster was and is required to provide an accessible web experience for disabled individuals who cannot hear or see or for those that use alternative navigation tools (keyboard only, touch-screens, modified mouse type input devices, etc.).
This is accomplished in several ways:
- Publishing Valid XHTML and CSS code and testing using W3C's Validation tools ( html | css )
By doing this one can try and provide the greatest amount of browser ubiquity and therefore limit the problems one might have viewing or navigating a site.
- Using Standards Based Web Publishing techniques by separating content from presentation using CSS and valid HTML.
Generally this is good practice methodology. By doing this a page can be presented in a raw state and even be viewed with alternative devices, such as a mobile phone, or a text based web browser such as lynx.
- Testing using Hi Software's online and desktop tools such as Cynthia Says
Testing using these tools helps bring to light potential problems with a website, but most of the time a spot check or real person has to validate visibly whether a page is accessible or not. There are many factors for why this has to occur.
- Providing text alternative representations for all images, especially when they themselves contain text
- Providing closed captioning for any media that contains narration or audible information delivery, especially where critical to student success and public interest