Basic guidelines drawn from W3C and Section 508
References: Section 508 Checklist from WebAIM and Electronic and Information Technology (EIT) Accessibility Compliance
Accessibility Checker: after implementing steps below copy page URL into WAVE Web Accessibility Tool and look for errors in main content area (i.e., note: review alerts also). [errors red and alerts are yellow coded]
- Use ALT tag description for graphics and photographs (i.e., especially for graphics with content information - needs to be entered that reflects the same approach a visual person would use to interact with graphic). See Drupal instructions
- Use descriptive text for hypertext links (“English Festival Society Form” as opposed to “click here”). See Drupal instructions.
- Tables with information require the following: i) caption (i.e., which means a title), ii) summary (i.e., brief description of data), and iii) table header (i.e., labels for columns) in order to be compliant. Here are instructions for creating an accessible table using Drupal.
- When adding headings/subheadings to a web page, implement them in sequential order (i.e., Heading 2, Heading 3, etc.). [Note: begin with Heading 2 on page].
- Avoid using click here for links. Instead use title of page as wording for link.
- Avoid underlining words as this may be mistaken by user for a link. Instead using Bold or Italics to emphasize wording.
- Create a definable contrast between text and background color.
- Convert all Word documents, if possible, to web pages instead of posting directly or converting to pdf's. The exception would be forms (i.e., these will need to be tagged individually using Adobe Acrobat Pro). In Drupal, use the Webform tool to create an equivalent new form.
Here are instructions for using ContentM (CMS) to convert a Word .doc to a web page:
- If a printable version is also needed, add printable version graphic at top of web page, and link this to PDF.
- If an accessible Word or PDF is preferred, follow the instructions on pages 8 and 9 of the Electronic Information Technology (EIT) Accessibility Standards* document.
- Place an asterisk * after each PDF or Word document on web page. Place the asterisk below all content and create a link to the Adobe Acrobat Reader download page. Example: *Requires Adobe Acrobat Reader. [Note: if including both PDF and Word documents, use a double asterisk ** after Word documents and reference link)s) at bottom of page as **Requires Microsoft Word or Word Viewer].
- On pages which consist of several PDF's, place a link at top of page labeled, "Request an accessible document for one or several of the following PDF's," and link this to the department contact's e-mail address. An accessible document (i.e., web page or tagged PDF) will then need to be created and e-mailed back to the requester and linked from web page.. Please consult Creating an Accessible PDF File for more information.
- If posting Excel, Word, PDF, or PowerPoint documents to your website, consult Electronic Information Technology (EIT) Accessibility Standards.* Consult Training Schedule and register for a workshop on making documents accessible.
- When using an IFrame to read in content from another site, insert link to web page into your <iframe></iframe> tags. Also, include link above iFrame. For example: View the content of this inline frame within your browser.
- Use YouTube for uploading video and audio files that will be placed on your website. See Creating a YouTube Video. YouTube has a built in closed caption feature that allows hearing impaired individuals to read words being spoken in the video. [Note: YSU Web Team will set-up YouTube videos on Drupal pages].
- Avoid blinking text or images. See Seizure Disorders for more information.
- Include Text-only link at the top of each web page to an equivalent page with no graphical elements (i.e., Drupal websites already have this included).