Skip to content
https://offroadmegastore.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
69
GRADE
D
FIX
7
REVIEW
5
PASS
12
INFO
0
Checks
24
12 PASS 5 REVIEW 7 FIX
D
Landmark Structure
Action
5 landmarks
FIX
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <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.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

F
Heading Hierarchy
Action
132 headings, 6 skip(s)
FIX
132 headings, 6 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H3 Upload Your Profile
  • H6 Ver carrito skipped
  • H2 BUSCAR SUSPENSIÓN Y ACCESORIOS POR VEHÍCULO
  • H2 BUSCAR SUSPENSIÓN Y ACCESORIOS POR VEHÍCULO
  • H2 FORD - EVEREST - 2022 - ON - 3" - IMS SHOCKS
  • H2 TOYOTA - TUNDRA - 2021 - ON - MRA SHOCKS
  • H2 ROUGH COUNTRY - 2 INCH LIFT KIT M1R TOYOTA LANDCRUISER 250 - 73041
  • H2 TOYOTA – LAND CRUISER – SERIE 250 – 2023 – ON – 2″ – MRA SHOCKS
  • H2 TOYOTA – LAND CRUISER – SERIE 250 – 2023 – ON – 2″ – IMS SHOCKS
  • H2 TOYOTA – LAND CRUISER – SERIE 250 – 2023 – ON – 2″ – TWIN TUBE
  • H2 FORD - EVEREST - 2022 - ON - 2" - TWINTUBE
  • H2 FORD - EVEREST - 2022 - ON - 3" - MRA SHOCKS
  • H2 FORD - EVEREST - 2022 - ON - 2" - MRA SHOCKS
  • H2 FORD - EVEREST - 2022 - ON - 2" - IMS SHOCKS
  • H2 FORD - EVEREST - 2022 - ON - 3" - IMS SHOCKS
  • H2 TOYOTA - TUNDRA - 2021 - ON - MRA SHOCKS
  • H2 ROUGH COUNTRY - 2 INCH LIFT KIT M1R TOYOTA LANDCRUISER 250 - 73041
  • H2 TOYOTA – LAND CRUISER – SERIE 250 – 2023 – ON – 2″ – MRA SHOCKS
  • H2 RC - TRACTION BOARD KIT
  • H2 Easy Hitch – Tiro de arrastre para FORD RANGER 2024 - ON
  • H2 ROLL-OUT AWNING 2.0M X 3.0M - CE80-3937
  • H2 RC - ROUGH COUNTRY ALUMINIUM FOLDABLE CAMP CHAIR
  • H2 4.75T BOW SHACKLE - RK80-3828
  • H2 SNATCH STRAP KIT - SS80-3804
  • H2 ROLL OUT AWNING 2.5M X 3.0M - CE80-3904
  • H2 RC - 12000-LB PRO SERIES WINCH RECOVERY SYSTEM W/SYNTHETIC ROPE
  • H2 170 L/MIN SINGLE MOTOR HYPER-FLOW COMPRESSOR - AC80-3846
  • H2 12000LB ELECTRIC WINCH WITH SYNTHETIC ROPE - EW80-3815S
  • H2 RC - TRACTION BOARD KIT
  • H2 Easy Hitch – Tiro de arrastre para FORD RANGER 2024 - ON
  • H2 ROLL-OUT AWNING 2.0M X 3.0M - CE80-3937
  • H2 RC - ROUGH COUNTRY ALUMINIUM FOLDABLE CAMP CHAIR
  • H2 RC - BLACK SERIES LED LIGHT PAIR 2 INCH | AMBER DRL
  • H2 Stedi - Type-X™ EVO MINI 4 Inch Spot Beam (UNIDAD)
  • H2 Stedi C-4 Black Edition led night Cube Spot - LEDWORK-C4-SPOT
  • H2 Stedi Surface Single White LED Rock Light
  • H2 Stedi LEDWORK-C4-FLOOD
  • H2 RC - MULTI LIGHT CONTROLLER / 8 PANEL RGB BLUETOOTH -70975
  • H2 Stedi SURFACE LED ROC LIGHT (1500K)
  • H2 Stedi - Type-X™ EVO MINI 4 Inch Flood Beam (UNIDAD) - ST-01-EVO-402
  • H2 STEDI - Type-X™ Evo 4 Inch Amber Cover - ST-12-EVO-945
  • H2 KC Hilites - 6" Pro6 Gravity® LED - Light Shield - Amber - 5112
  • H2 RC - BLACK SERIES LED LIGHT PAIR 2 INCH | AMBER DRL
  • H2 Stedi - Type-X™ EVO MINI 4 Inch Spot Beam (UNIDAD)
  • H2 Stedi C-4 Black Edition led night Cube Spot - LEDWORK-C4-SPOT
  • H2 Stedi Surface Single White LED Rock Light
  • H2 BLACK RHINO TALEO 17X8.5 6X139.7 106 +25 B-BRNZ - BR030ZX17856825
  • H2 BLACK RHINO ABRAMS 17X8.5 6X139.7 +0 112 OD GRN - 1785ABR006140N12
  • H2 RC - STEEL WHEEL GRAY 16X8 6X139.7 4.25BORE ET-12 - RC51-6883G
  • H2 RC - STEEL WHEEL SIMULATED BEA LOCK BLACK 17X9 6X139.7 4.25BORE ET-12 - RC51-7655SL
  • H2 RC - STEEL WHEEL GRAY 17X9 6X139.7 4.25 BORE ET-12 - EC51-7655G
  • H2 RC - STEEL WHEEL CHROME 17X9 6X139.7 ET-12 4.25BORE - RC51-7655C
  • H2 FUEL TRAX 18X9 6X139.7 106 +1 M-BLK - FC882MX18906801
  • H2 PRO COMP HERITAGE 17X8 5X150 110 +0 POLISH - PA201HX17805800
  • H2 FUEL COVERT 17X8.5 6X114.3 66.32 GDB 14MM - D71617858752
  • H2 BLACK RHINO STADIUM 17X8.5 6X114.3 76 +0 M-BRNZ - 1785SDM006114Z76A
  • H2 BLACK RHINO TALEO 17X8.5 6X139.7 106 +25 B-BRNZ - BR030ZX17856825
  • H2 BLACK RHINO ABRAMS 17X8.5 6X139.7 +0 112 OD GRN - 1785ABR006140N12
  • H2 RC - STEEL WHEEL GRAY 16X8 6X139.7 4.25BORE ET-12 - RC51-6883G
  • H2 RC - STEEL WHEEL SIMULATED BEA LOCK BLACK 17X9 6X139.7 4.25BORE ET-12 - RC51-7655SL
  • H2 RC - UTV ALUMINUM SIDE MIRRORS W/TURN SIGNAL (UNIVERSAL)
  • H2 RC - UTV ALUMINUM SIDE MIRRORS W/TURN SIGNAL (UNIVERSAL)
  • H2 ROUGH COUNTRY - BLUETOOTH LED SOUNDBAR - 99515_A
  • H2 RC - SYNTHETIC WINCH ROPE 3/8 85FT PURPLE - RS112
  • H2 RC - 1/4IN SYNTHETIC WINCH ROPE UTV, ATV (PURPLE) - RS162
  • H2 Easy Hitch –RAMPA PARA MOTO / CUATRIMOTO DEPORTIVA
  • H2 RC - WHIP MOUNT - POLARIS GENERAL/ RANGER 1000/ RANGER XP 900 / 1000
  • H2 RC - WHIP MOUNT / POLARIS RZR 1000XP
  • H2 RC - 1.65-2 IN UNIVERSAL LED LIGHT MOUNT -70171
  • H2 RC - UTV STORAGE COVER / UNIVERSAL 4-DOOR
  • H2 RC - UTV ALUMINUM SIDE MIRRORS W/TURN SIGNAL (UNIVERSAL)
  • H2 RC - UTV ALUMINUM SIDE MIRRORS W/TURN SIGNAL (UNIVERSAL)
  • H2 ROUGH COUNTRY - BLUETOOTH LED SOUNDBAR - 99515_A
  • H2 RC - SYNTHETIC WINCH ROPE 3/8 85FT PURPLE - RS112
  • H2 POWERBRAKE D-LINE FRONT BRAKE ROTOR & PAD KIT FOR TOYOTA 4RUNNER/PRADO/LEXUS - DT1003
  • H2 POWERBRAKE D-LINE REAR BRAKE ROTOR & PAD KIT FOR TOYOTA 4RUNNER/FJ/PRADO/FORTUNER/LEXUS - DT1004
  • H2 POWERBRAKE - LANDCRUISER 80 (17" WHEELS)90-97 STAGE-2: 6 PISTON CALIPER & 13.7" 2-PIECE ROTOR WHEEL SIZE REQUIRED 17 - TOY815GREY
  • H2 POWERBRAKE X-LINE LANDCRUISER 76 / 78 / 79 (M12 & M14 BRACKET INCLUDED) - 17"WHEELS 00-ON STAGE-1: 6 PISTON CALIPER & 13.7" 1-PIECE ROTOR WHEEL SIZE REQUIRED 17 - TOY2101RED
  • H2 POWERBRAKE - LANDCRUISER 80 (16" WHEELS)90-97 STAGE-2: 6 PISTON CALIPER & 13" 2-PIECE ROTOR WHEEL SIZE REQUIRED 16 - TOY823GREY
  • H2 POWERBRAKE X-LINE FRONT STAGE 1 RED/ 6 PISTON CALIPER/ TOYOTA HILUX 8TH GEN - TOY2103RED
  • H2 POWERBRAKE D-LINE FRONT BRAKE ROTOR & PAD KIT FOR TOYOTA LANDCRUISER 76/78/79 - DT1014
  • H2 POWERBRAKE D-LINE REAR BRAKE ROTOR & PAD KIT FOR TOYOTA 4RUNNER/FORTUNER/PRADO/LEXUS DT1008
  • H2 POWERBRAKE X-LINE FRONT STAGE 1 RED/ 6 PISTON CALIPER/ TOYOTA 4RUNNER/PRADO/LEXUS - TOY412RED
  • H2 POWERBRAKE D-LINE REAR BRAKE ROTOR & PAD KIT FOR TOYOTA LANDCRUISER 76/78/79 - DT1015
  • H2 POWERBRAKE D-LINE FRONT BRAKE ROTOR & PAD KIT FOR TOYOTA 4RUNNER/PRADO/LEXUS - DT1003
  • H2 POWERBRAKE D-LINE REAR BRAKE ROTOR & PAD KIT FOR TOYOTA 4RUNNER/FJ/PRADO/FORTUNER/LEXUS - DT1004
  • H2 POWERBRAKE - LANDCRUISER 80 (17" WHEELS)90-97 STAGE-2: 6 PISTON CALIPER & 13.7" 2-PIECE ROTOR WHEEL SIZE REQUIRED 17 - TOY815GREY
  • H2 POWERBRAKE X-LINE LANDCRUISER 76 / 78 / 79 (M12 & M14 BRACKET INCLUDED) - 17"WHEELS 00-ON STAGE-1: 6 PISTON CALIPER & 13.7" 1-PIECE ROTOR WHEEL SIZE REQUIRED 17 - TOY2101RED
  • H2 VENTANA DEL PANEL LATERAL SUPERIOR - TOYOTA LANDCRUISER FJ40 - SY-TY65-106
  • H2 VISAGRA DE PUERTAS LATERALES (PAR) - TOYOTA LANDCRUISER FJ40 / FJ45 - SY-TY65-89-1
  • H2 CARROCERIA COMPLETA CON PUERTAS (1977 - ON) - TOYOTA LANDCRUISER FJ40 - SY-TY65-65
  • H2 MITAD DE TUB (PARTE TRASERA) - TOYOTA LANDCRUISER FJ40 (1968 - ON) - SY-TY65-10-68
  • H2 TUB COMPLETO - TOYOTA LANDCRUISER FJ40 (1968 - ON) - SY-TY65-00-68
  • H2 CARROCERIA COMPLETA - TOYOTA LANDCRUISER FJ45 - SY-TY65-59
  • H2 ESTRIBO LATERLA DERECHO - TOYOTA LANDCRUISER FJ40 / FJ45 - SY-TY65-21R
  • H2 BISAGRA DE COMPUERTA TRASERA - TOYOTA LANDCRUISER FJ40 - SY-TY91-04
  • H2 COMPUERTA DELANTERA DERECHA - TOYOTA LAND CRUISER FJ SERIE 40 - SY-TY65-01R
  • H2 ESTRIBO LATERLA IZQUIERDO - TOYOTA LANDCRUISER FJ40 / FJ45 - SY-TY65-21L
  • H2 VENTANA DEL PANEL LATERAL SUPERIOR - TOYOTA LANDCRUISER FJ40 - SY-TY65-106
  • H2 VISAGRA DE PUERTAS LATERALES (PAR) - TOYOTA LANDCRUISER FJ40 / FJ45 - SY-TY65-89-1
  • H2 CARROCERIA COMPLETA CON PUERTAS (1977 - ON) - TOYOTA LANDCRUISER FJ40 - SY-TY65-65
  • H2 MITAD DE TUB (PARTE TRASERA) - TOYOTA LANDCRUISER FJ40 (1968 - ON) - SY-TY65-10-68
  • H2 ACCESORIOS
  • H4 BULL BARS skipped
  • H4 SNORKELS
  • H4 WINCHES
  • H4 DRIVING LIGHTS
  • H4 RECOVERY GEAR
  • H4 VER TODOS LOS ACCESORIOS
  • H4 Information
  • H6 About Us skipped
  • H6 Contact Us
  • H6 Distributor Map
  • H6 Our History
  • H6 FAQs
  • H4 Media
  • H6 Media Releases skipped
  • H4 T’s & C’s
  • H6 Privacy Policy skipped
  • H6 Conditions of Sale
  • H6 Disclaimer
  • H6 Warranty
  • H6 Price Enquiries
  • H6 Exchange Rates
  • H6 Website Usage
  • H6 (empty)
  • H6 Returns Policy
  • H4 Forms
  • H6 Distributor Enquiry Form skipped
  • H6 General Enquiry Form
  • H3 Suscribete a nuestro boletín:
  • H3 Síguenos:

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

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
No dark mode signals
FIX
No dark mode signals
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 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.

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
No navigation patterns
FIX
No navigation patterns
Info::
2 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Form Accessibility
Action
17 of 21 controls have issues
REVIEW
17 of 21 controls have issues
Critical::
17 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="file" name="profile" id="profile">; <input type="submit" name="submit">; <select name="year_id">; <select name="make">; <select name="model">; <select name="category">; <input type="submit">; <select name="year_id">; <select name="make">; <select name="model"> (+7 more)
Info::
4 control(s) properly labeled
21 controls
4 labeled
0 placeholder only
17 unlabeled
ControlTypeLabelMethod
#6a799732e5782searchBuscarfor/id
#6a799732ecc53searchBuscarfor/id
#field_tudnsemailCorreo electrónico *for/id
#field_5zj61textSi eres humano, deja este campo en blanco.for/id
makeselect(none)none
modelselect(none)none
categoryselect(none)none
inputsubmit(none)none
year_idselect(none)none
makeselect(none)none
modelselect(none)none
categoryselect(none)none
inputsubmit(none)none
submitsubmit(none)none
year_idselect(none)none
makeselect(none)none
modelselect(none)none
categoryselect(none)none
inputsubmit(none)none
#profilefile(none)none
year_idselect(none)none

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

<input type="file" name="profile" id="profile">; <input type="submit" name="submit">; <select name="year_id">; <select name="make">; <select name="model">; <select name="category">; <input type="submit">; <select name="year_id">; <select name="make">; <select name="model"> (+7 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
Tabindex Anti-Patterns
Action
0 positive, 8 -1-on-focusable
REVIEW
0 positive, 8 -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.)
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found - Offroad Megastore ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 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::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 86/100 — 5 failing, 26 passed
REVIEW
86

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
div.aws-container > form.aws-search-form > div.aws-wrapper > input#6a79a0ad78c43 div.aws-container > form.aws-search-form > div.aws-wrapper > input#6a79a0ad78c43
¿Cómo podemos ayudarte? div#ht-ctc-chat > div.ht_ctc_style > div.ctc_chip > span.ctc_cta

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
BULL BARS div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h4

These are opportunities to improve keyboard navigation in your application.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Marca VOLKSWAGEN UAZ TOYOTA SUZUKI SUBARU SSANGYONG RENAULT NISSAN MITSUBISHI M… div.widget-woo-vpf-ymm-filter > form > div.woo-vpf-ymm-field > select
Modelo div.widget-woo-vpf-ymm-filter > form > div.woo-vpf-ymm-field > select
Año div.widget-woo-vpf-ymm-filter > form > div.woo-vpf-ymm-field > select
Categoría ACCESORIOS 4X4 COMPONENTES DE SUSPENSION FRENOS KITS DE SUSPENSIÓN LU… div.widget-woo-vpf-ymm-filter > form > div.woo-vpf-ymm-field > select

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon
div.elementor-widget-container > div.elementor-icon-box-wrapper > div.elementor-icon-box-icon > a.elementor-icon div.elementor-widget-container > div.elementor-icon-box-wrapper > div.elementor-icon-box-icon > a.elementor-icon
div.elementor-widget-container > div.elementor-icon-box-wrapper > div.elementor-icon-box-icon > a.elementor-icon div.elementor-widget-container > div.elementor-icon-box-wrapper > div.elementor-icon-box-icon > a.elementor-icon
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a

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

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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
●Input buttons have discernible text.
●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
●`[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
●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.
●Skip links are focusable.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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
○Buttons have an accessible name
○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
○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 type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
A
Heading Text Quality
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Warning::
3 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: 129 chars - H2: 173 chars - H2: 127 chars
Got: 3 >120-char heading(s)
Info::
93 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: 93 all-caps heading(s)
A
Alt Text Quality
All 119 images OK
PASS
All 119 images OK
Info::
5 image(s) with alt text over 125 characters
Info::
21 decorative image(s) correctly marked
Info::
93 image(s) with good alt text
119 images 93 good alt text 21 decorative
IssueCount
too long5 image(s)
A+
Form Input Types
21 form control(s) checked, no type mismatches
PASS
21 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
21 form control(s) checked, no input-semantic issues
PASS
21 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 "es"
PASS
Lang attribute set to "es"
Info::
<html lang="es"> is set and valid
Got: es
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
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+
Mobile-Readable Font Sizes
All 6 visible text node(s) render at >= 12 CSS pixels
PASS
All 6 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
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::
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)
ElementRatioRequiredFGBGResult
h2 FORD - EVEREST - 202…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 TOYOTA - TUNDRA - 20…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 ROUGH COUNTRY - 2 IN…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 TOYOTA – LAND CRUI…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 TOYOTA – LAND CRUI…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 TOYOTA – LAND CRUI…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 FORD - EVEREST - 202…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 FORD - EVEREST - 202…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 FORD - EVEREST - 202…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 FORD - EVEREST - 202…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 FORD - EVEREST - 202…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 TOYOTA - TUNDRA - 20…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 ROUGH COUNTRY - 2 IN…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 TOYOTA – LAND CRUI…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 RC - TRACTION BOARD …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Easy Hitch – Tiro …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 ROLL-OUT AWNING 2.0M…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 RC - ROUGH COUNTRY A…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 4.75T BOW SHACKLE - …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 SNATCH STRAP KIT - S…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.

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

Send Feedback