Documentation
Common questions about auditing forms for accessibility.
Some websites block requests from serverless IPs (like ours) as a security measure. This is common with government sites and enterprise platforms. Use the "Audit by HTML upload" option instead – save the page source and upload it directly.
Yes! For forms with multiple pages, save each step as a separate HTML file and upload them all at once. The audit will process them in order and combine the results.
No. All audits are processed in memory and discarded immediately. We don't store your page content, form data, or audit results. Results go straight to your browser.
We support most web forms regardless of platform, including Drupal, OpenForms, Snapforms, Formlify, and custom-built forms. If the form renders as HTML, we can audit it.
The Resident Experience Score is strict by design. Common issues like missing labels, poor input types, or lack of error messages all contribute to deductions. Check the "Top drivers" section to see which issues have the biggest impact.
Our checks are based on WCAG 2.1 AA guidelines and form usability best practices. However, this audit is not a formal WCAG compliance assessment. It's a practical tool to identify common accessibility issues.
Not directly via URL. For authenticated pages, use the HTML upload option: log in to the site, navigate to the form, save the page source, and upload it.
We recommend auditing after any significant changes to form structure or styling. Many teams include form audits as part of their QA process before deploying updates.
Yes. AuditMyForm fetches publicly accessible HTML for accessibility analysis only – the same content any browser or search engine can access. We do not store, cache, or redistribute any content. Accessibility auditing is a legitimate public interest activity.
Email phil@auditmyform.com and we'll help you out.