Accessibility Issue Reporting Guide

A comprehensive guide to reporting and managing accessibility issues. This documentation explains each field in detail, provides templates for bulk importing, and introduces our automated risk and impact assessment system to help prioritize remediation efforts.

Getting Started

This guide explains how to document accessibility issues and understand our automated risk and impact assessment system. Required fields include Location, Page URL, Environment, Issue, WCAG, and Recommendation.

Our system automatically calculates Impact and Risk Factor scores based on the WCAG criteria you specify, helping you prioritize remediation efforts.

Risk & Impact Assessment System

Impact Score

Auto-Generated

A measurement (0-100) that quantifies how severely an accessibility issue affects users. Higher values indicate more significant barriers to usability.

How Impact Is Calculated:

Based on the specific WCAG success criterion
Considers the number of users potentially affected
Evaluates the severity of functional limitations caused
Accounts for the importance of the affected feature

Impact Scale:

86-100: High - Prevents use of core functionality

61-85: Medium-High - Significantly hinders important functionality

41-60: Medium - Causes difficulty but has workarounds

16-40: Medium-Low - Minor impediment to user experience

0-15: Low - Minimal impact on user experience

Risk Factor

Auto-Generated

A score (0-100, displayed as 0-10) that assesses the potential legal, financial, and reputational risk associated with not addressing the accessibility issue.

How Risk Is Calculated:

Based on the WCAG conformance level (A, AA, AAA)
Considers legal requirements in target markets
Evaluates potential for complaints or litigation
Assesses regulatory compliance implications

Risk Factor Scale:

86-100: Critical - Potential legal liability, significant compliance issue

76-85: Urgent - High risk of complaints, serious non-compliance

66-75: Pressing - Moderate risk, notable compliance concerns

51-65: Concern - Some compliance issues with potential consequences

26-50: Slight - Minor compliance issues with less severe consequences

0-25: Low - Minimal risk, best practice recommendations

Plan-Based Features

Issue Reporting by Plan Type

The accessibility issue reporting features available to you depend on your subscription plan. The paid plan offers more advanced tools for managing and remediating accessibility issues.

Free Plan

BasicStandard issue reporting with required fields only
LimitedExcel must follow a specific column pattern
LimitedMaximum 100 issues per import
BasicLimited access to AI features
❌No custom column mapping

Paid Plan

Recommended

AdvancedFull issue reporting with all fields
CustomCustom column mapping for Excel imports
Higher LimitsMore issues per import ( based on plan type)
FullAccess to all AI features
✓Combined field mapping (e.g., merge multiple columns)

Excel Import Differences by Plan

Free Plan

Fixed column names required
Excel must follow a specific pattern
No custom mapping
Basic validation only
Limited to 100 issues per import
Limited AI assistance

Paid Plan

Flexible column naming
Custom column mapping
Combine multiple columns into one field
Unlimited issues per import
Advanced field validation with error reporting
Full AI assistance for mapping and validation

Pro Tip: Paid users can save column mapping configurations for reuse with similar audit files, saving time on future imports.

Field Descriptions

Location

Required

Indicates where the issue is found within the interface. Use a hierarchical approach (e.g., "Header > Navigation > Dropdown Menu") and include component names and unique identifiers if available.

Provide specific area details
Maintain a logical structure
Reference unique IDs if applicable

Examples:

Good Example	Poor Example
"Main Navigation - Search Bar"	"Top"
"Footer - Newsletter Signup"	"Footer"

Page URL

Required

