Skip to content
https://www.winc.com.au

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
79
GRADE
C
FIX
4
REVIEW
8
PASS
12
INFO
0
Checks
24
12 PASS 8 REVIEW 4 FIX
D
Tabindex Anti-Patterns
Action
0 positive, 10 -1-on-focusable
FIX
0 positive, 10 -1-on-focusable
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ffffff
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModePartial Dark Mode
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Back-to-top link detected
Info::
9 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 9 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Landmark Structure
15 landmarks
REVIEW
15 landmarks
Info::
<main> landmark present
Info::
9 <nav> landmark(s) found
Warning::
1 of 9 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Top of Page" SEARCH MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

B
Heading Hierarchy
37 headings
REVIEW
37 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Shop products
  • H2 Discover why we're trusted by 100,000+ workplaces.
  • H3 Solutions tailored for your business.
  • H3 Individuals & small business accounts
  • H3 Enterprise accounts
  • H3 Education
  • H3 Facilities Management
  • H3 Aged Care
  • H3 Early Learning
  • H3 Industrial
  • H3 Hospitals and Allied Health
  • H3 Government
  • H3 Professional Services
  • H3 Retail
  • H3 Mining and Resources
  • H3 Hospitality
  • H3 You can depend on us to deliver in full and on time.
  • H3 We take pride in our award-winning customer service.
  • H2 We invest in technical experts to help you be more productive & successful.
  • H3 Furniture Solutions.
  • H3 Technology Solutions.
  • H3 Managed Print Services.
  • H3 Print & Marketing Services.
  • H2 Our Social Agenda guides us.
  • H3 Environmental sustainability
  • H3 First Nations reconciliation
  • H3 Community
  • H2 Latest news and updates.
  • H3 Winc Social Agenda Progress Report.
  • H3 Report: Buying local. The role of procurement in helping to make Australia.
  • H3 Art & Craft Favourites Look Book for Aged Care.
  • H2 Ready to make sourcing workplace supplies easier?
  • H3 Customer Service
  • H3 About Us
  • H3 Contact Us
  • H3 Become a Customer
  • H3 Join our community

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

B
Alt Text Quality
2 of 41 images have issues
REVIEW
2 of 41 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
5 decorative image(s) correctly marked
Info::
34 image(s) with good alt text
41 images 34 good alt text 5 decorative 2 missing
IssueCount
missing2 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

C
Form Accessibility
Action
12 of 14 controls have issues
REVIEW
12 of 14 controls have issues
Critical::
12 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="button" name="button" id="terms-clear">; <input type="checkbox" id="collapser_cbox_education">; <input type="checkbox" id="collapser_cbox_facilities_management">; <input type="checkbox" id="collapser_cbox_aged_care">; <input type="checkbox" id="collapser_cbox_early_learning">; <input type="checkbox" id="collapser_cbox_industrial">; <input type="checkbox" id="collapser_cbox_hospitals_and_allied_health">; <input type="checkbox" id="collapser_cbox_government">; <input type="checkbox" id="collapser_cbox_professional_services">; <input type="checkbox" id="collapser_cbox_retail"> (+2 more)
Info::
2 control(s) properly labeled
14 controls
2 labeled
0 placeholder only
12 unlabeled
ControlTypeLabelMethod
#termstextSearch termsaria-label
#searchbox_new_btnsubmitSearcharia-label
#terms-clearbutton(none)none
#collapser_cbox_educationcheckbox(none)none
#collapser_cbox_facilities_managementcheckbox(none)none
#collapser_cbox_aged_carecheckbox(none)none
#collapser_cbox_early_learningcheckbox(none)none
#collapser_cbox_industrialcheckbox(none)none
#collapser_cbox_hospitals_and_allied_healthcheckbox(none)none
#collapser_cbox_governmentcheckbox(none)none
#collapser_cbox_professional_servicescheckbox(none)none
#collapser_cbox_retailcheckbox(none)none
#collapser_cbox_mining_and_resourcescheckbox(none)none
#collapser_cbox_hospitalitycheckbox(none)none

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

<input type="button" name="button" id="terms-clear">; <input type="checkbox" id="collapser_cbox_education">; <input type="checkbox" id="collapser_cbox_facilities_management">; <input type="checkbox" id="collapser_cbox_aged_care">; <input type="checkbox" id="collapser_cbox_early_learning">; <input type="checkbox" id="collapser_cbox_industrial">; <input type="checkbox" id="collapser_cbox_hospitals_and_allied_health">; <input type="checkbox" id="collapser_cbox_government">; <input type="checkbox" id="collapser_cbox_professional_services">; <input type="checkbox" id="collapser_cbox_retail"> (+2 more)

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

