Life Time Accessibility Checklist
Life Time Fitness has agreed to be Level AA compliant with the addition of a few AAA requirements. To be AA compliant, a webpage must satisfy all of the level A and AA success criteria.
This checklist is intended to be a guide, but not a replacement for fully understanding or validating all of the criteria associated with each requirement. Items listed under each guideline are a combination of best practices, resources and documentation from W3C. If you’re not sure how to satisfy a guideline, follow the “Understanding …“ links within each section.
Perceivable
Create content and components that can be consumed and be used in multiple ways.
All non-text content has alternate ways of being consumed
For time-based media (audio and video), users are provided alternative ways to obtain the content
The information is presented in a meaningful order with clear relationships and structure
Content can easily been seen and heard
Operable
User interface components and navigation must be operable.
All functionality can be done from a keyboard
- Users should be able to navigate to, and interact with the content via a keyboard in a similar way as sighted users with a mouse
- Avoid creating keyboard traps that prevent a user from traversing the content
- Understanding Guideline 2.1
Users have enough time to read and use content
- Users should be able to complete a task without unexpected changes in content or context that are a result of a time limit
- Understanding Guideline 2.2
Content does not flash in a way that could cause seizures
Users can effectively navigate and find content while understanding where they are within the content
- Provide skip links to bypass blocks of content that are repeated on multiple pages (e.g. header navigation)
- Use descriptive page titles
- Headings and labels should describe topic or purpose
- Focus order should preserve meaning and context
- Focused elements should have a visible indication that they are focused
- Link purpose should be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general
- Separate content from presentation and behavior
- Use correct structural and text semantics
- Avoid choosing semantics based on how the element appears in the browser
- Leverage ARIA to add additional semantic value
- Understanding Guideline 2.4
Understandable
Information and the operation of user interface must be understandable.
Text content is readable and understandable
- Use plain language
- Provide clear calls to action
- Be careful when referencing content based on position in layout
- Understanding Guideline 3.1
Web pages and the content within have predictable behaviors and consistency between similar pages
- Do not change context on focus
- Use navigation in consistent ways across pages
- Components that have the same functionality within a set of Web pages are identified consistently
- Understanding Guideline 3.2
It is clear to users when they make mistakes and how to correct them
- Items in error should be identidied and the error described in text
- Provide labels and instructions when content requires input
- Provide suggestions for error correction unless it would jeopardize security or content purpose
- Legal and financial submissions should be reversible, checked and confirmed
- Understanding Guideline 3.3
Robust
Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
Compatibility with current and future user agents has been maximized
- For content implemented with markup languages:
- Elements have complete start and end tags
- Elements are nested correctly
- Elements do not contain duplicate attributes
- Use unique IDs (except where specifications allow)
- Name, role and value:
- Name and role can be programmatically determined
- States, properties, and values that can be set by the user can be programmatically set
- Notification of changes to these items is available to user agents, including assistive technologies
- Understanding Guideline 4.1