Guidelines, Standards & Laws

This article demonstrates a technique for preventing focused elements from being obscured by sticky headers or footers.

Describes how the Web Content Accessibility Guidelines (WCAG) can be applied to non-web information and communications technologies (ICT), including documents and software.

Explore the European Accessibility Act and its impact on the private sector.

An explaination of the European Accessibility Act: Article 32.

Discover the essential steps to achieve ADA compliance with our comprehensive guide, featuring expert tips and best practices from Nolan Klein

The U.S. Access Board is a federal agency that promotes equality for people with disabilities through leadership in accessible design and the development of accessibility guidelines and standards for the built environment, transportation, communication, medical diagnostic equipment, and information technology.

Accessible Rich Internet Applications (ARIA) is a set of roles and attributes that define ways to make web content and web applications (especially those developed with JavaScript) more accessible to people with disabilities.

Josh explains WCAG Article 1.1.1 Tools and info to get your website accessible and WCAG Compliant: http://OnlineADA.com Unlock the WCAG walkthroughs for level AA compliance, get accessibility web development training, and additional tools training in the Accessibility Academy: https://onlineada.com/academy/ Are you a digital agency? Join our Partner Agency Program! https://onlineada.com/partners/ Online ADA Advancing Digital Accessibility Transcript Below: Hey everybody! Josh here with Online ADA and in this video we're gonna cover WCAG article 1.1.1 of the WCAG accessibility guidelines. So what is WCAG 1.1.1? This is the alt text. It says non text content this is for level A compliance the actual documentation for this article reads "All non text content that is presented to the user has a text alternative that serves the equivalent purpose, except for situations listed below. Controls and input. If non text content is a control or accepts user input and it has a name that describes his purpose". This is in reference to form inputs, buttons on forms, first name, last name, email address. All of those forms. Those are gonna be inputs that require something from the user and they need to have labels and they need to have instructions that would comply with the alt text requirement. Time based media. These are gonna be things like your videos or audio tracks or animations, even carousels. Things that are playing that are animated or moving that a non visual user may have difficulty with when they visit your site. They need to have some sort of text alternative. Let's read that one. If non text content is time based media, then text alternatives at least provide descriptive identification of the non text content. Now this is saying that you don't necessarily have to have a text dictation of everything that's happening on that screen or in that animated element, but you have to have a descriptive identification of it so, you know they are tabbing through with their screen reader they come across that maybe isn't explaining everything that's happening in the animation but it's going to say this is an animation of 'insert description here'. Test. Test is literally what it sounds like if you are taking, like for a college exam or some sort of school related activity, Test is going to be an actual test that happens on the website. So if non text content is a test or exercise that would be invalid if presented in text, than text alternatives at least provide descriptive identification of the non text content. Most tests that you have on a website are probably gonna be like the radio buttons yes/no, a) b) c) d), something like that. So that is text content. This would be a situation where the test was presented in maybe like a video format or if there was, I can think of, software that might be teaching you how to speak Spanish or something and you have to speak into a microphone. That would be sort of the situation where you actually start to have a description of what is required for a non visual user. Sensory. I personally have not ever run into this one myself but it reads, "If non text content is primarily intended to create a specific sensory experience, than text alternatives at least provide descriptive identification of the non text content". Same story, you have that can't really be dictated or described perfectly you have to just give a description of an overview of what the content is to the user. CAPTCHA. This one happens all the time. Forms have these, you know anytime you have to sign up for newsletter. These are for avoiding spam and they are to make sure that you are a human that is submitting the form and not a robot or a spammer. It reads, "If the purpose of non text content is to confirm the content is being accessed by a person rather than a computer, than text alternatives that identify and describe the purpose of the non text content are provided and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities". Now that's a big one. I run into a lot of times on a forms where you only have like a check box or you have something where you have to pick all the storefronts out of a bunch of like a grid of squares. Those are great and they definitely provide their purpose to visual users, but somebody who's hard of seeing may have difficulty seeing those storefronts in the pictures. So this is saying that we need to have some way of switching that over to like an audio test. Or from the checking the store fronts to a check box or something like that. Some alternative that is text based that a non visual user can use as well. The next one and the last one on this list is decoration, formatting, invisible. "If non text content is pure decoration, is used only for visual formatting...

This is the United Nations Treaty Collection homepage. Here you will find related information and links.

Let’s review the Web Content Accessibility Guidelines (WCAG) four principles of web accessibility and digital accessibility-related laws in the U.K.

Presentations given for the Publishing@W3C September 2021 Seminar https://www.w3.org/2021/09/publishing-seminar/

First Published as part of European Accessibility Leadership Review, March 2020Version 3.0 of the Web Content Accessibility Guidelines (WCAG) are due for publication but what can you expect and how

W3C Accessibility Guidelines (WCAG) 3.0 will provide a wide range of recommendations for making web content more accessible to users with disabilities. Following these guidelines will address many of the needs of users with blindness, low vision and other vision impairments; deafness and hearing loss; limited movement and dexterity; speech disabilities; sensory disorders; cognitive and learning disabilities; and combinations of these. These guidelines address accessibility of web content on desktops, laptops, tablets, mobile devices, wearable devices, and other web of things devices. The guidelines apply to various types of web content including static, dynamic, interactive, and streaming content; visual and auditory media; virtual and augmented reality; and alternative access presentation and control. These guidelines also address related web tools such as user agents (browsers and assistive technologies), content management systems, authoring tools, and testing tools.

In this post, we look at the WAI ARIA roles to make your website more accessible to users of all abilities and disabilities.

Accessibility is critical, but it can be confusing. Kasey Bonafacio will demystify the 13 WCAG guidelines and show examples of each guideline in action, empo...

If you enjoyed this video, take a look at my WCAG course to become a web accessibility expert: https://myaccessible.website/accessibility-expert-------------...

What is new in WCAG 2.1 Label in Name.

By Genevieve Nelson | Originally posted at www.c2experience.com