1 / 10

V. Beyond HTML: CSS, JavaScript, Plug-ins

V. Beyond HTML: CSS, JavaScript, Plug-ins. A Web Accessibility Primer: Usability for Everyone Office of Web Communications. Cascading Style Sheets (CSS). CSS separates page appearance from page structure and content. Advantages: Don’t have to code each bit of formatting separately

job
Download Presentation

V. Beyond HTML: CSS, JavaScript, Plug-ins

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. V. Beyond HTML: CSS, JavaScript, Plug-ins A Web Accessibility Primer: Usability for Everyone Office of Web Communications

  2. Cascading Style Sheets (CSS) • CSS separates page appearance from page structure and content. Advantages: • Don’t have to code each bit of formatting separately • Users can turn off your style and use their own instead • Not hard to learn. CIT offers training.

  3. JavaScript – barriers • Can create barriers by: • requiring mouse navigation • hiding content from assistive technologies • reducing user control • disorienting users

  4. JavaScript – guidelines • Stay keyboard accessible. • Make content and function available to assistive technologies (e.g., enlarging, screen readers) • Don’t override normal browser functionality. • Provide accessible alternatives when your scripts are not accessible.

  5. Plug-ins • Plug-in itself should work with assistive technologies. • Your content must be accessible. E.g. synchronous captions and a transcript for a video. • Don’t make key functions (e.g., navigation) dependent on a plug-in. • Provide link to where users can download plug-in.

  6. VI. CommonSpot and BlackBoard A Web Accessibility Primer: Usability for Everyone Office of Web Communications

  7. CommonSpot • Author mode not accessible. But authored pages can be made accessible. • Turn on accessibility modes in author mode. • Make sure any downloadable files (e.g., PowerPoints, PDFs) are accessible.

  8. BlackBoard • Not as accessible as it could be. Other options are under review. • In the meantime, make sure any downloadable files you create (e.g., PowerPoints, PDFs) are accessible. • If BlackBoard won’t meet your students’ needs, consider using Cornell’s course site service to create your own site instead.

  9. VII. File Types: Choosing and Converting A Web Accessibility Primer: Usability for Everyone Office of Web Communications

  10. Choosing and Converting File Types • No magic bullet, no one right answer. • Consider your audience needs, your skills, your content, your budget. • Consider providing more than one option (e.g., PDF and HTML version) • Use accessible conversion tool to make Microsoft Office files available as accessible HTML.

More Related