The YuJa Workflow Orchestration Module is a project management add-on that allows users to create, track, and resolve accessibility issues directly within the platform. With the YuJa Workflow Orchestration Module, you can set up dedicated accessibility improvement tasks for different teams, campaigns, or initiatives within your organization to create a structured approach to remediation that aligns with your workflows.
Creating a task
Users can add a task to their Workflow Orchestration project board to keep track of accessibility issues and their remediation.
- Log in to the YuJa EqualGround platform as an admin.
-
Hover over the left side navbar and select Sites.
-
Select the website you would like to create a task for.
-
Hover over your desired web page and select its accessibility score.
-
In the Accessibility Report panel, select Create Task.
-
Choose the appropriate grouping for your task, then click Next. To read more about the grouping options the Workflow Orchestration Module offers, please refer to Understanding grouping types.
-
For conformance level, issue type, and specific issue tasks, select either Current Web Page or All Web Pages for where you'd like to create the task.
-
For Issue Type and Specific Issue tasks: Select the issues you’d like to create tasks for.
-
Enter the required details to create a task. This includes:
- Project: Select the project board you’d like to add this issue to. New project boards can be created in EqualGround's Workflow page.
- Summary: Enter a concise summary of the task. This will be used as the title for your task on the project board.
- Assignee: Select the team member you would like to assign the task to.
- Status: Assign a status to the task by selecting To-Do, In Progress, or Completed in the drop-down menu.
- Priority: Assign importance to the task by selecting Low, Medium, or High in the drop-down menu.
- Due date: Enter the desired date of completion for the task.
- Description: Based on the selected scope of the task, the platform will automatically create a description for your task. Review this information and modify it as necessary to accurately reflect the goals of the task.
-
Click Create Task(s).
-
Depending on the selected grouping of your task, a badge will appear by the Accessibility Report, the conformance level, the issue type, or the specific issue. Clicking this badge will take you directly to the project board, with the task details opened.
Understanding grouping types
The YuJa Workflow Orchestration Module allows users to create tasks based on four different groupings: conformance level, issue type, specific issue, and entire web page. Using the correct grouping type for your workflow can ensure you accurately reflect the scope of the task.
Conformance level, issue type, and specific issue groupings work best for workflows that approach remediation by assigning a team member to complete all issues of the same type. By contrast, the entire web page grouping works best for workflows that approach remediation on a page-by-page basis. Use the table below to help you understand what grouping type works best for your workflow.
| Remediation Strategy | Best Grouping Type |
| Assign one person to remediate all issues of a certain standard. | Conformance level |
| Assign a specialist to remediate all issues of a certain subject area. | Issue type |
| Assign an expert to remediate all issues of a specialized subject area. | Specific issue |
| Assign one person to remediate all the issues on a page. | Entire web page |
Continue reading to learn more about the different grouping types and their best use case.
Conformance level
Creating a task based on conformance level allows you to assign a team member to all issues that fall under WCAG Level A, AA, or AAA standards. The table below can be used to understand the difference between the three WCAG conformance levels.
| Level | Goal | Example of Key Requirements |
| A | Meeting basic accessibility standards and removing the most critical barriers to access. | Keyboard accessibility, alternative text, and captions for audio-visual content. |
| AA | Meeting benchmark accessibility standards and providing access to most users with disabilities. | Color contrast, resizable text, content reflow, and consistent navigation. |
| AAA | Meeting specialized accessibility standards and providing access to the widest range of users. Note that the W3C does not recommend Level AAA as the target standard for entire websites because it is not always possible to satisfy all criteria. | Enhanced color contrast, sign language for videos, and reduced distractions. |
The best use case for creating tasks based on conformance level is when an organization is completing broad accessibility remediation with users trained in general accessibility practices.
Issue type
Creating a task based on issue type allows you to assign a team member to all issues that fall under specific WCAG guidelines. WCAG 2.2 contains 12 guidelines, including:
- 1.1 Text Alternatives
- 1.2 Time-based Media
- 1.3 Adaptable
- 1.4 Distinguishable
- 2.1 Keyboard Accessible
- 2.2 Enough Time
- 2.4 Navigable
- 2.5 Input Modalities
- 3.1 Readable
- 3.2 Predictable
- 3.3 Input Assistance
- 4.1 Robust
Creating a task based on issue type allows for remediation of specific issues, as opposed to the broad scope of remediating based on conformance level.
The best use case for creating tasks based on issue type is when an organization is completing accessibility remediation for certain issues with users trained in specific accessibility practices. For example, a user who is trained in accessible website navigation may be the best person to assign all 2.1 Keyboard Accessible and 2.4 Navigable issues to.
Specific issue
Creating a task based on Specific Issues allows you to assign a team member all issues that fall under specific WCAG success criteria. WCAG 2.2 contains 87 highly specific success criteria, starting with 1.1.1 Non-text Content, and ending with 4.1.3 Status Messages. Creating a task based on specific issues allows for the most targeted accessibility remediation, as it is even more specific than issue type.
The best use case for creating tasks based on Specific Issues is when an organization is completing highly specific accessibility remediation with users trained in highly specific accessibility practices. For example, a user who is fluent in sign language may be the best person to assign all 1.2.6 Sign Language (Prerecorded) issues to.
Entire web page
Creating a task for an entire web page allows you to assign a team member to complete all issues that appear in a specific web page.
The best use case for creating tasks based on an entire web page is when an organization has chosen to complete website remediation on a page-by-page basis.