Help Documentation

The application is organized around Projects, which represent individual accessibility reviews. Each project contains:

• Scope items - The web pages or components being reviewed
• Issues - Accessibility problems identified during the review
• Observations - Specific instances of accessibility criteria failures
• Report data - Summary information and recommendations

The application follows Cornell's WCAG testing guidelines, which are based on the Web Content Accessibility Guidelines (WCAG) 2.2 AA standards.

The accessibility review process follows these steps:

1. Create a Project

   Start by creating a new review project from the Projects page or from a Team's Projects page. Projects can be set up like creating a new WA Checklist, or data can be imported via the Upload button.

2. Define the Scope

   Add scope items via the Scope tab on the Project page. You can manually add URLs or import scopes from a spreadsheet checklist using the standard sheets format.

3. Assign a Reviewer

   In the Workflow panel, assign the project to a reviewer and update the status to Start Review.

4. Document Issues

   Add accessibility issues via the Issues tab on the Project page or from a Scope page. For each issue, you can add observations manually or use AI to suggest observations (AI suggestions must be approved to be included in reports).

5. Complete the Review

   Fill out report fields, update the status to Complete Review in the Workflow panel, and view the report. You can add read-only viewers via the Report Viewers panel.

The application includes AI-powered features to help with accessibility reviews:

• AI Chat

  Ask questions about accessibility guidelines and best practices. The AI has access to Cornell's accessibility guidelines and can provide context-specific advice.

• Page Analysis

  Get AI-powered analysis of web pages to identify potential accessibility issues.

• Automated Suggestions

  Receive AI-generated suggestions for observations based on issue descriptions. These suggestions must be reviewed and approved before being included in reports.

The application uses a team-based approach to manage access:

• Site Administrators

  Can create teams, manage system-wide settings, and access all projects.

• Team Administrators

  Can manage team users and projects within their teams.

• Reviewers

  Can work on projects assigned to them, add issues, and complete reviews.

• Report Viewers

  Have read-only access to specific reports they've been granted access to.