Skip to content
https://raptonline.co.nz

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
73
GRADE
C
FIX
7
REVIEW
4
PASS
13
INFO
0
Checks
24
13 PASS 4 REVIEW 7 FIX
F
404 Error Page
Action
HTTP 403, custom page
FIX
HTTP 403, custom page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 403 ✗Page Title Verifying your connection... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

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: #111111
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
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Mobile Keyboard & Autofill
Action
4/6 eligible field(s) missing autocomplete or inputmode
REVIEW
4/6 eligible field(s) missing autocomplete or inputmode
Warning::
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, search.
Got: <input type="email" name="email">, <input type="search" name="q" id="Search">, <input type="email" name="email">, <input type="email" name="contact[email]" id="Email-footer2">
B
Tabindex Anti-Patterns
0 positive, 4 -1-on-focusable
REVIEW
0 positive, 4 -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 <input>
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 <input>
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.)
B
Iframe Accessibility
3/3 iframe(s) missing title; 0 placeholder(s)
REVIEW
3/3 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://raptonline.co.nz/web-pixels@9f5e2762wb720532ap19708c42m93b2bec3/custom/…")
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.
Warning::
<iframe> missing title attribute (src="https://raptonline.co.nz/web-pixels@9f5e2762wb720532ap19708c42m93b2bec3/custom/…")
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.
Warning::
<iframe> missing title attribute (src="https://www.google.com/shopping/merchantverse/?screenWidth=780&screenHeight=441…")
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.
C
Mobile-Readable Font Sizes
Action
85% of visible text renders at >= 12 CSS px (2 below threshold)
REVIEW
85% of visible text renders at >= 12 CSS px (2 below threshold)
Warning::
2 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 11.0px ("Join the RAPT list"); <span> 11.0px ("Unsubscribe anytime. See our privacy pol...").
A+
Landmark Structure
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Primary" MAIN CONTENTINFO footer
A
Heading Hierarchy
52 headings
PASS
52 headings
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H2 Unlock FREE shipping on your first order Enjoy 10% off your first order Be first to see new arrivals Win a $500 new season wardrobe
  • H2 Check your inboxYou're in the draw
  • H2 Currency
  • H2 CHRISTMAS 2026
  • H2 HAVEN WOMENS FASHION
  • H2 WOMENS CLOTHING SALE NOTHING OVER $55
  • H1 Women's Clothing, Gifts & Homeware NZ
  • H2 Shop by category
  • H2 Christmas best sellers
  • H2 Gifts they'll love, sorted
  • H2 Shop Christmas gifts & decorations
  • H2 Women's fashion best sellers
  • H2 Shop by fashion brand
  • H2 Fashion that fits and flatters
  • H2 Just landed
  • H2 WOMEN'S FASHION
  • H2 NOTHING OVER $55
  • H3 NZ OWNED & OPERATED
  • H3 FAST SHIPPING
  • H3 real people, real help
  • H2 SHOP HOME DECOR
  • H2 WILLOW TREE
  • H2 Gifts & homeware they'll love
  • H2 Home décor & gift favourites
  • H2 See what our customers have to say..
  • H2 THE LATEST ON SOCIAL - FOLLOW FOR INSPO, GIVEAWAYS & NEW ARRIVALS.
  • H3 12k followers
  • H3 FOLLOW US ON FACEBOOK
  • H3 FOLLOW US ON INSTAGRAM
  • H2 RAPT ONLINE FAQs
  • H3 Who is RAPT ONLINE?
  • H3 Which brands do you stock?
  • H3 Do you sell plus size clothing?
  • H3 How much is shipping?
  • H3 How fast is delivery?
  • H3 When do I need to order for Christmas?
  • H3 Can I send a gift straight to someone?
  • H3 What is your returns policy?
  • H3 How can I pay?
  • H3 Do you have a rewards programme?
  • H2 Online Boutique NZ for Women's Fashion, Gifts & Homeware
  • H3 Women's clothing in sizes that fit
  • H3 Christmas decorations and gifts
  • H3 Gifts and homeware for every occasion
  • H3 Shopping with RAPT ONLINE
  • H2 BUNDLE DEALS
  • H2 EARN VIP REWARDS
  • H2 GIFT CARDS AVAILABLE
  • H2 Sign up and save
  • H2 Currency
  • H1 403 duplicate H1
  • H1 403 duplicate H1

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A
Heading Text Quality
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Warning::
1 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H2: 176 chars
Got: 1 >120-char heading(s)
Info::
15 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: 15 all-caps heading(s)
A
Alt Text Quality
All 191 images OK
PASS
All 191 images OK
Info::
24 image(s) with alt text over 125 characters
Info::
6 decorative image(s) correctly marked
Info::
161 image(s) with good alt text
191 images 161 good alt text 6 decorative
IssueCount
too long24 image(s)
A+
Form Accessibility
All 6 controls labeled
PASS
All 6 controls labeled
Info::
6 control(s) properly labeled
6 controls
6 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#CartNoteDrawertextareaOrder notefor/id
inputtextDiscount codearia-label
emailemailEmail addressaria-label
#SearchsearchSearchfor/id
emailemailEmail addressaria-label
#Email-footer2emailEnter your emailfor/id
A+
Form Input Types
6 form control(s) checked, no type mismatches
PASS
6 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
6 form control(s) checked, no input-semantic issues
PASS
6 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
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+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues 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+
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)
ElementRatioRequiredFGBGResult
h1 Women's Clothing, Gi…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 40321.00:13.0:1
#000000
#FFFFFF
Pass
h1 40321.00:13.0:1
#000000
#FFFFFF
Pass
h2 Currency21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Shop by category21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Christmas best selle…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Gifts they'll love, …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Shop Christmas gifts…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Women's fashion best…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Shop by fashion bran…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Fashion that fits an…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Just landed21.00:13.0:1
#000000
#FFFFFF
Pass
h2 WOMEN'S FASHION21.00:13.0:1
#000000
#FFFFFF
Pass
h2 NOTHING OVER $5521.00:13.0:1
#000000
#FFFFFF
Pass
h2 Gifts & homeware the…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Home décor & gift f…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 See what our custome…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 THE LATEST ON SOCIAL…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 RAPT ONLINE FAQs21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Online Boutique NZ f…21.00:13.0:1
#000000
#FFFFFF
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
Lighthouse Accessibility Audits
Score 92/100 — 3 failing, 31 passed
PASS
92

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
JOIN THE RAPT LIST div.rapt-pop__body > div.rapt-pop__step > p.rapt-pop__kicker > span
No thanks div.rapt-pop__box > div.rapt-pop__body > div.rapt-pop__step > button.rapt-pop__no
Unsubscribe anytime. See our privacy policy. div.rapt-pop__body > div.rapt-pop__step > p.rapt-pop__fine > span
NEED HELP - JUST DROP US AN EMAIL INFO@RAPTONLINE.CO.NZ div.flickity-slider > div#AnnouncementSlide-announcement_fCnpUH > a.announcement-link > span.announcement-text
or 4 x $12.24 with Afterpay div.grid__item-image-wrapper > a.grid-product__link > div.grid-product__meta > div.rapt-card-ap
$12.99 a.grid-product__link > div.grid-product__meta > div.grid-product__price > span.grid-product__price--original
NEW IN div.grid > div.grid__item > div.grid-product__content > div.grid-product__tag
$99.95 a.grid-product__link > div.grid-product__meta > div.grid-product__price > span.grid-product__price--original
or 4 x $9.99 with Afterpay div.grid__item-image-wrapper > a.grid-product__link > div.grid-product__meta > div.rapt-card-ap
$109.99 a.grid-product__link > div.grid-product__meta > div.grid-product__price > span.grid-product__price--original
or 4 x $20.62 with Afterpay div.grid__item-image-wrapper > a.grid-product__link > div.grid-product__meta > div.rapt-card-ap
PLUS SIZE & CURVE div.page-width > div.rapt-hub__callout > div.rapt-hub__callout-body > p.rapt-hub__eyebrow
NEW IN div.grid > div.grid__item > div.grid-product__content > div.grid-product__tag
or 4 x $22.49 with Afterpay div.grid__item-image-wrapper > a.grid-product__link > div.grid-product__meta > div.rapt-card-ap
NEW IN div.grid > div.grid__item > div.grid-product__content > div.grid-product__tag
or 4 x $24.99 with Afterpay div.grid__item-image-wrapper > a.grid-product__link > div.grid-product__meta > div.rapt-card-ap
or 4 x $24.99 with Afterpay div.grid__item-image-wrapper > a.grid-product__link > div.grid-product__meta > div.rapt-card-ap
or 4 x $42.49 with Afterpay div.grid__item-image-wrapper > a.grid-product__link > div.grid-product__meta > div.rapt-card-ap
NEW IN div.grid > div.grid__item > div.grid-product__content > div.grid-product__tag
NEW IN div.grid > div.grid__item > div.grid-product__content > div.grid-product__tag
NEW IN div.grid > div.grid__item > div.grid-product__content > div.grid-product__tag
NEW IN div.grid > div.grid__item > div.grid-product__content > div.grid-product__tag
NEW IN div.grid > div.grid__item > div.grid-product__content > div.grid-product__tag
NEW IN div.grid > div.grid__item > div.grid-product__content > div.grid-product__tag
Rewards div.Avada-Joy_ButtonWidget > button#Avada-Joy_FloatingButtonTrigger > div.AvadaJoy-Launcher__Button > p.AvadaJoy-Launcher__ButtonLabel

These are opportunities to improve the legibility of your content.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.template-index > form > input body.template-index > form > input

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Rewards div#Avada-Joy_FloatingButton > div > div.Avada-Joy_ButtonWidget > button#Avada-Joy_FloatingButtonTrigger
○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
●`[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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[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.
○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
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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