Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 5 REVIEW 5 FIX

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

Theme color only

FIX

Theme color only

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: #373737

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 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.

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 ✗

Link & Button Quality

Action

4 issue(s) across 100 links and 52 buttons

REVIEW

4 issue(s) across 100 links and 52 buttons

4 link(s) with no accessible text

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

Got: /collections/yamaha; /collections/jbl; /collections/pioneer; /collections/fender

10 link(s) open in new tab without warning

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

Got: https://uniquetechnologies.co/policies/privacy-policy; https://web.facebook.com/UTdrc/; https://www.instagram.com/unique_techdrc/; https://www.pinterest.com/uniquetechkinshasa/; https://www.google.com/maps/search/?api=1&query=13+avenue+Colonel+Ebeya+Gombe…; https://wa.me/243904316200; https://web.facebook.com/UTdrc/; https://www.instagram.com/unique_techdrc/; https://www.pinterest.com/uniquetechkinshasa/; https://www.shopify.com?utm_campaign=poweredby&utm_medium=shopify&utm_source=…

86 link(s) with descriptive text

100 links

4 empty

0 generic text

10 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://uniquetechnologies.co/policies/p…	Privacy Policy	new tab	Add '(opens in new tab)' to text
/	Unique Technologies	img no alt	Add alt attribute to the image
https://web.facebook.com/UTdrc/	Follow on Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/unique_techdrc…	Follow on Instagram	new tab	Add '(opens in new tab)' to text
https://www.pinterest.com/uniquetechkins…	Follow on Pinterest	new tab	Add '(opens in new tab)' to text
/collections/drum	Drums	img no alt	Add alt attribute to the image
/collections/professional-speaker	SPEAKERS	img no alt	Add alt attribute to the image
/collections/yamaha	(empty)	empty	Add link text or aria-label
/collections/jbl	(empty)	empty	Add link text or aria-label
/collections/pioneer	(empty)	empty	Add link text or aria-label
/collections/fender	(empty)	empty	Add link text or aria-label
https://www.google.com/maps/search/?api=…	📍 Open location in Google M…	new tab	Add '(opens in new tab)' to text
https://wa.me/243904316200	WhatsApp Chat: +243904316200	new tab	Add '(opens in new tab)' to text
https://web.facebook.com/UTdrc/	Follow on Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/unique_techdrc…	Follow on Instagram	new tab	Add '(opens in new tab)' to text
https://www.pinterest.com/uniquetechkins…	Follow on Pinterest	new tab	Add '(opens in new tab)' to text
https://www.shopify.com?utm_campaign=pow…	Powered by P.A.N GROUP	new tab	Add '(opens in new tab)' to text

138 links and buttons have descriptive text

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

/collections/yamaha; /collections/jbl; /collections/pioneer; /collections/fender

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://uniquetechnologies.co/policies/privacy-policy; https://web.facebook.com/UTdrc/; https://www.instagram.com/unique_techdrc/; https://www.pinterest.com/uniquetechkinshasa/; https://www.google.com/maps/search/?api=1&query=13+avenue+Colonel+Ebeya+Gombe…; https://wa.me/243904316200; https://web.facebook.com/UTdrc/; https://www.instagram.com/unique_techdrc/; https://www.pinterest.com/uniquetechkinshasa/; 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

Tap Target Adequacy

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

REVIEW

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

3 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

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

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 ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h2 Cookie consent

1.37:1

#000000

#252525

needs 3.0:1 (large text)

24px · top of page (header area) · over background image/gradient

h2 Bienvenue chez Unique Technologies

1.90:1

#000000

#3C3C3C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Large Catégorie D'instruments De Musiqu…

1.90:1

#000000

#3C3C3C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 MUSIC FOR EVERYONE

1.90:1

#000000

#3C3C3C

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Explorer Par Marques

1.90:1

#000000

#3C3C3C

needs 3.0:1 (large text)

24px · bottom of viewport

