- Creating a Ruleset: Certain general principles apply when creating a ruleset.
- Rulesets: Rules typically align with a standard or set of guidelines (ie WCAG 2.0).
- Test Library: A test library should be created to verify any ruleset.
- ChromeDriver Help: Verification tests are performed using ChromeDriver.
- Exemptions: Ruleset failures may be post processed to handle exemptions.
- Test Library: A test library should be created to verify any ruleset.
- ChromeDriver Help: Rulesets are often run using ChromeDriver.
- Chrome Extension Development: Developing a Chrome Extension makes it easy for everyone to run the rulesets.
- Exemptions: Ruleset failures may be post processed to handle exemptions.
- General Steps for Running Rulesets: Running rulesets requires some general steps.
- Multiple Views: Often multiple Views can be tested simultaneously.
- Process Results: Results may be processes to take screenshots, store results or create reports.
- Selenium Grid: Building a Selenium Grid can help scale testing.
- View Setup: Prior to running a ruleset, it is important to clearly define the View (ie what is being tested).
- JSON Output: A JSON Object is used to store the results after running rulesets.
- HTML Report: Results can be visualized using an HTML Report with helpful links and screenshots.
- Headings Parser: Creating a tool to highlight landmarks and headers can be helpful for developers.
- MIND Patterns: Accessibility patterns help bake accessibility into the development process.