Skip to content
https://gar-bau.ro

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
79
GRADE
C
FIX
5
REVIEW
3
PASS
16
INFO
0
Checks
24
16 PASS 3 REVIEW 5 FIX
D
Mobile Keyboard & Autofill
Action
4/4 eligible field(s) missing autocomplete or inputmode
FIX
4/4 eligible field(s) missing autocomplete or inputmode
Warning::
2 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: name, email.
Got: <input type="text" name="name" id="name">, <input type="email" name="email" id="email">
Warning::
2 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: email, tel.
Got: <input type="email" name="email" id="email">, <input type="tel" name="phone" id="phone">
F
Favicon & Branding
Action
No icons detected
FIX
No icons 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::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
Critical::
No favicon or icon links detected
Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.
✗ favicon.ico Missing
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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
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
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404: This page could not be found. ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
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
h1 Solutii pentru Izolatii Industriale si R…
1.83:1
#000000
on
#1A3380
needs 3.0:1 (large text)
32px · above the fold
h2 Serviciile Noastre
1.83:1
#000000
on
#1A3380
needs 3.0:1 (large text)
24px · mid-page
h2 Tehnici și Materiale de Hidroizolație
1.83:1
#000000
on
#1A3380
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Proiecte Noastre Recente
1.83:1
#000000
on
#1A3380
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Despre GARBAU
1.83:1
#000000
on
#1A3380
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Partenerii Noștri din Industrie
1.83:1
#000000
on
#1A3380
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Întrebări Frecvente
1.83:1
#000000
on
#1A3380
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Contactați-ne
1.83:1
#000000
on
#1A3380
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Membrane PVC
1.83:1
#000000
on
#1A3380
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Membrane TPO
1.83:1
#000000
on
#1A3380
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Sisteme Bituminoase
1.83:1
#000000
on
#1A3380
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Membrane Lichide
1.83:1
#000000
on
#1A3380
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Istoria & Misiunea Noastră
1.83:1
#000000
on
#1A3380
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Certificări & Calificări
1.83:1
#000000
on
#1A3380
needs 3.0:1 (large text)
19px · bottom of viewport
h3 De Ce Să Alegeți GarBau?
1.83:1
#000000
on
#1A3380
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Sika
1.83:1
#000000
on
#1A3380
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Fatra
1.83:1
#000000
on
#1A3380
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Rockwool
1.83:1
#000000
on
#1A3380
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Knauf Insulation
1.83:1
#000000
on
#1A3380
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Bauder
1.83:1
#000000
on
#1A3380
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Solutii pentru Izola…1.83:13.0:1
#000000
#1A3380
Fail
h2 Serviciile Noastre1.83:13.0:1
#000000
#1A3380
Fail
h2 Tehnici și Material…1.83:13.0:1
#000000
#1A3380
Fail
h2 Proiecte Noastre Rec…1.83:13.0:1
#000000
#1A3380
Fail
h2 Despre GARBAU1.83:13.0:1
#000000
#1A3380
Fail
h2 Partenerii Noștri d…1.83:13.0:1
#000000
#1A3380
Fail
h2 Întrebări Frecvent…1.83:13.0:1
#000000
#1A3380
Fail
h2 Contactați-ne1.83:13.0:1
#000000
#1A3380
Fail
h3 Membrane PVC1.83:13.0:1
#000000
#1A3380
Fail
h3 Membrane TPO1.83:13.0:1
#000000
#1A3380
Fail
h3 Sisteme Bituminoase1.83:13.0:1
#000000
#1A3380
Fail
h3 Membrane Lichide1.83:13.0:1
#000000
#1A3380
Fail
h3 Istoria & Misiunea N…1.83:13.0:1
#000000
#1A3380
Fail
h3 Certificări & Calif…1.83:13.0:1
#000000
#1A3380
Fail
h3 De Ce Să Alegeți G…1.83:13.0:1
#000000
#1A3380
Fail
h3 Sika1.83:13.0:1
#000000
#1A3380
Fail
h3 Fatra1.83:13.0:1
#000000
#1A3380
Fail
h3 Rockwool1.83:13.0:1
#000000
#1A3380
Fail
h3 Knauf Insulation1.83:13.0:1
#000000
#1A3380
Fail
h3 Bauder1.83:13.0:1
#000000
#1A3380
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.

A
Landmark Structure
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
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 CONTENTINFO footer

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
41 headings
PASS
41 headings
Info::
Single H1 present
  • H1 Solutii pentru Izolatii Industriale si Rezidentiale
  • H2 Serviciile Noastre
  • H2 Tehnici și Materiale de Hidroizolație
  • H3 Membrane PVC
  • H3 Membrane TPO
  • H3 Sisteme Bituminoase
  • H3 Membrane Lichide
  • H2 Proiecte Noastre Recente
  • H2 Despre GARBAU
  • H3 Istoria & Misiunea Noastră
  • H3 Certificări & Calificări
  • H4 ISO 9001:2015
  • H4 ISO 14001:2015
  • H4 OHSAS 18001
  • H3 De Ce Să Alegeți GarBau?
  • H4 Echipă de Experți
  • H4 Tehnologie Avansată
  • H4 Executie Prompta
  • H4 Rentabil
  • H4 Suport pentru Întreținere
  • H4 Ecologic
  • H2 Partenerii Noștri din Industrie
  • H3 Sika
  • H3 Fatra
  • H3 Rockwool
  • H3 Knauf Insulation
  • H3 Bauder
  • H3 Kingspan
  • H3 Tremco
  • H3 Isover
  • H2 Întrebări Frecvente
  • H2 Contactați-ne
  • H3 Trimiteți-ne un Mesaj
  • H3 Luați Legătura
  • H4 Telefon
  • H4 Email
  • H4 Adresă
  • H4 Program
  • H3 Găsiți-ne
  • H3 Linkuri Rapide
  • H3 Contactați-ne
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
3 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: 3 all-caps heading(s)
A+
Alt Text Quality
All 2 images OK
PASS
All 2 images OK
Info::
2 image(s) with good alt text
2 images 2 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 7 controls labeled
PASS
All 7 controls labeled
Info::
7 control(s) properly labeled
7 controls
7 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#nametextNume Complet *for/id
#emailemailAdresă Email *for/id
#phonetelNumăr Telefonfor/id
#companytextNume Companiefor/id
#serviceTypeselectTip Serviciufor/id
#messagetextareaMesaj *for/id
#attachmentsfile📄Alegeți Fișierefor/id
A+
Form Input Types
7 form control(s) checked, no type mismatches
PASS
7 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
7 form control(s) checked, no input-semantic issues
PASS
7 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "ro"
PASS
Lang attribute set to "ro"
Info::
<html lang="ro"> is set and valid
Got: 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
All 1 iframe(s) have descriptive titles
PASS
All 1 iframe(s) have descriptive titles
Info::
All 1 iframe(s) have title attributes
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 186 visible text node(s) render at >= 12 CSS pixels
PASS
All 186 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
2 mobile-depth signal(s) detected
PASS
2 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.
Info::
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.
A+
Lighthouse Accessibility Audits
Score 100/100 — 1 failing, 26 passed
PASS
100

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.

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
ISO Certificat section.hero-module__NVBTOW__hero > div.hero-module__NVBTOW__container > div.hero-module__NVBTOW__statsGrid > button.hero-module__NVBTOW__statCard
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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.
●Select elements have associated label elements.
●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
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●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 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
○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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback