AccessFix home pageAccessibility and security report Back to websiteGet a free scan
AccessFix

Accessibility and security report

www.w3.org

An outside check of the pages shoppers use most, for barriers that stop disabled people from buying and for security gaps an attacker could use.

Prepared for
Sample: W3C’s demo site
Prepared by
AccessFix
Date
26 October 2026
Pages checked
4
Standard
WCAG 2.2 A and AA
01

At a glance

We found 21 problems that can stop shoppers from finishing a purchase, and 83 more that make the store confusing or hard to use. The security check found no high- or medium-risk issues.

Accessibility

7 problem types across 4 pages

21problems that can block shoppers
83problems that are confusing or hard to use
0polish items

Security

Passive check from the outside

0high-risk findings
0medium-risk findings
0low-risk findings
10checks passed

Pages checked

Accessibility problems by page
PageBlocks shoppersConfusingPolish
Homehttps://www.w3.org/WAI/demos/bad/before/home.html8380
Newshttps://www.w3.org/WAI/demos/bad/before/news.html5420
Ticketshttps://www.w3.org/WAI/demos/bad/before/tickets.html5370
Surveyhttps://www.w3.org/WAI/demos/bad/before/survey.html17270
Please read: automated checks catch only part of accessibility problems. Things like keyboard use, screen-reader flow and how pop-ups behave need a person to test. This report is not a legal assessment and does not certify compliance with any law or standard. 4 further checks could not be decided automatically and need a human review.
02

Accessibility: fix these first

The problems that affect shoppers most, across every page we checked.

Blocks shoppers

Form fields have no label

11 elements · Survey · WCAG 4.1.2

What it means for shoppers

Screen-reader users do not know what to type into a field (email, search, quantity, address), so they cannot complete it.

How to fix

Connect a visible <label> to each field, or add aria-label when a visible label is not possible.

Technical guidance for “Form fields have no label”

Screenshot of an element with this problem on the Survey page
Example on Survey
Blocks shoppers

Links have no name

7 elements · Home, News, Tickets and Survey · WCAG 2.4.4, 4.1.2

What it means for shoppers

Links made only of an icon or image are read as "link" with no destination, so shoppers cannot navigate.

How to fix

Add text inside the link, alt text on its image, or an aria-label that says where it goes.

Technical guidance for “Links have no name”

Screenshot of an element with this problem on the Home page
Example on Home
Blocks shoppers

Drop-down menus have no label

3 elements · Home, News, Tickets and Survey · WCAG 4.1.2

What it means for shoppers

Shoppers cannot tell what a drop-down is for (size, colour, sort order).

How to fix

Add a <label> or aria-label to every <select>.

Technical guidance for “Drop-down menus have no label”

Screenshot of an element with this problem on the Home page
Example on Home
Confusing or hard to use

Images have no description

64 elements · Home, News, Tickets and Survey · WCAG 1.1.1

What it means for shoppers

A blind shopper using a screen reader hears "image" or a file name instead of what the product or picture shows.

How to fix

Add short alt text that says what the image shows (for products: name, colour, angle). Decorative images get empty alt text (alt="").

Technical guidance for “Images have no description”

Screenshot of an element with this problem on the Home page
Example on Home
Confusing or hard to use

Text is hard to read (low contrast)

10 elements · Home and Tickets · WCAG 1.4.3

What it means for shoppers

Shoppers with low vision, older eyes or bright screens cannot read prices, labels or buttons.

How to fix

Darken the text or lighten the background until it meets WCAG AA (4.5:1 for normal text, 3:1 for large text).

Technical guidance for “Text is hard to read (low contrast)”

Screenshot of an element with this problem on the Home page
Example on Home
03

Security check

An outside look at the gaps an attacker could use, ranked by risk.

How this was checked: we only looked at what any visitor’s browser receives: response headers, page code, the site’s own scripts and the libraries they load. We did not try to break in, guess passwords or open hidden pages. A clean result does not mean a site cannot be hacked. Deeper testing needs the owner’s written permission.

No security problems were found by these outside checks.

