The major difference between scans in the Level Access Platform and AMP is the separation of on-demand scans and monitoring. While scanning and monitoring are both automated accessibility testing of code using testing tools, they serve different purposes, have different capabilities, and provide you with different insights.
Note: Unless otherwise mentioned, this article refers to the Level Access Platform features only.
On this page:
- Scans overview
- Monitoring overview
- Scanning and monitoring functionalities
- Scanning and monitoring page limits
- Monitoring functionalities in AMP compared to platform
Scans overview
Scans are automated accessibility tests that are on-demand and user-generated. Scans run once with the selected scan options, unless you re-run the scan. You can use scans for the following:
- Granular analysis
- Use scans to identify specific accessibility barriers throughout your website.
- Pre-production environment
- Scan your pre-production environment to make sure your code is accessible before it goes live. It's important to test pages frequently throughout the Software Development Life Cycle (SDLC), so you can catch issue earlier and save yourself time post-deployment.
- Automated flows
- Create a user flow to determine the accessibility of a user’s journey through your digital property.
- Remediation validation
- Run a scan after you’ve remediated scan findings to immediately validate the fix.
Monitoring overview
Monitoring scans are scheduled scans that occur on a given cadence without any prompting. With monitoring, you can see changes in status over time and easily pinpoint the areas of your digital experiences that require immediate attention. Monitoring is similar to scanning, but monitoring provides a larger picture analysis of your website and helps you identify trends over time. Monitoring is often used for the following purposes:
- Prioritization
- Monitoring allows you to see the frequency of findings across all your digital property, allowing you to make the biggest impact with your remediation work.
- Maintenance
- Once you’ve remediated the necessary findings, monitoring provides scheduled updates on the accessibility of your website so you can be sure your remediation was successful.
- If a new monitoring scan score drops below a certain threshold (customizable by the user) you'll receive an email notification.
- SDLC optimization
- Identify issues that continuously reappear and implement those fixes before future deployments.
Scanning and monitoring functionalities
The table below describes the availability of scanning functionalities for scans and monitoring.
Functionality | Package availability | Available in scanning | Available in monitoring |
---|---|---|---|
Automated flow testing |
Accelerate Enterprise |
✓ | |
PDF discovery | All | ✓ | ✓ |
Component testing |
Accelerate Enterprise |
✓ | ✓ |
Reporting with trend comparison |
All |
✓ |
Scanning and monitoring page limits
The table below describes the page limits for scanning and monitoring per scan.
Feature | Essentials | Accelerate | Enterprise |
---|---|---|---|
Monitoring | 500 | 1000 | 10,000 |
Scanning | 100 | 100 | 100 |
Monitoring functionalities in AMP compared to platform
The table below describes the monitoring functionalities in AMP compared to platform.
Functionality | AMP | Platform |
---|---|---|
Spider/crawl | ✓ | ✓ |
Customizable crawl depth | ✓ | ✓ |
Customizable viewport size | ✓ | ✓ |
HTTP basic authentication | ✓ | ✓ |
Secure web authentication | ✓ | |
Modify headers | ✓ | |
Reporting with trend comparison | ✓ | ✓ |
Comments
0 comments
Article is closed for comments.