Xavier University aims to meet or exceed the WCAG 2.0 AA standard for Website Accessibility. More on Xavier's stance can be found on our Website Accessibility web page.

For more information regarding tutorials and decision trees, visit Web Accessibility Tutorials. Please note that this is only one site and one interpretation of the WCAG2.0 rules.

Images

  • Alt tags are automatically loaded as alt="" thanks to the image editor. This satisfies the minimum requirement.
  • Images containing text should ALWAYS contain an alt attribute describing the item.
  • Images that are links should always have an alt attribute describing the image content, NOT the link as that is available elsewhere in the page.
  • Decorative images should maintain an alt=""
    • These include: visual stylings, supplementary to link text to improve appearance; illustration of adjacent text but not contributing information; identified and described by surrounding text.
  • Never use duplicate alternative texts on a page.
  • Additional examples
  • Decision tree

Tables

Tables should only be used to organize data into a logical relationship grid and SHOULD NOT be used to position elements on a web page. Accessible tables need HTML that indicates header cells and data cells and defines their relationship.

To make tables accessible, we have provided examples to outline how they should be used:

Examples of properly formatted tables.


Forms

All forms should be handled by Form Manager and are designed to meet WCAG 2.0 Standards. Forms not managed by Form Manager may not meet this requirement and should be reevaluated with assistances from the Marketing and Communications Web Team.

When forms are created using Form Manager, please make sure every item (text box, select menu, etc) has a title.


Carousels (V4 Rotator)

The V4 Rotator has been designed with Accessibility in mind, however rotators are not the most accessible way to display images and alternative methods should be considered.

Other image rotators being used on the Xavier.edu website should be reevaluated and inclusion of the V4 rotator should be considered.


Page Structure

Page Sections

  • Banded pages are laid out in a manner defining the various bands or sections utilizing the html5 section attribute
  • CMS pages are defined using role="main" for the main content accessible by the WYSIWIG editor.

Headings

  • h1 tags are managed on CMS generated pages in the breadcrumb section of the header. No other h1 headings should exist on a page.
  • When utilizing layout templates, the larger area of the template should typically use h2 class="subheader" or h3 class="subheader". The sidebar (or smaller) area should utilize h4 class="subheader" or h5 class="subheader". All of these styles are located in the styles dropdown of the editor toolbar.
  • Under no circumstance should headings be used for multiple line content areas. We understand some headings may wrap to a new line, use p tags to wrap copy.

Content Structure

Aside from Headings, there are many ways to structure HTML content

  • Paragraphs: Automatically added by the WYSIWIG editor, this provides consistent styling line to line. Separate content by a normal return instead of a hard break (shift+return). Do not be afraid of whitespace, this makes the text more readable and provides much more natural reading breaks for screen readers.
  • Lists: If you have a simple set of instructions or grouped content utilize the Ordered <ol>or Unordered lists <ul> available to you.
    • Ordered Lists: If content has instructions or information performed in sequence. Typically a numbered list
    • Unordered List: Order does not matter and is marked with a bullet.
    • Nested Lists: A nested list provides information that is easy to digest information and can easily display necessary steps to assistive technology. This list is an example of a nested unordered list.
  • Quotes: For longer quotes you wish to highlight, utilize the blockquote element. It may contain paragraphs, headings and other text structure elements. We've also provided a footer element for attaching the quote's author. This item is available through the editor toolbar.
    • For shorter or inline quotes use the q tag or just simple double quotes around your content

Blockquote Example

Blockquote Code example

<blockquote>
  <P&Gt;I am a blockquote, I can be added to your content using the double quote button in the editor.</P&Gt;
  <footer>Blockquote Author</footer>
</blockquote>
               

Display example

I am a blockquote, I can be added to your content using the double quote button in the editor.

Blockquote Author
  • Styling: Accepted styles have been added to the CMS WYSIWIG editor in the styles and markup dropdowns inside of the editor. New styles may be added and old styles may be retired as the site develops. All styles are supplied by Marketing and Communications to follow the Xavier Brand.
  • Underline:
    • If the text is not a link, DO NOT underline it using the editor button (next to bold and italics). Instead, use the styles dropdown to underline your text.
    • Text links should ALWAYS be underlined.
  • Strike:
    • Striking out content provides no value to users. Simply remove the content you intend to strike and update the page accordingly.