The Web Content Accessibility Guidelines (WCAG), developed by the Worldwide Web Consortium (W3C), provide an international set of guidelines which form the basis of most web accessibility laws in the world.
Available to the senses (vision and hearing primarily) either through the browser or through assistive technologies.
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
Time-based media: Provide alternatives for time-based media
Adaptable: Create content that can be presented in different ways
Distinguishable: Make it easier for users to see and hear content including separating foreground from background
Users can interact with all controls and interactive elements using either the mouse, keyboard, or an assistive device.
Keyboard accessible: Make all functionality available from a keyboard
Enough time: Provide users enough time to read and use content, no timing, interruptions can be postponed or suppressed by the user except interruptions involving an emergency, when an authenticated session expires, the user can continue the activity without loss of data after re-authenticating
Seizures: Do not design content in a way that is known to cause seizures, nothing that flashes more than three times in any one second period
Navigable: Provide ways to help users navigate, find content, and determine where they are, bypass blocks, page titles, focus order, link purpose from text alone, breadcrumbs
Content is clear and limits confusion and ambiguity.
Readable: Make text content readable and understandable, identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon, abbreviations, difficult pronunciations
Predictable: Make Web pages appear and operate in predictable ways, consistent navigation, consistent identification
Input assistance: Help users avoid and correct mistakes, error prevention – reversible, checked, confirmed
A wide range of technologies can access the content.
Compatible: Maximize compatibility with current and future user agents, including assistive technologies. Elements have complete start and end tags, no duplicate attributes, IDs are unique. For all UI components, the name and role can be programmatically determined
Most accessibility principles can be implemented very easily and will not impact the overall "look and feel" of a web site.
Use a for attribute on the
label element linked to the id attribute of the form element, or
using WAI-ARIA attributes. In specific situations, it may be acceptable to hide
elements visually, but in most cases labels are needed to help all readers understand the required
Ensure that alternative text for images is added to all informational and functional images. Use empty alternative text, alt="" for decorative images, or include them in the CSS instead. Text alternatives are usually provided by those responsible for written content.
Indicate the primary language of every page by using the lang attribute in the html tag, for example
html lang="en". Use the lang attribute on specific elements when the language of the
element differs from the rest of the page.
Use appropriate mark-up for headings, lists, tables, etc. HTML5 provides additional elements, such as
aside, to better structure your content.
WAI-ARIA roles can provide additional meaning, for example, using role="search" to identify search functionality.
Provide clear instructions, error messages, and notifications to help users complete forms on your site. When an error occurs:
Be as forgiving of format as possible when processing user input. For example, accept phone numbers that include spaces and delete the spaces as needed.
Ensure that the order of elements in the code matches the logical order of the information presented. One way to check this is to remove CSS styling and review that the order of the content makes sense.
Use responsive design to adapt the display to different zoom states and viewport sizes, such as on mobile devices and tablets. When font size is increased by at least 200%, avoid horizontal scrolling and prevent any clipping of content. Use progressive enhancement to help ensure that core functionality and content is available regardless of technology being used.
Use WAI-ARIA to provide information on function and state for custom widgets, such as accordions and custom-made buttons. For example, role="navigation" and aria-expanded="true". Additional code is required to implement the behavior of such widgets, such as expanding and collapsing content or how the widget responds to keyboard events.
Think about keyboard access, especially when developing interactive elements, such as menus, mouseover
information, collapsable accordions, or media players. Use tabindex="0" to add an element that does not
normally receive focus, such as
span, into the navigation order when it
is being used for interaction. Use scripting to capture and respond to keyboard events.
CAPTCHAs create problems for many people. There are other means of verifying that user input was generated by a human that are easier to use, such as automatic detection or interface interactions. If CAPTCHA really needs to be included, ensure that it is simple to understand and includes alternatives for users with disabilities, such as:
Having troubles with the guide? Please give us more details and we'll get back to you soon.Chat with the team