Enterprise Web Pages

While PSU websites are typically constructed in an enterprise content management system, departments and groups on campus also use other means of online communication and learning like Wordpress, Google Sites, etc. The following accessibility principles, though tailored to the enterprise environment, are applicable to most web environments.

Synopsis of Accessibility Guidelines

Guidelines adapted from WebAIM's Web Accessibility Principles

Insert/edit image window in Drupal

Provide Appropriate Alt Text

For every non-text element, provide a descriptive text alternative (alt text) that provides an equivalent to the image content. Please refer to WebAIM's Alternative Text web page for more information.

  • Select the image and then right click.
  • Select "Insert/edit image" from the drop-down menu.
  • Type your alt text in the box labeled "Image description."
  • The description should present the content and function of an image.
  • If an image is also a link, the alt text must describe the link’s function.
  • Avoid words like "picture of," "image of," or "link to."
  • Use the fewest number of words necessary.

Ensure that Content Is Clear and Navigable

  • Use only accessible Enterprise templates.
    • Recognize that "Branding Images" do not allow for alt text. Only use templates that include a Branding Image if the image content is solely decorative.
    • Do not use the Home Page Slider. This feature is extremely difficult for screen reader users to navigate.
  • ŸOrganize your content using true headings (e.g., <h1>, <h2>, etc.), numbered lists (e.g., <ol>), and bulleted lists (e.g., <ul>).
    • Rather than creating headings manually by underlining text or changing fonts to bold, use the format drop-down menu to create true headings.
    • Rather than creating lists by typing numbers manually, use the numbered and bulleted list drop-down menus to create true bulleted lists.

Body editing menu in Drupal. Format drop-down menu selected.

Additionally:

  • Do not rely on color alone to convey meaning. Please refer to WebAIM's Visual Disabilities: Color Blindness for more information.
    • The use of color can enhance comprehension, but do not use color alone to convey information. Be especially cautious of red/green color combinations.
    • Make sure that color contrast is strong, especially between text and background.
  • Use the simplest language appropriate for your content.
  • Use empty (white) space to improve readability.
  • Use graphics to supplement text.
  • Check spelling, grammar, and readability.

Provide Headers for Data Tables

Please refer to WebAIM's Creating Accessible Tables: Layout Tables for more information.

  • Identify all data table headers and provide appropriate scope attributes for row and column headers:
    • Highlight the header row (and header column, if applicable), select Table cell properties, and change the "Cell type" to "Header."
  • If appropriate, add a table <caption> for the data table.
    • In Table properties, check the box labeled "Captions."

Table row properties window in Drupal. Table Head is selected from the "Row in table part" drop-down menu.
Table cell properties window in Drupal. Header is selected from the "Cell type" drop-down menu.

Ensure Users can Complete and Submit all Forms and Surveys

Please refer to our guidelines for Forms and Surveys.

Ensure Links Make Sense out of Context

  • Rather than using phrases like "Click here", "Here", "More", "More information", "Read more", and "Continue," name links for their destination. For example, "refer to the Forms and Surveys web page to learn more about creating and including accessible forms and surveys on your website."
  • URL's as link text should usually be avoided, unless the URL is relevant content. If a document or presentation will be distributed in print form, the URL should be included in parentheses following a descriptive link. This allows those accessing the print document the ability to input the URL in their address bar.

Caption Audiovisual Media and Provide Transcripts for Audio Files

Please refer to our guidelines for Audio and Visual Media.

Ensure Accessibility of Non-HTML Content

Please refer to our guidelines for Audio and Visual Media, Documents and Presentations, and Google Applications.