throbber
7/19/22, 9:34 AM
`
`History of the Web Content Accessibility Guidelines (WCAG)
`
`Blog › Blog - Digital Accessibility
`
`History of the Web Content Accessibility Guidelines
`(WCAG)
`
`May 6, 2019
`This month, the Web Content Accessibility Guidelines (WCAG) turned 20 years old. WCAG version 1.0 was published on
`May 5, 1999 and was a total game-changer for web accessibility. Today, WCAG version 2.1 is cemented as the gold
`standard in accessibility. So, how did we get here?
`
`Quick history lesson: the Web Content Accessibility Guidelines (WCAG)
`What is WCAG?
`WCAG is a set of specic standards designed to make the web more accessible to people with disabilities. It is on its
`third version, updated over the years to account for changes in web-based digital technology, assistive technology,
`design and development trends, and the growth of the mobile web. It is published by the World Wide Web Consortium
`(W3C) Web Accessibility Initiative (WAI) in collaboration with individuals and organizations within the global
`accessibility community according to the W3C Process.
`
`Why is WCAG so universally accepted?
`WCAG offers an actionable framework for creating or remediating websites and apps to be accessible. It is not
`abstract, but specic and technical, and is supported by documentation that identies methods and techniques that
`would be considered to pass or fail the minimum accessibility expectations of each checkpoint. WCAG is broken into
`four guiding principles, which state that web content must be perceivable, operable, understandable, and robust.
`
`Developed for content creators, content authoring tool developers, accessibility testers and test tool developers, and
`anyone who wants to understand how to make digital experiences accessible, WCAG is used all over the world.
`
`"Rarely does a single document have such a direct impact on people’s lives, but the guidance that WCAG provides
`allows developers and content creators to include people who have historically been excluded from digital experiences,"
`said Mark Shapiro, President of the Bureau of Internet Accessibility.
`
`WCAG timeline
`
`May 5, 1999: WCAG 1.0 is born. It included 14 guidelines, ranging from the need to provide text equivalents to
`considering clarity and simplicity on the web. Each guideline had between one and 10 supporting checkpoints.
`December 11, 2008: WCAG 2.0 broadens scope and offers the four principles. The early 2000s were years of
`unbelievable changes in technology, so WCAG evolved to keep up. WCAG 2.0 was an incredible follow-up to its
`predecessor and was intended to be applied to almost all things digital (including documents and apps). WCAG 2.0
`also introduced the four guiding principles of accessibility, stating content must be perceivable, operable,
`
`https://www.boia.org/blog/history-of-the-web-content-accessibility-guidelines-wcag
`
`1/5
`
`ACCESSIBE LTD EXHIBIT 1024
`Page 1 of 5
`
`

`

`7/19/22, 9:34 AM
`
`History of the Web Content Accessibility Guidelines (WCAG)
`
`understandable, and robust, supported by success criteria for meeting those principles. WCAG 2.0 reigned as the
`gold standard for a long time.
`June 5, 2018: WCAG 2.1 builds on but does not replace WCAG 2.0. The latest version of WCAG is backwards-
`compatible with the previous, which means if you comply with WCAG 2.1, you automatically comply with WCAG
`2.0 — great news for website and app creators. WCAG 2.1 came as a highly-welcomed update, after the decade-old
`WCAG 2.0 could no longer completely account for advancements in technology and web use. The new WCAG 2.1
`standards include several success criteria for improving web accessibility on mobile devices, as well as for people
`with low vision and cognitive disabilities.
`
`Testing according to WCAG
`We believe our comprehensive testing strategy provides the best path to achieving, maintaining, and proving digital
`compliance. Our four-point hybrid testing combines the best of human and articial intelligence. Learn about our four-
`point hybrid testing.
`
`For information on how we apply WCAG to identify the actual accessibility barriers people may face, check out the
`following ve-part series:
`
`Accessibility testing for people with visual disabilities
`Accessibility testing for people with auditory disabilities
`Accessibility testing for people with cognitive, learning, and neurological disabilities
`Accessibility testing for people with physical disabilities
`Accessibility testing for people with speech disabilities
`
`Here to help with all your accessibility needs
`Talk to us to learn how we can customize a unique accessibility strategy to meet your needs. Or, get started with a free
`website accessibility scan.
`
`Search
`
`Subscribe To Blog
`
`Email
`
`SUBSCRIBE
`
`Most Recent
`
`What is ATAG? An Overview of Authoring Tool Accessibility Guidelines
`
`Website Accessibility Isn't All or Nothing: Start Somewhere
`
`What "Programmatically Determined" Means for Accessibility
`
`How Often Should You Test Your Website for Accessibility?
`
`4 Ways to Make Online Logos More Accessible
`
`Categories
`
`Knowing is half the battle (462)
`
`Insider (350)
`
`https://www.boia.org/blog/history-of-the-web-content-accessibility-guidelines-wcag
`
`2/5
`
`ACCESSIBE LTD EXHIBIT 1024
`Page 2 of 5
`
`

`

`7/19/22, 9:34 AM
`
`History of the Web Content Accessibility Guidelines (WCAG)
`
`Accessibility UX (302)
`
`Human Interest (287)
`
`Accessibility Requirements (285)
`
`People with Disabilities (233)
`
`Accessibility Guidelines (214)
`
`Defining Terms (153)
`
`Industry News (104)
`
`Lawsuits & Settlement (93)
`
`ADA Title II&III (84)
`
`Government (84)
`
`Employment (28)
`
`Receive an industry accessibility analysis of your website
`
`www.yourwebsite.com
`
`SUBMIT
`
`RECENT POSTS
`
`https://www.boia.org/blog/history-of-the-web-content-accessibility-guidelines-wcag
`
`3/5
`
`ACCESSIBE LTD EXHIBIT 1024
`Page 3 of 5
`
`

`

`7/19/22, 9:34 AM
`
`History of the Web Content Accessibility Guidelines (WCAG)
`
`
`
`How The HTML Lang Attribute Helps Accessibility
`
`How Do Refreshable Braille Displays Work?
`
`May 17, 2022
`
`Read more
`
`May 5, 2022
`
`Read more
`
`What Is Ableism? Fighting Assumptions About People
`with Disabilities
`
`May 4, 2022
`
`Read more
`
`strip1
`
`Stay current on digital accessibility news weekly by
`subscribing to our blog.
`
`Email
`
`SUBSCRIBE
`
`https://www.boia.org/blog/history-of-the-web-content-accessibility-guidelines-wcag
`
`4/5
`
`ACCESSIBE LTD EXHIBIT 1024
`Page 4 of 5
`
`

`

`7/19/22, 9:34 AM
`
`History of the Web Content Accessibility Guidelines (WCAG)
`
`Not sure where to start?
`
`Start with a free analysis of your website's accessibility.
`
`GET STARTED
`
`Contact Us
`
`Bureau of Internet Accessibility
`5600 Post Road #114-274
`East Greenwich, RI 02818
`
`401-830-0075
`
`contact@boia.org
`
`Get In Touch
`
`First Name*
`
`Email*
`
`Your Message*
`
`SUBMIT NOW
`
`Last Name*
`
`Phone*
`
`
`
`
`
`
`
`
`
`Accessibility Statement
`
`| Privacy Policy | Terms of Services
`
`Copyright 2021 Bureau of Internet Accessibility, Inc. All rights reserved.
`
`https://www.boia.org/blog/history-of-the-web-content-accessibility-guidelines-wcag
`
`5/5
`
`ACCESSIBE LTD EXHIBIT 1024
`Page 5 of 5
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket