Accessibility and UF Health Templates

UF Health templates are designed to meet Level A and Level AA standards set forth by the Web Content Accessibility Guideline (WCAG) 2.0. WCAG 2,0 was developed through the W3C in cooperation with individuals and organizations around the world with the goal of created a shared international standard for accessibility that meets the needs of individuals, organizations, and governments worldwide.

The following list summarizes how our templates meet Level A and Level AA requirements set forth in the WCAG 2.0. For a comprehensive list of the standards, refer to: the WCAG website.


Some of these requirements are hard coded into the template.  Others are available within the template but do require the web content provider to be mindful that certain fields are filled out within the WordPress dashboard. These requirements are indicated with the following tag after the recommendation: [PROVIDER].

Principle 1: Perceivable

Information and user interface components must be presentable to users in ways they can perceive.

  • Alternative and descriptive text is provided for images, input controls, time-based media, forms buttons and CAPTCHA. [PROVIDER]
  • Images that do not include content are rendered as part of the background and hidden from screen readers.
  • Frames are appropriately titled.
  • Descriptive text, captions, or transcripts are provided for pre-recorded and live audio, videos, and podcasts. [PROVIDER]
  • The templates use semantic markup for headings, lists, emphasized text to convey information, structure, and relationships. Instructions do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound.
  • Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
  • Audio controls are provided for any audio on a page that plays for more than 3 seconds [PROVIDER]
  • Text have a contrast ration of 4.5:1; Large text over 18 point has a contrast ratio of at least 3:1
  • The page is functional when the text size is doubled
  • Images are not used to present text. [PROVIDER]

Principle 2: Operable

User interface components and navigation must be operable.

  • All functionality of the web page can be accomplished with the key, unless the function is impossible to perform with a keyboard.
  • The user can navigate to and from all navigable page elements.
  • If a page or application has a time limit, the user is given options to turn off, adjust, or extend the time limit, unless the item in a real-time event or lasts longer than 20 hours.
  • Moving, blinking, or scrolling content that lasts longer than 3 seconds can be paused, stopped or hidden by the user.
  • Automatically updating content can be paused, stopped, or hidden by the user or manually controlled.
  • No page content flashes more than 3 times per second unless the flashing content is of a small size, has low contrast, and does not include red.
  • A link is provided to skip navigation and other repeated web elements that are common from page to page in the web site
  • If the page contains frames the frames are appropriately titled.
  • Pages have descriptive and informative page titles
  • Navigation order of links, form elements, etc. is logical and intuitive.
  • The purpose of each link can be determined by the link text or by the context of the link.
  • Multiple ways are available to find other web pages on the site, including site search and a site map.
  • Page headings and labels for forms and controls are informative and avoid duplication.
  • It is visually apparent which page element is currently focused on using the keyboard

Principle 3: Understandable

Information and the operation of user interface must be understandable.

  • The language of the page is identified in the coding
  • When appropriate, the language of sections of content that are a different language are identified as such in coding
  • When a page element receives focus, or when a user inputs information or interacts with a control, it does not result in a substantial change to the page, the creation of a pop up window, or any change that could confuse or disorient the user unless the user is informed of the change ahead of time.
  • Repeating navigation links are consistent from page to page
  • Common elements across multiple pages are consistently identified.
  • Required form elements or elements that require a specific format, value, or length provide that information in the element’s label or title.
  • Form validation cues are efficient, intuitive, and accessible [PROVIDER]
  • Labels, cues, and instructions are provided for required form elements [PROVIDER]
  • Row and header columns are identified for data tables [PROVIDER]
  • Suggestions for input errors are timely and accessible. 
  • If the user can delete legal, financial, or test data, the changes are reversible, verified, or confirmed.

Principle 4: Robust

Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.

  • HTML/XHTML validation/parsing errors are avoided and specifications are used in order to facilitate accessibility.