{"id":88218,"date":"2023-07-27T09:00:00","date_gmt":"2023-07-27T14:00:00","guid":{"rendered":"https:\/\/allyant.com\/?p=88218"},"modified":"2026-05-14T09:08:19","modified_gmt":"2026-05-14T14:08:19","slug":"what-is-the-web-accessibility-initiative-whats-its-purpose-what-does-it-do","status":"publish","type":"post","link":"https:\/\/allyant.com\/blog\/what-is-the-web-accessibility-initiative-whats-its-purpose-what-does-it-do\/","title":{"rendered":"What is the Web Accessibility Initiative? What’s Its Purpose, & What Does It Do?"},"content":{"rendered":"\n

The Web Accessibility Initiative (WAI) is a W3C initiative<\/a> that develops standards and other support materials to help people better understand and implement accessibility. The WAI was launched by the W3C, with help from the White House, in 1997. <\/p>\n\n\n\n

The WAI is made up of people from disability organizations, governments, and research labs throughout the world. The WAI\u2019s goal is \u201cto make the Web accessible to people with disabilities,” including users with auditory, cognitive, physical, speech, and visual impairments.<\/p>\n\n\n\n

Web Content Accessibility Guidelines (WCAG)<\/h2>\n\n\n\n

The Web Content Accessibility Guidelines (WCAG) are some of the most notable guidelines published by the WAI. The WCAG guidelines help form the foundation of driving digital accessibility, including much of our work for clients here at Allyant. <\/p>\n\n\n\n

Our digital accessibility auditing team audits websites and mobile apps based on the WCAG 2.1 guideline success criteria to determine how these deficiencies can be resolved to provide an equitable user experience.<\/p>\n\n\n\n

The WCAG is divided into four sections: Perceivable, Operable, Understandable, <\/strong>and Robust. <\/strong><\/p>\n\n\n\n

Perceivable<\/strong> refers to whether multiple senses can process digital content. For example, whether a video has captions would fall into the Perceivable category of the WCAG since people can either listen to what is being said or read the captions to understand what is happening in the video. <\/p>\n\n\n\n

Operable<\/strong> refers to whether users can access content through multiple devices, such as the ability to navigate a website using only a keyboard (rather than having to use a mouse).<\/p>\n\n\n\n

Understandable<\/strong> means that users need to be able to comprehend digital content. An example of this would be whether a website specifies the language. This is especially important when multiple languages are used on a webpage or throughout a website. <\/p>\n\n\n\n

The last WCAG category, Robust<\/strong>, refers to whether various technologies, such as screen readers, can access websites and mobile apps.<\/p>\n\n\n\n

Accessible Rich Internet Applications<\/h2>\n\n\n\n

Accessible Rich Internet Applications (ARIA) is another significant WAI guideline. ARIA is a set of roles and attributes that define ways to make the Internet more accessible to people with disabilities. In particular, ARIA benefits visually impaired and blind users. <\/p>\n\n\n\n

ARIA is used with HTML to provide assistive technologies, such as screen readers, information that is not otherwise available. For instance, ARIA can be used to ensure that screen readers can read error messages on a contact form.<\/p>\n\n\n\n

However, ARIA should only be used when absolutely necessary. <\/strong><\/p>\n\n\n\n

Developers should always use native HTML elements rather than ARIA whenever possible. Native HTML elements have built-in accessibility features that are more straightforward than ARIA elements. <\/p>\n\n\n\n

A WebAIM survey of more than one million home pages found that pages with ARIA averaged 41% more errors than home pages with no ARIA. <\/p>\n\n\n\n

Even though ARIA generally makes Web content more accessible, it can decrease accessibility if misused. Because of this, ARIA should only be used when there is no other alternative. <\/p>\n\n\n\n

Also, native HTML elements generally work better with various types of assistive technology and are more easily maintained by development teams.<\/p>\n\n\n\n

The WAI and Allyant<\/h2>\n\n\n\n

As a digital accessibility vendor, Allyant constantly deals with the WAI and standards or guidelines published under this initiative. Our\u00a0digital accessibility auditing team<\/a>\u00a0is particularly familiar with the WAI and the real-world impacts of not complying for businesses.<\/p>\n\n\n\n

The WAI (and WCAG in particular) provides standards and guidelines we use daily to educate the public on how to drive a more inclusive digital environment through audits of websites and mobile applications, technical design and development articles in our Knowledge Base, and Client Training we offer to design and development teams.<\/p>\n\n\n\n

Alternatively, and perhaps inadvertently, the WAI has also empowered consumers to file digital accessibility lawsuits (which have become increasingly more common), as it provides clear definitions of what is and is not accessible to users with disabilities. <\/p>\n\n\n\n

Please don\u2019t hesitate to contact us<\/a> if you have questions about the WAI or W3C, as we work together to create a more equitable and inclusive world for all.<\/p>\n","protected":false},"excerpt":{"rendered":"

The Web Accessibility Initiative (WAI) is a W3C initiative that develops standards and other support materials to help people better understand and implement accessibility. The WAI was launched by the W3C, with […]<\/p>\n","protected":false},"author":12,"featured_media":88268,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[14],"tags":[66,53,80],"class_list":["post-88218","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-accessibility","tag-accessibility-software","tag-web-accessibility"],"acf":[],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t