Checks with no problems found

  • Plain http:// visits are redirected to https://.
  • Pages are served over HTTPS.
  • Browsers are told to always use a secure connection (HSTS).
  • The store cannot be framed inside another site (clickjacking protection).
  • Browsers will not guess file types (X-Content-Type-Options).
  • A Content Security Policy is set.
  • No known-vulnerable versions of common libraries were detected.
  • No secret keys were found in page code or the store’s own scripts.
  • Every file on the scanned pages loads over HTTPS.
  • Forms send their data over HTTPS.
04

Accessibility, page by page

Every problem on every page, for whoever makes the fixes.

Home

https://www.w3.org/WAI/demos/bad/before/home.html

Problems on the Home page
ProblemPriorityElements
Links have no name
Show 7 affected elements for “Links have no name”
  • #home > a[onfocus="blur();"]
  • #news > a[onfocus="blur();"]
  • #tickets > a[onfocus="blur();"]
  • #survey > a[onfocus="blur();"]
  • .story:nth-child(1) > span > a[href$="news.html"][onfocus="blur();"]
  • .story:nth-child(2) > span > a[href$="news.html"][onfocus="blur();"]
  • .story:nth-child(3) > span > a[href$="news.html"][onfocus="blur();"]
Blocks shoppers7
Drop-down menus have no label
Show 1 affected element for “Drop-down menus have no label”
  • select
Blocks shoppers1
Images have no description
Show 33 affected elements for “Images have no description”
  • img[src$="border_left_top.gif"]
  • img[src$="border_top.gif"]
  • img[src$="border_right_top.gif"]
  • img[src$="border_left.gif"]
  • img[src$="top_logo_next_end.gif"]
  • img[src$="top_weather.gif"]
  • img[src$="top_logo_next_start.gif"]
  • img[src$="mark.gif"]
  • td[colspan="5"][background="./img/marker2_w.gif"][width="780px"] > img[src$="marker2_w.gif"][width="78px"][height="1px"]
  • td[width="155px"][background="./img/marker2_w.gif"] > img[src$="marker2_w.gif"][width="78px"][height="1px"]
  • img[width="1"]
  • img[name="nav_home"]
  • tr[height="1px"]:nth-child(3) > td[width="154px"][background="./img/marker2_w.gif"] > img[src$="marker2_w.gif"][width="78px"][height="1px"]
  • img[src$="nav_news.gif"]
  • tr[height="1px"]:nth-child(5) > td[width="154px"][background="./img/marker2_w.gif"] > img[src$="marker2_w.gif"][width="78px"][height="1px"]
  • img[name="nav_facts"]
  • tr[height="1px"]:nth-child(7) > td[width="154px"][background="./img/marker2_w.gif"] > img[src$="marker2_w.gif"][width="78px"][height="1px"]
  • img[src$="nav_survey.gif"]
  • tr[height="1px"]:nth-child(9) > td[width="154px"][background="./img/marker2_w.gif"] > img[src$="marker2_w.gif"][width="78px"][height="1px"]
  • td[width="20px"]:nth-child(2) > img[src$="blank_5x5.gif"][height="5px"][width="20px"]
  • .newsheadline:nth-child(1) > img[src$="headline_middle.gif"][width="23"][height="24"]
  • .newsheadline:nth-child(2) > img[src$="headline_middle.gif"][width="23"][height="24"]
  • .newsheadline:nth-child(3) > img[src$="headline_middle.gif"][width="23"][height="24"]
  • td[width="20px"]:nth-child(4) > img[src$="blank_5x5.gif"][height="5px"][width="20px"]
  • img[src$="marker2_t.gif"][height="30px"][width="1px"]
  • …and 8 more
Confusing or hard to use33
Text is hard to read (low contrast)
Show 2 affected elements for “Text is hard to read (low contrast)”
  • tr[height="25px"]:nth-child(2) > td[bgcolor="#A9B8BF"][width="150px"] > font[color="#41545D"][size="2"] > b
  • tr[height="25px"]:nth-child(7) > td[bgcolor="#A9B8BF"][width="150px"] > font[color="#41545D"][size="2"] > b
