Product Ideas Portal

Allow Custom AT Assignments in Use Cases

Provide a feature to assign an AT to a custom number of use cases.

Current Behavior

When an AT is assigned to a use case, the AT (and the singular tester it can be assigned to) is assigned to all use cases within a report.

Proposed Behavior

Allow report editors (potentially after an initial assignment to all use cases) to select and deselect the AT from testing certain use cases within a report.

Rationale

Oftentimes, especially with Responsive Web Design reports, use cases will apply to some, but not all, ATs. For example, if you are testing a responsive website, the steps to conduct a use case for navigating to a product may be different. Currently, editors must create two different sets of use cases to accommodate this task. When assigning the desktop ATs, they will also become assigned to the mobile use cases and vice versa. This creates confusion among clients & AT testers.

The alternative, creating two reports, separates out the violations for one code base into two reports, causes more set-up work for report editors, and causes report reviewers to look in two places for results around one site.

  • Guest
  • Jan 25 2018
  • Deferred to Next Gen
AMP
  • Attach files
  • Kevin Murphy commented
    5 Feb, 2019 06:00pm

    I have made a new request for this type of functionality here. 

    https://ideas.levelaccess.com/ideas/AMP-I-179

    As we move into acceleration project, this is going to become more and more critical. 

  • Jonathan Avila commented
    13 Dec, 2018 08:08pm

    I would add that this is particularly relevant to WCAG 2.1, responsive and combining reports into a master for Access Acceleration.

  • Admin
    Zahra Safavian commented
    2 Feb, 2018 02:58pm

    We are not making any updates to the Use Case testing feature within AMP, but we are considering all user feedback for development of this feature in the future AMP X platform.