Of course you might have done this (but don't do it in any way!): Google nothing! NVDA, or JAWS (which you definitely should test with, it's a major player!), or TalkBack on Android, or VoiceOver on Apple devices, will say: "Link Google", or "Google link" (depends on the screen reader and on particular user's settings). Let's take your example with the link to Google: you want your blind user to see the "Google" text and to understand that it is a link, right? Well, I'll tell you what you should do to achieve this. I.e.: If you can not to use ARIA, don't use it. If you can use a native HTML element or attribute with the semantics and behavior you require already built in, instead of re-purposing an element and adding an ARIA role, state or property You can do lots of crazy (and smart) stuff with it, it is great and mighty, but the first rule of the fight club, I mean, WAI-ARIA practices is: There is a way to customize the layout, though.
By "impact" I mean that your goal should be that your blind user would see just the same thing as a sighted user, but as the web site developer, you give him/her this ability to see, navigate, open, click and so on, and so forth. Well, there is something like that, I'll tell you about it below.īasically, when you try to make your web site more accessible (a very good thing to do, btw!), you should minimize your impact on screen reader users. There is no such thing as a custom mark-up for screen readers.
0 kommentar(er)
