Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

12 PASS 5 REVIEW 7 FIX

Landmark Structure

Action

4 landmarks

FIX

4 landmarks

No <main> landmark found

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

3 <nav> landmark(s) found

3 of 3 <nav> elements are unlabeled

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

No contentinfo (footer) landmark

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

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

Heading Hierarchy

Action

31 headings, 3 skip(s)

FIX

31 headings, 3 skip(s)

No H1 heading found

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

H2 ridicăm sarcini pe șantiere
H2 ȘI AFACERI LA URMĂTORUL NIVEL
H3 MACARALE SI ACCESORII
H3 SCHELE ȘI COFRAJE
H3 SCULE ȘI UTILAJE
H2 DESPRE FORTZA.RO
H2 Ne reprezintă
H4 Experiența skipped
H4 Calitatea
H4 Inovația
H4 Performanța
H2 Gamă largă de produse
H2 pentru lucrul pe șantier
H4 Macarale de închiriat sau vânzare skipped
H4 Cofraje din lemn, cofraje metalice sau PVC
H4 Schele metalice
H4 Popi metalici
H4 Scule și unelte pentru șantier
H4 Distanțiere pentru cofrare
H2 noutăți
H2 DIN BLOG
H3 Angajăm Specialist Suport Vanzari
H3 Coleg pentru online (anunțuri)
H3 Stație de incarcare
H2 experiență îndelungată
H2 CONFIRMATĂ DE EXPERȚI
H2 facem performanță în următoarele
H2 DOMENII
H2 nu ne lăudăm dar
H2 CIFRELE VORBESC
H4 Privacy Overview skipped

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 ▾

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

404 Error Page

Action

HTTP 500, custom page

FIX

HTTP 500, custom page

Unexpected status code: HTTP 500

Expected HTTP 404 but received 500. This may confuse search engine crawlers.

Got: HTTP 500

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 500 ✗Page Title Eroare la baza de date ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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

No dark mode signals

FIX

No dark mode signals

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

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

3 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

Skip Link

Labeled Navigation 3 <nav> element(s)

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.

Link & Button Quality

Action

9 issue(s) across 120 links and 2 buttons

REVIEW

9 issue(s) across 120 links and 2 buttons

9 link(s) with no accessible text

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

Got: https://twitter.com/FortzaRo; https://www.facebook.com/fortza.ro.medias.ghimbav.tunari/; https://plus.google.com/b/117599077801942609585/117599077801942609585; https://www.linkedin.com/company/fortza.ro; #; #; #; #; #top-of-page

32 link(s) open in new tab without warning

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

Got: https://fortza.ro; https://fortza.ro; http://www.macaraledeinchiriat.eu/; https://www.macaraledeinchiriat.eu/; http://www.schelametalica.eu/; http://www.popimetalici.eu/; http://www.cofraje.net/; https://www.cofraje.net/sistem-de-cofraje-pentru-santuri/; http://www.schelametalica.eu/; http://www.fortza.ro (+22 more)

79 link(s) with descriptive text

120 links

9 empty

0 generic text

