Workspace / Findings

Technical previewSign in

EVIDENCE & REMEDIATION

Assessment report.

Controlled fixture · http://127.0.0.1:63476 · Sep 9, 8:42 PM

This report was generated from a controlled local test fixture. It is not an assessment of your website.

YOUR WEBSITE, EXPLAINED

Review scan coverage

4 areas need attention.

Locate each button listed in the evidence.

Priorities to address46 recorded issue occurrences

Checks with passing results16Within the pages and conditions tested

Questions still open8Need evidence or a person’s review

Pages visited3151 URLs discovered

WHAT WE REACHED

Your plan’s page allowance was reached

3 pages inspected from 151 discovered URLs. 148 eligible URLs remain unchecked; 0 page attempts failed; 3 URLs were excluded.

Discovery covers public links and available sitemaps. Private pages, unlinked pages and journeys that require a person may need a separate review.

Collection details and limits

Page allowance: 3
Successful page responses: 3
Blocked requests: 5
Time used: 12 seconds

Excluded URLs include unsupported query routes, downloadable files and potential account or purchase actions; these were not assessed.
Coverage describes discovered public pages on this exact origin. Unlinked pages, sign-in areas, alternate domains and untested interactions may still exist.

YOUR ACTION PLAN

What to fix, and how to check it.

Start with the highest priority. Each item includes a concrete handoff for your maintainer.

Act firstAccessibility · 1 affected page

Give every button a clear name

An unnamed button leaves screen-reader users guessing which action it performs.

Who can help: Website developer

Make the correction

Locate each button listed in the evidence.
Add visible action text, or give an icon-only button an accessible name that describes its action.
If text is visible, keep the accessible name consistent with that text.

Know when it is done

Tab to each button and check its announced name and action with a screen reader. Rerun the button-name check.

A saved fix is a progress update. A new scan or documented human review verifies the result.

See affected pages and observations (1)

Why this may matter legally

Automated checks identify only some accessibility conditions. A human must assess the relevant journeys and legal context.

Read the source: Accessibility: applicability needs review

Act firstAccessibility · 1 affected page

Make images understandable without seeing them

Visitors using a screen reader may miss the information or action conveyed by an image.

Who can help: Website developer

Make the correction

Decide what each flagged image contributes in its page context.
Give informative images a concise text alternative; describe the action or destination when an image is a link or button.
Use an empty alt attribute for purely decorative images. Explain complex charts in nearby text as well.

Know when it is done

Rerun the image check and read the page with a screen reader. Confirm that meaningful information and linked actions are announced without decorative noise.

A saved fix is a progress update. A new scan or documented human review verifies the result.

See affected pages and observations (1)

Why this may matter legally

Automated checks identify only some accessibility conditions. A human must assess the relevant journeys and legal context.

Read the source: Accessibility: applicability needs review

Act firstAccessibility · 1 affected page

Make buttons and links easier to tap

Small, closely packed controls can make visitors activate the wrong button or link, especially on touchscreens or with limited hand control.

Who can help: Website developer

Make the correction

Locate the controls identified in the evidence and inspect their clickable area and nearby controls.
Make the target at least 24 by 24 CSS pixels, or provide the spacing required by the reported check. Padding can enlarge the clickable area without enlarging the icon.
Review applicable exceptions, including inline links or an equivalent control on the same page, before changing the layout.

Know when it is done

Rerun the target-size check at the affected viewport. Measure target size and spacing, record any applicable exception, and confirm adjacent controls are easy to select on a touchscreen.

A saved fix is a progress update. A new scan or documented human review verifies the result.

See affected pages and observations (1)

Why this may matter legally

Automated checks identify only some accessibility conditions. A human must assess the relevant journeys and legal context.

Read the source: Accessibility: applicability needs review

What held up in testing16 checks with passing results

These checks passed on the listed number of pages. A pass applies to that check and those conditions; another page or check can still need work.

Visitors can open this pageSite inventory
3 pages
Published content is ready for customersMarketing claims
3 pages
Stop browsers guessing executable file typesSecurity
3 pages
Control what page information links discloseSecurity
3 pages
aria-hidden="true" must not be present on the document bodyAccessibility
3 pages
Page must have means to bypass repeated blocksAccessibility
1 page
Make text easier to read against its backgroundAccessibility
3 pages
Give this page a useful browser titleAccessibility
3 pages
Tell assistive technology which language to useAccessibility
3 pages
<html> element must have a valid value for the lang attributeAccessibility
3 pages
Make each link’s destination understandableAccessibility
1 page
Zooming and scaling must not be disabledAccessibility
3 pages
Interactive controls must not be nestedAccessibility
1 page
IDs used in ARIA and labels must be uniqueAccessibility
1 page
Form field must not have multiple label elementsAccessibility
1 page
Tell people what to enter in each fieldAccessibility
1 page

What these results mean

3 pages sampled; 151 other URLs skipped. 6 issue occurrences are grouped into 4 check types. A scan can identify issues; it cannot establish liability, predict a lawsuit bill, or guarantee compliance.

3 pages visited / 3 page allowance

151 skipped · 5 blocked requests · partial

Print / PDF downloads the complete formatted assessment. Open the PDF to print or share it.

Visited and skipped pages (154 records)

Consent scenario evidence

Each scenario starts in an isolated browser context. Only storage names and third-party hosts are retained; values are not captured.

before interaction

observed

0 cookie names · 0 storage keys

No names or third-party hosts recorded.

after accept

observed

1 cookie names · 1 storage keys

127.0.0.1:analytics
local:analytics

after reject

observed

0 cookie names · 0 storage keys

No names or third-party hosts recorded.

after withdrawal

observed

0 cookie names · 0 storage keys

No names or third-party hosts recorded.

OUTSIDE THIS ASSESSMENT

Backend data processing, complete processor inventory, operational deletion, private cancellation flows, authenticated pages, and qualified legal interpretations remain unverified.