WAI-ARIA: Authoring Practices Guide
This repository maintains the WAI-ARIA Authoring Practices Guide.
- Latest editor's draft built from master branch
- Most recent version published on w3.org
- Developed by the Authoring Practices Task Force of the ARIA Working Group.
- Staff contact: Michael Cooper.
Please do not provide commit access to this repository without coordination.
How the work is organized
- Work is planned and prioritized in our milestones. Each milestone corresponds to a working draft or release published to w3.org.
- Work is organized by topic in our projects. Each project corresponds to a type of design pattern or section of guidance.
- The scope of work and roadmap are described in the project wiki.
- Comment in an existing issue or raise a new issue, expressing your willingness to help and briefly summarizing the nature of your proposed resolution.
- An editor will confirm there are no conflicting plans and, if needed, provide guidance.
- Be sure you have ESLint configured as described below.
- Read our wiki page about submitting pull requests.
- Do some fabulous work and submit a pull request.
Note: Please feel free to ask questions either through an issue or on the Authoring Practices Task Force mailing list.
- All HTML should validate in the NU HTML Validator. Exceptions to this rule are warnings and errors related to future ARIA features that are not yet implemented.
- To keep code in this repository consistent:
ESLint is an automated code style checker. We use it to ensure common code styling practices in this repository. Pull requests with ESLint errors will not be merged.
Setup ESLint so you can run it locally
- If you do not already have node.js installed, go to the node installer
- When you install Node, NPM is included.
- In a terminal window from the directory that contains the
npm install. A successful install will display a tree of installed packages.
Test and fix your code
- Open a terminal window to the directory that contains the
- Many errors can be fixed automatically with the command
npm run fix.
- After running fix, test again to see what you need to fix manually.
When the linter encounters errors, it will report them in the console. The error report will contain the file name and line number, and it will indicate the character or place in the line that raised the style violation. To fix an error, satisfy the change that the violation indicates.
For example, here is an error for an invalid variable name style. Variables must follow a camelCase convention.
/Users/user1/Documents/github/aria-practices/examples/slider/js/text-slider.js 19:8 error Identifier 'value_nodes' is not in camel case camelcase
The error occurred in
examples/slider/js/text-slider.js, on line 19 and the
offending character is indicated by the number
8 after the colon. Change the
valueNodes in your source file to eliminate this
To see the complete list of style rules that are applied by ESLint, review the .eslint.json file in the root of the project.
General documentation for editing ARIA deliverables is available in the ARIA repository. Some of that documentation covers technical procedures not needed for this specification.
How to update document snapshot
Note: These instructions are for editors of the APG who have repository commit access.
- Go to the editors draft on rawgit
- Press the ReSpec button (top right hand corner)
- Select 'Save snapshot'
- Select 'Save as HTML'
- Open the gh-pages branch of the
index.htmlin your preferred editor
- Overwrite contents of
index.htmlwith the snapshot copy you saved
- Commit and push changes
- Review changes at GitHub pages APG snapshot