• If possible create and share documents in HTML. It is the most accessible, multi-purpose digital format. 
  • Make source documents accessible
  • Structure:
    • Page Title and Description: Make sure the page title and description is clear and labeled as a title.
    • Use Heading Styles
    • Language: Define your site and digital material’s language
    • Use simple language and active voice
    • Do not use fonts that are too fancy, too thick or too thin
    • Use clear fonts such as Verdana, Helvectica and Arial
    • To leave space at the bottom of a page do not use the ENTER key to create space. Use a page break feature to advance to type on the next page.
    • Do not use color as the only method to make information known
    • Watermarks can impact readability and create low contrast
    • Provide a table of contents for long documents
    • Using periods between the letters of an acronym may help screen readers say each letter instead of reading one word. Try to avoid acronyms.
  • Video and Audio:
    • Provide text transcript for non-live audio and for video without sound: speaker's name, all speech content, relevant descriptions of speech
    • Provide synchronized captions for all video, animations and webinars
    • Video should include captions, transcripts and necessary audio descriptions. You can host your video on Youtube or Vimeo and use an accessible player like the one found from AccessibilityOz.
    • Video players should allow the viewer to pause, rewind, change volume, turn on captions and audio descriptions with the mouse or the keyboard only.
    • Videos should not start automatically.
  • Images: Use alternate text for logos, images and charts
  • Color Contrast: The text on the page should stand out against the background. Free color contrast checkers are available at:
  • WebAIM color contrast checker
  • Vision Australia color checker
  • Check My colors
  • Keyboard: All page elements should be accessible without a mouse.
  • Use the built-in accessibility checkers: found in Microsoft Office, Adobe and others. Google docs provides a free add-in Google grackle accessibility checker.
  • reference card for creating PDF files using Microsoft Word
  • Fixing PDFs should be a second choice. Scans are not accessible and Acrobat Pro can prove difficult in creating accessible PDFs.  Mathematical and scientific notation can not currently be made accessible in PDF. Check finished PDFs for accessibility. Always consider providing an HTML version of a document along with the PDF or in place of the PDF.
  • Tables require alt text and defined row headers (In Word select table properties>alt text AND >row>repeat as header row at the top of each page). Avoid using tables for layout.
  •  Links: Use text that describes the destination of a link. A screen reader alerts the user when they encounter a link. Web-Aim Links and Hyperlinks
  • Scientific Notation should be accessible by screen readers and assistive technology. Some Accessible tools are available and assist with creating accessible Math and Notation.

  • Formulas 

    • Use MathML to create formulas
    • Formulas are images with alternative text descriptions if MathML is not an option
  • Social Media - most sites do not offer a level of accessibility that includes everyone so try to place content on a site everyone can access and reference the site.
  • Accessible Design - Axaio
  • Test using Assistive Technology:
  • Free open source screen reader
  • 10 free screen readers
  • Web Testing tools suggested by W3C:
    The W3C Markup Validation Service
    W3C CSS Validation
    W3C Link Checker
    W3C RSS feed checker
    HTML Tidy

    Some others:
    Achecker
    CodeSniffer

Email access@kenyon.edu for help with digital material!