WCAG related insights

It identifies a WCAG criterion related to the check or finding. It provides a starting point for understanding the accessibility principle involved.

No. The reference indicates related guidance, while the finding itself may still need human review. Check the affected content and context before deciding what action is appropriate.

No. The scanner evaluates supported patterns only. Many criteria involve context, interaction, or user experience that require manual evaluation.

The app may show WCAG 2.2 references for supported checks. The criteria displayed depend on the finding and the checks available in the current product version.

Review the issue description and affected element. Some findings may not map to a displayed criterion or may need additional manual investigation.

AI assistance may help explain a finding or related accessibility concept in simpler terms. Its response can be incomplete or incorrect, so verify important details against authoritative WCAG guidance.

Not necessarily. Fixing one finding addresses only that issue. Full conformance requires a broader evaluation, including checks that automation cannot perform.

Automated checks cannot fully reproduce keyboard navigation, screen-reader behavior, focus visibility, dynamic interactions, contrast in context, or complete user journeys. Manual testing helps assess these experiences.

They can help organize review, but they do not determine actual impact in every context. Consider the content, affected users, and how the page functions when setting priorities.

Consult the official WCAG documentation for the complete criteria and supporting explanations. Use ScrollAccess references as navigation aids, then review the criterion in its full context.