32 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://twitter.com/FortzaRo	(empty)	empty	Add link text or aria-label
https://www.facebook.com/fortza.ro.media…	(empty)	empty	Add link text or aria-label
https://plus.google.com/b/11759907780194…	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/fortza.…	(empty)	empty	Add link text or aria-label
https://fortza.ro	Magazin	new tab	Add '(opens in new tab)' to text
https://fortza.ro	Magazin	new tab	Add '(opens in new tab)' to text
http://www.macaraledeinchiriat.eu/	închiriere de macarale	new tab	Add '(opens in new tab)' to text
https://www.macaraledeinchiriat.eu/	DETALII	new tab	Add '(opens in new tab)' to text
http://www.schelametalica.eu/	schele metalice second hand	new tab	Add '(opens in new tab)' to text
http://www.popimetalici.eu/	popi metalici second hand	new tab	Add '(opens in new tab)' to text
http://www.cofraje.net/	cofraje	new tab	Add '(opens in new tab)' to text
https://www.cofraje.net/sistem-de-cofraj…	cofraje sprijinire șanțuri	new tab	Add '(opens in new tab)' to text
http://www.schelametalica.eu/	DETALII	new tab	Add '(opens in new tab)' to text
http://www.fortza.ro	Fortza	new tab	Add '(opens in new tab)' to text
http://www.fortza.ro	DETALII	new tab	Add '(opens in new tab)' to text
http://www.macaraledeinchiriat.eu/	Macarale de închiriat sau vâ…	new tab	Add '(opens in new tab)' to text
https://www.cofraje.net/categorie-produs…	Cofraje din lemn	new tab	Add '(opens in new tab)' to text
https://www.cofraje.net/categorie-produs…	cofraje metalice	new tab	Add '(opens in new tab)' to text
https://www.cofraje.net/categorie-produs…	PVC	new tab	Add '(opens in new tab)' to text
http://www.schelametalica.eu/	Schele metalice	new tab	Add '(opens in new tab)' to text
http://www.popimetalici.eu/	Popi metalici	new tab	Add '(opens in new tab)' to text
http://fortza.ro/	Scule și unelte pentru șanti…	new tab	Add '(opens in new tab)' to text
https://www.distantiere-beton.ro	Distanțiere pentru cofrare	new tab	Add '(opens in new tab)' to text
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
http://www.macaraledeinchiriat.eu/	DETALII	new tab	Add '(opens in new tab)' to text
#	VEZI PAGINA	new tab	Add '(opens in new tab)' to text
http://www.schelametalica.eu/	Vezi pagina	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/fortza.ro.media…	Follow Us on facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/fortzaro	Follow Us on twitter	new tab	Add '(opens in new tab)' to text
https://automacara.ro	Automacara	new tab	Add '(opens in new tab)' to text
https://www.cofraje.net/	Sisteme de cofrare	new tab	Add '(opens in new tab)' to text
https://www.cofraje.net/	Distantieri cofraje	new tab	Add '(opens in new tab)' to text
https://bazarscule.ro	Bazar de scule	new tab	Add '(opens in new tab)' to text
https://fortza.ro	Magazin	new tab	Add '(opens in new tab)' to text
https://fortza.ro	FORTZA	new tab	Add '(opens in new tab)' to text
https://visteria.ro	VISTERIA	new tab	Add '(opens in new tab)' to text
#top-of-page	(empty)	empty	Add link text or aria-label
https://www.fortza.net/politica-de-confi…	Citește detaliile	new tab	Add '(opens in new tab)' to text

81 links and buttons have descriptive text

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

https://twitter.com/FortzaRo; https://www.facebook.com/fortza.ro.medias.ghimbav.tunari/; https://plus.google.com/b/117599077801942609585/117599077801942609585; https://www.linkedin.com/company/fortza.ro; #; #; #; #; #top-of-page

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://fortza.ro; https://fortza.ro; http://www.macaraledeinchiriat.eu/; https://www.macaraledeinchiriat.eu/; http://www.schelametalica.eu/; http://www.popimetalici.eu/; http://www.cofraje.net/; https://www.cofraje.net/sistem-de-cofraje-pentru-santuri/; http://www.schelametalica.eu/; http://www.fortza.ro (+22 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

Mobile-Readable Font Sizes

Action

89% of visible text renders at >= 12 CSS px (13 below threshold)

REVIEW

89% of visible text renders at >= 12 CSS px (13 below threshold)

13 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> 10.0px ("DETALII"); <span> 10.0px ("DETALII"); <span> 10.0px ("DETALII"); <a> 11.0px ("24/07/2025"); <a> 11.0px ("24/10/2023").

Favicon & Branding

Action

5 icon(s) detected

REVIEW

5 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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 8 fail WCAG AA

REVIEW

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

12 pass 8 fail WCAG AA 9 pass AA only

title Fortza – Macarale – Schele – Cofra…

3.23:1

#000000

#1D53D3

needs 4.5:1 (normal text)

16px · top of page (header area)

a 0269 838 450

3.23:1

#000000

#1D53D3

needs 4.5:1 (normal text)

16px · top of page (header area)

a office@fortza.ro

3.23:1

#000000

#1D53D3

needs 4.5:1 (normal text)

16px · top of page (header area)

a Blog

3.65:1

#000000

#75625A

needs 4.5:1 (normal text)

16px · above the fold

a Contact

2.13:1

#000000

#3A4454

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

a Fortza Medias

1.62:1

#000000

#003164

needs 4.5:1 (normal text)

16px · mid-page

a Fortza Brașov

1.62:1

#000000

#003164

needs 4.5:1 (normal text)

16px · mid-page

a Fortza București

1.62:1

#000000

#003164

needs 4.5:1 (normal text)

