Skip to content
https://distantiere-beton.ro

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
GRADE
C
FIX
5
REVIEW
5
PASS
14
INFO
0
Checks
24
14 PASS 5 REVIEW 5 FIX
F
404 Error Page
Action
HTTP 500, custom page
FIX
HTTP 500, custom page
Warning::
Unexpected status code: HTTP 500
Expected HTTP 404 but received 500. This may confuse search engine crawlers.
Got: HTTP 500
Info::
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 ✗
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::
1 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 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
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
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

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

B
Heading Hierarchy
17 headings, 2 skip(s)
REVIEW
17 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H4 (missing H2)
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.
  • H1 Distanțiere Cofraj
  • H4 Cofraje lemn, metal sau PVC skipped
  • H4 Service macarale turn
  • H4 Macarale turn si automontante
  • H4 Schele metalice
  • H4 Distanțiere cofraje
  • H4 Popi metalici pentru construcții
  • H4 Producător distanțiere cofraj
  • H4 Importator de distanțiere
  • H4 Distribuție distanțiere cofraj
  • H2 Nu există proiecte prea mici sau prea mari.
  • H3 Cere ofertă  distantiere cofraj
  • H2 Avem  peste 20 de ani experiență pe piața construcțiilor
  • H2 Contact
  • H4 FORTZA RO SRL skipped
  • H4 +40 269 838 450
  • H4 office@fortza.ro

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

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
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 16 fail WCAG AA
REVIEW

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

4 pass 16 fail WCAG AA
h1 Distanțiere Cofraj
1.67:1
#000000
on
#343334
needs 3.0:1 (large text)
32px · above the fold · over background image/gradient
title Distantiere cofraje - Distanțiere cofra…
1.66:1
#000000
on
#1C2A79
needs 4.5:1 (normal text)
16px · top of page (header area)
a Distantiere cofraj
1.66:1
#000000
on
#1C2A79
needs 4.5:1 (normal text)
16px · top of page (header area)
a Preț distanțiere
1.65:1
#000000
on
#272F5E
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Contact
1.60:1
#000000
on
#313030
needs 4.5:1 (normal text)
16px · top of page (header area)
span Selectează o Pagină
1.61:1
#000000
on
#35302C
needs 4.5:1 (normal text)
16px · above the fold
a Distantiere cofraj
1.63:1
#000000
on
#34312F
needs 4.5:1 (normal text)
16px · above the fold
a Preț distanțiere
1.69:1
#000000
on
#383331
needs 4.5:1 (normal text)
16px · above the fold
a Contact
1.64:1
#000000
on
#333231
needs 4.5:1 (normal text)
16px · above the fold
div Producător si importator distanțiere p…
1.64:1
#000000
on
#323234
needs 4.5:1 (normal text)
16px · above the fold
a Vezi oferta noastră pentru distanțiere…
1.98:1
#000000
on
#413E3E
needs 4.5:1 (normal text)
16px · above the fold
a Cofraje lemn, metal sau PVC
2.16:1
#000000
on
#444444
needs 4.5:1 (normal text)
16px · above the fold
p Distribuim cofraje de lemn, metalice si …
2.31:1
#000000
on
#4A4849
needs 4.5:1 (normal text)
16px · mid-page
a Service macarale turn
1.67:1
#000000
on
#333335
needs 4.5:1 (normal text)
16px · mid-page
div Oferim servicii complete pentru macarale…
2.21:1
#000000
on
#474545
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
a Macarale turn si automontante
3.07:1
#000000
on
#5C5A5A
needs 4.5:1 (normal text)
16px · mid-page

