All newly submitted or updated text and audio/visual content (A/V) is required to be accessible. In support of Cornell’s Web Accessibility Policy, we strongly encourage you to consider accessibility in your workflow.
Some general good practices for web accessible documents include:
If MS Word is where you start creating the documents you intend to upload to eCommons, 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:
For information on creating accessible PowerPoint and Excel documents, we recommend:
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).
See Google's guidance, Make your document or presentation more accessible. Use a browser plug-in such as WAVE to check the accessibility of your Google documents.
If you upload audio or video recordings that include spoken language to eCommons, they must be captioned.
If you are not creating captions as part of your production process, eCommons administrators can create machine-generated captions using Cornell's video platform (Kaltura), and embed a player for the captioned recording on the item page. Note that the resulting captions are quite variable in quality, and it may be necessary for you to correct the caption file, which we will provide to you upon request. More help on streaming and captioning is available.
Please notify us of items requiring captioning.
See the W3C's guidance, Plain Text Techniques for WCAG 2.0.
Most software vendors provide online guidance for their products, including how to create web accessible files.
eCommons supports specialized metadata related to web accessibility, which is available to submitters via the online submission interface and batch processes. If you have questions about adding accessibility metadata to your submission(s) or to previously submitted content, please contact the eCommons administrators.