Skip to content
https://fortzasolar.ro

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
73
GRADE
C
FIX
6
REVIEW
5
PASS
13
INFO
0
Checks
24
13 PASS 5 REVIEW 6 FIX
F
Heading Hierarchy
Action
67 headings, 8 skip(s)
FIX
67 headings, 8 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: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
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 Producători de structuri fotovoltaice
  • H4 Sistem Fotovoltaic Smart 1 skipped
  • H3 Sistem Fotovoltaic Smart Dual
  • H3 Structură EST-VEST
  • H3 Sistem Fotovoltaic cu Balast
  • H3 Structură Smart cu Țăruși
  • H2 Accesorii pentru structuri panouri fotovoltaice
  • H2 Set electrozi tarusi de impamantare 16×1500 mm + conector platbanda
  • H2 Electrod tarus impamatare tija prelungire 16x1500mm otel galvanizat
  • H2 Electrod tarus impamatare tija start 16x1500mm otel galvanizat
  • H3 Misiunea noastră este să susținem pe termen lung proiectele prietenoase cu mediul
  • H5 Despre Noi skipped
  • H2 Sisteme de structuri panouri fotovoltaice
  • H5 PORTOFOLIU skipped
  • H2 Lucrări recente
  • H3 Coca Cola Timisoara – 1 MW
  • H3 Parc Fotovoltaic MAX BAU – 500 KW
  • H3 Proiect structuri fotovoltaice Șușani 3.4 MW
  • H3 Preluare proiect fotovoltaic Zărnești 404 KW
  • H3 TG.Trotuș. 3, MW Structura Effe due profil tip Omega 25 grade
  • H3 Proiect panouri fotovoltaice Arad 250 KW
  • H3 Proiect Fotovoltaic Băilești 2,8 MW structura Est-Vest 10 grade
  • H3 Proiect Parc Fotovoltaic Giurgiu 52 MW
  • H3 Parc fotovoltaic Bistrița – DATACOR 700 kW
  • H3 2 parcuri fotovoltaice Oradea 2 x 800 kw
  • H3 Parc Fotovoltaic Ferma Frumusica – 3.1 MW
  • H3 Parc Fotovoltaic Blaj – 9 MW
  • H3 Montaj parc fotovoltaic în Italia
  • H3 Structuri fotovoltaice în Moglia (Lombardia) – 2MW
  • H3 Structuri fotovoltaice în Santa Maria Maddalena – 4.9 MW
  • H3 Coca Cola Timisoara 1 MW
  • H3 TG.Trotuș. 3 MW Structura Effe due profil tip Omega 25 grade
  • H3 Parc fotovoltaic Bistrița – DATACOR 700 kW
  • H3 Montaj parc fotovoltaic în Italia
  • H3 Parc Fotovoltaic MAX BAU 500 KW
  • H3 Proiect panouri fotovoltaice Arad 250 KW
  • H3 2 parcuri fotovoltaice Oradea 2 x 800 kw
  • H3 Structuri fotovoltaice în Moglia (Lombardia) 2MW
  • H3 Proiect structuri fotovoltaice Șușani 3.4 MW
  • H3 Proiect Fotovoltaic Băilești 2,8 MW structura Est-Vest 10 grade
  • H3 Parc Fotovoltaic Ferma Frumusica 3.1 MW
  • H3 Structuri fotovoltaice în Santa Maria Maddalena 4.9 MW
  • H3 Preluare proiect fotovoltaic Zărnești 404 KW
  • H3 Proiect Parc Fotovoltaic Giurgiu 52 MW
  • H3 Parc Fotovoltaic Blaj – 9 MW
  • H5 DE CE SISTEMELE NOASTRE skipped
  • H2 Avantajele sistemelor Fortza Solar
  • H3 DURABILITATE
  • H3 VERSABILITATE
  • H3 FLEXIBILITATE
  • H3 ECONOMIE
  • H5 Participări skipped
  • H2 Târguri și expoziții
  • H2 Participare la Intersolar Europe 19-21 Iunie 2024
  • H2 Participare la conferința Digitalizare și eficiență energetică – Cluj-Napoca
  • H2 Fortza Solar la Solar Energy Bucharest Summit 2024
  • H5 Solicită evaluare skipped
  • H2 Structuri panouri fotovoltaice. Soluții durabile la prețuri corecte.
  • H5 Articole skipped
  • H2 Noutăți și resurse
  • H2 The Future Economy Summit | Participant Fortza Solar
  • H2 Greșeli în montarea panourilor solare
  • H2 10 mituri despre panourile fotovoltaice
  • H4 Despre noi skipped
  • H4 Linkuri utile
  • H4 Sisteme
  • H4 Contact

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

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

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

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

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::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <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
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
Info::
Skip navigation link present
Warning::
Skip link target(s) don't exist on page: #content
The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.
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

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

