|
|
10 months ago | |
|---|---|---|
| .. | ||
| README.md | 10 months ago | |
| _template.json | 10 months ago | |
| da.json | 10 months ago | |
| de.json | 10 months ago | |
| el.json | 10 months ago | |
| es.json | 10 months ago | |
| eu.json | 10 months ago | |
| fr.json | 10 months ago | |
| he.json | 10 months ago | |
| it.json | 10 months ago | |
| ja.json | 10 months ago | |
| ko.json | 10 months ago | |
| nl.json | 10 months ago | |
| no_NB.json | 10 months ago | |
| pl.json | 10 months ago | |
| pt_BR.json | 10 months ago | |
| zh_CN.json | 10 months ago | |
| zh_TW.json | 10 months ago | |
README.md
Localizations
We welcome any localization for axe-core. For details on how to contribute, see the Contributing section of the main README. For details on the message syntax, see Check Message Template.
To create a new translation for axe, start by running grunt translate --lang=<langcode>. This will create a JSON file with the default English text in it for you to translate. Alternatively, you could copy _template.json.
To update an existing translation file, re-run grunt translate --lang=<langcode>. This will add new messages used in English and remove messages that are no longer used in English.
_template.json is a generated file which is created every time axe is built. It's compiled using each rule's description and help properties, as well as each check's metadata.messages property. To update the _template.json file you'll need to update the corresponding rule or check metadata file and rebuild.