Product Ideas Portal

Warn User if Manual Violation being created is not part of the OTC

When creating manual instances in AST, if a user creates a violation via Baseline testing that is not tied to the OTC, it will not show up via the "Violation Instances" view. Alerting the user to this would be beneficial in determining issues as well as delivering acceptable and correct information to clients.
  • Anna Kanterova
  • Jan 22 2020
  • Needs Clarification
  • Attach files
  • Anna Kanterova commented
    25 Feb, 2020 11:29pm

    Update: This bug is present even when the organization (OTC) has all levels of WCAG 2.1 tied.

  • Anna Kanterova commented
    24 Jan, 2020 07:10pm


    The organization had only WCAG 2.0 set, but with the time they started asking to do WCAG 2.1 testing, as it was the case in the most recent audit (where I got tricked by this feature, I can send you links via email if needed).

    When you go to the Violations table in the report, the report which has both WCAG 2.0 and 2.1 including Baseline set, you see only 51 instances, 21 of them are for module 04.

    Yet, in the module 04 itself you can find 24 reported instances, including instance of contrast elements [04-19] which is one of 4 that are not pulled into the Violations table. This is WCAG 2.1 requirement and it might be that 2.1 issues are not added into Violations while 2.1 Level A and AA are included in the report’s compliance… 

    I almost missed these 4 defects (gladly, I remembered about one of them while reporting to a client in their JIRA). Then I had to manually compare each defect if it was reported or not by opening it and checking the Defect ID field for each individual defect. 

    No doubt, I would have missed that if I'd just pull the Excel or did not remember one specific issue that was missing. When you create reports and assign specific standards you do not go to double-check the organization level standards because of the expectation from modern software and time limits for these tasks.

    Let me know if I can provide you with further details,


  • Admin
    Zahra Safavian commented
    24 Jan, 2020 06:51pm


    Can you provide more details about the scenarios in which you are creating manual violations against BPs and Standards that are not enabled for the customer's organization? I believe within the context of the baseline testing offering we are supposed to stick to violations within WCAG 2.0 or 2.1. The OTC exists to ensure that testing is done against standards that the organization supports and will comply with. This is why AMP has always limited reporting to violations within the organization's supported test set. Is there another use case that we should account for?

  • Guest commented
    24 Jan, 2020 04:37pm

    If users are not aware the violation instances report may not contain all issues identified in testing, this is a huge flag and concern from a customer success and experience POV.

  • Anna Kanterova commented
    22 Jan, 2020 08:52pm

    Or that be useful to prompt an admin while creating a report with some standards that are not mapped to OTC (aka to the organization) to notify them about the risks (i.e. "This is a new standard and it won’t be mapped to the organization by default and you will not see these violations elsewhere going forward") and offering to add these new standards to the OTC