# Scan WCAG 2.1 Flowy's Scan Tool lets you automatically assesses your website against the Web Content Accessibility Guidelines (WCAG) 2.1, with a detailed report of issues that could impede accessibility for users with disabilities. {% embed url="" %} ### **Why Use Flowy Scan Tool?** * **Automated testing -** The scan tool automates website accessibility checks, saving you time and effort, so you can focus on fixing issues. * **Extensive remediation guidance -** Get detailed instructions, code examples, and best practices to simplify the process of fixing issues. * **No false positives -** All identified issues are genuine problems that need to be addressed, saving valuable time and resources. * **Selective testing -** Focus on specific sections or components, rather than scanning the entire site. Ideal for large sites or when targeting known problem areas. * **Rescan tool -** Easily perform initial scans and re-scan your website after making changes to ensure issues are properly addressed. * **Customizable settings -** Customize your experience with options to fine-tune recommendations, specify website language, use a visual editor, and define themes or templates. * **Collaboration made easy**: Multiple team members can collaborate using the Scan tool, sharing scan results, remediation plans, and more. * **Review requests -** Similar to GitHub, you can request team members to review accessibility fixes to ensure effective accessibility improvements and compliance with organizational policies. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.equally.ai/flowy/flowy-tools/scan-wcag-2.1.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.