Auditing process
In the form below you can state your preferences for the auditing process. Here’s an example process:
- We could start with an online meeting where you demonstrate how people might use it. This is optional, but could be helpful if your product is very complex or technical.
- Our test team, consisting of IT and Design students and researchers, will do an accessibility scan. This is not a complete WCAG audit, but a scan of the most common issues. If you are interested in how we test, or want to learn how to do your own testing, we can do the testing together during a call.
- We provide a report with the accessibility issues along with a link to more info or possible solutions.
- If you have any questions, you can email them, or we can schedule a call to discuss our findings.
- You are welcome to request another scan after fixing the issues!
It usually takes around 4 weeks from completing the form to receiving a report. Update (19 Oct): we cannot schedule calls or ‘live’ audits in Oct/Nov since we are fully booked. We will continue our scans and reports, so you have the option to receive an auditing report, or to wait a while for a live audit.
Requirements
We need easy access to the product or prototype that needs testing. Installing an app is fine, but we won’t set up servers. Please include instructions, test account etc.
Note: we only audit NGI projects. NGI REVIEW requests need to go through NLNet first.
Scan request form