Issue severity and prioritization

Severity is a label that helps organize findings for review. It offers a prioritization signal, but it is not a definitive measurement of user impact or legal risk.

Use severity to guide your review, then consider page context and user impact. Findings affecting essential tasks or repeated across important pages may deserve early attention.

Yes. A lower-severity issue may affect important content or a key task. Review each finding in context rather than relying on the label alone.

No. Scan findings identify potential issues from supported checks. Verify the affected element and determine whether the result applies to your page.

Start with important visitor journeys, such as navigation, account access, checkout, or contact flows. Look for repeated patterns and address shared components where appropriate.

The scan review tools may provide filters for supported severity levels or categories. Use them to narrow the list while keeping track of findings that still need review.

No. Severity helps organize findings, but scans do not cover every accessibility requirement. Continue reviewing all relevant findings and perform manual accessibility testing.

Inspect the updated element and test the relevant experience. Publish through Webflow, then run a comparable scan to check whether the automated finding changed. Manual checks may still be necessary.

Comparing similar scans can help show which findings changed between runs. Differences do not automatically confirm a fix; verify the page and test the experience.

No. Severity labels and automated findings support review but do not replace a comprehensive accessibility evaluation by qualified professionals.

Test keyboard navigation, visible focus, screen-reader output, dynamic content, and complete task flows. Also evaluate contrast and other visual requirements in their actual page context.

No. They are product guidance for organizing scan findings, not a compliance determination, certification, or legal assessment.