Use Scripts

Link to Use Scripts copied to clipboard

Who should create scripts?

Important: It is important that the scripts are created by a qualified Web developer with a firm grasp of web events and CSS selectors. Script authors should also have a good understanding of what conditions might cause a given page to load with slightly different content, such as viewport size, user agent, or routine content updates. Crucially, script authors should also be familiar with which event hooks the page uses to process user input.

When should scripts be used?

While you are free to utilize scripts axe Monitor as you find beneficial, here are some good and bad use case scenarios for consideration:

Good Examples

The following uses of scripts with axe Monitor® are known to be commonly used with success to accomplish important tasks on the pages being tested:

  • Username/PW Entry & Submission: Secure session establishment that involves automating the sign-in authentication necessary for access to password-protected pages and sites.
  • Analysis of User Input Interactions, such as:
    • Search: Conducting a search in a website.
    • Basic Web Application Interactions: Closing a notification dialog, adding items to a shopping cart (when non-dynamic).

Bad Examples

The following uses of scripts with axe Monitor® are known to have potential to cause frustration due to limitation of the technologies involved on the pages being tested:

  • Q&A Chat Support Bots: Attempts to bypass/ignore comment/question form bots and similar interactive chat popup plugins used for customer service.
  • Dynamic Sites: Sites and pages with content that is not static are subject to changes upon subsequent scans that can prevent scripts from working.

How are scripts created?

Scripts can be created using axe DevTools CLI and then uploaded to an axe Monitor scan using the Add Script button in the Create or Edit Scan wizard in axe Monitor. Use case scripts can analyze content in axe Monitor. Scripts require at least one analyze step, and only the specified pages are scanned (child pages are not scanned).

To know more about sample CLI files, read the topic, Sample CLI Script Files.