Access Continuum Test Results

Access Continuum returns test results to users in JSON. The format of the JSON string looks something like this: 

"helperText":"Provide alternative text that describes the content conveyed by the image."
"attribute":"This element (role=img) does not have a mechanism that allows an accessible name value to be calculated",
"element":"<i role=\"img\" data-type=\"unauth\" class=\"icon-building-midsizedbuilding\"><\/i>"

The following list defines the contents of each of the name-value pairs in the JSON string: 

  1. path: This attribute displays the CSS selector for the node that failed the Access Engine test. 
  2. engineTestId: This attribute is an Access Engine-specific ID associated with the test that failed. Note that this is different from the Best Practice ID, and some Best Practices actually have many different tests that are run against them. 
  3. bestPracticeId: This is the ID for the Best Practice associated with the failed test. Users may use this ID to look up the Best Practice in the Best Practice library within AMP. 
  4. element: The HTML of the element that failed is displayed as the value of this attribute. For example, if a form input fails because an accessible name cannot be calculated the <input> tag, and it's attributes, would be displayed for this field. 
  5. testResult: In the context of Access Continuum this will always display '0,' which is the code for a failed test. Access Continuum only runs automatic tests, so only failed instances will ever be included in the test results.
  6. attribute: This is a textual description of the failure. It describes why the element was failed. 
  7. There are some Access Engine fields that are typically used by Access Alchemy, but they may be useful to users of other products that make use of Access Engine: 
    1. fixType: This is field that categories the type of fix Access Alchemy will make, such as adding a value for an attribute. This field can be ignored when reviewing Access Continuum output. 
    2. fix: This set of fields displays the values Access Alchemy would need to fix the issue automatically. It can be ignored when reviewing Access Continuum output. 
    3. helperText: The value of this field is typically used by Access Alchemy to guide users as to how to use that product to create an Alchemy remediation. However, this field can also be valuable for Access Continuum users, as it provides remediation guidance to the developer.
    4. domSpec: This field is also Access Alchemy specific but may be useful to developers using Access Continuum. This is a Boolean field, with "true" indicating that the violation is specific to the entire page -- e.g., the title or document language -- whereas "false" indicates that there  
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Level Access Support | 800.889.9659
© 2005 - 2018 - Level Access All rights reserved.
Privacy | Security | Credits | License