Confusing or hard to use2
Tap targets are too small
Show 2 affected elements for “Tap targets are too small”
  • .inaccessible > .report[href$="home.html"]
  • .accessible > .report[href$="home.html"]
Confusing or hard to use2
Page language is not set
Show 1 affected element for “Page language is not set”
  • html
Confusing or hard to use1

News

https://www.w3.org/WAI/demos/bad/before/news.html

Problems on the News page
ProblemPriorityElements
Links have no name
Show 4 affected elements for “Links have no name”
  • #home > a[onfocus="blur();"]
  • #news > a[onfocus="blur();"]
  • #tickets > a[onfocus="blur();"]
  • #survey > a[onfocus="blur();"]
Blocks shoppers4
Drop-down menus have no label
Show 1 affected element for “Drop-down menus have no label”
  • select
Blocks shoppers1
Images have no description
Show 39 affected elements for “Images have no description”
  • img[src$="border_left_top.gif"]
  • img[src$="border_top.gif"]
  • img[src$="border_right_top.gif"]
  • img[src$="border_left.gif"]
  • img[src$="top_logo_next_end.gif"]
  • img[src$="top_weather.gif"]
  • img[src$="top_logo_next_start.gif"]
  • img[src$="mark.gif"]
  • td[colspan="5"][width="780px"][background="./img/marker2_w.gif"] > img[width="78px"][src$="marker2_w.gif"][height="1px"]
  • td[width="155px"][background="./img/marker2_w.gif"] > img[width="78px"][src$="marker2_w.gif"][height="1px"]
  • img[height="30px"]
  • img[name="nav_home"]
  • tr[height="1px"]:nth-child(3) > td[width="154px"][background="./img/marker2_w.gif"] > img[width="78px"][src$="marker2_w.gif"][height="1px"]
  • img[src$="nav_news.gif"]
  • tr[height="1px"]:nth-child(5) > td[width="154px"][background="./img/marker2_w.gif"] > img[width="78px"][src$="marker2_w.gif"][height="1px"]
  • img[name="nav_facts"]
  • tr[height="1px"]:nth-child(7) > td[width="154px"][background="./img/marker2_w.gif"] > img[width="78px"][src$="marker2_w.gif"][height="1px"]
  • img[src$="nav_survey.gif"]
  • tr[height="1px"]:nth-child(9) > td[width="154px"][background="./img/marker2_w.gif"] > img[width="78px"][src$="marker2_w.gif"][height="1px"]
  • img[src$="blank_5x5.gif"]
  • table[cellspacing="0"][cellpadding="0"][width="100%"] > tbody > tr:nth-child(1) > td[background="./img/marker2_t.gif"][rowspan="9"][valign="top"] > img[height="30"][src$="marker2_t.gif"][width="1"]
  • table[cellspacing="0"][cellpadding="0"][width="100%"] > tbody > tr:nth-child(1) > td[background="./img/marker2_w.gif"] > img[height="1"][width="78"][src$="marker2_w.gif"]
  • table[cellspacing="0"][cellpadding="0"][width="100%"] > tbody > tr[bgcolor="#ededed"] > td:nth-child(1) > .headline > img[height="24"][src$="headline_middle.gif"][width="23"]
  • tr[bgcolor="#ededed"] > td[background="./img/marker2_t.gif"][rowspan="9"][valign="top"] > img[height="30"][src$="marker2_t.gif"][width="1"]
  • table[cellspacing="0"][cellpadding="0"][width="100%"] > tbody > tr:nth-child(4) > td[width="275"][background="./img/marker2_w.gif"] > img[height="1"][width="78"][src$="marker2_w.gif"]
  • …and 14 more
Confusing or hard to use39
Tap targets are too small
Show 2 affected elements for “Tap targets are too small”
  • .inaccessible > .report[href$="news.html"]
  • .accessible > .report[href$="news.html"]
Confusing or hard to use2
Page language is not set
Show 1 affected element for “Page language is not set”
  • html
Confusing or hard to use1

