You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Axe is an accessibility testing engine for websites and other HTML-based user interfaces. It's fast, secure, lightweight, and was built to seamlessly integrate with any existing test environment so you can automate accessibility testing alongside your regular functional testing.
45
-
46
-
[Sign up for axe news](https://hubs.ly/H0fsN0b0) to get the latest on axe features, future releases, and events.
47
-
48
-
## The Accessibility Rules
49
-
50
-
Axe-core has different types of rules, for WCAG 2.0 and 2.1 on level A and AA, as well as a number of best practices that help you identify common accessibility practices like ensuring every page has an `h1` heading, and to help you avoid "gotchas" in ARIA like where an ARIA attribute you used will get ignored.
51
-
52
-
With axe-core, you can find **on average 57% of WCAG issues automatically**. Additionally, axe-core will return elements as "incomplete" where axe-core could not be certain, and manual review is needed.
53
-
54
-
To catch bugs earlier in the development cycle we recommend using the [axe-linter vscode extension](https://marketplace.visualstudio.com/items?itemName=deque-systems.vscode-axe-linter). To improve test coverage even further we recommend the [intelligent guided tests](https://www.youtube.com/watch?v=AtsX0dPCG_4&feature=youtu.be&ab_channel=DequeSystems) in the [axe Extension](https://www.deque.com/axe/browser-extensions/).
55
-
56
-
The complete list of rules, grouped WCAG level and best practice, can found in [doc/rule-descriptions.md](./doc/rule-descriptions.md).
57
-
58
-
## Getting started
59
-
60
-
First download the package:
61
-
62
-
```console
63
-
npm install axe-core --save-dev
64
-
```
65
-
66
-
Now include the javascript file in each of your iframes in your fixtures or test systems:
Now insert calls at each point in your tests where a new piece of UI becomes visible or exposed:
73
-
74
-
```js
75
-
axe
76
-
.run()
77
-
.then(results=> {
78
-
if (results.violations.length) {
79
-
thrownewError('Accessibility issues found');
80
-
}
81
-
})
82
-
.catch(err=> {
83
-
console.error('Something bad happened:', err.message);
84
-
});
85
-
```
86
-
87
-
## Philosophy
88
-
89
-
The web can only become an accessible, inclusive space if developers are empowered to take responsibility for accessibility testing and accessible coding practices.
90
-
91
-
Automated accessibility testing is a huge timesaver, it doesn't require special expertise, and it allows teams to focus expert resources on the accessibility issues that really need them. Unfortunately, most accessibility tools are meant to be run on sites and applications that have reached the end of the development process and often don't give clear or consistent results, causing frustration and delays just when you thought your product was ready to ship.
92
-
93
-
Axe was built to reflect how web development actually works. It works with all modern browsers, tools, and testing environments a dev team might use. With axe, accessibility testing can be performed as part of your unit testing, integration testing, browser testing, and any other functional testing your team already performs on a day-to-day basis. Building accessibility testing into the early development process saves time, resources, and all kinds of frustration.
94
-
95
-
## About axe - our Manifesto
96
-
97
-
- Axe is open source.
98
-
- It returns zero false positives (bugs notwithstanding).
99
-
- It's designed to work on all modern browsers and with whatever tools, frameworks, libraries and environments you use today.
100
-
- It's actively supported by [Deque Systems](https://www.deque.com), a major accessibility vendor.
101
-
- It integrates with your existing functional/acceptance automated tests.
102
-
- It automatically determines which rules to run based on the evaluation context.
103
-
- Axe supports in-memory fixtures, static fixtures, integration tests and iframes of infinite depth.
104
-
- Axe is highly configurable.
105
-
106
-
## Supported Browsers
107
-
108
-
The [axe-core API](doc/API.md) fully supports the following browsers:
109
-
110
-
- Microsoft Edge v40 and above
111
-
- Google Chrome v42 and above
112
-
- Mozilla Firefox v38 and above
113
-
- Apple Safari v7 and above
114
-
- Internet Explorer v11
115
-
116
-
Support means that we will fix bugs and attempt to test each browser regularly. Only Firefox, Chrome, and Internet Explorer 11 are currently tested on every pull request.
117
-
118
-
There is limited support for JSDOM. We will attempt to make all rules compatible with JSDOM but where this is not possible, we recommend turning those rules off. Currently the `color-contrast` rule is known not to work with JSDOM.
119
-
120
-
We can only support environments where features are either natively supported or polyfilled correctly. We do not support the deprecated v0 Shadow DOM implementation.
121
-
122
-
## Contents of the API Package
123
-
124
-
The [axe-core API](doc/API.md) package consists of:
125
-
126
-
-`axe.js` - the JavaScript file that should be included in your web site under test (API)
127
-
-`axe.min.js` - a minified version of the above file
128
-
129
-
## Localization
130
-
131
-
Axe can be built using your local language. To do so, a localization file must be added to the `./locales` directory. This file must have be named in the following manner: `<langcode>.json`. To build axe using this locale, instead of the default, run axe with the `--lang` flag, like so:
132
-
133
-
`grunt build --lang=nl`
134
-
135
-
or equivalently:
136
-
137
-
`npm run build -- --lang=nl`
138
-
139
-
This will create a new build for axe, called `axe.<lang>.js` and `axe.<lang>.min.js`. If you want to build localized versions, simply pass in `--all-lang` instead. If you want to build multiple localized versions (but not all of them), you can pass in a comma-separated list of langages to the `--lang` flag, like `--lang=nl,ja`.
140
-
141
-
To create a new translation for axe, start by running `grunt translate --lang=<langcode>`. This will create a json file fin the `./locales` directory, with the default English text in it for you to translate. We welcome any localization for axe-core. For details on how to contribute, see the Contributing section below. For details on the message syntax, see [Check Message Template](/docs/check-message-template.md).
142
-
143
-
To update existing translation file, re-run `grunt translate --lang=<langcode>`. This will add new messages used in English and remove messages which were not used in English.
144
-
145
-
Additionally, locale can be applied at runtime by passing a `locale` object to `axe.configure()`. The locale object must be of the same shape as existing locales in the `./locales` directory. For example:
146
-
147
-
```js
148
-
axe.configure({
149
-
locale: {
150
-
lang:'de',
151
-
rules: {
152
-
accesskeys: {
153
-
help:'Der Wert des accesskey-Attributes muss einzigartig sein.'
154
-
}
155
-
// ...
156
-
},
157
-
checks: {
158
-
abstractrole: {
159
-
fail:'Abstrakte ARIA-Rollen dürfen nicht direkt verwendet werden.'
160
-
},
161
-
'aria-errormessage': {
162
-
// Note: doT (https://github.com/olado/dot) templates are supported here.
163
-
fail:
164
-
'Der Wert der aria-errormessage ${data.values}` muss eine Technik verwenden, um die Message anzukündigen (z. B., aria-live, aria-describedby, role=alert, etc.).'
165
-
}
166
-
// ...
167
-
}
168
-
}
169
-
});
170
-
```
171
-
172
-
### Supported Locales
173
-
174
-
Axe-core supports the following locales. Do note that since locales are contributed by our community, they are not guaranteed to include all translations needed in a release.
175
-
176
-
- Basque
177
-
- Danish
178
-
- Dutch
179
-
- French
180
-
- German
181
-
- Japanese
182
-
- Korean
183
-
- Polish
184
-
- Portuguese (Brazilian)
185
-
- Spanish
186
-
187
-
## Updates & Security
188
-
189
-
Axe-core has a new minor release every 3 to 5 months, which usually introduces new rules and features. We recommend scheduling time to upgrade to these versions. Security updates will be made available for minor version lines up to **18 months old**.
190
-
191
-
- See [release and support](doc/release-and-support.md) for details on the frequency of releases, long-term support and recommendations on upgrading axe-core.
192
-
- See [backward compatibility](doc/backwards-compatibility-doc.md) for details on the types of changes different releases may introduce.
193
-
194
-
## Supported ARIA Roles and Attributes.
195
-
196
-
Refer [axe-core ARIA support](./doc/aria-supported.md) for a complete list of ARIA supported roles and attributes by axe.
197
-
198
-
## Contributing
199
-
200
-
Read the [Proposing Axe-core Rules guide](./doc/rule-proposal.md)
201
-
202
-
Read the [documentation on the architecture](./doc/developer-guide.md)
203
-
204
-
Read the [documentation on contributing](CONTRIBUTING.md)
205
-
206
-
## Projects using axe-core
207
-
208
-
[List of projects using axe-core](doc/projects.md)
209
-
210
-
## Acknowledgements
211
-
212
-
Thanks to Dulin Marat for his [css-selector-parser](https://www.npmjs.com/package/css-selector-parser) implementation which is included for shadow DOM support.
213
-
214
-
Thanks to the [Slick Parser](https://github.com/mootools/slick/blob/master/Source/Slick.Parser.js) implementers for their contribution, we have used some of their algorithms in our shadow DOM support code.
0 commit comments