# axe-core

axe-core is an open-source accessibility testing engine for websites and HTML-based user interfaces that integrates with automated tests.

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

## Inside the AI software factory: Where accessibility is won or lost

DevFeed: [Inside the AI software factory: Where accessibility is won or lost](<https://devfeed.tech/articles/inside-the-ai-software-factory-where-accessibility-is-won-or-lost-147465.md>)

Original publisher: [Read original article](<https://www.deque.com/blog/inside-the-ai-software-factory-where-accessibility-is-won-or-lost/>)

Author: Dylan Barrell

Published: 2026-11-19T13:28:07Z

Content type: article

Language: en

Sources: [Deque](<https://devfeed.tech/sources/deque.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [AI in frontend development](<https://devfeed.tech/topics/ai-in-frontend-development.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Web Content Accessibility Guidelines](<https://devfeed.tech/topics/web-content-accessibility-guidelines.md>), [axe-core](<https://devfeed.tech/topics/axe-core.md>), [Software Process](<https://devfeed.tech/topics/software-process.md>), [Requirements](<https://devfeed.tech/topics/requirements.md>), [aria](<https://devfeed.tech/topics/aria.md>), [axe MCP Server](<https://devfeed.tech/topics/axe-mcp-server.md>), [Tech Debt](<https://devfeed.tech/topics/tech-debt.md>)

Tags: [a11y-for-developers](<https://devfeed.tech/tags/a11y-for-developers.md>), [accessibility](<https://devfeed.tech/tags/accessibility.md>), [accessibility-requirements](<https://devfeed.tech/tags/accessibility-requirements.md>), [accessibility-testing](<https://devfeed.tech/tags/accessibility-testing.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-software-factory](<https://devfeed.tech/tags/ai-software-factory.md>), [ai-workflows](<https://devfeed.tech/tags/ai-workflows.md>), [assistive-technology](<https://devfeed.tech/tags/assistive-technology.md>), [audit](<https://devfeed.tech/tags/audit.md>), [audits](<https://devfeed.tech/tags/audits.md>), [automation](<https://devfeed.tech/tags/automation.md>), [axe-core](<https://devfeed.tech/tags/axe-core.md>), [digital-accessibility](<https://devfeed.tech/tags/digital-accessibility.md>), [risk](<https://devfeed.tech/tags/risk.md>), [shift-left](<https://devfeed.tech/tags/shift-left.md>), [software-factory](<https://devfeed.tech/tags/software-factory.md>), [technical-debt](<https://devfeed.tech/tags/technical-debt.md>)

### AI overview

The article argues that accessibility should be built into AI software factories from the start, because late fixes increase rework and production fixes are reported to cost 30 times more than design fixes. It recommends accessibility criteria in UI tickets; deterministic checks such as Axe-core and lint rules wherever possible; agents steered with relevant context and integration tests; independent test records tied to the code; and monitoring, audits, and customer feedback after release. Use AI for judgment calls, such as whether a label fits its context, and rules based tools for repeatable checks. In the article's preliminary comparison, prompting was least predictable; open source tooling caught 50% of baseline audit defects, while paid tooling caught 69%, with fewer reported false positives and more consistent results. The authors say homegrown tools require maintenance and expertise. Automation still misses issues: end to end journeys, real assistive technology use, and human review remain necessary. Measure missed production issues and the share of UI changes with accessibility evidence, and feed recurring problems back into factory rules and tests.

### Source excerpt

As your organization moves development into AI software factories, you must fully embed digital accessibility, just as you must integrate privacy and security. Get it right, and your products, services, and experiences become and stay accessible. Get it wrong, and you increase risk, cost, and technical debt. The post Inside the AI software factory: Where accessibility is won or lost appeared first on Deque.

## Axe MCP Server now has a free plan

DevFeed: [Axe MCP Server now has a free plan](<https://devfeed.tech/articles/axe-mcp-server-now-has-a-free-plan-144205.md>)

Original publisher: [Read original article](<https://www.deque.com/blog/axe-mcp-server-now-has-a-free-plan/>)

Author: Harris Schneiderman

Published: 2026-11-16T14:02:00Z

Content type: release

Language: en

Sources: [Deque](<https://devfeed.tech/sources/deque.md>)

Topics: [axe MCP Server](<https://devfeed.tech/topics/axe-mcp-server.md>), [axe-core](<https://devfeed.tech/topics/axe-core.md>), [AI in frontend development](<https://devfeed.tech/topics/ai-in-frontend-development.md>)

Tags: [a11y-for-developers](<https://devfeed.tech/tags/a11y-for-developers.md>), [accessibility](<https://devfeed.tech/tags/accessibility.md>), [accessibility-testing](<https://devfeed.tech/tags/accessibility-testing.md>), [axe](<https://devfeed.tech/tags/axe.md>), [axe-core](<https://devfeed.tech/tags/axe-core.md>), [axe-mcp-server](<https://devfeed.tech/tags/axe-mcp-server.md>), [company-news-and-updates](<https://devfeed.tech/tags/company-news-and-updates.md>), [free-plan](<https://devfeed.tech/tags/free-plan.md>), [model-context-protocol-mcp](<https://devfeed.tech/tags/model-context-protocol-mcp.md>)

### AI overview

Deque's Axe MCP Server Free plan lets coding agents run unlimited scans of rendered web apps in a real browser using standard Axe-core rules, then rescan after fixes. This checks issues that source-code reasoning alone cannot measure, such as computed color contrast, component relationships, and script-added ARIA references. Axe-core reports detected violations and flags uncertain cases for review; its standard rules catch up to 57% of accessibility issues by volume. Deque says the paid Axe DevTools for Web plan, which includes the full server, adds advanced rules and automated Intelligent Guided Tests for up to 80% coverage, remediation guidance based on Deque's proprietary sources, and organization-wide configuration, user management, and SSO.

### Source excerpt

Deque is thrilled to announce that Axe MCP Server now has a free plan! The Axe MCP Server is a Model Context Protocol (MCP) server that integrates enterprise-grade accessibility testing directly into your development workflow. The post Axe MCP Server now has a free plan appeared first on Deque.

## How to Test WCAG 2.2 in CI: What axe-core Misses

DevFeed: [How to Test WCAG 2.2 in CI: What axe-core Misses](<https://devfeed.tech/articles/how-to-test-wcag-2-2-in-ci-what-axe-core-misses-139411.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/how-to-test-wcag-2-2-in-ci-what-axe-core-misses/>)

Author: Umair Ahmed

Published: 2026-11-16T13:52:13Z

Content type: tutorial

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

Topics: [Web Content Accessibility Guidelines](<https://devfeed.tech/topics/web-content-accessibility-guidelines.md>), [axe-core](<https://devfeed.tech/topics/axe-core.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [CSS](<https://devfeed.tech/topics/css.md>), [axe DevTools](<https://devfeed.tech/topics/axe-devtools.md>)

Tags: [2-2](<https://devfeed.tech/tags/2-2.md>), [a11y](<https://devfeed.tech/tags/a11y.md>), [accessibility](<https://devfeed.tech/tags/accessibility.md>), [accessible](<https://devfeed.tech/tags/accessible.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [automate](<https://devfeed.tech/tags/automate.md>), [axe-core](<https://devfeed.tech/tags/axe-core.md>), [ci](<https://devfeed.tech/tags/ci.md>), [design-ux](<https://devfeed.tech/tags/design-ux.md>), [mobile-web-development](<https://devfeed.tech/tags/mobile-web-development.md>), [responsive-web-design](<https://devfeed.tech/tags/responsive-web-design.md>), [test](<https://devfeed.tech/tags/test.md>), [wcag](<https://devfeed.tech/tags/wcag.md>), [wcag-2-2](<https://devfeed.tech/tags/wcag-2-2.md>)

### AI overview

A green axe-core CI run does not establish WCAG 2.2 conformance: most new criteria need human judgment or custom checks. The article shows Playwright tests for four AA criteria. Axe can check 2.5.8 Target Size, but its rule must be explicitly enabled; the excerpt reports axe-core 4.14.1's default run missed the sample violations. Custom checks can test whether keyboard focus is entirely obscured in both Tab directions, whether native draggable items have button alternatives, and whether password fields allow paste and use suitable autocomplete values. These checks have limits: the drag heuristic misses pointer-event libraries, while CAPTCHA alternatives and other context-dependent cases need people. The suggested CI setup targets selected pages such as sign-in and checkout. The author also recommends manual review, including a screen reader pass, and cautions that automated tests cannot establish that accessibility work is complete.

### Source excerpt

null Continue reading How to Test WCAG 2.2 in CI: What axe-core Misses on SitePoint.

## A Large-Scale Evaluation of Cookie Notice Privacy and Accessibility for Blind and Low Vision Users

DevFeed: [A Large-Scale Evaluation of Cookie Notice Privacy and Accessibility for Blind and Low Vision Users](<https://devfeed.tech/articles/a-large-scale-evaluation-of-cookie-notice-privacy-and-accessibility-for-blind-and-low-vision-users-114046.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.01211>)

Author: James M. Clarke, Maryam Mehrnezhad

Published: 2026-11-03T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [axe-core](<https://devfeed.tech/topics/axe-core.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [correlation](<https://devfeed.tech/tags/correlation.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [gdpr](<https://devfeed.tech/tags/gdpr.md>), [legal](<https://devfeed.tech/tags/legal.md>), [playwright](<https://devfeed.tech/tags/playwright.md>), [privacy](<https://devfeed.tech/tags/privacy.md>), [screen](<https://devfeed.tech/tags/screen.md>), [sites](<https://devfeed.tech/tags/sites.md>), [standards](<https://devfeed.tech/tags/standards.md>)

### AI overview

Across 2,061 domains, the evaluation found that 51% displayed cookie notices, and at least half of those notices violated UK GDPR/PECR requirements. Accepting a notice was associated with a mean five-fold increase in tracker activity and degraded page landmark structure on one in five sites. Although 95% of notices were screen-reader-readable, only 37% had meaningful titles, 39% were announced immediately on page load, and 42% used descriptive button labels. The abstract reports that notices failing legal privacy requirements disproportionately had the weakest screen-reader accessibility. The study used a Playwright crawler, a custom NVDA add-on, Lighthouse, and WAVE; the supplied text does not include further methods or results.

### Source excerpt

arXiv:2611.01211v1 Announce Type: new Abstract: We present the first large-scale privacy and accessibility evaluation of cookie notices across 2,061 domains for blind and low vision (BLV) users. Using a Playwright-based crawler, a custom NVDA screen reader add-on, and the Lighthouse and WAVE accessibility tools, we measure UK GDPR/PECR compliance, tracker activity across pre-interaction, post-accept, and post-reject phases, and cookie notice accessibility for screen reader users. We find that 51 % of sites display a cookie notice, of which (at least) 50 % violate UK GDPR/PECR requirements. Accepting a notice produces a mean five-fold increase in tracker activity, and degrades page landmark structure on one in five sites. While 95 % of notices are readable by a screen reader, only 37 % carry a meaningful title, 39 % are announced immediately on page load, and 42 % use descriptive button labels. We reveal a systemic correlation: cookie notices failing legal privacy requirements disproportionately exhibit the weakest screen reader accessibility. This compounding privacy burden on BLV users demands urgent intervention from developers, regulators, and standards bodies.

## 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](<https://devfeed.tech/articles/find-label-in-name-issues-in-every-scan-with-axe-core-4-14-0-95737.md>)

Original publisher: [Read original article](<https://www.deque.com/blog/find-label-in-name-issues-in-every-scan-with-axe-core-4-14-0/>)

Author: Wilco Fiers

Published: 2026-10-22T13:01:23Z

Content type: release

Language: en

Sources: [Deque](<https://devfeed.tech/sources/deque.md>)

Topics: [axe-core](<https://devfeed.tech/topics/axe-core.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [Web Content Accessibility Guidelines](<https://devfeed.tech/topics/web-content-accessibility-guidelines.md>), [EN 301 549](<https://devfeed.tech/topics/en-301-549.md>)

Tags: [a11y-for-developers](<https://devfeed.tech/tags/a11y-for-developers.md>), [accessibility](<https://devfeed.tech/tags/accessibility.md>), [accessibility-compliance](<https://devfeed.tech/tags/accessibility-compliance.md>), [accessibility-guidelines](<https://devfeed.tech/tags/accessibility-guidelines.md>), [assistive-technology](<https://devfeed.tech/tags/assistive-technology.md>), [automated](<https://devfeed.tech/tags/automated.md>), [axe-core](<https://devfeed.tech/tags/axe-core.md>), [en-301-549](<https://devfeed.tech/tags/en-301-549.md>), [eu](<https://devfeed.tech/tags/eu.md>), [release](<https://devfeed.tech/tags/release.md>), [standard](<https://devfeed.tech/tags/standard.md>), [support](<https://devfeed.tech/tags/support.md>), [web-content-accessibility-guidelines](<https://devfeed.tech/tags/web-content-accessibility-guidelines.md>)

### 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.

## Top Accessibility Errors in Production and How to Avoid Them

DevFeed: [Top Accessibility Errors in Production and How to Avoid Them](<https://devfeed.tech/articles/top-accessibility-errors-in-production-and-how-to-avoid-them-89684.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/top-accessibility-errors-in-production/>)

Author: SitePoint Sponsors

Published: 2026-10-18T15:35:14Z

Content type: tutorial

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [Web Content Accessibility Guidelines](<https://devfeed.tech/topics/web-content-accessibility-guidelines.md>), [axe-core](<https://devfeed.tech/topics/axe-core.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [axe MCP Server](<https://devfeed.tech/topics/axe-mcp-server.md>), [AI in frontend development](<https://devfeed.tech/topics/ai-in-frontend-development.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [accessibility-testing](<https://devfeed.tech/tags/accessibility-testing.md>), [automated-testing](<https://devfeed.tech/tags/automated-testing.md>), [automation](<https://devfeed.tech/tags/automation.md>), [code](<https://devfeed.tech/tags/code.md>), [design-ux](<https://devfeed.tech/tags/design-ux.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>)

### AI overview

The article explains common accessibility failures found on websites, including poor contrast, missing image descriptions and form labels, unnamed links and buttons, and keyboard navigation problems. It outlines fixes and recommends testing accessibility throughout development, combining automated scans with manual keyboard and screen reader checks because scans catch only some issues.

### Source excerpt

The same accessibility errors have topped WebAIM's report for seven years running. Here's what they are, why they keep shipping, and how to catch them before release. Continue reading Top Accessibility Errors in Production and How to Avoid Them on SitePoint.

## Find elements the way your users do with cy.getByRole()

DevFeed: [Find elements the way your users do with cy.getByRole()](<https://devfeed.tech/articles/find-elements-the-way-your-users-do-with-cy-getbyrole-87070.md>)

Original publisher: [Read original article](<https://www.cypress.io/blog/find-elements-the-way-your-users-do-with-cy-getbyrole/>)

Author: Jennifer Shehane

Published: 2026-10-14T17:54:38Z

Content type: article

Language: en

Sources: [Cypress Blog](<https://devfeed.tech/sources/cypress-blog.md>)

Topics: [ui-testing](<https://devfeed.tech/topics/ui-testing.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [aria](<https://devfeed.tech/topics/aria.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [axe-core](<https://devfeed.tech/topics/axe-core.md>), [testing-library](<https://devfeed.tech/topics/testing-library.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [ai](<https://devfeed.tech/tags/ai.md>), [assistive-technology](<https://devfeed.tech/tags/assistive-technology.md>), [audits](<https://devfeed.tech/tags/audits.md>), [button](<https://devfeed.tech/tags/button.md>), [cypress](<https://devfeed.tech/tags/cypress.md>), [native](<https://devfeed.tech/tags/native.md>), [query](<https://devfeed.tech/tags/query.md>), [testing-library](<https://devfeed.tech/tags/testing-library.md>), [tests](<https://devfeed.tech/tags/tests.md>)

### AI overview

Cypress 16.2.0 adds `cy.getByRole()`, which locates elements by role and optional accessible name, retries like other Cypress queries, and yields all matches. By default, it selects native HTML elements where available, so replacing a `<button>` with `<div role="button">` can make a test fail and expose missing keyboard behavior; `{ native: false }` includes role-attribute elements when needed. Compared with Cypress Testing Library's `findByRole()`, it also uses chained `.filter()` for states such as checked or selected, and multiple matches must be narrowed explicitly. Existing Testing Library tests can migrate gradually, and the plugin can remain for other queries. Cypress Accessibility is a separate Cypress Cloud feature that audits page states reached by recorded tests, including elements not directly asserted; `cy.getByRole()` works without Cloud.

### Source excerpt

Cypress 16.2.0 adds cy.getByRole(), a built-in query that finds elements by role and accessible name. By default, it matches only native elements, so your tests catch a swapped for a . Here's why that matters, and how to move off Cypress Testing Library.

## Nvidia tackles AI factory scaling bottlenecks with open rack designs and networking advances

DevFeed: [Nvidia tackles AI factory scaling bottlenecks with open rack designs and networking advances](<https://devfeed.tech/articles/nvidia-tackles-ai-factory-scaling-bottlenecks-with-open-rack-designs-and-networking-advances-85293.md>)

Original publisher: [Read original article](<https://siliconangle.com/2026/10/12/nvidia-tackles-ai-factory-scaling-bottlenecks-with-open-rack-designs-and-networking-advances/>)

Author: Kyt Dotson

Published: 2026-10-12T15:00:53Z

Content type: news

Language: en

Sources: [SiliconANGLE](<https://devfeed.tech/sources/siliconangle.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [NVIDIA Vera Rubin](<https://devfeed.tech/topics/nvidia-vera-rubin.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [GB300 NVL72](<https://devfeed.tech/topics/gb300-nvl72.md>), [NVIDIA Spectrum-X Ethernet](<https://devfeed.tech/topics/nvidia-spectrum-x-ethernet.md>), [Spectrum Ethernet](<https://devfeed.tech/topics/spectrum-ethernet.md>), [axe-core](<https://devfeed.tech/topics/axe-core.md>), [NVIDIA Research](<https://devfeed.tech/topics/nvidia-research.md>), [cornelis networks](<https://devfeed.tech/topics/cornelis-networks.md>)

Tags: [accelerated-computing](<https://devfeed.tech/tags/accelerated-computing.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agentic-ai-infrastructure](<https://devfeed.tech/tags/agentic-ai-infrastructure.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-factories](<https://devfeed.tech/tags/ai-factories.md>), [ai-infrastructure](<https://devfeed.tech/tags/ai-infrastructure.md>), [ai-systems](<https://devfeed.tech/tags/ai-systems.md>), [ai-training-and-inference](<https://devfeed.tech/tags/ai-training-and-inference.md>), [artificial-inteligence](<https://devfeed.tech/tags/artificial-inteligence.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-marketplace](<https://devfeed.tech/tags/aws-marketplace.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [infra](<https://devfeed.tech/tags/infra.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [joe-delaere](<https://devfeed.tech/tags/joe-delaere.md>), [nasdaq-csco](<https://devfeed.tech/tags/nasdaq-csco.md>), [nasdaq-goog](<https://devfeed.tech/tags/nasdaq-goog.md>), [nasdaq-meta](<https://devfeed.tech/tags/nasdaq-meta.md>), [nasdaq-nvda](<https://devfeed.tech/tags/nasdaq-nvda.md>), [news](<https://devfeed.tech/tags/news.md>), [nvidia](<https://devfeed.tech/tags/nvidia.md>), [nvidia-vera-cpu](<https://devfeed.tech/tags/nvidia-vera-cpu.md>), [nvidia-vera-rubin](<https://devfeed.tech/tags/nvidia-vera-rubin.md>), [open-compute-project](<https://devfeed.tech/tags/open-compute-project.md>), [open-compute-project-global-summit](<https://devfeed.tech/tags/open-compute-project-global-summit.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [the-latest](<https://devfeed.tech/tags/the-latest.md>), [top-story-3](<https://devfeed.tech/tags/top-story-3.md>), [vera-rubin](<https://devfeed.tech/tags/vera-rubin.md>)

### AI overview

Nvidia announced open Vera Rubin rack and compute tray designs through the Open Compute Project, alongside updates to its MGX architecture for AI factory systems. The announcements also include networking partnerships with Meta, Google and Cisco, covering Spectrum-6 Ethernet, Falcon Transport support and a proposed optical module format. The article describes how these infrastructure changes are intended to support large-scale AI training, inference and agent workloads.

### Source excerpt

Nvidia Corp. today announced new partnerships and contributions to the open-source community at the Open Compute Project Global Summit in San Jose, aimed at laying the foundation for the future of agentic artificial intelligence infrastructure. At the core of these announcements, the chip and hardware giant contributed key Vera Rubin rack and compute tray designs [...] The post Nvidia tackles AI factory scaling bottlenecks with open rack designs and networking advances appeared first on SiliconANGLE.

## Deque named a Leader in the 2026 Gartner® Magic Quadrant™ for Digital Accessibility

DevFeed: [Deque named a Leader in the 2026 Gartner® Magic Quadrant™ for Digital Accessibility](<https://devfeed.tech/articles/deque-named-a-leader-in-the-2026-gartner-magic-quadranttm-for-digital-accessibility-84195.md>)

Original publisher: [Read original article](<https://www.deque.com/blog/deque-named-a-leader-in-the-2026-gartner-magic-quadrant-for-digital-accessibility/>)

Author: Deque Systems

Published: 2026-10-09T15:03:01Z

Content type: news

Language: en

Sources: [Deque](<https://devfeed.tech/sources/deque.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [AI in frontend development](<https://devfeed.tech/topics/ai-in-frontend-development.md>), [axe MCP Server](<https://devfeed.tech/topics/axe-mcp-server.md>), [axe-core](<https://devfeed.tech/topics/axe-core.md>), [UI/UX Design](<https://devfeed.tech/topics/ui-ux-design.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [accessibility-testing](<https://devfeed.tech/tags/accessibility-testing.md>), [accessibility-tools](<https://devfeed.tech/tags/accessibility-tools.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [ai-development](<https://devfeed.tech/tags/ai-development.md>), [axe-core](<https://devfeed.tech/tags/axe-core.md>), [axe-mcp-server](<https://devfeed.tech/tags/axe-mcp-server.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [company-news-and-updates](<https://devfeed.tech/tags/company-news-and-updates.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [developer](<https://devfeed.tech/tags/developer.md>), [developer-workflows](<https://devfeed.tech/tags/developer-workflows.md>), [web-accessibility](<https://devfeed.tech/tags/web-accessibility.md>)

### AI overview

Deque says Gartner named it a Leader in the 2026 Magic Quadrant for Digital Accessibility. The company describes its approach as integrating accessibility testing and remediation into software development, including AI-assisted workflows, developer tools, CI/CD, and pull requests. It also highlights deployment options and resources for accessibility practitioners.

### Source excerpt

Deque has been recognized as a Leader in the 2026 Gartner® Magic Quadrant™ for Digital Accessibility! The post Deque named a Leader in the 2026 Gartner® Magic Quadrant™ for Digital Accessibility appeared first on Deque.

## 10 Most Common Accessibility Issues (1,025-Site Study)

DevFeed: [10 Most Common Accessibility Issues (1,025-Site Study)](<https://devfeed.tech/articles/10-most-common-accessibility-issues-1-025-site-study-50795.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/10-most-common-accessibility-issues-1-025-site-study/>)

Author: Umair Ahmed

Published: 2026-09-16T12:35:13Z

Content type: article

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [audit](<https://devfeed.tech/topics/audit.md>), [axe-core](<https://devfeed.tech/topics/axe-core.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [HTML](<https://devfeed.tech/topics/html.md>), [CSS](<https://devfeed.tech/topics/css.md>), [Website](<https://devfeed.tech/topics/website.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [audit](<https://devfeed.tech/tags/audit.md>), [automated](<https://devfeed.tech/tags/automated.md>), [axe-core](<https://devfeed.tech/tags/axe-core.md>), [bug](<https://devfeed.tech/tags/bug.md>), [color](<https://devfeed.tech/tags/color.md>), [core](<https://devfeed.tech/tags/core.md>), [css](<https://devfeed.tech/tags/css.md>), [design-ux](<https://devfeed.tech/tags/design-ux.md>), [html-css](<https://devfeed.tech/tags/html-css.md>), [lighthouse](<https://devfeed.tech/tags/lighthouse.md>), [mobile-web-development](<https://devfeed.tech/tags/mobile-web-development.md>), [problems](<https://devfeed.tech/tags/problems.md>), [quality](<https://devfeed.tech/tags/quality.md>), [scanner](<https://devfeed.tech/tags/scanner.md>), [screen](<https://devfeed.tech/tags/screen.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

A study of 1,025 websites identifies the most common accessibility problems found by automated scans between March and September 2026. Low color contrast affected 46.9% of sites, while unnamed links, buttons, and iframes were also frequent issues. The article explains the sampling method, scan coverage, axe-core and custom checks, and the limits of automated testing.

### Source excerpt

null Continue reading 10 Most Common Accessibility Issues (1,025-Site Study) on SitePoint.

## 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](<https://devfeed.tech/articles/test-your-custom-elements-and-trust-the-results-with-axe-core-s-support-for-elementinternals-9434.md>)

Original publisher: [Read original article](<https://www.deque.com/blog/test-your-custom-elements-and-trust-the-results-with-axe-cores-support-for-elementinternals/>)

Author: Wilco Fiers

Published: 2026-08-27T13:21:18Z

Content type: article

Language: en

Sources: [Deque](<https://devfeed.tech/sources/deque.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [axe-core](<https://devfeed.tech/topics/axe-core.md>), [interoperability](<https://devfeed.tech/topics/interoperability.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [browser](<https://devfeed.tech/topics/browser.md>), [Angular](<https://devfeed.tech/topics/angular.md>), [React](<https://devfeed.tech/topics/react.md>), [Vue.js](<https://devfeed.tech/topics/vue.md>), [aria](<https://devfeed.tech/topics/aria.md>)

Tags: [a11y-for-developers](<https://devfeed.tech/tags/a11y-for-developers.md>), [accessibility](<https://devfeed.tech/tags/accessibility.md>), [angular](<https://devfeed.tech/tags/angular.md>), [aria](<https://devfeed.tech/tags/aria.md>), [axe-core](<https://devfeed.tech/tags/axe-core.md>), [browser](<https://devfeed.tech/tags/browser.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [interoperability](<https://devfeed.tech/tags/interoperability.md>), [react](<https://devfeed.tech/tags/react.md>), [testing](<https://devfeed.tech/tags/testing.md>), [vue](<https://devfeed.tech/tags/vue.md>), [web-accessibility](<https://devfeed.tech/tags/web-accessibility.md>)

### 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.

## Your alt text passes automated checks. That doesn't mean it's any good.

DevFeed: [Your alt text passes automated checks. That doesn't mean it's any good.](<https://devfeed.tech/articles/your-alt-text-passes-automated-checks-that-doesn-t-mean-it-s-any-good-19853.md>)

Original publisher: [Read original article](<https://github.blog/engineering/user-experience/your-alt-text-passes-automated-checks-that-doesnt-mean-its-any-good/>)

Author: Taarik Ashenafi

Published: 2026-08-24T20:56:32Z

Content type: article

Language: en

Sources: [GitHub Blog](<https://devfeed.tech/sources/github-engineering.md>), [GitHub Engineering](<https://devfeed.tech/sources/github.md>)

Topics: [alt text](<https://devfeed.tech/topics/alt-text.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [Developer Tools](<https://devfeed.tech/topics/developer-tools.md>), [axe-core](<https://devfeed.tech/topics/axe-core.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-models](<https://devfeed.tech/tags/ai-models.md>), [alt-text](<https://devfeed.tech/tags/alt-text.md>), [automated](<https://devfeed.tech/tags/automated.md>), [automation](<https://devfeed.tech/tags/automation.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [false-positives](<https://devfeed.tech/tags/false-positives.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [image](<https://devfeed.tech/tags/image.md>), [layout](<https://devfeed.tech/tags/layout.md>), [markup](<https://devfeed.tech/tags/markup.md>), [pages](<https://devfeed.tech/tags/pages.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [quality](<https://devfeed.tech/tags/quality.md>), [rules](<https://devfeed.tech/tags/rules.md>), [scanner](<https://devfeed.tech/tags/scanner.md>), [user-experience](<https://devfeed.tech/tags/user-experience.md>)

### AI overview

The GitHub Accessibility Scanner's alt text plugin uses five default deterministic rules to flag issues provable from the text alone: missing or whitespace-only values, filenames, placeholders, generic medium labels, and repeated text on adjacent images. These checks require no AI credentials or network calls. The excerpt says markup alone cannot establish whether alt text adequately describes an image in context; the plugin therefore has a separate opt-in rule that uses a model with image content and surrounding context for judgments string-only checks cannot make. The design balances catching concrete problems with avoiding subjective rules that could produce false positives and be switched off.

### Source excerpt

We built a plugin for the GitHub Accessibility Scanner to make sure your alt text is actually accessible. Here's how it works. The post Your alt text passes automated checks. That doesn't mean it's any good. appeared first on The GitHub Blog.

## Axe-core at 5 billion: Accessibility meets the moment

DevFeed: [Axe-core at 5 billion: Accessibility meets the moment](<https://devfeed.tech/articles/axe-core-at-5-billion-accessibility-meets-the-moment-9428.md>)

Original publisher: [Read original article](<https://www.deque.com/blog/axe-core-at-5-billion-accessibility-meets-the-moment/>)

Author: Preety Kumar

Published: 2026-08-18T13:02:27Z

Content type: article

Language: en

Sources: [Deque](<https://devfeed.tech/sources/deque.md>)

Topics: [axe-core](<https://devfeed.tech/topics/axe-core.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [ai](<https://devfeed.tech/tags/ai.md>), [axe-core](<https://devfeed.tech/tags/axe-core.md>), [canada](<https://devfeed.tech/tags/canada.md>), [company-news-and-updates](<https://devfeed.tech/tags/company-news-and-updates.md>), [digital-accessibility](<https://devfeed.tech/tags/digital-accessibility.md>), [digital-products](<https://devfeed.tech/tags/digital-products.md>), [eaa](<https://devfeed.tech/tags/eaa.md>), [en-301-549](<https://devfeed.tech/tags/en-301-549.md>), [european-accessibility-act](<https://devfeed.tech/tags/european-accessibility-act.md>), [financial-services](<https://devfeed.tech/tags/financial-services.md>), [global](<https://devfeed.tech/tags/global.md>), [india](<https://devfeed.tech/tags/india.md>), [news](<https://devfeed.tech/tags/news.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

Axe-core has surpassed 5 billion downloads, up from 3 billion a year earlier, while daily downloads approach 10 million. The article connects this growth with accelerating global digital accessibility enforcement, including the European Accessibility Act, EN 301 549 updates, and developments in Canada, Australia, India, and South Korea. It also notes the continuing importance of open source and speculates about AI agents' role in using Axe-core.

### Source excerpt

The global digital accessibility community is experiencing a time of incredible momentum and incredible urgency. From every corner of the world, we are seeing new stories emerge--regulatory expansion, technological innovation, groundbreaking legal decisions, and more. This is happening at a time when AI is dramatically reshaping what it means to create digital products, services, and experiences. The post Axe-core at 5 billion: Accessibility meets the moment appeared first on Deque.

## GEO for JavaScript websites: why crawler-readable HTML matters

DevFeed: [GEO for JavaScript websites: why crawler-readable HTML matters](<https://devfeed.tech/articles/geo-for-javascript-websites-why-crawler-readable-html-matters-87427.md>)

Original publisher: [Read original article](<https://prerenderbuddy.com/blog/geo-for-javascript-websites>)

Author: Prerender Buddy

Published: 2026-06-26T00:00:00Z

Content type: article

Language: en

Sources: [Prerender Buddy](<https://devfeed.tech/sources/prerender-buddy-blog.md>)

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

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-crawlers](<https://devfeed.tech/tags/ai-crawlers.md>), [ai-visibility](<https://devfeed.tech/tags/ai-visibility.md>), [crawler](<https://devfeed.tech/tags/crawler.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [llms-txt](<https://devfeed.tech/tags/llms-txt.md>)

### AI overview

The article explains why JavaScript websites may serve crawlers thin HTML even when pages appear complete to visitors. It recommends checking crawler-visible content before improving GEO and describes prerendering as one way to serve readable rendered HTML, while noting that it does not guarantee search rankings or AI citations.

### Source excerpt

GEO starts with discoverable, readable content. For JavaScript sites, that means checking what crawlers actually receive.

## Automated Accessibility Tools Support Audits but Cannot Replace Human Evaluation

DevFeed: [Automated Accessibility Tools Support Audits but Cannot Replace Human Evaluation](<https://devfeed.tech/articles/llms-are-proving-that-it-is-impossible-to-automate-away-the-human-experience-33274.md>)

Original publisher: [Read original article](<https://8thlight.com/insights/llms-proving-impossible-automate-away-human-experience>)

Author: Celeste Aronow

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

Content type: opinion

Language: en

Sources: [8th Light](<https://devfeed.tech/sources/8th-light.md>), [8th Light Insights](<https://devfeed.tech/sources/8th-light-insights.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [Developer Tools](<https://devfeed.tech/topics/developer-tools.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [axe-core](<https://devfeed.tech/topics/axe-core.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [ai-and-emerging-tech](<https://devfeed.tech/tags/ai-and-emerging-tech.md>), [axe-core](<https://devfeed.tech/tags/axe-core.md>), [llms](<https://devfeed.tech/tags/llms.md>), [tooling](<https://devfeed.tech/tags/tooling.md>)

### AI overview

The article argues that automated accessibility scanners and LLM-assisted auditing can identify many concrete issues and expand teams' coverage, but they cannot fully assess what people with disabilities experience when using a screen reader. It also warns that scan output can include false violations and requires human judgment and accessibility expertise.

### Source excerpt

The Gap is Real If your accessibility process ends with a passing scan, your users with disabilities are likely encountering barriers you do not know about. Automated tools are useful. LLM-assisted auditing has raised the ceiling. Neither closes the gap between what a tool can verify and what a person actually experiences when navigating with a screen reader. The gap is real, it is measurable, and it has organizational consequences. I have spent years running every category of automated accessibility tool the industry has produced: rule-based scanners like axe-core and WAVE, visual analyzers like Lighthouse, browser extensions with built-in screen reader simulations. When LLMs entered the picture, the promise was compelling. Tools that could finally understand context, interpret user flows, and reason about accessibility the way a human specialist does. I wanted that to be true. It isn't. What Automation Does Well Let me be fair to the tools. Automated accessibility scanners like axe-core, Lighthouse, and WAVE are genuinely good at what they do. They catch heading hierarchy violations quickly and reliably. They flag color contrast failures with precision. They identify missing alt attributes on images in many cases. These are real wins. If you have run these tools on your product, you have addressed real issues, and the engineers who did that work should feel good about it. Automated tooling is a force multiplier. It speeds up the work and amplifies how much ground a team can cover. The problem is not what these tools do. It is what they cannot do, and what organizations assume they have done. What Automation Invents The same tools I praised above (SilkTide, axe-core, Lighthouse, and WAVE) are genuinely valuable parts of a real accessibility workflow. They speed up discovery, give teams a shared vocabulary, and help non-specialists see problems that would otherwise be invisible. They also generate a lot of output. A single scan on a moderately complex page can retur

## From a long list to a clear signal: baseline-driven accessibility reporting

DevFeed: [From a long list to a clear signal: baseline-driven accessibility reporting](<https://devfeed.tech/articles/from-a-long-list-to-a-clear-signal-baseline-driven-accessibility-reporting-28059.md>)

Original publisher: [Read original article](<https://tech.trivago.com/post/2026-03-13-from-a-long-list-to-a-clear-signal-baseline-driven-accessibility-reporting/>)

Author: Benjamin Bischoff Test Automation Engineer; Author; Speaker; Magician Github Profile Linkedin Profile

Published: 2026-03-13T00:00:00Z

Content type: tutorial

Language: en

Sources: [Trivago](<https://devfeed.tech/sources/trivago.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [axe-core](<https://devfeed.tech/topics/axe-core.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Automation](<https://devfeed.tech/topics/automation.md>), [Selenium](<https://devfeed.tech/topics/selenium.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [Extension](<https://devfeed.tech/topics/extension.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [accessibility-testing](<https://devfeed.tech/tags/accessibility-testing.md>), [automation](<https://devfeed.tech/tags/automation.md>), [axe-core](<https://devfeed.tech/tags/axe-core.md>), [eaa](<https://devfeed.tech/tags/eaa.md>), [european-accessibility-act](<https://devfeed.tech/tags/european-accessibility-act.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [quality-assurance](<https://devfeed.tech/tags/quality-assurance.md>), [selenium](<https://devfeed.tech/tags/selenium.md>), [test-automation](<https://devfeed.tech/tags/test-automation.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

The article describes a baseline-driven approach to accessibility reporting. It extends an in-house test automation framework so new test runs can be compared with a snapshot of known issues on the main branch, helping teams distinguish regressions from existing technical debt and track changes more clearly.

### Source excerpt

The output of most automated accessibility tests is a long list of violations. This format, while comprehensive, makes it difficult to distinguish new issues introduced in a feature branch from ...

## Not all automated testing tools support Shadow DOM in web components

DevFeed: [Not all automated testing tools support Shadow DOM in web components](<https://devfeed.tech/articles/not-all-automated-testing-tools-support-shadow-dom-in-web-components-52326.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/2024/automated-testing-tools-and-web-components>)

Author: Manuel Matuzović

Published: 2024-01-02T10:55:00Z

Content type: tutorial

Language: en

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

Topics: [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [Web Components](<https://devfeed.tech/topics/web-components.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [axe DevTools](<https://devfeed.tech/topics/axe-devtools.md>), [axe-core](<https://devfeed.tech/topics/axe-core.md>), [Web](<https://devfeed.tech/topics/web.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [axe-core](<https://devfeed.tech/tags/axe-core.md>), [axe-devtools](<https://devfeed.tech/tags/axe-devtools.md>), [lighthouse](<https://devfeed.tech/tags/lighthouse.md>), [testing](<https://devfeed.tech/tags/testing.md>), [web-components](<https://devfeed.tech/tags/web-components.md>)

### AI overview

This article examines how automated accessibility testing tools handle Shadow DOM in web components. It compares axe DevTools, Lighthouse, ARC Toolkit, WAVE, and IBM Equal Access, showing that tool support varies and recommending targeted testing for components that use Shadow DOM.

### Source excerpt

There isn't much more to say; it's all in the title. Many automated testing tools are a collection of JavaScript functions you run on a page. Most of those rely on querying the DOM. If a tool doesn't consider shadow trees, it only catches accessibility errors in the Light DOM, which may give you a wrong sense of safety and potentially affect your users. That's one more reason not to rely on automated testing only. That doesn't mean you shouldn't use automated testing if your site contains web components. You just have to ensure that the tool you're using supports them. A good way of doing that is creating a simple component that contains some accessibility bugs caused by nodes attached to the component's Shadow DOM, like the following component. <main> <h1 id="h1">Testing a11y bugs in web components</h1> <a href="#el">Jump to elem in shadow</a> <!-- Broken skip link --> <some-bugs></some-bugs> </main> <script> class SomeBugs extends HTMLElement { constructor() { super(); this.attachShadow({mode: 'open'}); this.shadowRoot.innerHTML = ` <style>:host { color: #efefef }</style> <!-- Low contrast. --> <h4 id="el">Heading</h4> <!-- Skipped heading. --> <img src="#test"> <!-- Missing alt. --> <button aria-labelledby="h1"></button> <!-- Broken ARIA reference/missing accessible name. --> <input type="text" id="input"> <!-- Missing label. --> ` } } customElements.define('some-bugs', SomeBugs); </script> CodePen: Test web component containing accessibility bugs If you add this component to a page, testing tools should find at least five issues. I picked five popular tools: axe DevTools, Google Lighthouse, ARC Toolkit, WAVE, and IBM Equal Access (IBM EAAC), and ran them against the component. axe DevTools and Lighthouse, both based on axe-core, found all five issues. WAVE found no problems in Shadow DOM, but reported a broken skip link in Light DOM. WAVE and ARC are the only tools that check for broken anchor links. Arguably, because it's not an obvious accessibility issue or W

## Use Firefox for accessibility testing

DevFeed: [Use Firefox for accessibility testing](<https://devfeed.tech/articles/use-firefox-for-accessibility-testing-9422.md>)

Original publisher: [Read original article](<https://a11yproject.com/posts/using-firefox-for-accessibility-testing/>)

Author: Todd Libby

Published: 2022-07-17T00:00:00Z

Content type: article

Language: en

Sources: [The A11Y Project](<https://devfeed.tech/sources/the-a11y-project.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [Firefox](<https://devfeed.tech/topics/firefox.md>), [Developer Tools](<https://devfeed.tech/topics/developer-tools.md>), [axe DevTools](<https://devfeed.tech/topics/axe-devtools.md>), [axe-core](<https://devfeed.tech/topics/axe-core.md>), [browser](<https://devfeed.tech/topics/browser.md>), [tabbing](<https://devfeed.tech/topics/tabbing.md>), [Web Content Accessibility Guidelines](<https://devfeed.tech/topics/web-content-accessibility-guidelines.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [accessibility-testing](<https://devfeed.tech/tags/accessibility-testing.md>), [accessibility-tools](<https://devfeed.tech/tags/accessibility-tools.md>), [audits](<https://devfeed.tech/tags/audits.md>), [firefox](<https://devfeed.tech/tags/firefox.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

Firefox's Accessibility tab helps inspect a page's accessibility tree and selected nodes, including their name, role, value, color contrast, and other properties. Its issue checks can flag contrast, keyboard, and form-label concerns; simulations cover several color-vision differences and contrast loss; and Show Tabbing Order displays keyboard tab stops and their sequence. The WAVE extension provides quick scans with errors, warnings, locations, and related code. The axe DevTools extension adds issue descriptions, severity estimates, best-practice toggles, and links into Firefox Inspector and Deque guidance. The excerpt also lists other extensions, and emphasizes that automated tools supplement rather than replace manual testing.

### Source excerpt

Firefox has become one of the best tools for accessibility audits. Let's go over Firefox's accessibility features that you can use today. Built-in accessibility tools In this article I'll discuss The Accessibility Tab, where we will begin and then move through to each component of the Accessibility Tab. First, the Check for issues tab, the Simulate menu, and end with the Show Tabbing Order checkbox. I'll finish with the Checks and Properties panel. The Accessibility tab Whenever you right-click on an element in a page, you can select Inspect Accessibility Properties to directly view that element in Firefox's accessibility tools. Similarly, if you're using the Inspector pane in Firefox's dev tools, you can right-click on any node and choose Show Accessibility Tools to view that node in Firefox's accessibility tools. Firefox's built-in accessibility tool is probably one of the best features in browsers' dev tools out there now. It shows you the current web page's accessibility tree, and it has panels for color-contrast checks and the current node's accessibility-tree properties. You can traverse the accessibility tree, and as you hover over each node, Firefox will show a tooltip over that node in the viewport with the name of the node and some basic properties. And the Checks and Properties panels can show you all the pertinent information for that node like its color and contrast ratio, name, role, and value. The Check for issues menu If you enable this handy feature, Firefox can check for color-contrast issues,it can do its best to try to find keyboard issues, and it can try to find form-label issues. There's also an All Issues option that will run all of those checks for the page. Each issue will show you the role and name of the element that has an issue, and the Checks and Properties panels will provide some information and values to help you resolve the issues. The Simulate menu This is a great tool for simulating visual differences. This can simulate: Protanopi

## Why a Perfect Lighthouse Accessibility Score Does Not Guarantee an Accessible Website

DevFeed: [Why a Perfect Lighthouse Accessibility Score Does Not Guarantee an Accessible Website](<https://devfeed.tech/articles/building-the-most-inaccessible-site-possible-with-a-perfect-lighthouse-score-52375.md>)

Original publisher: [Read original article](<https://www.matuzo.at/blog/building-the-most-inaccessible-site-possible-with-a-perfect-lighthouse-score>)

Author: Manuel Matuzović

Published: 2019-05-31T00: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>), [axe-core](<https://devfeed.tech/topics/axe-core.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [audit](<https://devfeed.tech/topics/audit.md>), [CSS](<https://devfeed.tech/topics/css.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>), [HTML](<https://devfeed.tech/topics/html.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [accessibility-testing](<https://devfeed.tech/tags/accessibility-testing.md>), [audit](<https://devfeed.tech/tags/audit.md>), [axe-core](<https://devfeed.tech/tags/axe-core.md>), [css](<https://devfeed.tech/tags/css.md>), [lighthouse](<https://devfeed.tech/tags/lighthouse.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

The article demonstrates that a perfect Lighthouse accessibility score does not prove a website is accessible. It explains that automated testing identifies only some problems and should be followed by manual testing and careful interpretation.

### Source excerpt

It's always nice to see when people post their Lighthouse scores on social media to highlight how well they've optimised their own or their client's website. It shows that they care about the quality of what they build. Lighthouse awards us with the number 100 in a green circle if we did an exceptional job. It's something you can proudly share with your client or on Twitter. It's important to measure the quality of our code, but it's even more important that we interpret the scores automatic testing tools give us correctly. If Lighthouse tells us that our site is 100% accessible, it doesn't mean it is. It just means we've laid the groundwork for manual testing. Lighthouse uses the axe-core accessibility testing library with a custom set of rules for its tests. It identifies some bad practices, but not all of them. Other practices aren't bad per se, but can be harmful, if we misuse them. With automatic testing alone you can't ensure good quality. To prove that, I built the most inaccessible site possible with a perfect Lighthouse score. Background Zach Leatherman recently posted this on twitter: Free blog post idea: How to Build the Slowest Website with a Perfect Lighthouse Score And here's Vadim Makeev's response to his tweet, which inspired me to write this post. That would be a wonderful read! Here's one for a11y audit: `<img src=picture.png alt=picture.png>` I thought it would be a fantastic idea to not just try to mess with as many people as possible, but get rewarded with a perfect Lighthouse score on top. Let's exclude as many people as possible We'll take this simple, accessible page as a basis. CodePen: "100%" accessible - step 0 Update 13.02.26: I don't know since when, but Lighthouse has been lowering the score if best-practice rules aren't met. Specifically, it complains about the absence of a main landmark. That's why I added it to the page. Thanks for the hint, Ria. 🖕 CSS only 🖕 Let's start nice and easy. I want to make sure that CSS is a dependency on