# 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. ## 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: [Accessibility](), [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. ## Axe-core at 5 billion: Accessibility meets the moment DevFeed: [Axe-core at 5 billion: Accessibility meets the moment]() Original publisher: [Read original article]() Author: Preety Kumar Published: 2026-08-18T13:02:27Z Content type: article Language: en Sources: [Deque]() Topics: [Accessibility](), [axe-core](), [Open Source](), [Artificial Intelligence]() Tags: [accessibility](), [ai](), [axe-core](), [canada](), [company-news-and-updates](), [digital-accessibility](), [digital-products](), [eaa](), [en-301-549](), [european-accessibility-act](), [financial-services](), [global](), [india](), [news](), [open-source](), [testing]() ### 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. ## Automated Accessibility Tools Support Audits but Cannot Replace Human Evaluation DevFeed: [Automated Accessibility Tools Support Audits but Cannot Replace Human Evaluation]() Original publisher: [Read original article]() Author: Celeste Aronow Published: 2026-04-15T13:44:00Z Content type: opinion Language: en Sources: [8th Light](), [8th Light Insights]() Topics: [Accessibility](), [Tooling](), [Large Language Model](), [axe-core]() Tags: [accessibility](), [ai-and-emerging-tech](), [axe-core](), [llms](), [tooling]() ### 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]() Original publisher: [Read original article]() 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]() Topics: [digital accessibility](), [Accessibility](), [axe-core](), [Test automation](), [Automation](), [Selenium](), [Testing](), [Extension]() Tags: [accessibility](), [accessibility-testing](), [automation](), [axe-core](), [eaa](), [european-accessibility-act](), [frontend](), [quality-assurance](), [selenium](), [test-automation](), [testing]() ### 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 ...