16px · mid-page

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
h3 MACARALE SI ACCESORI…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 SCHELE ȘI COFRAJE	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 SCULE ȘI UTILAJE	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Fortza – Macarale …	3.23:1	4.5:1	#000000	#1D53D3	Fail
a 0269 838 450	3.23:1	4.5:1	#000000	#1D53D3	Fail
a office@fortza.ro	3.23:1	4.5:1	#000000	#1D53D3	Fail
span Profesioniști pentr…	5.95:1	4.5:1	#000000	#8B8883	Pass
a Abonează-te	5.84:1	4.5:1	#000000	#8B8683	Pass
label Abonează-te la news…	5.84:1	4.5:1	#000000	#8B8683	Pass
a Acasă	5.76:1	4.5:1	#000000	#8A8582	Pass
a Despre noi	5.80:1	4.5:1	#000000	#898682	Pass
a Servicii	5.72:1	4.5:1	#000000	#888581	Pass
a Magazin	4.81:1	4.5:1	#000000	#78797A	Pass
a Cariere	4.90:1	4.5:1	#000000	#87776F	Pass
a Timite CV	4.81:1	4.5:1	#000000	#847671	Pass
a Blog	3.65:1	4.5:1	#000000	#75625A	Fail
a Contact	2.13:1	4.5:1	#000000	#3A4454	Fail
a Fortza Medias	1.62:1	4.5:1	#000000	#003164	Fail
a Fortza Brașov	1.62:1	4.5:1	#000000	#003164	Fail
a Fortza București	1.62:1	4.5:1	#000000	#003164	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

Score 80/100 — 4 failing, 16 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.

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
NOUTĂȚI `div.vc_col-sm-12 > h2#fancy-title-50 > span > p`
24/07/2025 `div.mk-blog-meta > div.mk-blog-meta-wrapper > time > a`
24/10/2023 `div.mk-blog-meta > div.mk-blog-meta-wrapper > time > a`
18/08/2023 `div.mk-blog-meta > div.mk-blog-meta-wrapper > time > a`
FACEM PERFORMANȚĂ ÎN URMĂTOARELE `div.vc_col-sm-12 > h2#fancy-title-63 > span > p`
Vânzare și închiriere de macarale. Service, mentenanță, transport, piese de sch… `div.mk-flipbox-holder > div.mk-flipbox-front > div.mk-flipbox-content > div.front-desc`
Secții dotare modern pentru confecții metalice de orice fel. O echipă de profes… `div.mk-flipbox-holder > div.mk-flipbox-front > div.mk-flipbox-content > div.front-desc`
Schele metalice, podine, diagonale, popi metalici și tot ce ține de lucrul pe ș… `div.mk-flipbox-holder > div.mk-flipbox-front > div.mk-flipbox-content > div.front-desc`

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
Experiența `div.vc_column-inner > div.wpb_wrapper > div#box-icon-35 > h4.icon-box-title`
Macarale de închiriat sau vânzare `div#list-44 > ul > li > h4`

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.wpb_row > div.vc_col-sm-12 > div.mk-pagination > a.mk-pagination-next `div.wpb_row > div.vc_col-sm-12 > div.mk-pagination > a.mk-pagination-next`
div#testimonial_60 > ul.flex-direction-nav > li > a.flex-prev `div#testimonial_60 > ul.flex-direction-nav > li > a.flex-prev`
div#testimonial_60 > ul.flex-direction-nav > li > a.flex-next `div#testimonial_60 > ul.flex-direction-nav > li > a.flex-next`
body.home > div.bottom-corner-btns > a.mk-go-top `body.home > div.bottom-corner-btns > a.mk-go-top`

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`

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-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●Image elements have `[alt]` attributes

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

●`[aria-hidden="true"]` elements do not contain focusable descendents

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

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

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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○ARIA attributes are used as specified for the element's role

○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 use only permitted 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

○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

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

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

○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

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○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

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

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

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

A+

Alt Text Quality

All 16 images OK

PASS

All 16 images OK

1 decorative image(s) correctly marked

15 image(s) with good alt text

16 images 15 good alt text 1 decorative

All images have appropriate alt text.

Form Accessibility

1 of 4 controls have issues

PASS

1 of 4 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="subscribe" id="mc-embedded-subscribe">

3 control(s) properly labeled

4 controls

3 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#mce-EMAIL	email	Abonează-te la newsletter	for/id
#wt-cli-checkbox-necessary	checkbox	Necessary	for/id
#wt-cli-checkbox-non-necessary	checkbox	Non-necessary	for/id
#mc-embedded-subscribe	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+

Form Input Types

4 form control(s) checked, no type mismatches

PASS

4 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

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+

Tabindex Anti-Patterns

4 explicit tabindex attribute(s) checked, no anti-patterns

PASS

4 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

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

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.

iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)

The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

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