Best of Accessibility — February 2026

  1. 1
    Article
    Avatar of mondaymonday Engineering·11w

    How We Use AI to Turn Figma Designs into Production Code

    Monday.com built an AI-powered system to convert Figma designs into production-ready code that adheres to their design system. Instead of directly generating code, they created a design-system MCP (Model Context Protocol) that exposes structured knowledge about components, tokens, and accessibility rules. An agentic workflow built with LangGraph breaks down design-to-code into 11 focused steps, analyzing layout, resolving tokens, identifying components, and planning implementation. The agent returns structured context rather than code, allowing different teams to generate code in their own style while ensuring design system compliance, accessibility, and proper component usage from the start.

  2. 2
    Article
    Avatar of lobstersLobsters·8w

    Death to Scroll Fade!

    A developer rant against the ubiquitous 'scroll fade' web design trend, where page elements fade in as they scroll into view. The author argues it's tacky, often demanded last-minute by stakeholders, and raises real concerns: accessibility issues for users with vestibular disorders, cognitive overload, cross-platform inconsistency, and negative impact on Core Web Vitals like LCP. The post crowdsources practical arguments to push back against scroll fade requests, while humorously suggesting developers collectively pretend the technique is now illegal.

  3. 3
    Article
    Avatar of cloudflareCloudflare·7w

    The most-seen UI on the Internet? Redesigning Turnstile and Challenge Pages

    Cloudflare serves 7.67 billion Turnstile widget and Challenge Page impressions daily, making it arguably the most-seen UI on the Internet. A comprehensive redesign effort addressed inconsistent visual language, overly technical error messages, alarming red backgrounds, and poor accessibility. Key changes include a unified information architecture across both products, simplified error states with a dedicated troubleshooting modal, WCAG 2.2 AAA accessibility compliance, and careful internationalization across 38+ languages. User testing with 8 participants across 8 countries validated design decisions, including keeping distinct state-specific copy over competitor-style static labels. On the engineering side, the team works in Rust rather than JavaScript frameworks, requiring manual DOM manipulation and extra care for RTL language support and locale-aware numbering. Success is being measured via challenge solve rate, time to complete, abandonment rate, support ticket volume, and social sentiment.

  4. 4
    Article
    Avatar of css_tricksCSS-Tricks·8w

    Potentially Coming to a Browser :near() You

    A deep dive into the proposed CSS :near() pseudo-class, which would match elements when the pointer is within a specified distance. The article explores practical use cases like dimming/hiding elements until proximity, prefetching via the Speculation Rules API, and improving hover-triggered overlays with the Interest Invoker API. Since :near() isn't browser-supported yet, demos simulate the behavior using padding, content-visibility, contain-intrinsic-size, and animation tricks. Accessibility concerns around WCAG criteria for focus visibility and target size are also discussed, along with potential abuses like fingerprinting and performance issues.

  5. 5
    Article
    Avatar of kittygiraudelKitty says hi.·7w

    Nerdy Design Details

    A personal blog post detailing CSS and design improvements made to a personal website. Covers a tri-state dark/light/auto theme switcher using aria-pressed, fluid typography with min/max/vw, styled blockquotes and callouts with gradient borders using background-clip tricks, typographic fleurons as decorative elements, squircle corners via the new CSS corner-shape property, improved focus styles with outline and scroll-margin-top, and smarter ad placement using Liquid templating and :has() CSS selector.

  6. 6
    Article
    Avatar of allthingsopenAll Things Open·10w

    Why 1.3 billion people depend on progress, not perfection

    GitHub is investing in open source accessibility to help 1.3 billion people with disabilities. The initiative focuses on three key areas: fixing foundational open source projects to create a multiplier effect downstream, enabling disabled developers to contribute and build careers, and supporting custom assistive technology development. GitHub's Open Source Accessibility Summit attracted 800 registrants, demonstrating strong community demand. The work emphasizes incremental progress over perfection, with resources available at gh.io/open-source-accessibility for developers at all skill levels to contribute.

  7. 7
    Video
    Avatar of wdsWeb Dev Simplified·8w

    Top 17 Accessibility Features No One Knows About

    A practical deep-dive into 17 lesser-known web accessibility features that most developers overlook. Topics covered include: using `aria-describedby` and `aria-live` (with `aria-atomic` and `aria-relevant`) for dynamic form errors and toast notifications; the `inert` HTML attribute to prevent keyboard focus on off-screen or hidden content like drawers and modals; proper `autocomplete` attribute values for form inputs; minimum touch target sizes (24×24px recommended, 44×44px ideal); avoiding ARIA role overrides when native HTML elements suffice; skip-to-main-content links; dyslexia-friendly fonts; and the importance of keeping visual CSS order aligned with HTML DOM order for correct tab navigation. The testing section covers Chrome DevTools rendering emulation (color blindness, reduced motion, contrast, font scaling), Lighthouse accessibility audits, and color contrast ratio checking.

  8. 8
    Video
    Avatar of kevinpowellKevin Powell·8w

    5 CSS fouls that I see way too often

    Five common CSS mistakes that even experienced developers make: (1) Useless declarations like unnecessary `width: 100%` that can cause overflow issues with margins or in flex/grid contexts. (2) Being overly prescriptive with fixed heights instead of using `min-height` or `max-width` to work with browser defaults. (3) Poor code organization and failing to refactor duplicated styles. (4) Removing focus outlines with `outline: none` instead of using `:focus-visible`, which breaks keyboard navigation accessibility. (5) Overusing flexbox or grid when the other layout tool would be more appropriate, a pattern increasingly seen in AI-generated CSS.

See all Accessibility archives