Steven Lambert
Steven Lambert
The following code returns `inapplicable` when running `input-button-name`. This is because the [rules selector](https://github.com/dequelabs/axe-core/blob/develop/lib/rules/input-button-name.json#L4) is case sensitive so does not match when running against non-lowercase types. ```html ```
ARIA practices created [a new tabs page](https://www.w3.org/WAI/ARIA/apg/patterns/tabs/examples/tabs-actions/) that uses [a proposed `aria-actions` attribute](https://github.com/w3c/aria/issues/1440) for handling tabs with a primary and secondary action. Our nightly tests are failing on the page...
When Chrome 128 released it introduced a problem with the way we are doing our unit tests. Specifically for our full integration tests dealing with partial runs. What would happen...
This is a mistake and they should have been running, but right now it's only running `npm run test` with different browsers.
I updated the release script to update the service worker version, but didn't commit that change to the doc before trying to publish a release, so releasing the docs fails...
This work is in preparation to support fallback roles. Any part of the code that used `.getAttribute('role')` or `.attr('role')` was migrated to use `getEplicitRole()` instead. There are a few places...
To build a translated version of axe-core, you run the build command by passing the `--lang` option. E.g. `npm run build -- --lang=es`. You can even pass multiple langs `npm...
Currently axe-core generates [unique CSS selectors](https://github.com/dequelabs/axe-core/blob/develop/lib/core/utils/get-selector.js) for each node returned in the results. Unfortunately this selector generation is the #1 performance bottleneck in axe core, [especially for large pages](https://github.com/dequelabs/axe-core/issues/4427) with...
Trying to debug Firefox nightly test failures and I kept running into a problem with debug mode freezing or having tests fail. I'm still working on fixing all the issues,...
With our [deprecation of IE11 support](https://github.com/dequelabs/axe-core/releases/tag/v4.5.0) we no longer need to run axe-core through babel. For v5 we should stop babeling axe-core, meaning v5 will no longer run in IE11....