You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Web accessibility is a requirement for all newly published content.

General good practices for ensuring web accessible content

  • Specifying the title and language of the document
  • Using proper headings, structure or tags (terminology varies by software), and not using formatting (e.g. font size and color) to convey document organization and structure
  • Including alternate text for embedded images
  • Using text for textual content, not images of text
  • Creating properly formatted lists and tables (e.g. using Word's tools to create lists and tables, rather than using tabs and spaces to position content)
  • Selecting color combinations with sufficient contrast
  • Not using color to convey meaning.

Microsoft Word documents

If MS-Word is your starting point, make sure the end result is accessible by using Word's built-in Check Accessibility tool, available on the Review tab.

For more information on creating accessible Word documents, please see:

PDF documents

WebAIM provides a very good overview of PDF Accessibility. WebAIM also has specific instructions for preserving accessibility features when converting Word documents to PDF. Many additional resources are available from IT@Cornell.

If you have access to it, use Adobe Acrobat Pro to run a Full Accessibility check on your document, before you upload it to eCommons. Make sure it passes without errors. Some items require human inspection, in addition to using Acrobat's checker.

If you do not have access to Acrobat Pro, a free option for checking accessibility is PAVE - Validate and Fix PDF Accessibility (maximum file size: 5MB).

  • No labels