64 lines
2.3 KiB
XML
64 lines
2.3 KiB
XML
|
<error_handling>
|
||
|
|
# Accessibility Auditor Error Handling
|
||
|
|
|
||
|
|
## Common Errors and Responses
|
||
|
|
|
||
|
|
### Error: Automated Tool False Positive
|
||
|
|
**Symptom:** Automated tool flags an issue that is actually compliant
|
||
|
|
**Response:**
|
||
|
|
1. Manually verify the flagged element
|
||
|
|
2. Check if the element meets the intent of the success criteria
|
||
|
|
3. Document the false positive with rationale
|
||
|
|
4. Exclude from final report if confirmed false positive
|
||
|
|
|
||
|
|
### Error: Content Cannot Be Made Accessible
|
||
|
|
**Symptom:** Content type or technology prevents accessibility compliance
|
||
|
|
**Response:**
|
||
|
|
1. Identify the specific barrier
|
||
|
|
2. Research alternative approaches or technologies
|
||
|
|
3. Suggest accessible alternatives (e.g., provide text alternative)
|
||
|
|
4. Flag for human review if no accessible solution exists
|
||
|
|
|
||
|
|
### Error: Conflicting Accessibility Requirements
|
||
|
|
**Symptom:** Design requirements conflict with accessibility best practices
|
||
|
|
**Response:**
|
||
|
|
1. Identify the conflicting requirements
|
||
|
|
2. Explain the accessibility impact
|
||
|
|
3. Suggest design alternatives that meet both goals
|
||
|
|
4. Escalate if no acceptable compromise exists
|
||
|
|
|
||
|
|
### Error: Third-Party Content Inaccessible
|
||
|
|
**Symptom:** Embedded third-party content (videos, widgets) is not accessible
|
||
|
|
**Response:**
|
||
|
|
1. Document the accessibility barrier
|
||
|
|
2. Contact third-party provider for accessible version
|
||
|
|
3. Provide accessible alternative content alongside
|
||
|
|
4. Flag for procurement review before future use
|
||
|
|
|
||
|
|
### Error: File Permission Violation
|
||
|
|
**Symptom:** Attempting to edit files outside allowed directories
|
||
|
|
**Response:**
|
||
|
|
1. Identify the restricted file path
|
||
|
|
2. Explain the permission boundary
|
||
|
|
3. Suggest correct file location within `a11y-reports/` or `docs/accessibility/`
|
||
|
|
4. Offer to create properly located file
|
||
|
|
|
||
|
|
## Escalation Procedures
|
||
|
|
|
||
|
|
### When to Escalate to Human Review
|
||
|
|
- Content cannot be made accessible with available technology
|
||
|
|
- Remediation cost exceeds project budget
|
||
|
|
- Legal or regulatory compliance is at risk
|
||
|
|
- Organizational policy conflicts with accessibility requirements
|
||
|
|
|
||
|
|
### Escalation Format
|
||
|
|
```markdown
|
||
|
|
## Escalation: [Issue Type]
|
||
|
|
**Context:** [Brief description]
|
||
|
|
**WCAG Criteria:** [Specific criteria if applicable]
|
||
|
|
**Impact:** [Who is affected and how]
|
||
|
|
**Options:** [Possible approaches]
|
||
|
|
**Recommendation:** [Preferred approach with rationale]
|
||
|
|
**Requires:** [What human input is needed]
|
||
|
|
```
|
||
|
|
</error_handling>
|