Available
How to organise fixes and follow up
An analysis is not the end of the work but the starting point. This is how the process continues, what SiteNorma does in each phase and what is up to you or your team.
The four phases and who does what
| Phase | What SiteNorma does | What you or your team do |
|---|---|---|
| 1. Analyse your website | Goes through the pages with a real browser, on desktop and mobile, and detects issues with automated tests. Shows the pages affected by each one. | You choose the website and start the analysis. The quick scan analyses up to 3 pages; the full scan needs you to have verified that the website is yours. |
| 2. Prioritise and fix | Sorts the issues by severity, explains each one and proposes how to fix it. The same failure repeated on many pages is a single issue. | You decide what to fix first and apply the changes on your website. SiteNorma does not modify it. |
| 3. Review and check | Saves every analysis and compares it with the previous one: resolved and new issues. Guides you through the manual review, criterion by criterion. | You complete the manual review, which no tool can do for you, and run the analysis again after fixing. |
| 4. Keep following up | Keeps the history and the evolution of the estimate. | You run the analysis again when you publish content or make changes. |
Organise the issues
Each element of an issue has its “Issue status”, in three parts that do not stand in for each other:
- Work tracking
- Pending fix, in progress, fix applied awaiting verification or fix postponed. The problem stays in the results and in the score.
- Detection validation
- Pending validation, detection confirmed or detection discarded with justification and evidence. Discarded detections are excluded from the counts and score.
- Check result
- Still detected, not detected in the latest check, could not be checked or needs manual review.
Who can change it and what is recorded
The owner, the administrators and the editors of the organisation can track the work; only the owner and the administrators can discard a detection. Viewers can only look. Each change goes into a history that is never edited, with who made it and when, and discards appear in the reports with their justification and evidence.
Grouping and owners
A failure repeated on many pages, such as a menu button, is a single issue with the list of affected pages: you fix it once. In the PDF reports, each issue says which profile usually fixes it (development, design or content). SiteNorma does not assign issues to specific people: your team organises that.
A recommendation is not a fix
SiteNorma tells you what fails and how to fix it. You or your team apply the changes on your website, or whoever maintains it: SiteNorma does not change your website or fix anything automatically.
Changing an issue’s status does not fix it or change your website. A fix is only counted as checked when a comparable analysis no longer detects it, or when a person reviews it by hand. You can then archive the work; archiving does not certify that your website complies with any regulation.
Manual review is part of the process
Automated tests only detect some of the barriers. Guided manual review completes what no automated test can check. It records results and evidence per criterion; look at the automated result and the review progress separately.
Run the analysis again and check the history
- From your website’s page you start a new quick scan or, if you have verified that the website is yours, a full one.
- Each analysis is saved. The list shows the latest 20 and the evolution of the estimate.
- Each analysis is compared with the previous one: the difference in points, the resolved issues and the new ones.
- To look after the service, a website allows up to 30 analyses a day.
How rescans count towards your plan
Plans are measured in scanned pages per month. Every web address that is analysed counts as one scanned page, desktop and mobile included, also when you run an analysis again. If a page cannot be loaded, the website blocks it or limits the requests, or it fails, it uses nothing, and if the analysis fails no page is used. For example, a weekly scan of 100 pages uses about 430 pages a month.
Before an analysis starts, the dashboard shows how many pages it may use and how many you have left this month. The pages included in each plan are those of the current plan. What is a scanned page? and the plans.
Manual and scheduled follow-up
Manual
You decide when to run the analysis again: after publishing content, changing the design or installing an extension. This is what you can do today.
Scheduled
Scheduled scans are not available yet. When they arrive, weekly scans will come with the paid plans (verified websites only) and daily scans with the Agency plan.
Start using SiteNorma
Create your account and start improving your website’s accessibility. The Free plan includes 10 scanned pages a month, with no card required.