Tickets

https://www.w3.org/WAI/demos/bad/before/tickets.html

Problems on the Tickets page
ProblemPriorityElements
Links have no name
Show 4 affected elements for “Links have no name”
  • #home > a[onfocus="blur();"]
  • #news > a[onfocus="blur();"]
  • #tickets > a[onfocus="blur();"]
  • #survey > a[onfocus="blur();"]
Blocks shoppers4
Drop-down menus have no label
Show 1 affected element for “Drop-down menus have no label”
  • select
Blocks shoppers1
Images have no description
Show 26 affected elements for “Images have no description”
  • img[src$="border_left_top.gif"]
  • img[src$="border_top.gif"]
  • img[src$="border_right_top.gif"]
  • img[src$="border_left.gif"]
  • img[src$="top_logo_next_end.gif"]
  • img[src$="top_weather.gif"]
  • img[src$="top_logo_next_start.gif"]
  • img[src$="mark.gif"]
  • td[background="./img/marker2_w.gif"][colspan="5"][width="780px"] > img[src$="marker2_w.gif"][width="78px"][height="1px"]
  • td[width="155px"][background="./img/marker2_w.gif"] > img[src$="marker2_w.gif"][width="78px"][height="1px"]
  • img[src$="marker2_t.gif"]
  • img[name="nav_home"]
  • tr[height="1px"]:nth-child(3) > td[background="./img/marker2_w.gif"][width="154px"] > img[src$="marker2_w.gif"][width="78px"][height="1px"]
  • img[src$="nav_news.gif"]
  • tr[height="1px"]:nth-child(5) > td[background="./img/marker2_w.gif"][width="154px"] > img[src$="marker2_w.gif"][width="78px"][height="1px"]
  • img[name="nav_facts"]
  • tr[height="1px"]:nth-child(7) > td[background="./img/marker2_w.gif"][width="154px"] > img[src$="marker2_w.gif"][width="78px"][height="1px"]
  • img[src$="nav_survey.gif"]
  • tr[height="1px"]:nth-child(9) > td[background="./img/marker2_w.gif"][width="154px"] > img[src$="marker2_w.gif"][width="78px"][height="1px"]
  • img[src$="blank_5x5.gif"]
  • p:nth-child(1) > img[border="0"]
  • th > img[border="0"]
  • img[src$="border_right.gif"]
  • img[src$="border_bottom_left.gif"]
  • img[src$="border_bottom.gif"]
  • …and 1 more
Confusing or hard to use26
Text is hard to read (low contrast)
Show 8 affected elements for “Text is hard to read (low contrast)”
  • table[width="250px"] > tbody > tr[bgcolor="#A9B8BF"] > td:nth-child(1) > b > font[color="41545D"]
  • table[width="250px"] > tbody > tr[bgcolor="#A9B8BF"] > td:nth-child(2) > b > font[color="41545D"]
  • .prices > tbody > tr[bgcolor="#A9B8BF"]:nth-child(1) > td:nth-child(1) > b > font[color="41545D"]
  • .prices > tbody > tr[bgcolor="#A9B8BF"]:nth-child(1) > td:nth-child(2) > b > font[color="41545D"]
  • td:nth-child(3) > b > font[color="41545D"]
  • td:nth-child(4) > b > font[color="41545D"]
  • td:nth-child(5) > b > font[color="41545D"]
  • tr[bgcolor="#A9B8BF"]:nth-child(7) > td[colspan="5"] > b > font[color="41545D"]
Confusing or hard to use8
Tap targets are too small
Show 2 affected elements for “Tap targets are too small”
  • .inaccessible > .report[href$="tickets.html"]
  • .accessible > .report[href$="tickets.html"]
Confusing or hard to use2
Page language is not set
Show 1 affected element for “Page language is not set”
  • html
Confusing or hard to use1

Survey

https://www.w3.org/WAI/demos/bad/before/survey.html