The complete URL of the page where the issue is observed. Ensure that the URL is valid and includes the protocol (http:// or https://).

Include full URL (e.g., https://example.com/page)
Do not omit the protocol
Double-check for typos

Environment

Required

Describes the browser and operating system where the issue was observed. This helps in replicating and debugging the problem.

Include browser name and version
Include operating system details
Mention device type if relevant

Example: "Chrome 120, Windows 11"

Issue

Required

A clear and concise description of the accessibility issue. Focus on what's not working and how it affects user experience.

Describe the problem precisely
Indicate which user group is impacted
Mention any error messages if applicable

Example: "The search input field lacks an aria-label, making it inaccessible for screen readers."

WCAG

Required

Enter the WCAG success criterion that this issue violates. This field is critical as it determines the automated Impact and Risk Factor scores.

Format: [Principle.Guideline.Success_Criterion] [Name] [(Level)]

Example: "4.1.2 Name, Role, Value (Level A)"

The WCAG criterion you select will automatically determine the Impact and Risk Factor scores, helping prioritize remediation efforts.

Recommendation

Required

Provide a suggested solution or workaround for the reported issue. This may include code changes, configuration adjustments, or design updates.

Explain the fix clearly
Include code snippets if applicable
Mention any testing or verification steps

Example: "Add a visually hidden label using aria-label to the search field."

Bulk Import Template

Audit File Format

Use this Excel template for bulk importing accessibility issues. The required columns are Location, Page URL, Environment, Issue,WCAG, and Recommendation. Optional fields include Priority, Status, and Notes.

Column Name	Required	Format	Example
Location	Required	Text	"Header > Navigation > Search Bar"
Page URL	Required	URL	https://example.com/home
Environment	Required	Text	"Chrome 120, Windows 11"
Issue	Required	Long Text	"Input field missing aria-label"
WCAG	Required	Text	"4.1.2 Name, Role, Value (Level A)"
Recommendation	Required	Long Text	"Add aria-label to input"
Priority	Optional	High/Medium/Low (defaults to None)	"High"
Status	Optional	In Progress / Completed / On Hold / Not Applicable / Not Started (defaults to Not Started)	"Not Started"
Notes	Optional	Long Text	"Tested on multiple devices"

Excel Upload Instructions:

The Excel file should contain only one sheet.
If multiple sheets exist, ensure the first sheet contains all the issues.
If the sheet order is different, make sure a sheet is named Audit.
Preference is as follows: if one sheet exists, use it; if multiple, check for a sheet named Audit; if not found, extract issues from the first sheet. If all fails, an error is shown.

Demo: Logged Issues with Risk & Impact Assessment

Issues Log

Below is a demo of how issues are logged with their automatically calculated Impact and Risk Factor scores. Click on any row to see detailed information about the issue, including remediation recommendations.

Location	Page URL	WCAG	Issue	Impact	Risk	Priority	Status
Header > Navigation > Search Bar	https://example.com/home	4.1.2 Name, Role, Value (Level A)	Search input field lacks proper label causing screen readers to misinterpret its function.	92/100	9/10	High	Not Started
Footer > Newsletter Signup	https://example.com/contact	1.4.3 Contrast (Minimum) (Level AA)	Button color contrast is too low making it hard to read for users with low vision.	59/100	8/10	Medium	In progress
Product Page > Details Section	https://example.com/product/123	1.3.1 Info and Relationships (Level A)	The product details are not announced correctly by screen readers due to missing ARIA roles.	81/100	10/10	High	On Hold

Showing 3 issues

Impact Score Risk Factor

Risk & Impact Assessment System

Impact Score

Auto-Generated

A measurement (0-100) that quantifies how severely an accessibility issue affects users. Higher values indicate more significant barriers to usability.

How Impact Is Calculated:

Based on the specific WCAG success criterion
Considers the number of users potentially affected
Evaluates the severity of functional limitations caused
Accounts for the importance of the affected feature

Impact Scale:

86-100: High - Prevents use of core functionality

61-85: Medium-High - Significantly hinders important functionality

41-60: Medium - Causes difficulty but has workarounds

16-40: Medium-Low - Minor impediment to user experience

0-15: Low - Minimal impact on user experience

Risk Factor

Auto-Generated

A score (0-100, displayed as 0-10) that assesses the potential legal, financial, and reputational risk associated with not addressing the accessibility issue.

How Risk Is Calculated:

Based on the WCAG conformance level (A, AA, AAA)
Considers legal requirements in target markets
Evaluates potential for complaints or litigation
Assesses regulatory compliance implications

Risk Factor Scale:

86-100: Critical - Potential legal liability, significant compliance issue

76-85: Urgent - High risk of complaints, serious non-compliance

66-75: Pressing - Moderate risk, notable compliance concerns

51-65: Concern - Some compliance issues with potential consequences

26-50: Slight - Minor compliance issues with less severe consequences

0-25: Low - Minimal risk, best practice recommendations

Plan-Based Features

Issue Reporting by Plan Type

The accessibility issue reporting features available to you depend on your subscription plan. The paid plan offers more advanced tools for managing and remediating accessibility issues.

Free Plan

BasicStandard issue reporting with required fields only
LimitedExcel must follow a specific column pattern
LimitedMaximum 100 issues per import
BasicLimited access to AI features
❌No custom column mapping

Paid Plan

Recommended

AdvancedFull issue reporting with all fields
CustomCustom column mapping for Excel imports
Higher LimitsMore issues per import ( based on plan type)
FullAccess to all AI features
✓Combined field mapping (e.g., merge multiple columns)

Excel Import Differences by Plan

Free Plan

Fixed column names required
Excel must follow a specific pattern
No custom mapping
Basic validation only
Limited to 100 issues per import
Limited AI assistance

Paid Plan

Flexible column naming
Custom column mapping
Combine multiple columns into one field
Unlimited issues per import
Advanced field validation with error reporting
Full AI assistance for mapping and validation

Pro Tip: Paid users can save column mapping configurations for reuse with similar audit files, saving time on future imports.

Field Descriptions

Location

Required

Indicates where the issue is found within the interface. Use a hierarchical approach (e.g., "Header > Navigation > Dropdown Menu") and include component names and unique identifiers if available.

Provide specific area details
Maintain a logical structure
Reference unique IDs if applicable

Examples:

Good Example	Poor Example
"Main Navigation - Search Bar"	"Top"
"Footer - Newsletter Signup"	"Footer"

Page URL

Required

The complete URL of the page where the issue is observed. Ensure that the URL is valid and includes the protocol (http:// or https://).

Include full URL (e.g., https://example.com/page)
Do not omit the protocol
Double-check for typos

Environment

Required

Describes the browser and operating system where the issue was observed. This helps in replicating and debugging the problem.

Include browser name and version
Include operating system details
Mention device type if relevant

Example: "Chrome 120, Windows 11"

Issue

Required

A clear and concise description of the accessibility issue. Focus on what's not working and how it affects user experience.

Describe the problem precisely
Indicate which user group is impacted
Mention any error messages if applicable

Example: "The search input field lacks an aria-label, making it inaccessible for screen readers."

WCAG

Required

Enter the WCAG success criterion that this issue violates. This field is critical as it determines the automated Impact and Risk Factor scores.

Format: [Principle.Guideline.Success_Criterion] [Name] [(Level)]

Example: "4.1.2 Name, Role, Value (Level A)"

The WCAG criterion you select will automatically determine the Impact and Risk Factor scores, helping prioritize remediation efforts.

Recommendation

Required

Provide a suggested solution or workaround for the reported issue. This may include code changes, configuration adjustments, or design updates.

Explain the fix clearly
Include code snippets if applicable
Mention any testing or verification steps

Example: "Add a visually hidden label using aria-label to the search field."

Bulk Import Template

Audit File Format

Column Name	Required	Format	Example
Location	Required	Text	"Header > Navigation > Search Bar"
Page URL	Required	URL	https://example.com/home
Environment	Required	Text	"Chrome 120, Windows 11"
Issue	Required	Long Text	"Input field missing aria-label"
WCAG	Required	Text	"4.1.2 Name, Role, Value (Level A)"
Recommendation	Required	Long Text	"Add aria-label to input"
Priority	Optional	High/Medium/Low (defaults to None)	"High"
Status	Optional	In Progress / Completed / On Hold / Not Applicable / Not Started (defaults to Not Started)	"Not Started"
Notes	Optional	Long Text	"Tested on multiple devices"

Excel Upload Instructions:

The Excel file should contain only one sheet.
If multiple sheets exist, ensure the first sheet contains all the issues.
If the sheet order is different, make sure a sheet is named Audit.
Preference is as follows: if one sheet exists, use it; if multiple, check for a sheet named Audit; if not found, extract issues from the first sheet. If all fails, an error is shown.

Demo: Logged Issues with Risk & Impact Assessment

Issues Log

Location	Page URL	WCAG	Issue	Impact	Risk	Priority	Status
Header > Navigation > Search Bar	https://example.com/home	4.1.2 Name, Role, Value (Level A)	Search input field lacks proper label causing screen readers to misinterpret its function.	92/100	9/10	High	Not Started
Footer > Newsletter Signup	https://example.com/contact	1.4.3 Contrast (Minimum) (Level AA)	Button color contrast is too low making it hard to read for users with low vision.	59/100	8/10	Medium	In progress
Product Page > Details Section	https://example.com/product/123	1.3.1 Info and Relationships (Level A)	The product details are not announced correctly by screen readers due to missing ARIA roles.	81/100	10/10	High	On Hold

Showing 3 issues

Impact Score Risk Factor