If you are a frontend developer, or if you have been practicing frontend development either professionally or in your spare time, chances are you h...
For further actions, you may consider blocking this person and/or reporting abuse
Thanks for the article! Accessibility does not get enough focus.
This does help resolve the accessibility issue, but it creates a separate usability concern for all other uses. The empty link covering the content means we no longer have the ability to interact with any of the elements on the card other than click. No text selection, or saving of images, etc. This may seem minor, but it can have a big impact.
One solution we have implemented is for the card to accept a linkRef or selector for locating the action link within the content, and applying a card-level click handler. While this violates rules around what elements can be interactive, we found it provided a balance, where an action link is provided in the content so accessibility use is preserved, and both the user interaction and the full-card click ability is preserved.
Interesting! Could you provide a small example? In most cases where click events are attched to an element, there's no option to right-click > "Open in new tab (t)" or middle click (opens in new tab) for power users.
You make a good point. Our "redirected click" solution depends on a visible action or link in the content, which itself can be interacted with directly for those behaviors. For the application in which it is implemented, Open in new tab is not a desired capability, so we didn't have to support it.
It's definitely a balance of interacting with the card content naturally vs interacting with it as a link.