Accessibility Report Manual
This manual provides detailed instructions on how to fill out the accessibility report in the Excel file. Each column in the report is designed to capture specific information about the accessibility issues found during testing.
Columns Overview
1. Issue Nr
- Purpose: To assign a unique identifier to each accessibility issue.
- Usage: Start with
1and increment the number for each new issue. This number will be used for reference throughout the report and discussions.
2. Location
- Purpose: To specify exactly where the issue occurs on the website.
- Usage: Provide a clear description of the location, such as the URL of the page and, if applicable, the specific section or element (e.g., “Homepage - Hero Banner” or “Contact Us form - Submit Button”). This helps the PM/customer easily identify where the problem is.
3. Impact
- Purpose: To categorize the severity of the issue and its effect on users.
- Usage: Refer to the impact documentation to determine the correct impact level (High, Medium, or Low). Indicate the impact level in this column to help prioritize the issue.
4. Issue
- Purpose: To describe what is wrong with the element or functionality.
- Usage: Provide a brief, clear description of the problem. For example, “Submit button is not accessible via keyboard navigation” or “Insufficient color contrast on main navigation links”.
5. WCAG
- Purpose: To reference the specific WCAG (Web Content Accessibility Guidelines) criterion that the issue violates.
- Usage: After identifying the issue in the WAVE tool or other testing tools, copy and paste the relevant WCAG guideline(s) into this column. This serves as a technical reference for why the issue needs to be addressed.
6. Notes
- Purpose: To include any additional information that may be helpful for understanding or resolving the issue.
- Usage: This field is optional. Use it to provide context, suggestions, or any other relevant details that don’t fit neatly into the other columns. For example, “Issue occurs only in Safari browser” or “Consider using ARIA labels for better screen reader support”.
Example Entry
| Issue Nr | Location | Impact | Issue | WCAG | Notes |
|---|---|---|---|---|---|
| 1 | Homepage - Hero Banner | High | Keyboard navigation skips hero banner | WCAG 2.1 - 2.1.1: Keyboard | Affects all users navigating with keyboard only |
| 2 | Contact Us - Submit Button | Medium | Submit button is not focusable | WCAG 2.1 - 2.4.7: Focus Visible | Occurs only on mobile devices |
| 3 | Product Page - Add to Cart Button | High | ”Add to Cart” button is missing alt text | WCAG 2.1 - 1.1.1: Non-text Content | Critical for users relying on screen readers |
| 4 | Footer - Social Media Links | Low | Social media icons lack descriptive text | WCAG 2.1 - 1.1.1: Non-text Content | Icons are decorative but should have alt text |
| 5 | Blog Page - Read More Links | Medium | ”Read More” links are not descriptive | WCAG 2.1 - 2.4.4: Link Purpose (In Context) | Consider adding context to link text |
By following these guidelines, we can ensure that our accessibility reports are clear, consistent, and actionable.