Skip to main content

List View

The List View provides a centralized view of all issues within a project. It enables teams to view, manage and track issues by providing access to issue details, types and statuses from a single location. Users can create issues manually, edit issue details, assign issues to team members, update issue types and statuses, and filter the list to locate specific records quickly. By consolidating these actions into single interface, the List helps teams manage issues more efficiently and maintain accurate data.

Purpose of List View​

The list is designed to give users:

  1. View all accessibility issues identified in the project.
  2. Ability to view, track and manage issues throughout the project.
  3. Quick access to severity, ownership.

Report Table Structure in List View​

This section displays each accessibility issues along with its key attributes:

1. ID​

Displays the ID assigned to the issue.

2. Page​

Displays the page where the issue was identified. Click the page link to open the corresponding website page.

3. Element​

Displays the UI element associated with the issue, such as:

  • Forms
  • Landmarks
  • Page Titles
  • Keyboard interactions
  • ARIA components

4. Issue​

Displays a clear, concise description of the accessibility issue.

5. Attribute​

Displays a accessibility attribute associated with the issue.

6. Updated Type​

Allows you to update the issue type, such as:

  • Fail
  • Pass
  • Validate
  • Suggestion

7. Type​

Displays the current issue type:

  • Validate
  • Suggestion
  • Fail

8. WCAG SC​

Displays the applicable WCAG criteria.

9. Status​

Displays the status of the issue, such as:

  • To Do
  • In Progress
  • Done

10. Severity​

Indicates the impact of the issue, such as:

  • Major
  • Minor
  • Critical
  • Blocker
  • Best Practice

11. Level​

Displays the applicable WCAG conformance level associated with the issue.

12. Assignee​

Displays the user assigned to resolve the issue.

13. Environment​

Displays the testing environment in which the issue was identified.

14. Device​

Displays the device used to identify the issue.

15. Reporter​

Displays the name of the user who reported the issue.

16. Role​

Displays the recommended role suitable for addressing the issue.