Should it require such a deep analysis to recommend the right HTML element? In a client-rendered app with proper focus management, the user may not be impacted by this—a link with ng-click and tabindex will still have the implicit link role. However, it would be much more declarative to use a populated href and routing if an anchor navigates the user to a new resource.
Tabindex and click events tacked onto an anchor tag are a markup anti-pattern that will trip up future developers and code reviewers. Making routing a core part of a web application makes it easier for developers to use links where appropriate and helps to clarify the purpose of buttons. It also makes it easier to create progressively-enhanced, server-rendered JavaScript applications using URL schemes instead of relying on click events.
I'll say it out loud: this confusion often begins with Design and UX. A design comp comes to you with boxy interface buttons, and—because reasons—they have to be coded as links. Where does that become a problem? If a screen reader user calls tech support and gets instructions to "click the button" in your UI that's really coded as a link, they may have trouble finding it.
Also, consider voice interfaces: if you say a command to click a button but it's really coded as a link, you might have problems, no? Frameworks admittedly blur this line and make it easy to choose the wrong element, like the above ng-click example. We can use JavaScript to trigger asynchronous form submissions on any element we want without a form tag, even, but you still need one. Similarly, we can initiate view changes without routing, even if it's best handled with link.
Some elements are better for the job than others: it's all about taking advantage of the most native features of that element as possible. To learn more or opt-out, read our Cookie Policy. Today the judge in Epic v. Apple issued a lengthy ruling holding that Epic failed to prove that Apple has a monopoly in mobile gaming transactions. To fix that, the court issued the following permanent injunction barring Apple from having rules against other payment systems. Apple Inc. Indeed, the court was clear that it will enforce this rule, and that if anyone thinks Apple is breaking it, it wants to know.
Again, my bolding:. The Court will retain jurisdiction over the enforcement and amendment of the injunction. If any part of this Order is violated by any party named herein or any other person, plaintiff may, by motion with notice to the attorneys for defendant, apply for sanctions or other relief that may be appropriate. So now comes the really complicated part. What does this injunction mean for Apple and the App Store?
Well, shit. CSS frameworks give you the opportunity to style your links like buttons. You can see that in every framework you can apply something like. Maybe that's not so bad, but a link and a button are completely different things.
They behave differently. So why should they look the same? A link is focusable and can be triggered by the enter key. A link will redirect you to a new page or a section within the same page. In VoiceOver's rotator, it will also be collected within the "Links" window.
A button is focusable, too, and can be triggered by the space key. A button will trigger an action like opening or closing something.
Or sending a form. In most cases JavaScript is used to do this. In VoiceOver's rotator, it will be collected within the "Form controls" window.
New window or tab : If a link opens a new tab, or takes the user out of the current format or application, that action should be indicated by the link text. It can be disorienting to users — especially those with cognitive, sight, or mobility problems — to unexpectedly open an item in a new format or application. Indicate either via contextual text near the links, or preferably with very clear link text, where links lead, and how they will open.
If you need to add contextual text to the link text, consider using a nested tag that is visually hidden for sighted users.
0コメント