WCAG Principles and Guidelines

Web Content Accessibility Guidelines (WCAG) 2.0 are organized into four Principles with supporting Guidelines. Some Principles and Guidelines are more relevant to specific roles.

The following is a summary of WCAG 2.0 AA Principles and Guidelines.


    • Does video have captions and does audio have a transcript?
    • Does the web page or document include headings, lists, and other semantic elements to communicate document structure?
    • Is the tab order and read order logical and intuitive?
    • Do form fields within web pages and documents have appropriately coded labels and prompts?
    • Have you avoided using visual characteristics to communicate information (e.g., “click the circle on the right” or “required fields are in red”)?
    • Does the interface have sufficient contrast between text color and background color?
    • Does the content scale well when page is zoomed?


    • Can all menus, links, buttons, and other controls be operated by keyboard, to make them accessible to users who are unable to use a mouse?
    • Does the web page include a visible focus indicator so all users, especially those using a keyboard, can easily track their current position?
    • Does your site have a slideshow? If so, please reconsider.
    • Do features that scroll or update automatically (e.g., slideshows, carousels) have prominent accessible controls that enable users to pause or advance these features on their own?
    • Do pages that have time limits include mechanisms for adjusting those limits for users who need more time?
    • Have you avoided using content that flashes or flickers?
    • Does the web page or document have a title that describes its topic or purpose?
    • Are mechanisms in place that allow users to bypass blocks of content (e.g., a “skip to main content” link on a web page or bookmarks in a PDF)?
    • Does the website include two or more ways of finding content, such as a navigation menu, search feature, or site map?
    • Is link text meaningful, independent of context?


    • Has the language of the web page or document been defined?
    • Have you avoided links, controls, or form fields that automatically trigger a change in context?
    • Does the website include consistent and persistent navigation?
    • Do online forms provide helpful, accessible error and verification messages?


    • Is the web page coded using valid HTML?
    • Do rich, dynamic, web interfaces, such as modal windows, drop-down menus, slideshows, and carousels, include ARIA markup?