Here are some common terms used in the platform interface and documentation:
| Term | Definition |
|---|---|
Dashboard |
The dashboard displays policy compliance data and common trends from the digital assets across your workspace. |
Digital asset |
Digital assets are the individual websites and apps that are tested in a workspace. For details, refer to Your digital assets. |
Digital asset key |
The unique 2-5 letter/number value that’s assigned when the digital asset is created.
For more information, refer to Edit digital asset details. |
Evaluation |
There are two types of evaluations:
|
Files |
Upload files that you want to store in platform or share with Level Access team members. For details, review Workspace files (create, view, download). |
Finding ID |
A unique identifier of a finding. Findings can be a result of manual testing or scans. They are instances where scan rules are violated or manual testing detects an issue. The same rule can be violated more than once on a digital asset, so you can have multiple findings from the same rule. |
Level Access browser extension |
An extension that runs accessibility scans from your browser. |
PDF accessibility checker |
A testing feature of the platform that runs automated tests on PDFs you've uploaded. For details, refer to PDF accessibility checker. |
Organization |
An organization is the highest level of the platform hierarchy. Organizations hold workspaces and their digital assets. For details, refer to Your organization. |
Overview |
The overview shows the overall accessibility stats of a digital asset. For details, refer to Get started with Digital Asset Overview. |
Resolved findings |
Findings with the statuses of Closed, Dismissed, Fixed, Not reproducible, and Dismissed. For more information, refer to View details of resolved findings in the Workspace Dashboard and Filter Dashboard findings by source (scans or evaluations). |
Scans |
Scans are automated accessibility tests that use the testing tools in the Level Access Platform. For more information, refer to Scanning. |
Scan rules |
Use scan rules to configure which rules you want to include for testing on specific digital assets. |
Testing tool |
An accessibility testing tool or testing engine, also known as a rule library, is a structured collection of automated tests designed to evaluate digital assets—such as websites, mobile apps, and documents—for compliance with accessibility standards and best practices. These engines apply predefined rules to identify potential barriers that could prevent people with disabilities from fully interacting with or understanding the content. Our default testing engine is Access Engine. You can change your default testing tool, as well as view results originating from different testing tools. You can view the results from the workspace dashboard or the Program dashboard. |
Unresolved findings |
Findings with the statuses of Open, Re-open, Not fixed, Partially fixed, and Cannot be fixed. For more information, refer to View details of unresolved findings in the Workspace Dashboard.
|
User groups |
A user group consists of one or more entities and an associated set of security permissions used to manage access to the platform’s areas and functionality. For details, refer to User groups and permissions.
|
Workspace |
Workspaces hold digital assets and their testing and remediation data. Projects and tasks are configured at the workspace level and if you belong to more than one workspace, you can switch between them using the dropdown in the top-level navigation. For details, refer to Your workspace. |
Comments
0 comments
Article is closed for comments.