Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 12 -1-on-focusable

FIX

0 positive, 12 -1-on-focusable

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

tabindex="-1" on naturally-focusable <input id="ify-newsletter-company">

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

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.

D

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

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.

D

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 ✗

F

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

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

Mobile Keyboard & Autofill

Action

4/8 eligible field(s) missing autocomplete or inputmode

REVIEW

4/8 eligible field(s) missing autocomplete or inputmode

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: search, email.

Got: <input type="search" name="s" id="mobile-site-search">, <input type="search" name="s" id="site-search-input">, <input type="email" name="email" id="email">, <input type="email" name="email" id="ify-newsletter-email">

C

Mobile-Readable Font Sizes

Action

85% of visible text renders at >= 12 CSS px (11 below threshold)

REVIEW

85% of visible text renders at >= 12 CSS px (11 below threshold)

11 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: <p> 10.6px ("Livrare gratuită pentru comenzile de pes..."); <span> 0.0px ("Adaugă în coș"); <span> 9.6px ("Reducere 35%"); <span> 0.0px ("Adaugă în coș"); <span> 0.0px ("Adaugă în coș").

C

404 Error Page

Action

Could not test

REVIEW

Could not test

404 page could not be tested

The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

C

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 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

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 1 fail WCAG AA

REVIEW

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

19 pass 1 fail WCAG AA

title Pisica Decorativa Alba - ify.ro

3.76:1

#000000

on

#A44F3B

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Pisica Decorativa Al…	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h2 Descriere	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h2 Recenzii	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h2 Produse similare	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h2 Pisica Decorativa	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h2 Love Rose	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h2 Bichon	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h2 Cuplu Îndrăgostiț…	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h2 Ai o întrebare desp…	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h2 10% reducere la prim…	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h2 Bine ai venit în co…	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h2 Tu alegi cookie-uril…	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h3 Descoperă	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h3 Informații	20.67:1	3.0:1	#000000	#FFFDF9	Pass
h3 Contact	20.67:1	3.0:1	#000000	#FFFDF9	Pass
title Pisica Decorativa Al…	3.76:1	4.5:1	#000000	#A44F3B	Fail
a Sari la conținut	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Livrare gratuită pe…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Deschide meniul	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Înapoi	21.00:1	4.5: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

Landmark Structure

7 landmarks

PASS

7 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

A+

Heading Hierarchy

15 headings

PASS

15 headings

Single H1 present

H1 Pisica Decorativa Alba
H2 Descriere
H2 Recenzii
H2 Produse similare
H2 Pisica Decorativa
H2 Love Rose
H2 Bichon
H2 Cuplu Îndrăgostiți
H2 Ai o întrebare despre produse?
H3 Descoperă
H3 Informații
H3 Contact
H2 10% reducere la prima comandă
H2 Bine ai venit în comunitatea IFY!
H2 Tu alegi cookie-urile

A+

Heading Text Quality

All 15 heading(s) have substantive, well-formed text

PASS

All 15 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 8 images OK

PASS

All 8 images OK

1 decorative image(s) correctly marked

7 image(s) with good alt text

8 images 7 good alt text 1 decorative

All images have appropriate alt text.

A

Form Accessibility

1 of 12 controls have issues

PASS

1 of 12 controls have issues

1 control(s) without accessible label

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

Got: <input type="submit" name="submit" id="submit">

11 control(s) properly labeled

12 controls

11 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#mobile-site-search	search	Caută în site	for/id
#site-search-input	search	Caută produse	for/id
#quantity_6a9d68680644f	number	Cantitate de produse	aria-label
#rating	select	Evaluarea ta *	for/id
#comment	textarea	Recenzia ta *	for/id
#author	text	Nume *	for/id
#email	email	Email *	for/id
#wp-comment-cookies-consent	checkbox	Salvează-mi numele, emailul și site-ul web în acest navigator pentru data viitoare când o să comentez.	for/id
#ify-newsletter-name	text	Nume	none
#ify-newsletter-email	email	E-mail	none
#ify-newsletter-consent	checkbox		none
#submit	submit	(none)	none

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

Why this matters

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

Source: WCAG 2.1 SC 3.3.2

A

Link & Button Quality

65 links, 22 buttons — all OK

PASS

65 links, 22 buttons — all OK

12 link(s) open in new tab without warning

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

Got: https://wa.me/40750403095?text=Bun%C4%83%21%20Am%20o%20%C3%AEntrebare%20despr…; https://www.instagram.com/ify.3d; https://www.facebook.com/ify3d; https://www.tiktok.com/@ify3dro; https://wa.me/40750403095?text=Bun%C4%83%21%20Am%20o%20%C3%AEntrebare%20despr…; https://wa.me/40750403095?text=Bun%C4%83%21%20Am%20o%20%C3%AEntrebare%20despr…; https://www.instagram.com/ify.3d; https://www.facebook.com/ify3d; https://www.tiktok.com/@ify3dro; https://wa.me/40750403095?text=Bun%C4%83%21%20Am%20o%20%C3%AEntrebare%20despr… (+2 more)

53 link(s) with descriptive text

65 links

0 empty

0 generic text

12 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://wa.me/40750403095?text=Bun%C4%83…	Răspundem cu dragScrie-ne pe …	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/ify.3d	Instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/ify3d	Facebook	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@ify3dro	Tiktok	new tab	Add '(opens in new tab)' to text
https://wa.me/40750403095?text=Bun%C4%83…	Întreabă-ne pe WhatsApp desp…	new tab	Add '(opens in new tab)' to text
https://wa.me/40750403095?text=Bun%C4%83…	Scrie-ne pe WhatsApp	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/ify.3d	Instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/ify3d	Facebook	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@ify3dro	Tiktok	new tab	Add '(opens in new tab)' to text
https://wa.me/40750403095?text=Bun%C4%83…	WhatsApp	new tab	Add '(opens in new tab)' to text
https://ify.ro/	ify.ro	new tab	Add '(opens in new tab)' to text
https://wa.me/40750403095?text=Bun%C4%83…	Scrie-ne pe WhatsApp	new tab	Add '(opens in new tab)' to text

75 links and buttons have descriptive text

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

https://wa.me/40750403095?text=Bun%C4%83%21%20Am%20o%20%C3%AEntrebare%20despr…; https://www.instagram.com/ify.3d; https://www.facebook.com/ify3d; https://www.tiktok.com/@ify3dro; https://wa.me/40750403095?text=Bun%C4%83%21%20Am%20o%20%C3%AEntrebare%20despr…; https://wa.me/40750403095?text=Bun%C4%83%21%20Am%20o%20%C3%AEntrebare%20despr…; https://www.instagram.com/ify.3d; https://www.facebook.com/ify3d; https://www.tiktok.com/@ify3dro; https://wa.me/40750403095?text=Bun%C4%83%21%20Am%20o%20%C3%AEntrebare%20despr… (+2 more)

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

A+

Form Input Types

12 form control(s) checked, no type mismatches

PASS

12 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

A+

Document Language

Lang attribute set to "ro-RO"

PASS

Lang attribute set to "ro-RO"

<html lang="ro-RO"> is set and valid

Got: ro-RO

A+

Iframe Accessibility

No iframes on this page

PASS

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

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

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

A+

Lighthouse Accessibility Audits

Score 100/100 — 1 failing, 29 passed

PASS

100

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.

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
0 `header.site-header > div.site-shell > div.header-actions > a.icon-button`

○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]`s are contained by their required parent element

●`[role]` values are valid

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

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

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

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

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

○Identical links have the same purpose.

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