Let's have a look at a website that's using something like more. There are a lot of teasers that should get your interest, so you'll click on the link and read the whole article. What’s important here is that you should write clear copy instead of using aria-label as some sort of crutch. In this example we'll see and hear how VoiceOver is handling such an enhanced link.Įspecially ChromeVox shows us that the aria-label will overrule any “native” text or hint.
Key signature change aria maestosa how to#
This video shows how to give a "stupid" link more meaning by adding an aria-label. Now we extend the button with an aria-label: But screen readers have difficulties in identifying the purpose of this button. Click on it and a menu is likely to appear. All sighted persons (who are familiar with this vocabulary) will identify this as a hamburger button. With the class selector “menu-burger” we’ll apply a SVG with three lines, maybe a border and a light-grey background. Let’s assume you’re using a hamburger menu without a descriptive text. In this case we could use the aria-label attribute. There are cases where you don’t have an extra element that can function as a label. In the case of the element we’ll use the element to describe what the is about. They can create a logic connection between an element and its description. Currently there are 22 attributes you can use. In this chapter we’ll have a look at some ARIA attributes. By the way - you already came across some ARIA when we were talking about landmarks and roles. Especially when it comes to the interaction between good ol’ markup and JavaScript. But sometimes our markup isn’t enough on its own. Let’s stick with ARIA…Īs the previous examples hopefully demonstrated, it’s very important to use the correct markup. Actually - to be more precise - we should say WAI-ARIA, which stands for “Web Accessibility Initiative – Accessible Rich Internet Applications”.