h3 PLATEAU PODIUM 1.22x1.22m – Structure …

1.90:1

#000000

#3C3C3C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 ÉCRAN EXTÉRIEUR

1.90:1

#000000

#3C3C3C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 ÉCRAN INTERIEUR

1.90:1

#000000

#3C3C3C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 TRUSS

1.90:1

#000000

#3C3C3C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 YAMAHA PSR-E283

1.90:1

#000000

#3C3C3C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 YAMAHA PSR-E383

1.90:1

#000000

#3C3C3C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 YAMAHA PSR-E483

1.90:1

#000000

#3C3C3C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 YMAHA PSR-SX600

1.90:1

#000000

#3C3C3C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 YAMAHA PSR-A5000 ORIENTAL WORKSTATION

1.90:1

#000000

#3C3C3C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 YAMAHA PSR-E473

1.90:1

#000000

#3C3C3C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Unique Technologies Beam Moving Head Lig…

1.90:1

#000000

#3C3C3C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Unique Technologies Saxophone

1.90:1

#000000

#3C3C3C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 PLATEAU PODIUM 1.22x1.22m – Structure …

1.90:1

#000000

#3C3C3C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 ÉCRAN EXTÉRIEUR

1.90:1

#000000

#3C3C3C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 ÉCRAN INTERIEUR

1.90:1

#000000

#3C3C3C

needs 3.0:1 (large text)

19px · bottom of viewport

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Cookie consent	1.37:1	3.0:1	#000000	#252525	Fail
h2 Bienvenue chez Uniqu…	1.90:1	3.0:1	#000000	#3C3C3C	Fail
h2 Large Catégorie D'i…	1.90:1	3.0:1	#000000	#3C3C3C	Fail
h2 MUSIC FOR EVERYONE	1.90:1	3.0:1	#000000	#3C3C3C	Fail
h2 Explorer Par Marques	1.90:1	3.0:1	#000000	#3C3C3C	Fail
h3 PLATEAU PODIUM 1.22x…	1.90:1	3.0:1	#000000	#3C3C3C	Fail
h3 ÉCRAN EXTÉRIEUR	1.90:1	3.0:1	#000000	#3C3C3C	Fail
h3 ÉCRAN INTERIEUR	1.90:1	3.0:1	#000000	#3C3C3C	Fail
h3 TRUSS	1.90:1	3.0:1	#000000	#3C3C3C	Fail
h3 YAMAHA PSR-E283	1.90:1	3.0:1	#000000	#3C3C3C	Fail
h3 YAMAHA PSR-E383	1.90:1	3.0:1	#000000	#3C3C3C	Fail
h3 YAMAHA PSR-E483	1.90:1	3.0:1	#000000	#3C3C3C	Fail
h3 YMAHA PSR-SX600	1.90:1	3.0:1	#000000	#3C3C3C	Fail
h3 YAMAHA PSR-A5000 ORI…	1.90:1	3.0:1	#000000	#3C3C3C	Fail
h3 YAMAHA PSR-E473	1.90:1	3.0:1	#000000	#3C3C3C	Fail
h3 Unique Technologies …	1.90:1	3.0:1	#000000	#3C3C3C	Fail
h3 Unique Technologies …	1.90:1	3.0:1	#000000	#3C3C3C	Fail
h3 PLATEAU PODIUM 1.22x…	1.90:1	3.0:1	#000000	#3C3C3C	Fail
h3 ÉCRAN EXTÉRIEUR	1.90:1	3.0:1	#000000	#3C3C3C	Fail
h3 ÉCRAN INTERIEUR	1.90:1	3.0:1	#000000	#3C3C3C	Fail

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

Action

Score 76/100 — 6 failing, 21 passed

REVIEW

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.

