Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

12 PASS 4 REVIEW 8 FIX

Link & Button Quality

Action

9 issue(s) across 480 links and 76 buttons

FIX

9 issue(s) across 480 links and 76 buttons

7 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: #; #; #; #; #; #; #

10 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://timesact.com; https://facebook.com/elwdworkwear; https://instagram.com/elwdworkwear; https://facebook.com/elwdworkwear; https://instagram.com/elwdworkwear; https://facebook.com/elwdworkwear; https://instagram.com/elwdworkwear; https://facebook.com/elwdworkwear; https://instagram.com/elwdworkwear; https://www.shopify.com?utm_campaign=poweredby&utm_medium=shopify&utm_source=…

2 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.timesact_bis_submit_button (#332 on page); button.md-trigger (#348 on page)

463 link(s) with descriptive text

480 links

7 empty

0 generic text

10 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://timesact.com	by Timesact	new tab	Add '(opens in new tab)' to text
https://facebook.com/elwdworkwear	Facebook	new tab	Add '(opens in new tab)' to text
https://instagram.com/elwdworkwear	Instagram	new tab	Add '(opens in new tab)' to text
https://facebook.com/elwdworkwear	Facebook	new tab	Add '(opens in new tab)' to text
https://instagram.com/elwdworkwear	Instagram	new tab	Add '(opens in new tab)' to text
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
https://facebook.com/elwdworkwear	Facebook	new tab	Add '(opens in new tab)' to text
https://instagram.com/elwdworkwear	Instagram	new tab	Add '(opens in new tab)' to text
https://facebook.com/elwdworkwear	Facebook	new tab	Add '(opens in new tab)' to text
https://instagram.com/elwdworkwear	Instagram	new tab	Add '(opens in new tab)' to text
https://www.shopify.com?utm_campaign=pow…	Powered by Shopify	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

537 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

#; #; #; #; #; #; #

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://timesact.com; https://facebook.com/elwdworkwear; https://instagram.com/elwdworkwear; https://facebook.com/elwdworkwear; https://instagram.com/elwdworkwear; https://facebook.com/elwdworkwear; https://instagram.com/elwdworkwear; https://facebook.com/elwdworkwear; https://instagram.com/elwdworkwear; https://www.shopify.com?utm_campaign=poweredby&utm_medium=shopify&utm_source=…

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.timesact_bis_submit_button (#332 on page); button.md-trigger (#348 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Mobile Keyboard & Autofill

Action

5/5 eligible field(s) missing autocomplete or inputmode

FIX

5/5 eligible field(s) missing autocomplete or inputmode

1 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.

Got: <input type="email" name="email" id="timesact_bis_email">

4 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email, numeric.

Got: <input type="email" name="email" id="timesact_bis_email">, <input type="number" name="quantity" id="quantity">, <input type="email" name="contact[email]">, <input type="email" name="contact[email]">

Tabindex Anti-Patterns

Action

0 positive, 149 -1-on-focusable

FIX

0 positive, 149 -1-on-focusable

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModeNo Dark Mode Detected

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

Form Accessibility

2 of 15 controls have issues

REVIEW

2 of 15 controls have issues

1 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="checkbox" name="newsletter" id="newsletter">

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="email" name="email" id="timesact_bis_email">

13 control(s) properly labeled

15 controls

13 labeled

1 placeholder only

1 unlabeled

Control	Type	Label	Method
q	text	Search	aria-label
#product-form-template--21523961643230__featured_product_wz79fD-7770470187230-1-opt-0	radio	28	for/id
#product-form-template--21523961643230__featured_product_wz79fD-7770470187230-1-opt-1	radio	30	for/id
#product-form-template--21523961643230__featured_product_wz79fD-7770470187230-1-opt-2	radio	32	for/id
#product-form-template--21523961643230__featured_product_wz79fD-7770470187230-1-opt-3	radio	34	for/id
#product-form-template--21523961643230__featured_product_wz79fD-7770470187230-1-opt-4	radio	36	for/id
#product-form-template--21523961643230__featured_product_wz79fD-7770470187230-1-opt-5	radio	38	for/id
#product-form-template--21523961643230__featured_product_wz79fD-7770470187230-1-opt-6	radio	40	for/id
#product-form-template--21523961643230__featured_product_wz79fD-7770470187230-1-opt-7	radio	42	for/id
#product-form-template--21523961643230__featured_product_wz79fD-7770470187230-1-opt-8	radio	44	for/id
#quantity	number	Quantity	aria-label
contact[email]	email	Email	aria-label
contact[email]	email	Email	aria-label
#timesact_bis_email	email	(eg. username@example.com)	placeholder only
#newsletter	checkbox	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Iframe Accessibility

2/2 iframe(s) missing title; 0 placeholder(s)

REVIEW

2/2 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

Tap Target Adequacy

Action

7 tap target(s) too small or too close together

REVIEW

7 tap target(s) too small or too close together

7 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found – ELWD WORKWEAR ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

A+

Landmark Structure

10 landmarks

PASS

10 landmarks

<main> landmark present

4 <nav> landmark(s) found

All <nav> elements are properly labeled

No contentinfo (footer) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

32 headings

PASS

32 headings

Single H1 present

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H3 (empty)
H1 WORKWEAR THAT MOVES WITH YOU
H2 PERFORMANCE PROVEN ON AND OFF THE TRACK
H2 Mens Workwear
H2 Mens Light Pant Black
H2 What Tradies Are Saying
H2 Shop by Trade
H3 CHIPPIES
H3 CHIPPIES
H3 REFLECTIVE
H3 REFLECTIVE
H3 PLUMBERS
H3 PLUMBERS
H3 SPARKIES
H3 SPARKIES
H3 PAINTERS
H3 PAINTERS
H2 Womens Workwear
H2 Meet the Founders
H2 SHOP WORKWEAR
H2 TEAM 18 SUPERCAR TEAM
H2 MASTER BUILDERS APP AWARDS
H2 TICKFORD RACING TEAM
H2 MORNINGSIDE PANTHERS
H2 PRO RACE BIKES
H2 Learn more about ELWD
H3 ELWD Reflective Elastic Light Short: Stretch Comfort Meets Site-Compliant Hi-Vis
H3 ELWD - Australian owned and operated
H3 Unveiling Innovation: The Canvas ELWD Work Pant Revolution
H2 Performance workwear for men and women
H2 WORKWEAR SHORTS
H2 GRAB A FIRST ORDER DISCOUNT

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

20 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 20 all-caps heading(s)

Alt Text Quality

1 of 419 images have issues

PASS

1 of 419 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

7 decorative image(s) correctly marked

411 image(s) with good alt text

419 images 411 good alt text 7 decorative 1 missing

Issue	Count
missing	1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "q" should use type="search" (currently type="text")

Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

15 form control(s) checked, no input-semantic issues

PASS

15 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Mobile-Readable Font Sizes

All 17 visible text node(s) render at >= 12 CSS pixels

PASS

All 17 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 WORKWEAR THAT MOVES …	9.90:1	3.0:1	#000000	#B2B2B2	Pass
h2 PERFORMANCE PROVEN O…	9.90:1	3.0:1	#000000	#B2B2B2	Pass
h2 What Tradies Are Say…	9.90:1	3.0:1	#000000	#B2B2B2	Pass
h2 Shop by Trade	9.90:1	3.0:1	#000000	#B2B2B2	Pass
h2 Meet the Founders	9.90:1	3.0:1	#000000	#B2B2B2	Pass
h2 SHOP WORKWEAR	9.90:1	3.0:1	#000000	#B2B2B2	Pass
h2 TEAM 18 SUPERCAR TEA…	9.90:1	3.0:1	#000000	#B2B2B2	Pass
h2 MASTER BUILDERS APP …	9.90:1	3.0:1	#000000	#B2B2B2	Pass
h2 TICKFORD RACING TEAM	9.90:1	3.0:1	#000000	#B2B2B2	Pass
h2 MORNINGSIDE PANTHERS	9.90:1	3.0:1	#000000	#B2B2B2	Pass
h2 PRO RACE BIKES	9.90:1	3.0:1	#000000	#B2B2B2	Pass
h2 Performance workwear…	9.90:1	3.0:1	#000000	#B2B2B2	Pass
h2 WORKWEAR SHORTS	9.90:1	3.0:1	#000000	#B2B2B2	Pass
h2 GRAB A FIRST ORDER D…	9.90:1	3.0:1	#000000	#B2B2B2	Pass
h3 CHIPPIES	9.90:1	3.0:1	#000000	#B2B2B2	Pass
h3 CHIPPIES	9.90:1	3.0:1	#000000	#B2B2B2	Pass
h3 REFLECTIVE	9.90:1	3.0:1	#000000	#B2B2B2	Pass
h3 REFLECTIVE	9.90:1	3.0:1	#000000	#B2B2B2	Pass
h3 PLUMBERS	9.90:1	3.0:1	#000000	#B2B2B2	Pass
h3 PLUMBERS	9.90:1	3.0:1	#000000	#B2B2B2	Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

Lighthouse Accessibility Audits

Score 93/100 — 2 failing, 28 passed

PASS

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Reviews `body.template-index > div.okeReviews > div.oke-reviewsTab > span.oke-reviewsTab-label`

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Load slide 1 of 2 `slide-show > div.slideshow-ctrl > div.slideshow-pagination > button.page-btn`
Load slide 2 of 2 `slide-show > div.slideshow-ctrl > div.slideshow-pagination > button.page-btn`
Load slide 1 of 5 `slide-show > div.slideshow-ctrl > div.slideshow-pagination > button.page-btn`
Load slide 2 of 5 `slide-show > div.slideshow-ctrl > div.slideshow-pagination > button.page-btn`
Load slide 3 of 5 `slide-show > div.slideshow-ctrl > div.slideshow-pagination > button.page-btn`
Load slide 4 of 5 `slide-show > div.slideshow-ctrl > div.slideshow-pagination > button.page-btn`
Load slide 5 of 5 `slide-show > div.slideshow-ctrl > div.slideshow-pagination > button.page-btn`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.