Simply defined as Website Accessibility Guidelines, WCAG 3.0 was published on 1/21/2020 and brings new changes over 2.2 for users with disabilities. Why do these changes matter and why should your website take WCAG into account? Here are a few points to consider and implement to comply with these new standards.
Who and what do these guidelines affect?
Users defined as having blindness, low vision or vision impairments, deafness or hearing loss, speech and cognitive learning disabilities, or physical limitations. These guidelines affect web content on laptops, desktops, wearables, mobile devices, and other devices. Content included is static and interactive, augmented reality, visual and auditory media. The guidelines also affect the web tools, browsers, content management and testing tools as well.
Goals of WCAG 3.0
The primary goal of WCAG is to improve accessibility for the previously defined set of users for Web XR, or augmented, virtual and emerging technologies to coincide with normalized usage from other groups.It also seeks to maintain the level of usability over time as these technologies naturally evolve in utility and usage. Additional applications are Web, ePub, PDF, and mobile apps.
Ease of use
WCAG also seeks to increase the usage of all emerging technologies creation by beginner and advanced users thereby creating uniform accessibility for digital products. This tenant allows for higher adoption rates and uniformity.
.png?width=431&name=download%20(2).png)
These changes are considered a best practice set for any website, mobile app, or other previously defined medium similar to A.D.A requirements. To view the entire abstract click here, and for additional information as it relates to web, VR, mobile, or app builds, contact On-Target for more help and more information on compliance. If you still have questions, try this resource.
