Chris recently highlighted the accessibility and UX drawbacks of "block links"—wrapping entire card elements within anchor tags. This article revisits the challenge, exploring whether the problem lies in the pattern itself or its implementation. We'll aim to create a card component that addresses these issues. Throughout, "card" refers to a component employing the block link pattern.
Our ideal Card Component should meet these criteria:
- Fully clickable and linked.
- Accommodate multiple internal links.
- Maintain semantic HTML for assistive technology compatibility.
- Allow text selection, like standard links.
- Support right-clicks and keyboard shortcuts.
- Ensure proper tab order for focusable elements.
This presents a significant challenge, as browsers lack a standard card widget. Let's examine several approaches:
Method 1: The Simple (but Flawed) <a></a> Wrap
The simplest approach—wrapping the entire card in an <a></a> tag—is also the least effective. While achieving basic clickability and right-click/keyboard shortcut functionality, it fails on several fronts:
- Prevents nested links within the card.
- Compromises accessibility; screen readers may announce the entire card's content indiscriminately.
- Disables text selection.
This method is clearly inadequate.
Method 2: Linking Only Necessary Elements
This approach prioritizes accessibility by linking only individual elements needing links. This successfully addresses:
- Multiple internal links.
- Semantic HTML.
- Text selection.
- Right-click/keyboard shortcuts.
- Tab order.
However, it lacks the crucial feature of full card clickability.
Method 3: The ::before Pseudo-element Approach
Using a ::before or ::after pseudo-element positioned absolutely over the card provides a clickable area. However, this method still suffers from:
- Limitations on nested links; the pseudo-element layer obstructs clicks on underlying links.
- Text selection remains problematic.
A more robust solution is needed.
Method 4: JavaScript Enhancement of Method 2
Building upon Method 2, we can leverage JavaScript for progressive enhancement. We'll add a click event listener to the card and programmatically trigger the main link's click event. To prevent interference with text selection, we'll use window.getSelection().toString() to check if text is selected before triggering the link click:
const card = document.querySelector(".card");
const mainLink = document.querySelector('.main-link');
card.addEventListener("click", handleClick);
function handleClick(event) {
const isTextSelected = window.getSelection().toString();
if (!isTextSelected) {
mainLink.click();
}
}
// Prevent event propagation on clickable elements within the card
const clickableElements = Array.from(card.querySelectorAll("a"));
clickableElements.forEach((ele) =>
ele.addEventListener("click", (e) => e.stopPropagation())
);
This approach successfully meets all our requirements. However, potential double-event triggering on internal links and buttons may require further refinement.
This solution provides a functional and accessible clickable card component. Further considerations, such as handling cards with "Read More" links or images, require additional exploration.
For further reading:
- Cards by Heydon Pickering
- Block Links, Cards, Clickable Regions, Rows, Etc. by Adrian Roselli
- Block Links Are a Pain (and Maybe Just a Bad Idea) by Chris Coyier
- Pitfalls of Card UIs by Dave Rupert
The above is the detailed content of Block Links: The Search for a Perfect Solution. For more information, please follow other related articles on the PHP Chinese website!
Hot AI Tools
Undress AI Tool
Undress images for free
Undresser.AI Undress
AI-powered app for creating realistic nude photos
AI Clothes Remover
Online AI tool for removing clothes from photos.
Clothoff.io
AI clothes remover
Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!
Hot Article
Hot Tools
Notepad++7.3.1
Easy-to-use and free code editor
SublimeText3 Chinese version
Chinese version, very easy to use
Zend Studio 13.0.1
Powerful PHP integrated development environment
Dreamweaver CS6
Visual web development tools
SublimeText3 Mac version
God-level code editing software (SublimeText3)
CSS tutorial for creating loading spinners and animations
Jul 07, 2025 am 12:07 AM
There are three ways to create a CSS loading rotator: 1. Use the basic rotator of borders to achieve simple animation through HTML and CSS; 2. Use a custom rotator of multiple points to achieve the jump effect through different delay times; 3. Add a rotator in the button and switch classes through JavaScript to display the loading status. Each approach emphasizes the importance of design details such as color, size, accessibility and performance optimization to enhance the user experience.
Addressing CSS Browser Compatibility issues and prefixes
Jul 07, 2025 am 01:44 AM
To deal with CSS browser compatibility and prefix issues, you need to understand the differences in browser support and use vendor prefixes reasonably. 1. Understand common problems such as Flexbox and Grid support, position:sticky invalid, and animation performance is different; 2. Check CanIuse confirmation feature support status; 3. Correctly use -webkit-, -moz-, -ms-, -o- and other manufacturer prefixes; 4. It is recommended to use Autoprefixer to automatically add prefixes; 5. Install PostCSS and configure browserslist to specify the target browser; 6. Automatically handle compatibility during construction; 7. Modernizr detection features can be used for old projects; 8. No need to pursue consistency of all browsers,
What is the difference between display: inline, display: block, and display: inline-block?
Jul 11, 2025 am 03:25 AM
Themaindifferencesbetweendisplay:inline,block,andinline-blockinHTML/CSSarelayoutbehavior,spaceusage,andstylingcontrol.1.Inlineelementsflowwithtext,don’tstartonnewlines,ignorewidth/height,andonlyapplyhorizontalpadding/margins—idealforinlinetextstyling
Styling visited links differently with CSS
Jul 11, 2025 am 03:26 AM
Setting the style of links you have visited can improve the user experience, especially in content-intensive websites to help users navigate better. 1. Use CSS's: visited pseudo-class to define the style of the visited link, such as color changes; 2. Note that the browser only allows modification of some attributes due to privacy restrictions; 3. The color selection should be coordinated with the overall style to avoid abruptness; 4. The mobile terminal may not display this effect, and it is recommended to combine it with other visual prompts such as icon auxiliary logos.
Creating custom shapes with css clip-path
Jul 09, 2025 am 01:29 AM
Use the clip-path attribute of CSS to crop elements into custom shapes, such as triangles, circular notches, polygons, etc., without relying on pictures or SVGs. Its advantages include: 1. Supports a variety of basic shapes such as circle, ellipse, polygon, etc.; 2. Responsive adjustment and adaptable to mobile terminals; 3. Easy to animation, and can be combined with hover or JavaScript to achieve dynamic effects; 4. It does not affect the layout flow, and only crops the display area. Common usages are such as circular clip-path:circle (50pxatcenter) and triangle clip-path:polygon (50%0%, 100 0%, 0 0%). Notice
How to create responsive images using CSS?
Jul 15, 2025 am 01:10 AM
To create responsive images using CSS, it can be mainly achieved through the following methods: 1. Use max-width:100% and height:auto to allow the image to adapt to the container width while maintaining the proportion; 2. Use HTML's srcset and sizes attributes to intelligently load the image sources adapted to different screens; 3. Use object-fit and object-position to control image cropping and focus display. Together, these methods ensure that the images are presented clearly and beautifully on different devices.
Demystifying CSS Units: px, em, rem, vw, vh comparisons
Jul 08, 2025 am 02:16 AM
The choice of CSS units depends on design requirements and responsive requirements. 1.px is used for fixed size, suitable for precise control but lack of elasticity; 2.em is a relative unit, which is easily caused by the influence of the parent element, while rem is more stable based on the root element and is suitable for global scaling; 3.vw/vh is based on the viewport size, suitable for responsive design, but attention should be paid to the performance under extreme screens; 4. When choosing, it should be determined based on whether responsive adjustments, element hierarchy relationships and viewport dependence. Reasonable use can improve layout flexibility and maintenance.
What are common CSS browser inconsistencies?
Jul 26, 2025 am 07:04 AM
Different browsers have differences in CSS parsing, resulting in inconsistent display effects, mainly including the default style difference, box model calculation method, Flexbox and Grid layout support level, and inconsistent behavior of certain CSS attributes. 1. The default style processing is inconsistent. The solution is to use CSSReset or Normalize.css to unify the initial style; 2. The box model calculation method of the old version of IE is different. It is recommended to use box-sizing:border-box in a unified manner; 3. Flexbox and Grid perform differently in edge cases or in old versions. More tests and use Autoprefixer; 4. Some CSS attribute behaviors are inconsistent. CanIuse must be consulted and downgraded.
