Who can use this feature?
- Organization administrators and workspace administrators
- Enterprise customers
Expand your evaluation rules library with custom rules. Custom rules give you flexibility to define the testing criteria for your accessibility program, so you can meet specific, complex needs that are beyond WCAG and other non-WCAG standards. Custom rules gives you greater control over your compliance efforts and allows you to proactively address emerging accessibility challenges.
Custom rules are available in the Test Accelerator for self-performed evaluations.
The Level Access testing team does not perform evaluations against custom rules.
Add a custom rule
To add a custom rule:
- From the Control hub, go to Organization settings.
- Select Rule libraries.
- Choose Add rule.
- Fill out the rule details. Learn more about rule details.
- Select Save.
Rule details
The table below describes the details required for each custom rule.
| Field | Description | Example |
|---|---|---|
| Rule ID |
Unique ID of the accessibility rule the finding is associated with. |
A11y-01 |
| Description | A description of the issue that the rule addresses. | Img element has suspicious alternative text. |
| Testing medium | The type of digital interface to perform the test on. | iOS |
| Category | The issue category for a finding associated with the rule. | Focus control |
| Criteria | Criterion associated with the rule. Criterion may come from WCAG, EN 301 549, or Section 508. | 1.1.1 Non-text Content |
| Accessibility standards |
Accessibility standards associated with selected criteria. Note: The standards are auto-populated based on the selected criteria. |
WCAG 2.0 A WCAG 2.1 A WCAG 2.2 A EN 301 549 Section 508 |
| Severity | How much an accessibility finding impacts someone with a disability (critical, high, low). Learn more about severity. | High |
| Steps to reproduce | Step-by-step method to reproduce the finding. |
|
| Actual result | Description of what the user actually experiences in relation to the finding. | The image "Common types of fracture lines" description doesn't accurately describe the content or its purpose. |
| Recommendation | Proposed solution to remediate the finding. |
The screen reader should read the text provided on the image when it is reached. If text is inserted as an image without a description, some users won't be able to read it. Also, remove aria-hidden="true" from the <div> tag. |
| Functional impact | Estimated costs associated with ensuring instances of a violation are fixed in accordance with the rule. | Low |
| Disabilities Affected | Gives an overview of the categories of disabilities affected by the specific issue. |
Visual Speech |
| Test ID | Unique ID of the manual test associated with the rule. | TA-01 |
| Test name | The name of the test associated with the rule. This name is shown in the Test Accelerator. | Ensure custom controls are keyboard accessible |
| Manual test steps | The list of requirements and series of steps to test the digital property against the rule. |
Tools: Mouse, keyboard, and ANDI Test instructions:
|
| Optional: Compliant code example | Example of code that meets the rule's compliance. | <img alt="Close-up of an employee sitting next to their work computer."> |
| Optional: Non-compliant code example | Example of code that doesn't meet the rule's compliance. | <img alt="3hd23457f_image."> |
| Techniques | Practical methods, developed by WCAG, to implement accessibility requirements. Learn more about techniques. | F32: Failure of Success Criterion 1.3.2 due to using white space characters to control spacing within a word |
Comments
0 comments
Article is closed for comments.