AI guided accessibility recommendations
Explore next steps for a scan finding. AI uses available issue details to suggest ideas you can review before making a change.
Ideas to help you explore possible next steps
Suggestions depend on the selected finding and available context.
01
Finding-specific ideas
Options tied to the selected issue.
02
Wording improvements
Alt text or labels to review.
03
Examples to explore
Possible code or structure ideas.
04
Helpful explanations
Context for a suggested change.
05
Human review first
Confirm supported changes yourself.
Keep each recommendation in context
Treat the AI response as a draft. Check it against your page and visitors.
01
Open a supported finding
Start with the issue and affected element.
02
Request a recommendation
Explore possible wording or implementation.
03
Review it in context
Check surrounding content and guidance.
04
Confirm a supported change
Inspect the Designer update before applying.
05
Publish, test, and rescan
Verify behavior after Webflow publish.
Review recommendations in context
AI may miss the image purpose, nearby text, or site-specific rules.
Check the element, surrounding content, and relevant guidance. Adapt code samples to your implementation. A suggestion does not confirm a fix or WCAG conformance.
Test the experience, not just the suggestion
AI and automated checks cover supported information only.
Keyboard navigation
Can people complete tasks by keyboard?
Focus visibility
Is the active control clear?
Screen-reader behavior
Are names and instructions clear?
Contrast in context
Can text and controls be distinguished?
Dynamic interactions
Do updates and feedback work?
Complete journeys
Can users finish the whole task?
Frequently asked questions
Get answers about ScrollAccess, website accessibility scanning, AI powered guidance, accessibility tools, WCAG insights, and supported platforms.
They are AI-generated ideas for reviewing or addressing a selected scan finding. Recommendations may include suggested wording, explanations, or examples, depending on the issue and available context.
Run a scan, open a supported finding, and use the available AI assistance in ScrollAccess to request guidance or a suggestion.
They are based on the finding details and context available to the assistant, but they may not include everything about your page, design, visitors, or business rules. Review each recommendation in its actual context.
No. Recommendations are suggestions. Where a supported Designer change is offered, review and confirm it before it is applied. Publishing remains a separate action in Webflow.
No. Suggestions are available only where the feature has enough relevant information. Some issues require design decisions, user testing, or manual expertise.
No. AI may misunderstand an image, miss surrounding context, or suggest a change that does not fit your site. Verify the suggestion before using it.
No. They provide guidance for individual findings and do not certify that a site meets WCAG or legal requirements.
Review the result in the page context, test the relevant experience, and publish through Webflow when you are ready. Then rescan where applicable. Some behavior still needs manual testing.
It may provide HTML or CSS examples when relevant. Treat code as a draft: inspect it, adapt it to your implementation, and test it before use.
No. The finding and its recommendation both need review. Inspect the affected element and determine whether the issue applies to your content and use case.
The assistant uses relevant finding details available in ScrollAccess and any text you provide. See the in-app privacy notice and ScrollAccess Privacy Policy for information about data transmission, retention, and AI processing.
Recommendations can help you decide what to investigate, but they do not replace manual testing. Check keyboard access, focus, screen-reader behavior, dynamic interactions, and full user journeys as appropriate.
No matching FAQs found.