Nautil Control
accessibility audits by your own team
The same panel Nautil’s auditors use for WCAG audits, for teams that want to audit on their own. Websites, mobile apps and files: errors with screenshots and fix guidance, criteria calculated from the errors and a report generated from a template.
See how the panel works in practice
Six short recordings from the demo version of the panel, on an audit of the nautil.pl website — from the error list and AI to what the audit recipient sees. The recordings have no sound, and below each one we describe what it shows.
Errors
- Error list. Grouped by WCAG principles, with severity, page area and a screenshot thumbnail.
- Filter. Only the two critical errors.
- Error window. Screenshots with markings, WCAG criteria, severity, area, who fixes it and a description of the problem.
- How to fix. AI writes it from the description and screenshots, and the auditor marks the error as ready.
- Export. The error list downloaded as an Excel file.
AI and scanner
- Sample errors. Three errors from the nautil.pl audit with a screenshot, title and area — without a description, severity or fix guidance.
- Generate everything at once. AI fills in the description, severity, fix guidance and role in all of the audit’s errors (about a minute, cut from the recording).
- The result in the error window. The description, severity, role and fix guidance written by AI, each with a button for the auditor to verify it.
- Scanner. The axe-core tool checks two pages on the server, and the auditor approves the findings with screenshots.
- Error list. The new errors among the recently added ones.
File audit
- Audit details. The file and document platform and a PDF/UA-1 conformance check.
- File check. The panel reads a sample PDF file in the browser — tags, alternative texts, headings and metadata. The file is not sent to the server.
- Suggested errors. Four errors, each with a WCAG criterion or a PDF/UA condition.
- Adding. The selected suggestions go to the audit’s error list.
Criteria and statement
- Success criteria. WCAG 2.2 AA: 29 met, 12 not met and 14 not applicable — calculated from the errors.
- Not met. The filter shows the 12 criteria with errors.
- Accessibility statement. The checker finds the statement on the website by itself and checks the requirements of Article 10 of the Polish Digital Accessibility Act and the technical conditions.
- Result. Each gap marked as an error or a remark.
- Auditor’s assessment. The checker’s suggestion fills in the verdict, and the auditor saves it.
Re-audit and report
- Re-audit. A copy of the audit for re-verification after fixes.
- Verification. A keyboard error marked as fixed.
- Criteria. Recalculated from the errors and compared with the previous audit, with the changed criterion marked as improved.
- Report. Generated from a template in Google Docs (about 3 minutes, cut from the recording).
- Finished document. The re-audit report: cover, basic information and the team.
Results for the recipient
- Recipient’s dashboard. The audit result: 78% conformance, the severity breakdown and the most frequently failed criteria.
- Errors. Each with a description and fix guidance.
- Question. A thread with the auditor on a specific error.
- Fix. The recipient marks the error as fixed.
- Summary and documents. Results of all audits and the audit files.
What the panel looks like — demo version
-
The audit’s error list -
An error with screenshots, criteria and fix guidance -
WCAG criteria calculated from the errors -
Automatic check of the accessibility statement -
The audit result in the recipient’s panel -
Summary of all audits
An audit that lives in spreadsheets and e-mails
Many teams run accessibility audits the same way: errors in a spreadsheet, screenshots in a folder, a report put together by hand in a text editor, results sent by e-mail. It works — until there are a dozen audits and, after the re-audit, nobody knows what was fixed.
-
Errors in a spreadsheet
The description in a spreadsheet, the screenshot in a folder, and every auditor marks severity and criteria in their own way.
-
A report put together by hand
Descriptions, error numbers and the criteria table copied into the editor for every audit.
-
The statement checked by hand
The requirements of Article 10 of the act and the technical conditions ticked off one by one.
-
A re-audit without a comparison
After the fixes it is hard to tell what was fixed, and the results circulate by e-mail.
The whole audit in one panel
The auditor describes an error once — it goes into the criteria table, the report and the recipient’s panel. The whole team sees the same state of the audit, and the recipient knows straight away what to fix.
-
Errors ready to fix
A screenshot with markings, WCAG criteria, severity, fix guidance and the role that should fix it: developer, designer, editor or author.
-
Compliance with the law
WCAG criteria calculated from the errors, an automatic check of the accessibility statement and EN 301 549 tables for mobile apps and files.
-
Fixing progress
The recipient marks fixed errors and asks the auditor about a specific error, and the re-audit compares the result with the previous one.
-
All of the organisation’s audits
A summary with the median conformance, fixing progress and the criteria not met in the largest number of audits.
Panel features
There is one panel with all the features below — the same ones Nautil’s auditors use every day.
-
Error list and error window
Errors grouped by WCAG principles, with a number, severity, area, screenshots with markings and a change history. Search, filters and export to CSV, Excel and JSON.
-
AI assistant
Descriptions, titles, severity, fix guidance and the role for a single error or many at once. AI suggests and the auditor checks — it never overwrites the auditor’s text.
-
Automatic scanner
The axe-core tool checks the chosen pages on the server. You review the findings with screenshots before saving — only the approved ones go into the audit.
-
Success criteria
A WCAG 2.1 or 2.2 criteria table: met, not met and not applicable calculated from the errors, with manual changes where needed.
-
Accessibility statement
The checker finds the statement on the website by itself and checks the requirements of Article 10 of the Polish act and the technical conditions. The verdict for the report is approved by the auditor.
-
Mobile apps and files
Audits of mobile apps and of PDF, Word, Excel and PowerPoint files, with EN 301 549 tables. The panel pre-checks PDF files in the browser, including PDF/UA conditions — the file is not sent to the server.
-
Scenarios with testers
Tasks for testers with disabilities, a tester form under a separate link and a summary table of the results in the report.
-
Report and re-audit
A report in Google Docs from a template — criteria, charts, errors, the statement and scenarios — with export to PDF and DOCX. The re-audit compares the result with the previous audit.
-
Audit recipient’s panel
A dashboard with the result, errors with descriptions and fix guidance, questions to the auditor about a specific error, marking fixes and a summary of all audits.
-
Compliance statistics
The state of all audited websites and apps: non-compliant with the act, with a critical criterion, statements with gaps, the most frequently failed criteria and who should fix them — with export to PDF.
Nautil’s auditors work in this panel
We use the panel to audit websites, mobile apps and files for public offices, universities, hospitals, museums and companies. The figures below come from the panel (November 2026).
- 260+ audits run in the panel
- 160+ websites and mobile apps audited
- 6,900+ errors described by auditors
- 120+ accessibility statements assessed
96% of the audited websites and apps fail criterion 1.3.1.
From contract to launch — 3 to 5 weeks
Below is the process for the full scope. With a smaller scope, the rollout is shorter. The first 60 days after launch are a support period — configuration fixes and the team’s questions are free of charge.
-
Analysis and configuration
A kick-off meeting, the choice of standards (WCAG 2.1 or 2.2, EN 301 549) and configuration of the panel instance.
-
Accounts and structure
Accounts for auditors and audit recipients, the list of audited websites, apps and files.
-
Report template
A report in your organisation’s identity: logo, details and footer.
-
Testing and training
A trial audit, acceptance tests and online training for auditors — included in the rollout.
-
Launch
The panel under your domain, the official launch and 60 days of post-rollout support.
60 days of support
at no extra cost
What the rollout includes
- Configuration of a panel instance for your organisation.
- Colours and logo matched to your organisation’s identity.
- Accounts for auditors and audit recipients.
- A report template with your organisation’s logo and details.
- Domain or subdomain and SSL certificate setup.
- Online training for the team of auditors.
- 60 days of free fixes after launch.
What annual support includes
- Hosting, monitoring and daily backups.
- Ongoing panel updates and security patches.
- E-mail and phone support for the team.
- Minor configuration adjustments.
- A licence to use the panel during the support period.
We agree the scope and price after a conversation. We send the full price list in an individual offer.
See how it works
The simplest way to assess Nautil Control is a short online consultation. We will show you the working panel live and agree together how to roll it out in your team.
