Web Accessibility Guidelines for Developers
Breadcrumb
- RIT/
- Brand Portal/
- University Web Standards/
- Web Accessibility Guidelines for Developers
RIT strives to achieve WCAG level AA compliance throughout the university’s official web presence. According to the World Wide Web Consortium (W3C), Web Content Accessibility Guidelines (WCAG) 2.1 defines how to make web content more accessible to people with disabilities, including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities.
These webpages will help developers follow these accessibility guidelines. WCAG 2.1 is broken down into 4 principles.
Principle 1 - Perceivable
Information and user interface components must be presentable to users in ways they can perceive.
This principle is broken into 4 guidelines:
- Guideline 1.1 – Text Alternatives
Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language. - Guideline 1.2 – Time-based Media
Provide alternatives for time-based media. - Guideline 1.3 – Adaptable
Create content that can be presented in different ways (for example, simpler layout) without losing information or structure. - Guideline 1.4 – Distinguishable
Make it easier for users to see and hear content including separating foreground from background.
Principle 2 - Operable
User interface components and navigation must be operable.
This principle is broken into 5 guidelines:
- Guideline 2.1 – Keyboard Accessible
Make all functionality available from a keyboard. - Guideline 2.2 – Enough Time
Provide users enough time to read and use content. - Guideline 2.3 – Seizures and Physical Reactions
Do not design content in a way that is known to cause seizures. - Guideline 2.4 – Navigable
Provide ways to help users navigate, find content, and determine where they are. - Guideline 2.5 – Input Modalities
Make it easier for users to operate functionality through various inputs beyond keyboard.
Principle 3 - Understandable
Information and the operation of the user interface must be understandable.
This principle is broken into 3 guidelines:
- Guideline 3.1 – Readable
Make text content readable and understandable. - Guideline 3.2 – Predictable
Make Web pages appear and operate in predictable ways. - Guideline 3.3 – Input Assistance
Help users avoid and correct mistakes.