3 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)
ElementRatioRequiredFGBGResult
h1 Distanțiere Cofraj1.67:13.0:1
#000000
#343334
Fail
h2 Nu există proiecte …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Avem  peste 20 de a…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Contact21.00:13.0:1
#000000
#FFFFFF
Pass
h3 distantiere cofraj21.00:13.0:1
#000000
#FFFFFF
Pass
title Distantiere cofraje …1.66:14.5:1
#000000
#1C2A79
Fail
a Distantiere cofraj1.66:14.5:1
#000000
#1C2A79
Fail
a Preț distanțiere1.65:14.5:1
#000000
#272F5E
Fail
a Contact1.60:14.5:1
#000000
#313030
Fail
span Selectează o Pagin…1.61:14.5:1
#000000
#35302C
Fail
a Distantiere cofraj1.63:14.5:1
#000000
#34312F
Fail
a Preț distanțiere1.69:14.5:1
#000000
#383331
Fail
a Contact1.64:14.5:1
#000000
#333231
Fail
div Producător si impor…1.64:14.5:1
#000000
#323234
Fail
a Vezi oferta noastră…1.98:14.5:1
#000000
#413E3E
Fail
a Cofraje lemn, metal …2.16:14.5:1
#000000
#444444
Fail
p Distribuim cofraje d…2.31:14.5:1
#000000
#4A4849
Fail
a Service macarale tur…1.67:14.5:1
#000000
#333335
Fail
div Oferim servicii comp…2.21:14.5:1
#000000
#474545
Fail
a Macarale turn si aut…3.07:14.5:1
#000000
#5C5A5A
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.

B
Lighthouse Accessibility Audits
Score 80/100 — 5 failing, 16 passed
REVIEW
80

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
VEZI OFERTA NOASTRĂ PENTRU DISTANȚIERE COFRAJ div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a.et_pb_button
DESPRE NOI div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a.et_pb_button
div.et_pb_contact > form.et_pb_contact_form > p.et_pb_contact_field > input#et_pb_contact_nume_0 div.et_pb_contact > form.et_pb_contact_form > p.et_pb_contact_field > input#et_pb_contact_nume_0
div.et_pb_contact > form.et_pb_contact_form > p.et_pb_contact_field > input#et_pb_contact_email_0 div.et_pb_contact > form.et_pb_contact_form > p.et_pb_contact_field > input#et_pb_contact_email_0
div.et_pb_contact > form.et_pb_contact_form > p.et_pb_contact_field > textarea#et_pb_contact_mesaj_0 div.et_pb_contact > form.et_pb_contact_form > p.et_pb_contact_field > textarea#et_pb_contact_mesaj_0
TRIMITE MESAJ div.et_pb_contact > form.et_pb_contact_form > div.et_contact_bottom_container > button.et_pb_contact_submit

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
Cofraje lemn, metal sau PVC div.et_pb_module > div.et_pb_blurb_content > div.et_pb_blurb_container > h4.et_pb_module_header
FORTZA RO SRL div.et_pb_module > div.et_pb_blurb_content > div.et_pb_blurb_container > h4.et_pb_module_header

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.container > ul.et-social-icons > li.et-social-icon > a.icon div.container > ul.et-social-icons > li.et-social-icon > a.icon
div.container > ul.et-social-icons > li.et-social-icon > a.icon div.container > ul.et-social-icons > li.et-social-icon > a.icon
div.container > ul.et-social-icons > li.et-social-icon > a.icon div.container > ul.et-social-icons > li.et-social-icon > a.icon

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

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

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
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[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.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA 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
○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.
○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
Info::
1 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: 1 all-caps heading(s)
A+
Alt Text Quality
All 11 images OK
PASS
All 11 images OK
Info::
11 image(s) with good alt text
11 images 11 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 4 controls have issues
PASS
1 of 4 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="s">
Info::
3 control(s) properly labeled
4 controls
3 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#et_pb_contact_nume_0textNumefor/id
#et_pb_contact_email_0textEmailfor/id
#et_pb_contact_mesaj_0textareaMesajfor/id
ssearch(Caută …)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="search" name="s">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "et_pb_contact_email_0" should use type="email" (currently type="text")
Field name "et_pb_contact_email_0" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
A+
Form Input Quality
4 form control(s) checked, no input-semantic issues
PASS
4 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 "ro-RO"
PASS
Lang attribute set to "ro-RO"
Info::
<html lang="ro-RO"> is set and valid
Got: ro-RO
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
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 55 visible text node(s) render at >= 12 CSS pixels
PASS
All 55 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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback