Skip to content
https://containere.eu

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
74
GRADE
C
FIX
6
REVIEW
3
PASS
15
INFO
0
Checks
24
15 PASS 3 REVIEW 6 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 Database Error ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
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
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Tabindex Anti-Patterns
Action
0 positive, 9 -1-on-focusable
REVIEW
0 positive, 9 -1-on-focusable
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 17 fail WCAG AA
REVIEW

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

3 pass 17 fail WCAG AA 3 pass AA only
h2 Experiență de peste 10 ani în confec…
2.87:1
#000000
on
#1A4CC3
needs 3.0:1 (large text)
24px · bottom of viewport
h2 servicii Oferite
2.87:1
#000000
on
#1A4CC3
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Avantajele containerelor
2.87:1
#000000
on
#1A4CC3
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Din portofoliul de lucrări
2.87:1
#000000
on
#1A4CC3
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Articole despre containere
2.87:1
#000000
on
#1A4CC3
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Prtoducător de containere cu experienț…
2.87:1
#000000
on
#1A4CC3
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Executăm
2.87:1
#000000
on
#1A4CC3
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Date contact
2.87:1
#000000
on
#1A4CC3
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Newsletter
2.87:1
#000000
on
#1A4CC3
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ocazional postam articole utile despre c…
2.87:1
#000000
on
#1A4CC3
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Containere de locuit
2.87:1
#000000
on
#1A4CC3
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Containere speciale
2.87:1
#000000
on
#1A4CC3
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Detalii
2.87:1
#000000
on
#1A4CC3
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Satisfacție garantată
2.87:1
#000000
on
#1A4CC3
needs 3.0:1 (large text)
19px · bottom of viewport
title Fortza BOX – Producator de containere …
3.58:1
#000000
on
#285CD5
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
3.49:1
#000000
on
#245AD4
needs 4.5:1 (normal text)
16px · top of page (header area)
p Producător de containere
3.36:1
#000000
on
#2358CE
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Fortza BOX3.06:13.0:1
#000000
#1F51C7
Pass
h2 Experiență de pest…2.87:13.0:1
#000000
#1A4CC3
Fail
h2 servicii Oferite2.87:13.0:1
#000000
#1A4CC3
Fail
h2 Avantajele container…2.87:13.0:1
#000000
#1A4CC3
Fail
h2 Din portofoliul de l…2.87:13.0:1
#000000
#1A4CC3
Fail
h2 Articole despre cont…2.87:13.0:1
#000000
#1A4CC3
Fail
h2 Prtoducător de cont…2.87:13.0:1
#000000
#1A4CC3
Fail
h2 Executăm2.87:13.0:1
#000000
#1A4CC3
Fail
h2 Date contact2.87:13.0:1
#000000
#1A4CC3
Fail
h2 Newsletter2.87:13.0:1
#000000
#1A4CC3
Fail
h2 Ocazional postam art…2.87:13.0:1
#000000
#1A4CC3
Fail
h3 Cauți un producăto…3.27:13.0:1
#000000
#2456CB
Pass
h3 Contanere birou3.02:13.0:1
#000000
#1F50C6
Pass
h3 Containere de locuit2.87:13.0:1
#000000
#1A4CC3
Fail
h3 Containere speciale2.87:13.0:1
#000000
#1A4CC3
Fail
h3 Detalii2.87:13.0:1
#000000
#1A4CC3
Fail
h3 Satisfacție garanta…2.87:13.0:1
#000000
#1A4CC3
Fail
title Fortza BOX – Produ…3.58:14.5:1
#000000
#285CD5
Fail
a Skip to content3.49:14.5:1
#000000
#245AD4
Fail
p Producător de conta…3.36:14.5:1
#000000
#2358CE
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
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No contentinfo (footer) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Menu" MAIN CONTENTINFO (missing!)

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

A
Heading Hierarchy
23 headings, 1 skip(s)
PASS
23 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Cauți un producător de containere ?
  • H1 Fortza BOX
  • H3 Contanere birou skipped
  • H3 Containere de locuit
  • H3 Containere speciale
  • H2 Experiență de peste 10 ani în confecții metalice și containere pentru birouri și șantier
  • H3 Detalii
  • H2 servicii Oferite
  • H3 Proiectare
  • H3 Execuție
  • H3 Amenajare
  • H2 Avantajele containerelor
  • H2 Din portofoliul de lucrări
  • H3 Satisfacție garantată
  • H2 Articole despre containere
  • H3 FORTZA – Producător containere de șantier în Mediaș
  • H3 Containere de locuit
  • H3 Containere pentru vânzări stradale sezoniere
  • H2 Prtoducător de containere cu experiență și capacitate mare de producție.
  • H2 Executăm
  • H2 Date contact
  • H2 Newsletter
  • H2 Ocazional postam articole utile despre containerele pe care le producem sau montăm. Dacă vă interesează subietul vă puteti abona cu adresa de email.

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

A
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Warning::
1 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H2: 148 chars
Got: 1 >120-char heading(s)
A+
Alt Text Quality
All 12 images OK
PASS
All 12 images OK
Info::
7 decorative image(s) correctly marked
Info::
5 image(s) with good alt text
12 images 5 good alt text 7 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#form-field-nameemailEmailfor/id
A+
Form Input Types
1 form control(s) checked, no type mismatches
PASS
1 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
1 form control(s) checked, no input-semantic issues
PASS
1 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 "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
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 84 visible text node(s) render at >= 12 CSS pixels
PASS
All 84 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.
A
Lighthouse Accessibility Audits
Score 92/100 — 4 failing, 25 passed
PASS
92

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
0269 838 450 ul.elementor-icon-list-items > li.elementor-icon-list-item > a > span.elementor-icon-list-text
0269 838 450 a.ekit_global_links > div.elementskit-infobox > div.box-body > p

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
Contanere Birou a.ekit_global_links > div.elementskit-infobox > div.box-body > h3.elementskit-info-box-title

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.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon
div.elementor-posts-container > article.elementor-post > div.elementor-post__card > a.elementor-post__thumbnail__link div.elementor-posts-container > article.elementor-post > div.elementor-post__card > a.elementor-post__thumbnail__link
div.elementor-posts-container > article.elementor-post > div.elementor-post__card > a.elementor-post__thumbnail__link div.elementor-posts-container > article.elementor-post > div.elementor-post__card > a.elementor-post__thumbnail__link

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.

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
CONTINUARE » article.elementor-post > div.elementor-post__card > div.elementor-post__text > a.elementor-post__read-more
CONTINUARE » article.elementor-post > div.elementor-post__card > div.elementor-post__text > a.elementor-post__read-more
CONTINUARE » article.elementor-post > div.elementor-post__card > div.elementor-post__text > a.elementor-post__read-more
○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
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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.
●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
○Links are distinguishable without relying on color.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback