Using WAI-ARIA roles

https://www.linkedin.com/learning/html-essential-training-2017/using-wai-aria-roles?autoAdvance=true&autoSkip=true&autoplay=true&resume=false https://www.w3.org/TR/html-aria/ WAI-ARIA stands for Web Accessibility Initiative Accessible Rich Internet Applications. It's a bit of a mouthful, but it's the umbrella name for this specification that's centered on creating accessible sites and applications. As I'm sure you can understand, it's more commonly referred to as ARIA. It allows you to extend the semantic meaning of your html document for screen readers. https://www.w3.org/TR/wai-aria-1.0/roles https://www.w3.org/TR/wai-aria-1.0/roles#landmark_roles Well, when you apply a role attribute to an element, that allows screen readers, assisted devices, and other user agents to quickly scan that page content, and then to navigate to those specific sections when required. So, let's say, for example, that on the page navigation, you give it a roll equals navigation. That allows the screen reader to either jump to the navigation, or skip that navigation very easily, because you've identified that content. So, it's a very important part of the authoring content, because it's going to make your content more accessible to a greater number of users. Banner, for example, is a region that contains mostly site oriented content, it talks about things like logos, identity, site specific search tools. It also talks about how banners should only be used once within a document. In the specification it tells you that if there's an element that passes along the same semantic value, you should use the element and not the attribute. In practice, however, most screen readers now don't yet recognize elements like main. So, for the time being, and for the foreseeable future, it's actually a good idea to apply both of them, semantic HTML elements and ARIA roles to extend the meaning of your content. Articles, for example, can have a role of article. So, now in just a few short moments, we've made our page significantly more accessible than it was before. So, as an author, one of the things that you want to do is get comfortable with these landmark roles and when they're appropriate to use. In addition to the specification that I talked about earlier, there are two other sites that I want to pass along to you. https://www.w3.org/TR/html-aria/ https://www.tpgi.com/using-wai-aria-landmarks-2013/ https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA So, I know this was just sort of a brief introduction into it, but these ARIA roles are definitely worth your time as an author to explore. They offer a tremendous amount of functionality for very little investment on your part. So, as an author, I would encourage you to make them a default part of your authoring process.
Aria and structure data https://www.linkedin.com/learning/html-structured-data/welcome Use aria to extend the semantic meaning of your html document for screen readers. Item type and property https://www.linkedin.com/learning/html5-structure-syntax-and-semantics/using-microdata Click here, say download the brochure instead Say the action Use plain text no jargon