B
Mobile-Readable Font Sizes
93% of visible text renders at >= 12 CSS px (4 below threshold)
REVIEW
93% of visible text renders at >= 12 CSS px (4 below threshold)
Info::
4 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: <div> 11.0px ("Contactează-ne — răspundem rapid!"); <span> 8.0px ("AI"); <span> 11.0px ("Răspunde instant 24/7"); <span> 11.0px ("0269 838 450").
C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
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
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 Producători de structuri fotovoltaice
2.63:1
#000000
on
#3F5078
needs 3.0:1 (large text)
32px · mid-page · over background image/gradient
h2 Accesorii pentru structuri panouri fotov…
1.49:1
#000000
on
#172958
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sisteme de structuri panouri fotovoltaic…
1.49:1
#000000
on
#172958
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Lucrări recente
1.49:1
#000000
on
#172958
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Avantajele sistemelor Fortza Solar
1.49:1
#000000
on
#172958
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Târguri și expoziții
1.49:1
#000000
on
#172958
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Structuri panouri fotovoltaice.
1.49:1
#000000
on
#172958
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Soluții durabile la prețuri corecte.
1.49:1
#000000
on
#172958
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Noutăți și resurse
1.49:1
#000000
on
#172958
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Sistem Fotovoltaic Smart Dual
1.49:1
#000000
on
#172958
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Structură EST-VEST
1.49:1
#000000
on
#172958
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Sistem Fotovoltaic cu Balast
1.49:1
#000000
on
#172958
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Structură Smart cu Țăruși
1.49:1
#000000
on
#172958
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Misiunea noastră este să susținem pe …
1.49:1
#000000
on
#172958
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Coca Cola Timisoara – 1 MW
1.49:1
#000000
on
#172958
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Parc Fotovoltaic MAX BAU – 500 KW
1.49:1
#000000
on
#172958
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Proiect structuri fotovoltaice Șușani …
1.49:1
#000000
on
#172958
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Preluare proiect fotovoltaic Zărnești …
1.49:1
#000000
on
#172958
needs 3.0:1 (large text)
19px · bottom of viewport
h3 TG.Trotuș. 3, MW Structura Effe due pro…
1.49:1
#000000
on
#172958
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Proiect panouri fotovoltaice Arad 250 KW
1.49:1
#000000
on
#172958
needs 3.0:1 (large text)
19px · bottom of viewport

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)
ElementRatioRequiredFGBGResult
h1 Producători de stru…2.63:13.0:1
#000000
#3F5078
Fail
h2 Accesorii pentru str…1.49:13.0:1
#000000
#172958
Fail
h2 Sisteme de structuri…1.49:13.0:1
#000000
#172958
Fail
h2 Lucrări recente1.49:13.0:1
#000000
#172958
Fail
h2 Avantajele sistemelo…1.49:13.0:1
#000000
#172958
Fail
h2 Târguri și expozi…1.49:13.0:1
#000000
#172958
Fail
h2 Structuri panouri fo…1.49:13.0:1
#000000
#172958
Fail
h2 Soluții durabile la…1.49:13.0:1
#000000
#172958
Fail
h2 Noutăți și resurs…1.49:13.0:1
#000000
#172958
Fail
h3 Sistem Fotovoltaic S…1.49:13.0:1
#000000
#172958
Fail
h3 Structură EST-VEST1.49:13.0:1
#000000
#172958
Fail
h3 Sistem Fotovoltaic c…1.49:13.0:1
#000000
#172958
Fail
h3 Structură Smart cu …1.49:13.0:1
#000000
#172958
Fail
h3 Misiunea noastră es…1.49:13.0:1
#000000
#172958
Fail
h3 Coca Cola Timisoara …1.49:13.0:1
#000000
#172958
Fail
h3 Parc Fotovoltaic MAX…1.49:13.0:1
#000000
#172958
Fail
h3 Proiect structuri fo…1.49:13.0:1
#000000
#172958
Fail
h3 Preluare proiect fot…1.49:13.0:1
#000000
#172958
Fail
h3 TG.Trotuș. 3, MW St…1.49:13.0:1
#000000
#172958
Fail
h3 Proiect panouri foto…1.49:13.0:1
#000000
#172958
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+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
6 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: 6 all-caps heading(s)
A+
Alt Text Quality
All 36 images OK
PASS
All 36 images OK
Info::
8 decorative image(s) correctly marked
Info::
28 image(s) with good alt text
36 images 28 good alt text 8 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Form Input Types
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Mobile Keyboard & Autofill
No form controls -- mobile keyboard check is N/A
PASS
No form controls -- mobile keyboard check is N/A
Info::
No form controls on this page
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+
Tabindex Anti-Patterns
15 explicit tabindex attribute(s) checked, no anti-patterns
PASS
15 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
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+
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 91/100 — 3 failing, 25 passed
PASS
91

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
Detalii div.elementskit-post-image-card > div.elementskit-post-body > div.btn-wraper > a.elementskit-btn
Detalii div.elementskit-post-image-card > div.elementskit-post-body > div.btn-wraper > a.elementskit-btn
Detalii div.elementskit-post-image-card > div.elementskit-post-body > div.btn-wraper > a.elementskit-btn

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
Sistem Fotovoltaic Smart 1 div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h4.elementor-heading-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-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer
div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer
div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer
div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer
div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer
div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer
div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer
div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer
div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer
div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer
div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer
div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer
div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer
div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer
div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer div.elementor-element > div.elementor-widget-container > div.elementor-flip-box > a.elementor-flip-box__layer
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a

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.

○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
●`[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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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
○`<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
○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.
○Skip links are focusable.
○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
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○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