ARIA

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Open search `div.header__wrapper > div.header__main-nav > div.header__icon-list > a.tap-area`
Open cart 0 `div.header__wrapper > div.header__secondary-nav > div.header__icon-list > a.relative`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Home `div.footer__block > ul.v-stack > li > a.inline-block`
All Catagories `div.footer__block > ul.v-stack > li > a.inline-block`
About Us `div.footer__block > ul.v-stack > li > a.inline-block`
Contact Us `div.footer__block > ul.v-stack > li > a.inline-block`
What's New `div.footer__block > ul.v-stack > li > a.inline-block`
Blogs `div.footer__block > ul.v-stack > li > a.inline-block`
Privacy Policy `div.footer__block > ul.v-stack > li > a.inline-block`
Contact Information `div.footer__block > ul.v-stack > li > a.inline-block`
Terms of Service `div.footer__block > ul.v-stack > li > a.inline-block`
Refund Policy `div.footer__block > ul.v-stack > li > a.inline-block`
Projects `div.footer__block > ul.v-stack > li > a.inline-block`
Company Corporate Profile `div.footer__block > ul.v-stack > li > a.inline-block`
Social Welfare `div.footer__block > ul.v-stack > li > a.inline-block`
Sustainable Efforts `div.footer__block > ul.v-stack > li > a.inline-block`

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.footer__block-list > div.footer__block > div.footer-map-box > iframe `div.footer__block-list > div.footer__block > div.footer-map-box > iframe`

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.section > div.section-stack > reveal-items.logo-list > a.logo-list__item `div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item`
div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item `div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item`
div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item `div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item`
div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item `div.section > div.section-stack > reveal-items.logo-list > a.logo-list__item`

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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
Go to item 1 `div.press > div.press__controls > page-dots.page-dots > button.tap-area`
Go to item 2 `div.press > div.press__controls > page-dots.page-dots > button.tap-area`
Go to item 3 `div.press > div.press__controls > page-dots.page-dots > button.tap-area`

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

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

●`[role]` values are valid

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●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.

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○`[accesskey]` values are unique

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○`[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

○`<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

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○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

○Identical links have the same purpose.

○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.

A+

Landmark Structure

9 landmarks

PASS

9 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

30 headings

PASS

30 headings

Single H1 present

H2 Cookie consent
H1 Unique Technologies
H2 Bienvenue chez Unique Technologies
H3 PLATEAU PODIUM 1.22x1.22m – Structure Métallique Professionnelle
H3 ÉCRAN EXTÉRIEUR
H3 ÉCRAN INTERIEUR
H3 TRUSS
H3 YAMAHA PSR-E283
H3 YAMAHA PSR-E383
H3 YAMAHA PSR-E483
H3 YMAHA PSR-SX600
H3 YAMAHA PSR-A5000 ORIENTAL WORKSTATION
H3 YAMAHA PSR-E473
H3 Unique Technologies Beam Moving Head Light
H3 Unique Technologies Saxophone
H3 PLATEAU PODIUM 1.22x1.22m – Structure Métallique Professionnelle
H3 ÉCRAN EXTÉRIEUR
H3 ÉCRAN INTERIEUR
H3 TRUSS
H3 YAMAHA PSR-E283
H3 YAMAHA PSR-E383
H3 YAMAHA PSR-E483
H3 YMAHA PSR-SX600
H3 YAMAHA PSR-A5000 ORIENTAL WORKSTATION
H3 YAMAHA PSR-E473
H3 Unique Technologies Beam Moving Head Light
H3 Unique Technologies Saxophone
H2 Large Catégorie D'instruments De Musique
H2 MUSIC FOR EVERYONE
H2 Explorer Par Marques

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

19 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: 19 all-caps heading(s)

A+

Alt Text Quality

All 40 images OK

PASS

All 40 images OK

13 decorative image(s) correctly marked

27 image(s) with good alt text

40 images 27 good alt text 13 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

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

Got: en

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

Iframe Accessibility

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

PASS

1/1 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.

A+

Mobile-Readable Font Sizes

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

PASS

All 117 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

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.

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