Problems on the Survey page
ProblemPriorityElements
Form fields have no label
Show 11 affected elements for “Form fields have no label”
  • input[value="1"]
  • input[value="2"]
  • input[value="3"]
  • input[value="4"]
  • input[value="5"]
  • input[value="6"]
  • input[value="mr"]
  • input[value="mrs"]
  • #em
  • #n
  • #ev
Blocks shoppers11
Links have no name
Show 4 affected elements for “Links have no name”
  • #home > a[onfocus="blur();"]
  • #news > a[onfocus="blur();"]
  • #tickets > a[onfocus="blur();"]
  • #survey > a[onfocus="blur();"]
Blocks shoppers4
Drop-down menus have no label
Show 2 affected elements for “Drop-down menus have no label”
  • select[onchange="location.href = this.value;"]
  • select[name="cc"]
Blocks shoppers2
Images have no description
Show 24 affected elements for “Images have no description”
  • img[src$="border_left_top.gif"]
  • img[src$="border_top.gif"]
  • img[src$="border_right_top.gif"]
  • img[src$="border_left.gif"]
  • img[src$="top_logo_next_end.gif"]
  • img[src$="top_weather.gif"]
  • img[src$="top_logo_next_start.gif"]
  • img[src$="mark.gif"]
  • td[colspan="5"][background="./img/marker2_w.gif"][width="780px"] > img[src$="marker2_w.gif"][width="78px"][height="1px"]
  • td[width="155px"][background="./img/marker2_w.gif"] > img[src$="marker2_w.gif"][width="78px"][height="1px"]
  • img[src$="marker2_t.gif"]
  • img[name="nav_home"]
  • tr[height="1px"]:nth-child(3) > td[background="./img/marker2_w.gif"][width="154px"] > img[src$="marker2_w.gif"][width="78px"][height="1px"]
  • img[src$="nav_news.gif"]
  • tr[height="1px"]:nth-child(5) > td[background="./img/marker2_w.gif"][width="154px"] > img[src$="marker2_w.gif"][width="78px"][height="1px"]
  • img[name="nav_facts"]
  • tr[height="1px"]:nth-child(7) > td[background="./img/marker2_w.gif"][width="154px"] > img[src$="marker2_w.gif"][width="78px"][height="1px"]
  • img[src$="nav_survey.gif"]
  • tr[height="1px"]:nth-child(9) > td[background="./img/marker2_w.gif"][width="154px"] > img[src$="marker2_w.gif"][width="78px"][height="1px"]
  • img[src$="blank_5x5.gif"]
  • img[src$="border_right.gif"]
  • img[src$="border_bottom_left.gif"]
  • img[src$="border_bottom.gif"]
  • img[src$="border_bottom_right.gif"]
Confusing or hard to use24
Tap targets are too small
Show 2 affected elements for “Tap targets are too small”
  • .inaccessible > .report[href$="survey.html"]
  • .accessible > .report[href$="survey.html"]
Confusing or hard to use2
Page language is not set
Show 1 affected element for “Page language is not set”
  • html
Confusing or hard to use1
05

How we checked

Date
26 October 2026, 17:36 UTC
Pages
Home, News, Tickets and Survey
Accessibility
axe-core 4.14.0 with WCAG 2.0, 2.1 and 2.2 A and AA rules
Security
Passive check of headers, page code, the site’s own scripts and known-vulnerable libraries
Tool
AccessFix scanner 0.1.0
  • Only public pages were visited. Nothing was logged into, submitted or changed.
  • Automated checks catch only part of accessibility problems. Keyboard use, screen-reader flow and pop-up behaviour need a person to test.
  • The security check did not try to break in. A clean result does not mean a site cannot be hacked.
  • This report is not legal advice and does not certify compliance with any law or standard.
06

Next steps

  1. Fix what blocks shoppers

    Start with the “Fix these first” list and any high-risk security finding. Make changes on a duplicate theme, not the live store.

  2. Test by hand

    Check the fixed pages with a screen reader and a keyboard, then run this scan again to compare.

  3. Keep it fixed

    New apps and theme updates can bring problems back. A monthly re-scan catches them early.

Want AccessFix to fix these for you, or have a question about this report?

hello@accessfixhq.com