# Manuel Matuzović

My Blog about accessibility, performance, and CSS architecture and layout.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## My HTML boilerplate in 2026

DevFeed: [My HTML boilerplate in 2026](<https://devfeed.tech/articles/my-html-boilerplate-in-2026-52357.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/2026/html-boilerplate>)

Author: Manuel Matuzović

Published: 2026-08-17T00:00:00Z

Content type: tutorial

Language: en

Sources: [Manuel Matuzović](<https://devfeed.tech/sources/manuel-matuzovic-blog.md>)

Topics: [HTML](<https://devfeed.tech/topics/html.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>), [Web platform](<https://devfeed.tech/topics/web-platform.md>), [browser](<https://devfeed.tech/topics/browser.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [css](<https://devfeed.tech/tags/css.md>), [design](<https://devfeed.tech/tags/design.md>), [html](<https://devfeed.tech/tags/html.md>), [ios](<https://devfeed.tech/tags/ios.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [property](<https://devfeed.tech/tags/property.md>), [viewport](<https://devfeed.tech/tags/viewport.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

An updated HTML boilerplate for 2026 is presented with a line-by-line explanation of document structure, language metadata, JavaScript handling, character encoding, viewport settings, and related head elements.

### Source excerpt

Every element I use for the basic structure of a HTML document, with explanations why. Five years ago, I shared the HTML boilerplate I use for most of my projects. Since then, a lot has happened in HTML. It's time to give it an update. My boilerplate This is the final document. Scroll down for details. <!DOCTYPE html> <html lang="en" class="no-js"> <head> <meta charset="UTF-8"> <meta name="viewport" content="width=device-width"> <meta name="text-scale" content="scale"> <title>Unique page title - My Site</title> <script src="/js/render-blocking-scripts.js"></script> <script> document.documentElement.classList.replace('no-js', 'js'); </script> <link rel="stylesheet" href="/css/styles.css"> <link rel="stylesheet" href="/css/print.css" media="print"> <script src="/js/non-render-blocking-script.js" type="module"></script> <link rel="icon" href="/favicon.ico"> <link rel="icon" href="/favicon.svg" type="image/svg+xml"> <link rel="apple-touch-icon" href="/apple-touch-icon.png"> <link rel="manifest" href="/site.webmanifest"> <link rel="canonical" href="https://web.site/page"> <link rel="alternate" type="text/markdown" href="https://web.site/page.md"> <link rel="me" href="https://mastodon.social/@username"> <link rel="site.standard.publication" href="at://[DID]/site.standard.publication/[RKEY]"> <meta name="description" content="Page description"> <meta property="og:image" content="https://web.site/sm.jpg"> <meta property="og:url" content="https://web.site/page"> <meta name="theme-color" content="#FF5302"> <meta property="fediverse:creator" content="@user@mastodon.social" > </head> <body> <!-- Content --> <script src="/js/non-render-blocking-script.js"></script> </body> </html> Line by line explanation Doctype required <!DOCTYPE html> Since HTML is a living standard, we no longer need different doctypes, but we still have to define one for compatibility. Natural language required <html lang="en"> The lang attribute is one of the most important attributes in HTML, because it's

## Progressively enhancing Grid Lanes

DevFeed: [Progressively enhancing Grid Lanes](<https://devfeed.tech/articles/progressively-enhancing-grid-lanes-52356.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/2026/grid-lanes-progressive-enhancement>)

Author: Manuel Matuzović

Published: 2026-06-30T07:45:00Z

Content type: tutorial

Language: en

Sources: [Manuel Matuzović](<https://devfeed.tech/sources/manuel-matuzovic-blog.md>)

Topics: [CSS](<https://devfeed.tech/topics/css.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>), [browser](<https://devfeed.tech/topics/browser.md>), [Web platform](<https://devfeed.tech/topics/web-platform.md>), [web-standards](<https://devfeed.tech/topics/web-standards.md>)

Tags: [accessible](<https://devfeed.tech/tags/accessible.md>), [browser](<https://devfeed.tech/tags/browser.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [css](<https://devfeed.tech/tags/css.md>), [css-grid](<https://devfeed.tech/tags/css-grid.md>), [edge](<https://devfeed.tech/tags/edge.md>), [firefox](<https://devfeed.tech/tags/firefox.md>), [wcag](<https://devfeed.tech/tags/wcag.md>)

### AI overview

This follow-up examines whether CSS Grid Lanes can be progressively enhanced safely. It explains that unsupported browsers can fall back to regular Grid, but recommends using Grid Lanes only when both Grid Lanes and Reading Flow are supported because of focus-order and accessibility concerns.

### Source excerpt

This post is a follow-up on my previous post. I was wondering whether it's safe to use Grid Lanes today. I came up with a solution I find okay, but there is a caveat. Note: This post contains interactive demos. If you want to see them instead of screenshots, enable the CSS Grid Lanes Layout flag in Edge or Chrome or use Safari 26.4+ or Polypane 29+. In my last blog post, Your Grid Lanes will likely fail WCAG 2.4.3, I explained how Grid Lanes are inherently inaccessible by default unless you take extra measures. I also concluded that it's probably only safe to use Grid Lanes with Reading Flow. According to Rachel Andrew, Google Chrome also made sure to first ship Reading Flow and then Grid Lanes. Unfortunately, that's not what all browsers did. Safari shipped it, but doesn't support Reading Flow yet. Is it a big deal? Now you may think it's not a big deal because most people won't use Grid Lanes anyway until all browsers support it, and maybe, when that happens, Safari will also support Reading Flow. The thing is, Grid Lanes share many properties with Grids, and because CSS is beautifully designed, it's very easy to convert regular grids into Grid Lanes for browsers that support it. HTML <div class="grid-lanes"> <button class="s">1</button> <button class="m">2</button> <button class="l">3</button> <button class="l">4</button> <button class="m">5</button> <button class="s">6</button> </div> In one line, you set the display property to grid, and in the next, you overwrite it with grid-lanes. CSS .grid-lanes { display: grid; display: grid-lanes; grid-template-columns: repeat(3, 1fr); } Browsers that support it will create Grid Lanes, and those that don't will just fall back to a regular Grid. The grid in browsers that don't support CSS Grid Lanes The grid in browser that support CSS Grid Lanes In theory, that's all you need to create future-proof Grid Lanes. People will use it, and some are actually already doing it. Jeremy Keith, for example, explains how he uses @supp

## Your Grid Lanes will likely fail WCAG 2.4.3

DevFeed: [Your Grid Lanes will likely fail WCAG 2.4.3](<https://devfeed.tech/articles/your-grid-lanes-will-likely-fail-wcag-2-4-3-52355.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/2026/grid-lanes-accessibility>)

Author: Manuel Matuzović

Published: 2026-06-24T09:00:00Z

Content type: tutorial

Language: en

Sources: [Manuel Matuzović](<https://devfeed.tech/sources/manuel-matuzovic-blog.md>)

Topics: [CSS](<https://devfeed.tech/topics/css.md>), [layout](<https://devfeed.tech/topics/layout.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>)

Tags: [browser](<https://devfeed.tech/tags/browser.md>), [css](<https://devfeed.tech/tags/css.md>), [grid](<https://devfeed.tech/tags/grid.md>), [wcag](<https://devfeed.tech/tags/wcag.md>)

### AI overview

The article explains how CSS Grid Lanes automatically places items into balanced columns or rows, then highlights an accessibility risk: visual order can differ from keyboard tab and screen-reader reading order.

### Source excerpt

I saw a great introduction to CSS Grid Lanes, aka Masonry Layouts, by Patrick Brosset at CSS Day 2026. I liked the versatility of its use cases, but I was also concerned that it's inaccessible by default. Note: This post contains interactive demos. If you want to see them instead of screenshots, enable the CSS Grid Lanes Layout flag in Edge or Chrome or use Safari 26.4+ or Polypane 29+. Intro to Grid lanes CSS Grid Lanes is a new layout technique in CSS. Although the name suggests it, you don't create grids with it; instead, you create columns or rows that automatically get populated with items. The layout kinda looks like a grid, but the big difference from regular grids is that you can only control one axis. By default, the browser decides where to place each item: it's placed in whichever column brings it closest to the start of the container. HTML <div class="grid-lanes"> <button class="s">1</button> <button class="m">2</button> <button class="l">3</button> <button class="l">4</button> <button class="m">5</button> <button class="s">6</button> </div> CSS .grid-lanes { display: grid-lanes; grid-template-columns: repeat(3, 1fr); } button { block-size: var(--h)} .s { --h: 2lh; } .m { --h: 4lh; } .l { --h: 6lh; } 1 2 3 4 5 6 Demo: Items stacked from left to right, from top to bottom In the demo above, you can see what makes Grid Lanes special: you can arrange differently sized items in a grid-like fashion with equal gaps. You may have noticed that the columns in this demo are equal in height. That's because I arranged them that way, but one of the strengths of Grid Lanes is that you don't have to care about that. The browser looks at the items you give it and tries to create balanced columns (or rows). It does so by placing items as close as possible to the grid's start edge. In the following demo, items 1-3 are each placed in a separate column because this brings them as close as possible to the start of the container. Item 4 is in the second column because that's t

## Setting the width of selects to the width of the selected option

DevFeed: [Setting the width of selects to the width of the selected option](<https://devfeed.tech/articles/setting-the-width-of-selects-to-the-width-of-the-selected-option-52362.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/2026/select-fieldsize>)

Author: Manuel Matuzović

Published: 2026-06-22T07:30:00Z

Content type: tutorial

Language: en

Sources: [Manuel Matuzović](<https://devfeed.tech/sources/manuel-matuzovic-blog.md>)

Topics: [Code](<https://devfeed.tech/topics/code.md>), [Firefox](<https://devfeed.tech/topics/firefox.md>)

Tags: [blog](<https://devfeed.tech/tags/blog.md>), [blog-post](<https://devfeed.tech/tags/blog-post.md>), [code](<https://devfeed.tech/tags/code.md>), [firefox](<https://devfeed.tech/tags/firefox.md>)

### AI overview

This tutorial demonstrates how the CSS field-sizing property changes a select element's width to match its selected option. It also notes that the property is coming to Firefox 152 and will be available across major browser engines.

### Source excerpt

The field-sizing property is coming to Firefox 152, making it available across all major engines. It allows you to control the sizing behavior of elements with a default preferred size, such as form elements. I'll take a closer look at the field-sizing property in another blog post, but I wanted to show you a cool feature first. By default, the width of a select element is determined by its largest option. Pick a city Amsterdam Rotterdam Scheveningen Utrecht Show code <label for="place">Pick a city</label> <select id="place"> <option>Amsterdam</option> <option>Rotterdam</option> <option>Scheveningen</option> <option selected>Utrecht</option> </select> You can see how the select element here is much wider than the width of the characters in the word "Utrecht". It's large enough to fit "Scheveningen", the largest option. That may or may not be desired. At least, I remember occasions in the past where I wanted it to be only as large as the selected option. With field-sizing that's now possible. select { field-sizing: content; } Pick a city Amsterdam Rotterdam Scheveningen Utrecht Now you can see how the width of the select changes with its selected option. My blog doesn't support comments yet, but you can reply via blog@matuzo.at.

## How to Change the Zen Browser Icon on macOS

DevFeed: [How to Change the Zen Browser Icon on macOS](<https://devfeed.tech/articles/zen-zed-and-zits-52366.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/2026/zen-zed-zits>)

Author: Manuel Matuzović

Published: 2026-06-19T11:00:00Z

Content type: tutorial

Language: en

Sources: [Manuel Matuzović](<https://devfeed.tech/sources/manuel-matuzovic-blog.md>)

Topics: [browser](<https://devfeed.tech/topics/browser.md>), [macOS](<https://devfeed.tech/topics/macos.md>), [Icons](<https://devfeed.tech/topics/icons.md>), [Terminal](<https://devfeed.tech/topics/terminal.md>), [App](<https://devfeed.tech/topics/app.md>)

Tags: [browser](<https://devfeed.tech/tags/browser.md>), [icons](<https://devfeed.tech/tags/icons.md>), [macos](<https://devfeed.tech/tags/macos.md>), [terminal](<https://devfeed.tech/tags/terminal.md>)

### AI overview

A short tutorial explains how to replace the Zen browser application's icon on macOS using Finder, with a Terminal command to restart the Dock if necessary.

### Source excerpt

Don't worry, this post is not about zits, but something comparably annoying: Zen and Zed. One is a browser and the other an editor. Even writing this, I don't know which is which. Their names and icons are so similar that I keep getting them confused. I couldn't take it anymore; I had to take drastic measures. That's why I replaced the icon of the Zen browser application with a nice-looking e logo. Here's how to do it on macOS: Close Zen. Create or download an alternative icon. Highlight the downloaded file in Finder and press CMD + C. Go to your applications folder, find Zen, right-click it, and select "Get info". Highlight the icon on the top left and press CMD + V. Open Zen. (If the icon hasn't changed, open Terminal, type killall Dock and Press Enter) You're welcome. My blog doesn't support comments yet, but you can reply via blog@matuzo.at.

## Context-aware headings in HTML

DevFeed: [Context-aware headings in HTML](<https://devfeed.tech/articles/context-aware-headings-in-html-52352.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/2026/content-aware-headings>)

Author: Manuel Matuzović

Published: 2026-06-03T14:30:00Z

Content type: article

Language: en

Sources: [Manuel Matuzović](<https://devfeed.tech/sources/manuel-matuzovic-blog.md>)

Topics: [HTML](<https://devfeed.tech/topics/html.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>), [Web platform](<https://devfeed.tech/topics/web-platform.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [cms](<https://devfeed.tech/tags/cms.md>), [components](<https://devfeed.tech/tags/components.md>), [firefox](<https://devfeed.tech/tags/firefox.md>), [html](<https://devfeed.tech/tags/html.md>), [markup](<https://devfeed.tech/tags/markup.md>)

### AI overview

The article explains how the experimental HTML headingoffset attribute can make reusable components produce context-aware heading levels. It discusses applying offsets to nested elements, the effect on accessibility trees, and when the technique is useful compared with manually selecting heading levels in a CMS.

### Source excerpt

A common issue that we've probably all faced at some point is having a component that includes a heading, which sometimes should be an H2 and sometimes maybe an H3, depending on where it's used. We solved this by giving editors an option to pick the appropriate heading level in the CMS. That works, but it means more work for them, because they need to keep track of the document outline, and it's also a potential source of error. The headingoffset attribute Yesterday, I heard about a new experimental attribute that offers a better solution to this problem. The heading offset content attribute allows us to offset heading levels for descendants. Let's take the outline from the page in the screenshot and see how we can make it more context-aware. <h1>Museums</h1> <section> <h2>Free entry to the museum</h2> </section> <section> <h2>All museums and collections</h2> <h3>Aphabetical</h3> <h3>By district</h3> </section> First, we turn all headings into H1s. Then we add the headingoffset attribute with a value of 1 to every parent element where we want to increase the heading level by 1. <h1>Museums</h1> <!-- heading level 1 --> <section headingoffset="1"> <h1>Free entry to the museum</h1> <!-- heading level 2 --> </section> <section headingoffset="1"> <h1>All museums and collections</h1> <!-- heading level 2 --> <div class="cards" headingoffset="1"> <h1>Aphabetical</h1> <!-- heading level 3 --> <h1>By district</h1> <!-- heading level 3 --> </div> </section> The heading offset attribute increases the current heading level by the specified number; in this case, by 1 (h1 + 1 = h2). The H1s inside the sections become H2s and the H1s nested in another heading offset container become H3s. In the accessibility panel in Firefox, you can see that the tag for the "All museums and collections" heading is H1, but the level is 2. Now that we know how it works, let's do a quick Q&A based on the questions I had when I first saw this. On a really large page, I would need a bachelor's degree

## Don't put aria-label on generic elements like divs

DevFeed: [Don't put aria-label on generic elements like divs](<https://devfeed.tech/articles/don-t-put-aria-label-on-generic-elements-like-divs-52349.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/2026/aria-label-generic-elements>)

Author: Manuel Matuzović

Published: 2026-05-22T10:20:00Z

Content type: article

Language: en

Sources: [Manuel Matuzović](<https://devfeed.tech/sources/manuel-matuzovic-blog.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [aria](<https://devfeed.tech/topics/aria.md>), [browser](<https://devfeed.tech/topics/browser.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [aria](<https://devfeed.tech/tags/aria.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [ios](<https://devfeed.tech/tags/ios.md>), [macos](<https://devfeed.tech/tags/macos.md>), [testing](<https://devfeed.tech/tags/testing.md>), [windows](<https://devfeed.tech/tags/windows.md>), [windows-11](<https://devfeed.tech/tags/windows-11.md>)

### AI overview

This article explains why aria-label and aria-labelledby should generally not be used on generic elements such as divs and spans. It combines ARIA specification guidance with tests showing that browsers and screen readers announce labeled generic elements inconsistently. It also notes exceptions for elements whose implicit roles change, including labeled sections and popovers.

### Source excerpt

The title already tells most of the story, but here's why you must avoid labeling generic elements like divs or spans using aria-label or aria-labelledby. Looking at the ARIA spec, you'll find section "5.2.8.6 Roles which cannot be named (Name prohibited)". It lists all roles that cannot be named. It includes "generic", which is the default role of divs and spans. caption code deletion emphasis generic insertion paragraph presentation strong subscript superscript So, in theory, it's not allowed, but there is also a practical reason to avoid it. Browsers treat labeled generic elements very differently. Below you'll find the results for the following three elements I tested. The results were the same for every element. I've used the arrow keys on desktop and swipe on mobile to navigate. <div aria-label="News">Content</div> <p> Some inline <span aria-label="News">content</span> </p> <ge-neric aria-label="News"> Content </ge-neric> VoiceOver in Safari on macOS announces "News, group", Talkback in Chrome on Android "News", and Narrator on Windows 11 with Chrome "News, group, content". All the other tested screen readers ignore the author-defined label completely and announce the text content. Results from testing labeled generic containers Screen Reader Browser Announcement VoiceOver macOS Safari 26.3.1 News, group VoiceOver iOS Safari 26.3 Content Talkback Android Chrome 148 News Talkback Android Firefox 150 Content Jaws 2026 Windows 11 Chrome 148 Content NVDA 2026.1.1 Windows 11 Chrome 148 Content NVDA 2026.1.1 Windows 11 Firefox 150 Content Narrator, Windows 11 Chrome 148 News, group, content Update: Verena made me aware that results may differ if the element is empty. So, I tested that as well. I tested both an empty div with 0 width and height, and one that takes up space. There was no announcement in VoiceOver on iOS, JAWS and Narrator in Chrome, or Talkback in Firefox. <div aria-label="News" style="width:100px; height:100px"></div> <div aria-label="News"></div> Re

## box-shadow is no alternative to outline

DevFeed: [box-shadow is no alternative to outline](<https://devfeed.tech/articles/box-shadow-is-no-alternative-to-outline-52351.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/2026/box-shadow-no-alternative-to-outline>)

Author: Manuel Matuzović

Published: 2026-04-15T13:50:00Z

Content type: tutorial

Language: en

Sources: [Manuel Matuzović](<https://devfeed.tech/sources/manuel-matuzovic-blog.md>)

Topics: [CSS](<https://devfeed.tech/topics/css.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>), [browser](<https://devfeed.tech/topics/browser.md>), [Developer Tools](<https://devfeed.tech/topics/developer-tools.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [browser](<https://devfeed.tech/tags/browser.md>), [css](<https://devfeed.tech/tags/css.md>), [devtools](<https://devfeed.tech/tags/devtools.md>), [property](<https://devfeed.tech/tags/property.md>), [user-experience](<https://devfeed.tech/tags/user-experience.md>)

### AI overview

This accessibility-focused web development post explains why box-shadow should not replace outline for focus indicators. In forced-colors mode, box-shadow computes to none, so the post recommends using an outline or combining a transparent outline with box-shadow.

### Source excerpt

People like to use the box-shadow property for styling focus outlines because it gives them more flexibility. A focused button That's okay in browsers' default color mode, but in forced colors mode, it's problematic because the box-shadow property computes to none, which means that there are no shadows and consequently no focus styles in this mode. You can confirm that by opening this page in a Chromium-based browser, switching to the Rendering tab in DevTools, and setting forced-colors to active. There are two solutions to that problem. Either don't try to be fancy and simply use an outline, or, if you think the user experience will be better with a box shadow, don't set outline: none; instead, set outline: 2px solid transparent. button:focus-visible { outline: 2px solid transparent; outline-offset: 2px; box-shadow: 0 0 0px 1px blue, 0 0 0px 2px white, 0 0 0 4px blue; } A focused button The outline will be transparent in the regular mode but visible in forced colors mode. That works because in forced colors mode, colors on the page are constrained to a restricted, user-chosen palette. For transparent, which is a CSS color, this means it becomes visible. My blog doesn't support comments yet, but you can reply via blog@matuzo.at.

## The geolocation element's user intent, permission recovery, and styling constraints

DevFeed: [The geolocation element's user intent, permission recovery, and styling constraints](<https://devfeed.tech/articles/the-geolocation-element-is-odd-52354.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/2026/geolocation-is-odd>)

Author: Manuel Matuzović

Published: 2026-03-11T11:30:00Z

Content type: article

Language: en

Sources: [Manuel Matuzović](<https://devfeed.tech/sources/manuel-matuzovic-blog.md>)

Topics: [Website](<https://devfeed.tech/topics/website.md>), [permission](<https://devfeed.tech/topics/permission.md>), [Users](<https://devfeed.tech/topics/users.md>), [browser](<https://devfeed.tech/topics/browser.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>)

Tags: [browser](<https://devfeed.tech/tags/browser.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [geolocation](<https://devfeed.tech/tags/geolocation.md>), [permission](<https://devfeed.tech/tags/permission.md>), [users](<https://devfeed.tech/tags/users.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

An examination of a web geolocation element, including its user-intent model, permission recovery and refresh behavior, and restrictions intended to prevent deceptive styling.

### Source excerpt

Imagine the following scene: you're on a website, and there's a button. When you click the button, it shows some text, but the website's font size is really small. So, you change the default font size in your browser from 16 to 24 pixels. You go back to the website and click the button again, but it doesn't work now. That's not just very unfortunate, but it's also absolutely unexpected, confusing, and irritating. With that picture in mind. Let's talk about some things that I find odd about the geolocation element. First impression When I first read about the geolocation element, my initial reaction was surprise. I was surprised to find a dedicated element for obtaining the user's location. I thought that could've also been a relatively simple web component instead. On the Chrome for Developers blog, the authors explain that there are three main reasons for the existence of the element. Clear intent and timing - By clicking a button, users show clear intent. That's in contrast to how it works on many websites, where, out of nowhere, they will automatically ask you to share your location. Users often dismiss or decline these requests, which can be problematic because it's not easy to change that decision later. Simplified recovery - If a user or browser has previously blocked access to a location, the element enables them to change their settings. Automatic refresh - If a permission has already been granted, users can click the button to update it. I wasn't 100% convinced, but the recovery and refresh features sold it to me. Still, I didn't think I would use this element much because I don't need to know the user's location very often. That's, of course, my problem. When I learned everything I wanted to know, I wrote a simple introductory post about the element on my website. Five weeks later, I'm writing another post because I've learned some more surprising and strange things. Styling constraints You can style the geolocation element, but there are styling constrain

## Your skip link targets may not need tabindex=-1 to work properly

DevFeed: [Your skip link targets may not need tabindex=-1 to work properly](<https://devfeed.tech/articles/your-skip-link-targets-may-not-need-tabindex-1-to-work-properly-52363.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/2026/skip-links-tabindex>)

Author: Manuel Matuzović

Published: 2026-03-04T20:35:00Z

Content type: article

Language: en

Sources: [Manuel Matuzović](<https://devfeed.tech/sources/manuel-matuzovic-blog.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [browser](<https://devfeed.tech/topics/browser.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [browser](<https://devfeed.tech/tags/browser.md>), [testing](<https://devfeed.tech/tags/testing.md>), [tests](<https://devfeed.tech/tags/tests.md>)

### AI overview

The article tests whether skip-link targets still need tabindex="-1" for keyboard and screen-reader navigation. It explains that modern browsers use a sequential focus navigation starting point when navigating to a page fragment, addressing the historical focus-management problem, and reports tests of keyboard and screen-reader behavior.

### Source excerpt

Recently, someone posted on LinkedIn that skip links are often broken because their target elements are missing a tabindex attribute. I was really surprised to see that because I thought that was an issue of the past. That's why I decided to test it. The original problem The author explained in their post that when you use a keyboard and press Enter on a skip link, the page scrolls down to the target, but focus stays on the link. When you press Tab, focus doesn't jump to the target; it jumps to the next focusable element after the skip link. He calls that a "phantom jump". <a href="#content">Jump to content</a> <nav> <!-- A bunch of links --> </nav> <main id="content"> </main> They explain that the problem is that the main element is not an interactive element and thus cannot be focused. That's why their proposed solution is adding a tabindex attribute. <a href="#content">Jump to content</a> <nav> <!-- A bunch of links --> </nav> <main id="content" tabindex="-1"> </main> What the author describes was a problem... a long time ago. As Sara Higley reconstructs, Firefox was the first browser to fix it in 2013, followed by Internet Explorer, and finally Chrome in 2016. I don't know about Safari, but it was long enough ago that I can't remember anymore. The solution The fix browsers implemented is a feature called "sequential focus navigation starting point (SFNSP)". Rob Dodson defines it well in his post "Remove headaches from focus management". The 'sequential focus navigation starting point' feature defines where we start to search for focusable elements for sequential focus navigation (Tab or Shift-Tab) when there is no focused area. Prior to that, there were only two possible starting points. If there is no other starting point, it's the document or, if available, the currently active dialog. If an element is focused, it's also the starting point With SFNSP, there can now be more starting points. Navigating to a page fragment, e.g., by clicking a skip link, sets the st

## role=presentation is no alternative for aria-hidden=true

DevFeed: [role=presentation is no alternative for aria-hidden=true](<https://devfeed.tech/articles/role-presentation-is-no-alternative-for-aria-hidden-true-52361.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/2026/role-presentation-no-alternative-for-aria-hidden>)

Author: Manuel Matuzović

Published: 2026-02-27T10:50:00Z

Content type: tutorial

Language: en

Sources: [Manuel Matuzović](<https://devfeed.tech/sources/manuel-matuzovic-blog.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [aria](<https://devfeed.tech/topics/aria.md>), [SVG](<https://devfeed.tech/topics/svg.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [android](<https://devfeed.tech/tags/android.md>), [aria](<https://devfeed.tech/tags/aria.md>), [assistive-technology](<https://devfeed.tech/tags/assistive-technology.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [developers](<https://devfeed.tech/tags/developers.md>), [firefox](<https://devfeed.tech/tags/firefox.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [macos](<https://devfeed.tech/tags/macos.md>), [screen](<https://devfeed.tech/tags/screen.md>), [svg](<https://devfeed.tech/tags/svg.md>), [testing](<https://devfeed.tech/tags/testing.md>), [windows-11](<https://devfeed.tech/tags/windows-11.md>)

### AI overview

This accessibility article explains the difference between aria-hidden="true" and role="presentation" or role="none". It shows that role="presentation" removes an element's native role but does not necessarily remove the element or its children from the accessibility tree, especially for labelled or text-containing SVGs. It recommends aria-hidden="true" when an element should be hidden from assistive technology.

### Source excerpt

In the previous post, I explained how to hide presentational SVGs using aria-hidden="true". That's a reliable technique, but sometimes I see developers use role="presentation" instead, which may or may not work as expected. Before I show you where it fails, let's first try to understand the difference between role="presentation" and aria-hidden="true". aria-hidden="true" According to the spec, aria-hidden indicates, when set to true, that an element and its entire subtree are hidden from assistive technology, regardless of whether it is visibly rendered. The following heading is visually accessible, but hidden from assistive technology. <h2 aria-hidden="true"> Hello World </h2> The same applies to the following SVG. <svg viewBox="0 0 39 44" aria-hidden="true"> <text x="20" y="35">🥔</text> </svg> Screen readers skip both elements entirely and don't announce anything. role="presentation" According to the spec, the native role semantics of an element with role="presentation" (or role="none", which is a synonym) will not be mapped to the accessibility API. This means that the main difference from aria-hidden="true" is that role="presentation" only removes the native role of an element, not the element or its children. Instead of something like "heading level 2, Hello World" a screen announces "Hello World" only. So, in terms of semantics, this element isn't a heading anymore but just static text. <h2 role="presentation"> Hello World </h2> Images are different Images are an exception, as noted in the ARIA specification. In HTML, the <img> element is treated as a single entity regardless of the type of image file. Consequently, using role="none" or role="presentation" on an HTML img is equivalent to using aria-hidden="true". Just because that's true for images doesn't mean that it's always true for SVGs. Where role="presentation" fails (your expectations) If you put role="presentation" on an unlabelled SVG without any text nodes, VoiceOver, Talkback, JAWS, and NVDA will i

## Put aria-hidden=true on decorative SVGs

DevFeed: [Put aria-hidden=true on decorative SVGs](<https://devfeed.tech/articles/put-aria-hidden-true-on-decorative-svgs-52360.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/2026/put-aria-hidden-on-presentational-svgs>)

Author: Manuel Matuzović

Published: 2026-02-27T09:20:00Z

Content type: tutorial

Language: en

Sources: [Manuel Matuzović](<https://devfeed.tech/sources/manuel-matuzovic-blog.md>)

Topics: [SVG](<https://devfeed.tech/topics/svg.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [android](<https://devfeed.tech/tags/android.md>), [aria](<https://devfeed.tech/tags/aria.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [edge](<https://devfeed.tech/tags/edge.md>), [firefox](<https://devfeed.tech/tags/firefox.md>), [macos](<https://devfeed.tech/tags/macos.md>), [safari](<https://devfeed.tech/tags/safari.md>), [svg](<https://devfeed.tech/tags/svg.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

This accessibility post explains why decorative SVGs should include aria-hidden="true". Without it, some screen readers may announce the SVG as an image or graphic, and SVGs containing presentational text may be read aloud.

### Source excerpt

The title says it all: put aria-hidden="true" on decorative SVGs, or they'll be announced by some screen readers. <svg viewBox="0 0 39 44" aria-hidden="true"> <path d="M19.5 36.5 1.6 26.1v-3.6l16.3 9.4V1.5h3.2v30.4l16.3-9.4v3.6z"/> </svg> Similar to when you set alt="" on an img element, screen readers will ignore this SVG Without aria-hidden="true", you get the following results: <svg viewBox="0 0 39 44"> <path d="M19.5 36.5 1.6 26.1v-3.6l16.3 9.4V1.5h3.2v30.4l16.3-9.4v3.6z"/> </svg> Bad practice: Missing aria-hidden="true" state Most current screen readers ignore the SVG, but there are exceptions. VoiceOver, macOS 26.3, Chrome 145: Image Narrator, Windows 11, Edge/Chrome 145: Graphic VoiceOver, macOS 26.3, Safari: Ignores the SVG Talkback, Android 16, Chrome 145: Ignores the SVG JAWS 2026, Windows 11, Chrome 145: Ignores the SVG NVDA 2025.3.3, Windows 11, Firefox 147 Ignores the SVG Adding the attribute is especially important if your SVG contains presentational text. <svg viewBox="0 0 39 44"> <text x="20" y="35">🥔</text> </svg> Bad practice: Missing aria-hidden="true" state VoiceOver, macOS 26.3, Chrome 145: Potato VoiceOver, macOS 26.3, Safari: Potato Talkback, Android 16, Chrome 145: Potato emoji JAWS 2026, Windows 11, Chrome 145: Potato NVDA 2025.3.3, Windows 11, Chrome146 Graphic, Potato NVDA 2025.3.3, Windows 11, Firefox 147 Potato Narrator, Windows 11, Edge: Graphic, Potato My blog doesn't support comments yet, but you can reply via blog@matuzo.at.

## Why aria-haspopup Can Mislead Users in Site Navigation

DevFeed: [Why aria-haspopup Can Mislead Users in Site Navigation](<https://devfeed.tech/articles/aria-haspopup-might-not-do-what-you-think-it-does-52348.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/2026/aria-haspopup-menu>)

Author: Manuel Matuzović

Published: 2026-02-23T19:45:00Z

Content type: tutorial

Language: en

Sources: [Manuel Matuzović](<https://devfeed.tech/sources/manuel-matuzovic-blog.md>)

Topics: [aria](<https://devfeed.tech/topics/aria.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [navigation](<https://devfeed.tech/topics/navigation.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [aria](<https://devfeed.tech/tags/aria.md>), [keyboard](<https://devfeed.tech/tags/keyboard.md>), [navigation](<https://devfeed.tech/tags/navigation.md>)

### AI overview

Using aria-haspopup alone on navigation buttons can confuse users or make subnavigation inaccessible. The article explains that its value must match the role of the popup container and distinguishes navigation links from action menus.

### Source excerpt

To kick off my new article series, #WebAccessibilityFails, I decided to focus on a bad practice I often see in main navigations during accessibility audits. Developers like to put aria-haspopup on buttons inside main navigations to indicate that the buttons control subnavigations. <nav> <ul> <li> <button aria-haspopup="menu">Products</button> <ul> <li><a href="#">Wood</a></li> <li><a href="#">Steel</a></li> <li><a href="#">Plastic</a></li> </ul> </li> </ul> </nav> The purpose of aria-haspopup There is no particular problem with the aria-haspopup property itself, but when used alone without any extra work, it can confuse users or even prevent them from accessing the submenu. To understand why, let's first look at the definition. [aria-haspopup] Indicates the availability and type of interactive popup element, such as menu or dialog, that can be triggered by an element. A popup element usually appears as a block of content that is on top of other content. That sounds like the property is spot on in this case, but the next sentence is important. Authors MUST ensure that the role of the element that serves as the container for the popup content is menu, listbox, tree, grid, or dialog, and that the value of aria-haspopup matches the role of the popup container. aria-haspopup doesn't just indicate that the button controls any popup, but a specific type of popup. It can either be a menu, listbox, tree, grid, or a dialog. In the example above, the button controls an element with the list role. A list doesn't become a menu just because you use it inside a nav element. Also, it's likely that it shouldn't be a menu in the first place because a navigation is different from a menu. Here's the definition of the menu role. A type of widget that offers a list of choices to the user. A menu is often a list of common actions or functions that the user can invoke. The menu role is appropriate when a list of menu items is presented in a manner similar to a menu on a desktop application

## A new meta tag for respecting text scaling on mobile

DevFeed: [A new meta tag for respecting text scaling on mobile](<https://devfeed.tech/articles/a-new-meta-tag-for-respecting-text-scaling-on-mobile-52364.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/2026/text-scaling-meta-tag>)

Author: Manuel Matuzović

Published: 2026-02-06T08:24:00Z

Content type: article

Language: en

Sources: [Manuel Matuzović](<https://devfeed.tech/sources/manuel-matuzovic-blog.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [browser](<https://devfeed.tech/topics/browser.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [Firefox](<https://devfeed.tech/topics/firefox.md>), [Website](<https://devfeed.tech/topics/website.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [color](<https://devfeed.tech/topics/color.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [canary](<https://devfeed.tech/tags/canary.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [chrome-canary](<https://devfeed.tech/tags/chrome-canary.md>), [firefox](<https://devfeed.tech/tags/firefox.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [web](<https://devfeed.tech/tags/web.md>), [website](<https://devfeed.tech/tags/website.md>)

### AI overview

The article examines a proposed text-scale meta tag that would let websites respect system font-size settings. It compares behavior in Chrome, Chrome Canary, Firefox, and Safari, noting that the proposal currently works only in Chrome Canary and applies to text using relative units such as em and rem. It also warns that the feature may cause horizontal scrolling.

### Source excerpt

When you open the accessibility settings on your smartphone and increase the font size, you will immediately notice that the system font size increases. On Android, as a Firefox user, you will also notice that websites scale. As a Chrome user, you won't see any difference because Chrome doesn't respect the font size settings for web content. As an iOS user, it's the same. Comparison of Firefox, Chrome, and Safari with a large system font size. In a recent blog post by Josh Tumath, I learned about a proposal for a new meta tag that, in the future, may enable us to instruct browsers to respect text size settings on websites. <meta name="text-scale" content="scale" /> With the meta tag in place, text scales with the system settings (currently only in Chrome Canary). This only applies to text that uses relative units. In the screenshots below, you can see that the text size defined in pixels stays the same, while the text size defined in rem and em scales relative to the system font size. <div style="font-size: 16px;">My pixel test</div> <div style="font-size: 1em;">My em test</div> <div style="font-size: 1rem;">My rem test</div> A comparison of Chrome, which doesn't support the meta tag yet, Chrome Canary, and Firefox. You may notice that Firefox also scales the text defined in px. That's because Firefox doesn't just scale the text; it performs a full-page zoom, which is something completely different. To prove that I added a border to the body that changes color at different breakpoints. body { border-top: 20px solid var(--color, black); } @media (min-width: 200px) { body { --color: aqua; } } @media (min-width: 300px) { body { --color: fuchsia; } } @media (min-width: 400px) { body { --color: salmon; } } In Firefox, the border is aqua. Because of full-page scaling, it doesn't even reach the 300px breakpoint. Try it yourself Conclusion I understand why they made this an option rather than changing how browsers behaved by default, because it would break too many websites

## A Practical Look at the New HTML Geolocation Element

DevFeed: [A Practical Look at the New HTML Geolocation Element](<https://devfeed.tech/articles/introduction-to-the-new-html-element-52353.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/2026/geolocation-element>)

Author: Manuel Matuzović

Published: 2026-02-04T10:00:00Z

Content type: article

Language: en

Sources: [Manuel Matuzović](<https://devfeed.tech/sources/manuel-matuzovic-blog.md>)

Topics: [HTML](<https://devfeed.tech/topics/html.md>), [browser](<https://devfeed.tech/topics/browser.md>), [permission](<https://devfeed.tech/topics/permission.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [browser](<https://devfeed.tech/tags/browser.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [html](<https://devfeed.tech/tags/html.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [permission](<https://devfeed.tech/tags/permission.md>)

### AI overview

An overview of the new HTML <geolocation> element, including its permission flow, accuracy settings, privacy implications, JavaScript events, accessibility, and styling constraints. The article also reports limited testing with keyboard input, VoiceOver on macOS, and location updates while moving.

### Source excerpt

There is a new HTML element called geolocation. I checked it out and here's what I learned. The <geolocation> element The <geolocation> element provides a button that, when activated, prompts the user for permission to access their location. Originally, it was designed as a general <permission> element, but browser vendors indicated that implementing a "one-size-fits-all" element would be too complex. The result was a single-purpose element, probably the first of several. <geolocation> <strong>Your browser doesn't support &lt;geolocation&gt;. Try Chrome 144+</strong> </geolocation> Your browser doesn't support <geolocation>. Try Chrome 144+ When a user clicks the button, three things can happen: If they haven't granted permission yet, the browser will ask them for permission. If they have previously denied permission, they can undo it or keep denying. If they have granted permission already, clicking the button again will get the current location without re-prompting. It acts like a refresh button. Attributes Retrieving the user's location is the core functionality of the element, but you can adjust what and how you get it. accuracymode Using the accuracymode attribute, you can enable high accuracy to get the most accurate position. The result may be more precise, but it can also result in slower response times and increased power consumption. Another factor is privacy; if you don't need the user's exact position, it's probably best to leave it at the default (approximate). <geolocation accuracymode="precise"> Your browser doesn't support &lt;geolocation&gt;. </geolocation> When you set accuracymode to precise, the icon and button text change from a pin and "Use location" to a crosshair and "Use precise location". Your browser doesn't support <geolocation>. Try Chrome 144+ Note: You may notice that accuracymode="precise" gives you the same or even a worse result than the default setting. To see a difference, try the demo on a smartphone and outside of a building. au

## Lowering the specificity of multiple rules at once

DevFeed: [Lowering the specificity of multiple rules at once](<https://devfeed.tech/articles/lowering-the-specificity-of-multiple-rules-at-once-52358.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/2026/lowering-specificity-of-multiple-rules>)

Author: Manuel Matuzović

Published: 2026-01-20T15:00:00Z

Content type: tutorial

Language: en

Sources: [Manuel Matuzović](<https://devfeed.tech/sources/manuel-matuzovic-blog.md>)

Topics: [CSS](<https://devfeed.tech/topics/css.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>)

Tags: [cascade](<https://devfeed.tech/tags/cascade.md>), [css](<https://devfeed.tech/tags/css.md>), [layer](<https://devfeed.tech/tags/layer.md>), [selectors](<https://devfeed.tech/tags/selectors.md>), [specificity](<https://devfeed.tech/tags/specificity.md>), [usability](<https://devfeed.tech/tags/usability.md>)

### AI overview

This article explains how to lower the specificity of multiple CSS rules by placing them in an anonymous cascade layer instead of wrapping each selector in :where(). It covers precedence relative to unlayered rules, layer ordering, naming, and build-pipeline considerations.

### Source excerpt

You probably already knew that you can use :where() to lower the specificity of a single selector, but did you know that you can achieve a similar effect on multiple rules at once? The other day, I had an Aha! moment when someone suggested something I knew existed but hadn't considered using. In my reset style sheet UA+, I used :where() for combined selectors to keep specificity low. Here's an example: :where(abbr[title]) { cursor: help; text-decoration-line: underline; text-decoration-style: dotted; } Someone suggested using it everywhere for consistency and to achieve the lowest possible specificity for all rules. I liked the idea and wrapped all selectors in :where(). :where(h1) { font-size: 2em; margin-block: 0.67em; } This change improved usability but reduced readability. It was like that for a while until Emilio asked why I didn't wrap everything in an anonymous @layer instead. When I read his question, I needed some time to process because the solution felt so obvious, yet I was surprised I hadn't thought of it. @layer { abbr[title] { cursor: help; text-decoration-line: underline; text-decoration-style: dotted; } h1 { font-size: 2em; margin-block: 0.67em; } } Here are the things that went through my head when I saw Emilio's post: Using an anonymous layer without any other cascade layers Let's say you don't have any cascade layers in your CSS. By adding a third-party file containing all rules nested in a layer, all your rules will override the rules within that layer, since unlayered rules have precedence over layered ones. /* uaplus.css */ @layer { h1 { color: red; } } /* your.css */ h1 { color: blue; } /* Result: blue */ Of course, that's only the case as long as I'm not using !important in UA+. What's cool about this is that it doesn't even matter where or how you include the reset stylesheet. Normal unlayered rules always override normal layered rules. /* your.css */ h1 { color: blue; } /* uaplus.css */ @layer { h1 { color: red; } } /* Result: blue */ Usi

## My favourite front-end and web development conferences

DevFeed: [My favourite front-end and web development conferences](<https://devfeed.tech/articles/my-favourite-front-end-and-web-development-conferences-52359.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/2026/my-favorite-web-development-conferences>)

Author: Manuel Matuzović

Published: 2026-01-19T15:00:00Z

Content type: opinion

Language: en

Sources: [Manuel Matuzović](<https://devfeed.tech/sources/manuel-matuzovic-blog.md>)

Topics: [Web Development](<https://devfeed.tech/topics/web-development.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [CSS](<https://devfeed.tech/topics/css.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [browser](<https://devfeed.tech/topics/browser.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [browser](<https://devfeed.tech/tags/browser.md>), [conferences](<https://devfeed.tech/tags/conferences.md>), [css](<https://devfeed.tech/tags/css.md>), [development](<https://devfeed.tech/tags/development.md>), [front-end](<https://devfeed.tech/tags/front-end.md>), [web-development](<https://devfeed.tech/tags/web-development.md>)

### AI overview

The author shares a personal list of favorite front-end and web development conferences, highlighting events focused on web development, design, CSS, browser topics, accessibility, and community networking.

### Source excerpt

As someone who enjoys attending conferences, I thought it might be helpful to share a list of my favourite front-end and web development conferences. Smashing Conf 🇩🇪🇳🇱🇧🇪 I've been attending Smashing Conf for more than 10 years now. It's obviously one of my favourite events. It's a relatively small conference, the topics focus on web development and design, the atmosphere is fantastic, and you can learn a lot. Attend Smashing Conf to learn new web development and design techniques. Beyond Tellerrand 🇩🇪 Beyond Tellerrand is a one-of-a-kind event. It's not necessarily a web conference, but there are always several talks about web development. I would say the core topic of the event is design and creativity. Attend Beyond Tellerrand to meet like-minded people and get inspired. Fronteers Dark Mode 🇳🇱 I've never attended Fronteers Dark mode, but I did attend the original Fronteers conference, which I liked a lot. In terms of the topics and the atmosphere, it's very similar to Smashing Conf. Dark Mode is a spinoff from the original event and sounds super interesting. I definitely plan to attend it. Attend Fronteers Dark Mode to learn new web development and design techniques. CSS Day 🇳🇱 If you're into CSS, you would love CSS Day. It's two days focused on CSS with skilled and talented speakers from all around the world. What's great about CSS Day is the conversations you will have in between and after the talks, because there are so many smart and friendly people there who love CSS. Attend CSS Day if you want to learn a lot about CSS. I will be there this year. State of the Browser 🇬🇧 State of the Browser is a nice little community-driven web development conference, which I immediately fell in love with. High-quality talks, nice people, great atmosphere. Attend State of the Browser to learn new web development techniques. I will be there this year. A-Tag 🇦🇹 A-Tag is where the Austrian web accessibility community meets every year. It's the perfect event to stay up to date o

## Better defaults for popovers

DevFeed: [Better defaults for popovers](<https://devfeed.tech/articles/better-defaults-for-popovers-52350.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/2026/better-defaults-for-popovers>)

Author: Manuel Matuzović

Published: 2026-01-16T14:00:00Z

Content type: tutorial

Language: en

Sources: [Manuel Matuzović](<https://devfeed.tech/sources/manuel-matuzovic-blog.md>)

Topics: [CSS](<https://devfeed.tech/topics/css.md>), [dialog](<https://devfeed.tech/topics/dialog.md>), [HTML](<https://devfeed.tech/topics/html.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>), [Web platform](<https://devfeed.tech/topics/web-platform.md>)

Tags: [browser](<https://devfeed.tech/tags/browser.md>), [css](<https://devfeed.tech/tags/css.md>), [dialog](<https://devfeed.tech/tags/dialog.md>), [html](<https://devfeed.tech/tags/html.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

A CSS technique for improving popover defaults by aligning popovers with their triggering buttons using CSS anchor positioning. The article also shows how to add fallback positioning for viewport overflow and notes browser support considerations.

### Source excerpt

I recently added a rule to my reset style sheet UA+ that I wanted to share with you. When you add a popover to a page and open it, it looks similar to a dialog in terms of its styling. It's positioned at the center of the viewport. HTML Hypertext Markup Language (HTML) is the standard markup language for documents designed to be displayed in a web browser. That's okay, but I would argue that in most cases you want your popovers aligned closely with the button that controls them. As it turns out, that's super easy to achieve in browsers that support CSS anchor positioning, since popovers already have an implicit anchor. All you need to do is overwrite the margin property and position the popover. I'm wrapping the rule in a feature query to ensure the margin isn't reset in browsers that don't support CSS anchor positioning (At the time of writing, most importantly Safari). @supports(position-area: end) { [popover] { margin: 0; position-area: end span-end; position-try-fallbacks: flip-block, flip-inline, flip-block flip-inline; } } If you're in Chrome or Firefox, you should see the popover aligned and the bottom left (or right for RTL) edge of the button. HTML Hypertext Markup Language (HTML) is the standard markup language for documents designed to be displayed in a web browser. You can also add position-try-fallbacks: flip-block, flip-inline, flip-block flip-inline;, as I did here, to tell the popover to try flipping its position along the inline and block axis if it overflows the viewport in its initial position (Thanks, Temani, for the hint). Nice and easy, and it's a much better default. My blog doesn't support comments yet, but you can reply via blog@matuzo.at.

## Workshop: Deep Dive on Accessibility Testing

DevFeed: [Workshop: Deep Dive on Accessibility Testing](<https://devfeed.tech/articles/workshop-deep-dive-on-accessibility-testing-52365.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/2026/workshop-deep-dive-on-accessibility-testing>)

Author: Manuel Matuzović

Published: 2026-01-13T13:45:00Z

Content type: tutorial

Language: en

Sources: [Manuel Matuzović](<https://devfeed.tech/sources/manuel-matuzovic-blog.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [Developer Tools](<https://devfeed.tech/topics/developer-tools.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [accessibility-testing](<https://devfeed.tech/tags/accessibility-testing.md>), [automated](<https://devfeed.tech/tags/automated.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [build](<https://devfeed.tech/tags/build.md>), [command-line](<https://devfeed.tech/tags/command-line.md>), [deep-dive](<https://devfeed.tech/tags/deep-dive.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [testing](<https://devfeed.tech/tags/testing.md>), [web-accessibility](<https://devfeed.tech/tags/web-accessibility.md>), [workflow](<https://devfeed.tech/tags/workflow.md>), [workshop](<https://devfeed.tech/tags/workshop.md>)

### AI overview

A five-day workshop on web accessibility testing covers automatic and manual testing, accessibility tools, keyboard and screen reader testing, Single Page Applications, command-line test execution, automated reports, and build-pipeline integration.

### Source excerpt

Once again, I've teamed up with my friends at Smashing Magazine 😻 to share with you everything I know about web accessibility testing! In this smashing workshop we'll talk about automatic and manual testing, screen reader basics, Single Page Applications, Dev Tools, and more. What you will learn in this workshop Which testing tools are available and most commonly used. How to assess the accessibility of a component or page. The difference between automatic and manual testing. How to use automatic accessibility testing tools and how to interpret the results. How to use the keyboard to discover accessibility bugs. Screen reader basics and how to use them for accessibility testing, both on desktop and mobile devices. How to test the accessibility of Single Page Applications. Common pitfalls of Single Page Applications and how to avoid them. How to integrate accessibility testing in your day-to-day development workflow. Running tests on the command line and creating automated reports. Integrating accessibility testing in your build pipeline. Where to find information and help on how to build complex components. Time and schedule This workshop is split over five days. The workshop sessions will run on the following days: Mon, January 19, 9:00 - 11:30 AM PT (18:00 - 20:30 CET) Tue, January 20, 9:00 - 11:30 AM PT (18:00 - 20:30 CET) Mon, January 26, 9:00 - 11:30 AM PT (18:00 - 20:30 CET) Tue, January 27, 9:00 - 11:30 AM PT (18:00 - 20:30 CET) Mon, February 2, 9:00 - 11:30 AM PT (18:00 - 20:30 CET) Ticket Get your ticket with 15% off on the Smashing Magazine website! If you have any questions about the workshop, feel free to get in touch via mail. I hope to see you soon! My blog doesn't support comments yet, but you can reply via blog@matuzo.at.

## I'm speaking at Web Day Out 2026

DevFeed: [I'm speaking at Web Day Out 2026](<https://devfeed.tech/articles/i-m-speaking-at-web-day-out-2026-52345.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/2025/web-day-out-2026>)

Author: Manuel Matuzović

Published: 2025-12-05T13:13:00Z

Content type: news

Language: en

Sources: [Manuel Matuzović](<https://devfeed.tech/sources/manuel-matuzovic-blog.md>)

Topics: [Web platform](<https://devfeed.tech/topics/web-platform.md>), [CSS](<https://devfeed.tech/topics/css.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [blog](<https://devfeed.tech/tags/blog.md>), [css](<https://devfeed.tech/tags/css.md>), [event](<https://devfeed.tech/tags/event.md>), [web](<https://devfeed.tech/tags/web.md>), [web-platform](<https://devfeed.tech/tags/web-platform.md>)

### AI overview

An announcement for the first Web Day Out conference, taking place in Brighton on March 12, 2026. The event will cover current web platform features, with a focus on CSS, and will include eight speakers.

### Source excerpt

The first Web Day Out conference is taking place next year on March 12, my birthday, in Brighton, and I'm one of eight speakers. The core idea of the event is to get you up to speed on the most powerful web platform features that you can use right now. I love that because it aligns perfectly with what I've been working on over the last couple of years: finding ways to break old habits to get the most out of CSS. The seven other speakers are Jemima Abu, Rachel Andrew, Jake Archibald, Aleth Gueguen, Lola Odelola, Harry Roberts, and Richard Rutter. Let me tell you, that's a great lineup! You can use the discount code JOIN_MANUEL to save 10% off the original price. I'm super excited for this event, and I'm looking forward to meeting you there. My blog doesn't support comments yet, but you can reply via blog@matuzo.at.

## Dealbreaker bugs in native popovers

DevFeed: [Dealbreaker bugs in native popovers](<https://devfeed.tech/articles/dealbreaker-bugs-in-native-popovers-52337.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/2025/deal-breaker-bugs-in-popovers>)

Author: Manuel Matuzović

Published: 2025-12-05T00:00:00Z

Content type: article

Language: en

Sources: [Manuel Matuzović](<https://devfeed.tech/sources/manuel-matuzovic-blog.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [bug](<https://devfeed.tech/topics/bug.md>), [HTML](<https://devfeed.tech/topics/html.md>), [browser](<https://devfeed.tech/topics/browser.md>), [Web Components](<https://devfeed.tech/topics/web-components.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [Firefox](<https://devfeed.tech/topics/firefox.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [browser](<https://devfeed.tech/tags/browser.md>), [browser-bugs](<https://devfeed.tech/tags/browser-bugs.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [firefox](<https://devfeed.tech/tags/firefox.md>), [html](<https://devfeed.tech/tags/html.md>), [keyboard](<https://devfeed.tech/tags/keyboard.md>), [web-components](<https://devfeed.tech/tags/web-components.md>)

### AI overview

An accessibility bug in native HTML popovers causes keyboard focus to skip focusable elements when popovers contain slots or a details element. The issue affects Chromium-based browsers and Firefox versions below 145, creating problems for reusable web-component pattern libraries.

### Source excerpt

One of my clients decided to write a custom popover component that uses native popovers under the hood. We built the component and were happy with it. They were about to ship it until we realised there was an accessibility bug so severe that it was a dealbreaker for us. Popovers are floating UI elements you can show or hide by pressing a button. They come with many accessibility features built in, so you don't have to handle most of the work. You can learn more about that in "The accessibility of the popover attribute" (YouTube). All you need to use popovers is the popover and popovertarget attributes. <button popovertarget="popover-html">HTML</button> <div popover id="popover-html"> Hypertext Markup Language (HTML) is the standard markup language for documents designed to be displayed in a web browser. </div> Try it yourself: HTML Hypertext Markup Language (HTML) is the standard markup language for documents designed to be displayed in a web browser. Bugs Popovers can contain focusable elements, such as buttons. In the following example, if you use the keyboard and focus the first button, press Enter, and press Tab again, you can see how focus jumps from the trigger to the first button inside the popover. By pressing tab repeatedly, you can move from button to button until you finally reach the next button outside the popover. <p> <button popovertarget="popover-buttons">First Button</button> <button>Second Button</button> </p> <div popover id="popover-buttons"> <button>Focusable</button> <button>Focusable</button> <button>Focusable</button> </div> First Button Second Button Focusable Focusable Focusable That works as long as you don't use slots or the details element inside your popovers. If you do, focus will still move from the trigger to the first button inside the popover, but if you press Enter, focus doesn't jump to the next focusable element inside the popover; it skips all remaining elements, leaves the popover, and then jumps to the next button outside the

## What's an interactive element?

DevFeed: [What's an interactive element?](<https://devfeed.tech/articles/what-s-an-interactive-element-52346.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/2025/whats-an-interactive-element>)

Author: Manuel Matuzović

Published: 2025-10-24T00:00:00Z

Content type: opinion

Language: en

Sources: [Manuel Matuzović](<https://devfeed.tech/sources/manuel-matuzovic-blog.md>)

Topics: [HTML](<https://devfeed.tech/topics/html.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>), [Web platform](<https://devfeed.tech/topics/web-platform.md>), [web-standards](<https://devfeed.tech/topics/web-standards.md>)

Tags: [article](<https://devfeed.tech/tags/article.md>), [blog-post](<https://devfeed.tech/tags/blog-post.md>), [html](<https://devfeed.tech/tags/html.md>), [opinions](<https://devfeed.tech/tags/opinions.md>)

### AI overview

A blog post examines whether the HTML dialog element should use the tabindex attribute, arguing that MDN's warning and usage note describe the element's focus behavior and interactivity inaccurately. It distinguishes the HTML specification's prohibition from the practical behavior observed by the author.

### Source excerpt

Two years ago, I wrote an article about the dialog element. I tested where focus goes when you open a modal dialog via the showModal() method. I tried different combinations of elements and attributes to see what happens because back in 2023, the behaviour was very inconsistent. In one of my tests, I put the tabindex attribute on the dialog element. That's why Joy contacted me earlier this week, because she was unsure whether this was a good idea since the page on MDN about the dialog element says the following: And here's the usage note: Do not add the tabindex property to the <dialog> element as it is not interactive and does not receive focus. The dialog's contents, including the close button contained in the dialog, can receive focus and be interactive. I recommended to ignore this warning and I also promised to give a proper, more detailed answer in a blog post. Disclaimer Before I share my opinions with you, let me clarify that this post is not about MDN. MDN is one of the few websites I visit every day, and I'm a big fan. I also understand that the content is open source and a community effort. One will likely disagree with some opinions at some point. Using tabindex on the dialog element I couldn't stop thinking about this warning the entire week because I don't understand why the authors put so much emphasis on it. There is this big fat red warning early on the page saying that you must not use the tabindex attribute on the dialog element. I know where this is coming from. In the HTML spec for the dialog element it says: The tabindex attribute must not be specified on dialog elements. So, technically, they're right because the spec says that you must not use the tabindex attribute on the dialog element. I don't understand why, though, or at least I don't understand the phrasing, because it's absolutely fine to use the tabindex attribute on the dialog element. It doesn't break anything. The only reason I can think of not to use it is that it's not necessary.

## A workaround for using custom properties in media queries

DevFeed: [A workaround for using custom properties in media queries](<https://devfeed.tech/articles/a-workaround-for-using-custom-properties-in-media-queries-52347.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/2025/workaround-for-custom-properties-in-media-queries>)

Author: Manuel Matuzović

Published: 2025-10-22T00:00:00Z

Content type: article

Language: en

Sources: [Manuel Matuzović](<https://devfeed.tech/sources/manuel-matuzovic-blog.md>)

Topics: [Media Queries](<https://devfeed.tech/topics/media-queries.md>), [Responsive Design](<https://devfeed.tech/topics/responsive-design.md>)

Tags: [custom-properties](<https://devfeed.tech/tags/custom-properties.md>), [media-queries](<https://devfeed.tech/tags/media-queries.md>), [workaround](<https://devfeed.tech/tags/workaround.md>)

### AI overview

The excerpt shows a CSS workaround for applying a custom-property breakpoint through a style container query. It registers `--inline-size-s` with `@property`, defines it as the smaller of `--breakpoint-s` (`48em`) and `100vi`, then uses `@container style()` to change the body background when the inline-size value matches that breakpoint. The text is a sneak peek and does not explain broader support requirements or limitations.

### Source excerpt

I'm a big fan of custom properties and I use them almost everywhere. One of the places where I'd love to use them, but can't, is with media queries. I came up with a workaround and wrote about it on Piccalilli. Here's a sneak peek: @property --inline-size-s { syntax: "<length-percentage>"; inherits: true; initial-value: 100vi; } :root { --breakpoint-s: 48em; --inline-size-s: min(var(--breakpoint-s), 100vi); } body { background-color: var(--bg-color); --bg-color: oklch(0.94 0.01 99); @container style(--inline-size-s: var(--breakpoint-s)) { --bg-color: oklch(0.87 0.21 95.82); } } My blog doesn't support comments yet, but you can reply via blog@matuzo.at.

## Never lose a z-index battle again

DevFeed: [Never lose a z-index battle again](<https://devfeed.tech/articles/never-lose-a-z-index-battle-again-52342.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/2025/never-lose-a-z-index-battle-again>)

Author: Manuel Matuzović

Published: 2025-04-11T00:00:00Z

Content type: tutorial

Language: en

Sources: [Manuel Matuzović](<https://devfeed.tech/sources/manuel-matuzovic-blog.md>)

Topics: [CSS](<https://devfeed.tech/topics/css.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>)

Tags: [background](<https://devfeed.tech/tags/background.md>), [calc](<https://devfeed.tech/tags/calc.md>), [css](<https://devfeed.tech/tags/css.md>), [position](<https://devfeed.tech/tags/position.md>), [z-index](<https://devfeed.tech/tags/z-index.md>)

### AI overview

This tutorial explains how CSS's infinity keyword in calc() can be used as a very large z-index value. It also describes the signed 32-bit limits of z-index and how ties are resolved by document order.

### Source excerpt

Recently, I learned about numeric keywords. Since I was terrible in school, I didn't know what to do with them, but when I saw infinity, I immediately thought of a great use case. According to the spec, the infinity keyword in the calc() function can be used to indicate the largest possible value of something since an infinite value gets clamped to the allowed range. For example, you can set an element's largest possible inline size. CSS button { inline-size: calc(infinity * 1px); } Really large button Of course, that's not the great use case I'm talking about. Infinity can be super helpful when you want to ensure an element is at the top of the z-axis. HTML <button class="a">A</button> <button class="b">B</button> CSS button { position: absolute; } button.a { z-index: calc(infinity); background: green; } button.b { z-index: 2147483646; background: blue; } A B You can see how the first button with calc(infinity) set as the z-index is above the button with z-index: 2147483646;. 2147483646 is not an arbitrary number; it's the second-largest possible z-index. A z-index can be any signed 32-bit integer value, ranging from −2,147,483,648 through 2,147,483,647. If you change the value of the second button to 2147483647, it's on top of the first button because 2147483647 and infinity are the same in this case and the second button comes later in the document. button { position: absolute; } button.a { z-index: calc(infinity); background: green; } button.b { z-index: 2147483647; background: blue; } A B Changing the z-index to calc(infinity + 1) or 2147483648 doesn't make a difference because we've already reached the limit with 2147483647 or calc(infinity). button { position: absolute; } button.a { z-index: calc(infinity + 1); background: green; } button.b { z-index: 2147483647; background: blue; } A B Credit for the title of this blog post goes to Will Boyd My blog doesn't support comments yet, but you can reply via blog@matuzo.at.

[Next page](<https://devfeed.tech/sources/manuel-matuzovic-blog.md?cursor=WyIyMDI1LTA0LTExVDAwOjAwOjAwKzAwOjAwIiwgIjYwMWQ1ZmVkLTUwMDAtNDAxZi04NzY5LTc3YzUxNzk2NzRkMSJd>)