Product · one finding, end to end
Follow one barrier from found to fixed.
Instead of a feature list, this page takes a single real finding — an unlabelled search box in a site header — and walks it through every stage OpenForAll puts it through. Same box, five chapters, nothing skipped.
Real browser renderingWCAG 2.2 AA mappingVersioned rule set
header > .site-search input[type="search"]A real browser looks at the page your visitor actually gets
The search box is built by JavaScript after the page loads, so a source-code checker never sees it. OpenForAll opens each page in a real browser, waits for it to finish building, then checks what is on screen — and points at the one element that failed, not just the page it sat on.
- Follows your sitemap on its own, with a stated limit on how far it goes
- Pages it did not open are listed for you, never quietly dropped
- Runs in the background, so a slow site never blocks your account
/Scanned/moebel/stuhl-eicheScanned/kasseScanned/moebel/stuhl-eiche?ref=mailDuplicatehttps://external.example/previewDifferent domain
Both skipped URLs are named in the report with the reason. Coverage is part of the result, not a footnote.
Same selector on every page — this is one shared header component, not 48 separate jobs.
/1 occurrence/moebel/stuhl-eiche1 occurrence/kasse1 occurrence- + 45 more pages
One component, forty-eight pages, one line in your list
A raw scanner would hand you 48 findings. They are the same box in the same header, so OpenForAll folds them into one item with every affected page underneath — and tells you plainly that this is a shared component, so you fix it once.
- See how many times, and on exactly which pages
- A suggested owner — content, design, or development — so it lands on the right desk
- Sorted by how much of your site it actually affects, not by when it was found
The rule, the screenshot, and the exact line to change
Whoever picks this up should not have to reproduce it. The finding carries the success criterion in plain words, a cropped screenshot of the box itself, and the markup as it is today next to the markup it should be. Nobody has to guess which input, on which page, in which state.
A screen-reader user reaches this box and hears only "edit text, blank". There is nothing to say what typing here does, so the site's search is unusable without sighted guesswork.
Cropped to the element, captured at scan time — kept as-is even after the fix.
header > .site-search input[type="search"]<input type="search"
placeholder="Suche"><label for="site-search"
class="visually-hidden">
Website durchsuchen
</label>
<input type="search" id="site-search"
placeholder="Suche">A placeholder is not a label — it disappears the moment someone types, and most screen readers never announce it. The guidance names the fix; it does not just name the rule.
It becomes somebody’s job, with a date on it
Findings that belong to nobody get fixed by nobody. This one goes to whoever maintains the header, with a due date and the whole evidence trail attached — so the handover is the finding itself, not a screenshot pasted into a chat.
- Assign to a teammate, a freelancer, or an agency colleague
- Due dates with reminders, so nothing stays open for months
- Anything a machine cannot judge goes to a human-review list instead of being called a pass
"Fixing in header.twig — same box is in the checkout header, so both come with this release."
The audit trail: a dated record, not a status flag
Marking something fixed proves nothing. OpenForAll re-scans the 48 pages, writes a second piece of evidence beside the first, and keeps both. The original failure is never deleted — which is what turns "we handled it" into something you can hand to a client, a procurement officer, or an auditor two years later.
And if the box loses its label again in a later release, the trail says so, on the date it happened.
- 04 Mar 2026Found on 48 pagesScan #1184 · rule set v2026.02 · evidence screenshot storedEvidence 1
- 05 Mar 2026Assigned to DevelopmentDue 11 Mar · note added by M. Weber
- 11 Mar 2026Marked handled, re-scan requestedTargeted re-scan queued for all 48 affected pages
- 12 Mar 2026Re-scan passed — 48 of 48 pagesScan #1207 · second screenshot stored beside the first, neither overwrites the otherEvidence 2
- 18 Jun 2026Came back on 2 pages after a theme updateFlagged as a regression against the March fix, not filed as a brand-new finding
Everything else
That was one finding. Here is the rest, in one screen.
Scanning
- Real browser, JavaScript included
- Automatic sitemap discovery
- Scheduled weekly or monthly monitoring
- Scans behind a login, with your permission
- Coverage report naming every skipped URL
Findings
- Grouped by rule across pages
- WCAG 2.2 AA criterion and level
- Cropped evidence screenshot
- Selector and the markup to change
- Suggested owner and severity
Getting it fixed
- Assignment, due dates, reminders
- Targeted re-scan on request
- Regression detection against past fixes
- Human-review list for judgement calls
- Dated audit trail per finding paid plans
Sharing and teams
- PDF reports with your methodology stated
- Recurring report subscriptions
- White-label branding Agency +
- Role-based access and invitations
- Read API and data export
Managing this across client sites instead of your own? The agency portfolio view groups the same findings by client.
Find your version of the search box.
One scan, no payment, no call. You will get the same five chapters for whatever your own header is hiding.