C
Tap Target Adequacy
Action
5 tap target(s) too small or too close together
REVIEW
5 tap target(s) too small or too close together
Warning::
5 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.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Work Incorporated
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: minimal-ui
PWA Install Criteria Not Installable
Name Work Incorporated ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode minimal-ui ✓
Name Work Incorporated Display Mode minimal-ui Theme Color #2d3278 Background Color #f9f8f5 Icons 2 icon(s)
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 1 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Shop products3.01:13.0:1
#000000
#56567A
Pass
h2 Discover why we're t…19.30:13.0:1
#000000
#F5F5F8
Pass
h2 workplaces.19.30:13.0:1
#000000
#F5F5F8
Pass
h2 We invest in technic…19.30:13.0:1
#000000
#F5F5F8
Pass
h2 Our Social Agenda gu…19.30:13.0:1
#000000
#F5F5F8
Pass
h2 Latest news and upda…19.30:13.0:1
#000000
#F5F5F8
Pass
h2 Ready to make sourci…19.30:13.0:1
#000000
#F5F5F8
Pass
h3 Solutions tailored f…19.30:13.0:1
#000000
#F5F5F8
Pass
h3 Individuals & small …19.30:13.0:1
#000000
#F5F5F8
Pass
h3 Enterprise accounts19.30:13.0:1
#000000
#F5F5F8
Pass
h3 Education19.30:13.0:1
#000000
#F5F5F8
Pass
h3 Facilities Managemen…19.30:13.0:1
#000000
#F5F5F8
Pass
h3 Aged Care19.30:13.0:1
#000000
#F5F5F8
Pass
h3 Early Learning19.30:13.0:1
#000000
#F5F5F8
Pass
h3 Industrial19.30:13.0:1
#000000
#F5F5F8
Pass
h3 Hospitals and Allied…19.30:13.0:1
#000000
#F5F5F8
Pass
h3 Government19.30:13.0:1
#000000
#F5F5F8
Pass
h3 Professional Service…19.30:13.0:1
#000000
#F5F5F8
Pass
h3 Retail19.30:13.0:1
#000000
#F5F5F8
Pass
h3 Mining and Resources19.30:13.0:1
#000000
#F5F5F8
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.

A+
Heading Text Quality
All 37 heading(s) have substantive, well-formed text
PASS
All 37 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
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
Info::
Input "Ntt" should use type="search" (currently type="text")
Field name "Ntt" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
14 form control(s) checked, no input-semantic issues
PASS
14 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A
Iframe Accessibility
1/2 iframe(s) missing title; 0 placeholder(s)
PASS
1/2 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://staplesanz.my.site.com/ESWWinc1726793112974/assets/htdocs/sitecontext.m…")
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.
A+
Mobile-Readable Font Sizes
All 120 visible text node(s) render at >= 12 CSS pixels
PASS
All 120 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A
Favicon & Branding
6 icon(s) detected
PASS
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
A+
PWA Depth
1 PWA signal(s) surfaced
PASS
1 PWA signal(s) surfaced
Info::
Manifest has no maskable icon
Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /media/print__9418ec2c.css?t=1
Print Stylesheet ✓ Print Optimized
Print stylesheet /media/print__9418ec2c.css?t=1 ✓Inline @media print Not detected ✗
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
A
Lighthouse Accessibility Audits
Score 91/100 — 2 failing, 23 passed
PASS
91

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.scrolling-masthead > div.scrolling-masthead-inner > div.masthead__dashboard > button.masthead_button div.scrolling-masthead > div.scrolling-masthead-inner > div.masthead__dashboard > button.masthead_button

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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
div.grid_3 > ul.footer__ul > li.footer__li > a.footer__a div.grid_3 > ul.footer__ul > li.footer__li > a.footer__a
div.grid_3 > ul.footer__ul > li.footer__li > a.footer__a div.grid_3 > ul.footer__ul > li.footer__li > a.footer__a
div.grid_3 > ul.footer__ul > li.footer__li > a.footer__a div.grid_3 > ul.footer__ul > li.footer__li > a.footer__a
div.grid_3 > ul.footer__ul > li.footer__li > a.footer__a div.grid_3 > ul.footer__ul > li.footer__li > a.footer__a
div.grid_3 > ul.footer__ul > li.footer__li > a.footer__a div.grid_3 > ul.footer__ul > li.footer__li > a.footer__a

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
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○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
○Form elements have associated labels
○Links are distinguishable without relying on color.
○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.
○Elements with visible text labels have matching accessible names.
○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.

Send Feedback