Best of Accessibility — March 2026

  1. 1
    Article
    Avatar of nuxt_sourceNuxt·5w

    Nuxt 4.4 · Nuxt Blog

    Nuxt 4.4 ships several developer experience and performance improvements. Key additions include createUseFetch/createUseAsyncData factories for custom composable instances with typed defaults, an upgrade to vue-router v5 (dropping unplugin-vue-router), typed layout props via definePageMeta, and a new useAnnouncer composable for accessibility announcements. Route generation migrates to the unrouting library using a trie structure, delivering up to 28x faster dev server updates. Smarter payload handling for cached/ISR routes reduces redundant SSR re-renders in serverless environments. Other highlights: useCookie refresh option for session expiration, useState reset-to-default behavior, improved import protection with traces and suggestions, view transition types support, build profiling via nuxt build --profile, and a 14,000x faster module ID parsing optimization.

  2. 2
    Article
    Avatar of gitlabGitLab·5w

    Navigate repositories faster with the file tree browser

    GitLab 18.9 introduces a collapsible, resizable file tree browser panel in the repository view, bringing an IDE-like navigation experience to the web interface. The panel stays visible alongside file and directory views, expands parent directories automatically when navigating to nested files, and syncs with the current location. Key features include keyboard-first navigation following the W3C ARIA treeview pattern, filename filtering via a global search dialog, responsive behavior across desktop and mobile viewports, and pagination support for large repositories. Available now on GitLab.com, Self-Managed, and Dedicated.

  3. 3
    Article
    Avatar of smashingSmashing Magazine·6w

    Getting Started With The Popover API — Smashing Magazine

    A developer shares their experience migrating tooltip implementations from JavaScript libraries to the browser-native Popover API. The Popover API handles keyboard interactions (including Escape key), ARIA state synchronization, and focus management automatically through HTML attributes like `popover`, `popovertarget`, and `popovertargetaction`. The author details accessibility improvements gained for free, remaining gaps (hover timing delays, manual focus restoration for `popover="manual"`), and when tooltip libraries like Floating UI still make sense — complex positioning, large design systems, or teams lacking accessibility expertise. CSS anchor positioning is also highlighted as an emerging complement to the API.

  4. 4
    Article
    Avatar of sitepointSitePoint·5w

    There Is No “Wrong” in CSS

    There is no objectively "wrong" CSS, and four reasons support this claim. First, if CSS works without practical disadvantages, there's no reason to change it, especially given the web platform's strong backwards-compatibility guarantees. Second, any consequences of suboptimal CSS fall on the developer or organization, making it their call to address. Third, CSS is easy to refactor when a better approach is needed, so no mistake is truly grave. Fourth, when CSS creates real barriers for users, that's arguably a platform-level responsibility rather than a developer failure. CSS advice should always be understood as context-dependent guidance, not universal law — and distinguishing advice from dogma is key to evaluating criticism of your code.

  5. 5
    Article
    Avatar of tkdodoTkDodo·3w

    Test IDs are an a11y smell

    Using data-testid attributes in tests is an accessibility smell because users can't see or interact with test IDs. Role-based selectors (via Testing Library or Playwright) are superior because they mirror how real users interact with apps, catch inaccessible markup like clickable divs lacking semantic roles, and provide implicit a11y testing. If a role-based selector can't find an element, that's a signal the UI itself is inaccessible. Practical tips include using semantic HTML for implicit ARIA roles, associating form labels, using headings and landmarks, leveraging Testing Playground, and navigating with the keyboard to catch issues.

  6. 6
    Article
    Avatar of lnLaravel News·4w

    Lens for Laravel Brings WCAG Auditing to Your Local Dev Workflow

    Lens for Laravel is a dev-only package that scans Laravel applications for WCAG accessibility violations using Axe-core and a headless Chromium browser. It maps each issue back to the specific Blade template file and line number, and provides a web dashboard, an Artisan CLI command for CI/CD integration, and optional AI-assisted fix suggestions via Gemini, OpenAI, or Anthropic. The dashboard supports single-page, multi-URL, and full-site crawl audits, groups results by WCAG level (A, AA, AAA), and can export PDF reports. The package is restricted to local environments by default. Automated scanning catches roughly 20–30% of WCAG violations, so manual testing remains necessary for full compliance.

  7. 7
    Article
    Avatar of netguruNetguru·5w

    Silk Design System Documentation

    Silk is a free, open design system by Netguru built for mobile and responsive web in Figma. The documentation covers full setup (publishing Phosphor icons and Silk libraries), and deep customization across colors (built-in palette swapping and custom palette generation using AI prompts), typography (font families, sizes, weights, line heights), iconography, shapes, spacing, grid/layout, and component architecture. It also details naming conventions, component property patterns, and WCAG 2.2 AA accessibility requirements for building or extending components.

See all Accessibility archives