How Shadow DOM Breaks Screen Reader Accessibility and Ways to Fix It

·1 views

Web components built with Shadow DOM can appear visually flawless yet remain largely invisible or confusing to screen readers, because browsers construct a separate accessibility tree that does not always expose a shadow root's internals correctly. A developer discovered this while testing a custom dropdown with VoiceOver and NVDA, finding that ARIA roles set inside the shadow root were ignored and keyboard focus behaved unpredictably. The root cause lies in how browsers treat shadow boundaries differently from standard light DOM when building the accessibility tree, with behavior varying across browsers and assistive technologies. Practical fixes include creating shadow roots with the delegatesFocus option, applying explicit ARIA roles such as listbox and option to internal elements, and using aria-hidden to conceal purely decorative nodes. Using native HTML semantics wherever possible inside shadow components is also recommended, as ARIA attributes alone cannot fully compensate for poor structural exposure.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Dev team shipped and pulled a guest play feature within 56 minutes after spotting a flaw

A software team at a quiz or practice-game platform launched a guest play feature allowing signed-out users to try one free game per provider, only to remove it 56 minutes later. The feature broke immediately because question banks had recently been moved behind an authenticated API route, causing guests to hit a 401 error and see a loading spinner instead of content. Two potential fixes — opening the bank route publicly or mapping free games to specific banks — were both rejected as unreliable or counterproductive. The team instead built a short-lived signed permit system to grant guests temporary access to question banks, a solution they considered well-designed. However, building that workaround made it clear the overall guest play approach was too complex, prompting them to delete the feature and require account creation for game access.

0 comments Read more at DEV Community

ProgrammingHacker News ·

NEC V20 CPU Upgrade Offers Performance Boost for Vintage IBM XT PCs

The NEC V20 is a drop-in CPU replacement for the Intel 8088 found in classic IBM XT-class personal computers. The chip, manufactured by NEC, offered modest but measurable speed improvements over the original Intel processor it was designed to replace. It achieved this through a more efficient internal architecture while maintaining full compatibility with existing 8088 software. The upgrade was popular among vintage PC enthusiasts seeking a simple, low-cost way to improve system performance. The topic resurfaced on Hacker News, attracting discussion among retro computing fans.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

kern: Open-Source Tool Maps Codebases Locally for AI Agents via AST Analysis

Developer Jayveer Prajapati has released kern, a free open-source tool that builds a local Abstract Syntax Tree index of code repositories to give AI agents like Claude and Cursor precise, context-aware code insights. The tool integrates with AI workflows through the Model Context Protocol and runs entirely on the user's machine, eliminating cloud data exposure and API costs. kern detects over 74 programming frameworks and uses native AST parsing to map call paths, identify dead code, and flag architectural issues without relying on regex guesswork. It also includes a reusable GitHub Action that calculates a mathematical risk score for pull requests and can automatically block high-risk merges before they reach production. Users can set up and index a project with a few commands, and the tool tracks token and cost savings natively through built-in analytics commands.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Guide Shows How to Build a Self-Healing Web Data Pipeline with Node.js and Bright Data

A developer tutorial published on DEV Community outlines how to construct a modular, AI-ready web data pipeline using Node.js and Bright Data's Scraper Studio. The guide uses a Texas real-estate listing tracker on HAR.com as a practical example, demonstrating live data collection filtered by city and bedroom count with price-change detection over time. The architecture separates web extraction from application logic into two distinct layers, so the pipeline can be repaired when a target site changes without rewriting core application code. This separation follows the Dependency Inversion and Ports-and-Adapters design principles, ensuring the Node.js layer interacts only with a stable data contract rather than raw HTML or DOM structure. The tutorial claims the same pipeline design can be reused across domains such as e-commerce, job boards, and financial data monitoring.

0 comments Read more at DEV Community