# A11y for developers Published articles for A11y for developers. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Find Label in Name issues in every scan with Axe-core 4.14.0 DevFeed: [Find Label in Name issues in every scan with Axe-core 4.14.0]() Original publisher: [Read original article]() Author: Wilco Fiers Published: 2026-10-22T13:01:23Z Content type: release Language: en Sources: [Deque]() Topics: [axe-core](), [Web Accessibility (a11y)](), [Web Content Accessibility Guidelines](), [EN 301 549]() Tags: [a11y-for-developers](), [accessibility](), [accessibility-compliance](), [accessibility-guidelines](), [assistive-technology](), [automated](), [axe-core](), [en-301-549](), [eu](), [release](), [standard](), [support](), [web-content-accessibility-guidelines]() ### AI overview Axe-core 4.14.0 turns on the Label in Name check by default: scans now report controls whose accessible name omits visible label text, under `label-content-name-mismatch`. The rule compares word by word, ignores parenthetical text, and supports CJK scripts and full-width characters. Tests found that voice-control tools respond to accessible names; Dragon also responds to visible text. Most tested tools accept visible text anywhere in the accessible name, while macOS requires an exact match and iOS requires it at the start, so passing WCAG's inclusion rule may not work with Apple Voice Control. Deque plans a separate best-practice rule. The release also reports scans 20-40% faster on most pages (up to 15 times faster on especially large pages), clearer rule messages, and several false-positive fixes. It adds EN 301 549 v4 tags to the target-size rule; the broader rule set was described as coming in November. Issue totals may rise as new findings are reported. ### Source excerpt With our latest update, when you scan with Axe-core 4.14.0, you'll now get a result for any control whose accessible name doesn't contain its visible label. This Axe-core release also speeds up scans, makes fix instructions clearer, and begins support for EN 301 549 v4.1.1, the pending update to the European Union's (EU) harmonized standard for accessibility requirements. The post Find Label in Name issues in every scan with Axe-core 4.14.0 appeared first on Deque. ## Debunking AI agent accessibility claims and solving AI alignment for accessibility DevFeed: [Debunking AI agent accessibility claims and solving AI alignment for accessibility]() Original publisher: [Read original article]() Author: Dylan Barrell Published: 2026-10-21T14:11:48Z Content type: opinion Language: en Sources: [Deque]() Topics: [ai alignment](), [Web Accessibility (a11y)](), [Test automation](), [AI Agent](), [axe MCP Server](), [aria]() Tags: [a11y-for-developers](), [accessibility](), [accessibility-best-practices](), [agent](), [ai](), [ai-agent](), [ai-alignment](), [ai-powered](), [alignment](), [approach](), [automated-accessibility-testing](), [automation](), [based](), [best](), [can](), [first](), [gap](), [gives](), [intelligent-guided-tests](), [reliability](), [rules](), [testing](), [this](), [velocity]() ### AI overview The article argues that AI agents' reports of successful work can diverge from what they actually did, so accessibility checks should not rely on one agent validating another. It proposes a deterministic harness that limits AI to focused tasks, such as interpreting semantics or judging equivalence, while rules control test scope and determine pass or fail. The harness records evidence that can be audited. Deque's Intelligent Guided Tests use this approach: for a dialog, rules check markup while an IGT opens and closes it to observe keyboard focus, then a person confirms the result. The article says this can reduce a manual check from 30-45 minutes to seconds; it does not remove the human confirmation step. ### Source excerpt There is a digital accessibility approach that gives us the best of both worlds: the reliability and predictability of rules-based testing and the velocity of AI-powered automation. By taking this approach, we can close the gap between presumed and actual accessibility. The post Debunking AI agent accessibility claims and solving AI alignment for accessibility appeared first on Deque. ## How to test MCP Apps for accessibility, and why it matters DevFeed: [How to test MCP Apps for accessibility, and why it matters]() Original publisher: [Read original article]() Author: Harris Schneiderman Published: 2026-10-01T13:33:34Z Content type: tutorial Language: en Sources: [Deque]() Topics: [User interface design](), [Web Content Accessibility Guidelines](), [axe DevTools](), [axe MCP Server](), [MSP MCP]() Tags: [a11y-for-developers](), [accessibility](), [accessibility-testing](), [ai](), [how-to](), [mcp](), [web]() ### AI overview The tutorial explains how to test MCP Apps for accessibility by replaying host messages with a local stub host, making app states addressable through fixture URLs, and scanning each state with accessibility tools. It also covers keyboard access, headings, color and contrast, safe-area insets, and media query behavior. ### Source excerpt MCP Apps are still new enough that whatever approaches we can establish now will be the ones that stick over the long term. Which means if we can get accessibility right at this stage, it will stay right as the ecosystem grows. This is how we can avoid introducing the same problems we've had to deal with across the rest of the web for so long. The post How to test MCP Apps for accessibility, and why it matters appeared first on Deque. ## Automated Intelligent Guided Tests bring accessibility testing into developers' coding environments DevFeed: [Automated Intelligent Guided Tests bring accessibility testing into developers' coding environments]() Original publisher: [Read original article]() Author: Harris Schneiderman Published: 2026-09-21T12:48:01Z Content type: article Language: en Sources: [Deque]() Topics: [Automation](), [axe MCP Server](), [Model Context Protocol](), [User interface design]() Tags: [a11y-for-developers](), [accessibility](), [accessibility-automation](), [accessibility-testing](), [automation](), [axe-mcp-server](), [developer](), [intelligent-guided-test](), [mcp]() ### AI overview The article explains how Deque's automated Intelligent Guided Tests use the Axe MCP Server to run accessibility tests within a developer's coding environment. The tests automate actions and assessments such as keyboard-focus checks, image-meaning judgments, and accessible-name evaluation while allowing humans to confirm or override conclusions. ### Source excerpt Automated IGTs run through the Axe MCP Server, which puts them inside the environment where code is being written, so a developer can run a guided test and get remediation guidance without leaving their editor. The post Intelligent automation and the new era of guided testing appeared first on Deque. ## Test your custom elements and trust the results with Axe-core's support for ElementInternals DevFeed: [Test your custom elements and trust the results with Axe-core's support for ElementInternals]() Original publisher: [Read original article]() Author: Wilco Fiers Published: 2026-08-27T13:21:18Z Content type: article Language: en Sources: [Deque]() Topics: [Web Accessibility (a11y)](), [axe-core](), [interoperability](), [Front end](), [browser](), [Angular](), [React](), [Vue.js](), [aria]() Tags: [a11y-for-developers](), [accessibility](), [angular](), [aria](), [axe-core](), [browser](), [compliance](), [frontend](), [interoperability](), [react](), [testing](), [vue](), [web-accessibility]() ### AI overview The article explains how custom elements and ElementInternals can standardize components across React, Angular, and Vue while allowing components to declare accessibility semantics. It highlights axe-core support for ElementInternals, enabling teams to test accessibility consistently across framework implementations and support compliance at enterprise scale. ### Source excerpt If you're a large enterprise organization with accessibility issues resulting from interoperability challenges, moving to ElementInternals is a savvy move. You can standardize, and safely test. And, with Axe-core now supporting ElementInternals, you can test those components and trust the results. The post Test your custom elements and trust the results with Axe-core's support for ElementInternals appeared first on Deque. ## The anatomy of accessible forms: Required form fields DevFeed: [The anatomy of accessible forms: Required form fields]() Original publisher: [Read original article]() Author: Aparna Pasi Published: 2026-08-06T15:47:31Z Content type: article Language: en Sources: [Deque]() Topics: [Web Accessibility (a11y)](), [Forms](), [Web Content Accessibility Guidelines](), [Usability](), [Web](), [User interface design]() Tags: [a11y-for-developers](), [accessibility](), [accessibility-best-practices](), [accessible-forms](), [accessible-required-form-field](), [eaa](), [errors](), [european-accessibility-act](), [standards](), [usability](), [web](), [web-content-accessibility-guidelines]() ### AI overview This article explains why accessible forms matter for inclusive digital experiences, usability, and compliance with the European Accessibility Act, the Americans with Disabilities Act, and WCAG. It uses a rental-car booking example to show how unclear required-field indicators and vague error messages can make forms difficult to complete, then introduces methods for indicating required fields, including placing the word "required" in the visible label. ### Source excerpt Creating accessible forms ensures your forms are accessible to all users while meeting standards like ADA, WCAG, and EAA compliance. The post The anatomy of accessible forms: Required form fields appeared first on Deque. ## New in Axe MCP Server: More automated coverage and streamlined developer workflows DevFeed: [New in Axe MCP Server: More automated coverage and streamlined developer workflows]() Original publisher: [Read original article]() Author: Harris Schneiderman Published: 2026-08-05T11:23:58Z Content type: article Language: en Sources: [Deque]() Topics: [axe MCP Server](), [Web Accessibility (a11y)](), [axe DevTools](), [AI-assisted coding](), [Developer Tools](), [Claude Code]() Tags: [a11y-for-developers](), [accessibility](), [ai-coding](), [axe-devtools](), [axe-mcp-server](), [claude-code](), [company-news-and-updates](), [developer](), [intelligent-guided-tests](), [mcp](), [mcp-server](), [testing]() ### AI overview Axe MCP Server updates expand automated accessibility testing within developers' coding workflows. The update adds support for automated Intelligent Guided Tests, beginning with keyboard testing, and introduces advanced rules for issues including heading semantics, focus indicators, text contrast, and decorative images. Governance controls let administrators enforce WCAG levels and confidence thresholds, while improved coverage targets authenticated flows, dynamic interfaces, and interactive application states. ### Source excerpt Automated accessibility testing helps teams catch issues earlier in the development workflow and reduce manual effort. However, some of the most complex accessibility checks have traditionally required guided or manual testing. With the latest Axe MCP Server updates, your developers can now automate even more accessibility testing directly inside their coding workflows. The post New in Axe MCP Server: More automated coverage and streamlined developer workflows appeared first on Deque. ## Use the Axe Monitor MCP integration within your preferred AI assistant to accelerate issue prioritization DevFeed: [Use the Axe Monitor MCP integration within your preferred AI assistant to accelerate issue prioritization]() Original publisher: [Read original article]() Author: Kate Spalla Published: 2026-07-30T11:57:11Z Content type: article Language: en Sources: [Deque]() Topics: [axe monitor](), [Web Accessibility (a11y)](), [Model Context Protocol](), [Data analysis]() Tags: [a11y-for-developers](), [accessibility](), [agentic-ai](), [axe-monitor](), [company-news-and-updates](), [efficiency](), [integration](), [mcp](), [selectors]() ### AI overview The article explains how the Axe Monitor MCP integration works with a preferred AI assistant to help accessibility program managers compare scan results, identify changes, prioritize remediation, and create actionable sprint plans using natural-language prompts. ### Source excerpt Now, by using our new Axe Monitor MCP integration within your preferred AI assistant, you can use natural language prompts to dramatically speed up the process of creating and comparing scans, prioritizing fixes, and building and delivering actionable accessibility sprint plans. The post Use the Axe Monitor MCP integration within your preferred AI assistant to accelerate issue prioritization appeared first on Deque.