Skip to content
https://conengagroup.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
79
GRADE
C
FIX
5
REVIEW
6
PASS
13
INFO
0
Checks
24
13 PASS 6 REVIEW 5 FIX
D
Heading Hierarchy
Action
27 headings, 2 skip(s)
FIX
27 headings, 2 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H6 (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.
  • H2 Science meets hands-on expertise – for the future of your technical systems
  • H2 What we do
  • H2 What we do
  • H2 News
  • H2 Our services
  • H6 Potential studies skipped
  • H6 Risk analysis, HAZOP
  • H6 Energy park management
  • H6 Fluidized-bed technology
  • H6 SNCR-Plant with AI Technologie
  • H6 Laser scanning
  • H6 CO₂ separation / carbon capture
  • H6 Fire position detection
  • H6 BCS® Biomass Control Solution
  • H6 EPOC® Energy Production Optimization Control
  • H2 Testimonials
  • H2 Testimonials
  • H2 CONENGA Blog
  • H2 CONENGA Blog
  • H3 Read the latest CONENGA blog posts here:
  • H5 TSA Technology: Research Findings skipped
  • H5 Measurement Campaigns: A Practical Example
  • H5 Data evaluation
  • H5 Potential studies – more than just analyses
  • H2 Press
  • H2 Press
  • H3 Unsere Kunden

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

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

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

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::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Tap Target Adequacy
Action
8 tap target(s) too small or too close together
REVIEW
8 tap target(s) too small or too close together
Warning::
8 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
B
Mobile-Readable Font Sizes
98% of visible text renders at >= 12 CSS px (1 below threshold)
REVIEW
98% of visible text renders at >= 12 CSS px (1 below threshold)
Info::
1 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 ("COPYRIGHT 2026 CONENGA Group GmbH").
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, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA
h3 Read the latest CONENGA blog posts here:
2.82:1
#000000
on
#515561
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Unsere Kunden
2.82:1
#000000
on
#515561
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h3 Read the latest CONE…2.82:13.0:1
#000000
#515561
Fail
h3 Unsere Kunden2.82:13.0:1
#000000
#515561
Fail
title CONENGA: Solutions f…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to content21.00:14.5:1
#000000
#FFFFFF
Pass
span Search for:21.00:14.5:1
#000000
#FFFFFF
Pass
span Services21.00:14.5:1
#000000
#FFFFFF
Pass
span Control engineering20.29:14.5:1
#000000
#FBFBFB
Pass
span Advanced Process Con…20.47:14.5:1
#000000
#FCFCFC
Pass
span Artificial Intellige…21.00:14.5:1
#000000
#FFFFFF
Pass
span Simulations10.24:14.5:1
#000000
#B5B5B5
Pass
span Dynamic simulation10.24:14.5:1
#000000
#B5B5B5
Pass
span Softsensor10.24:14.5:1
#000000
#B5B5B5
Pass
span Fire power control10.24:14.5:1
#000000
#B5B5B5
Pass
span Plant Balance Soluti…10.24:14.5:1
#000000
#B5B5B5
Pass
span Deployed controller …10.24:14.5:1
#000000
#B5B5B5
Pass
span Process engineering10.24:14.5:1
#000000
#B5B5B5
Pass
span Waste incineration p…10.24:14.5:1
#000000
#B5B5B5
Pass
span Plant Balancing10.24:14.5:1
#000000
#B5B5B5
Pass
span Firing technologies10.24:14.5:1
#000000
#B5B5B5
Pass
span Flexibilization of c…10.24:14.5:1
#000000
#B5B5B5
Pass

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 88/100 — 4 failing, 24 passed
REVIEW
88

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
Explore all our service areas and products: div.fusion-layout-column > div.fusion-column-wrapper > div.fusion-text > p
CONENGA works on its own initiative in close coordination with the plant person… div.awb-quote-content > p > span.TextRun > span.NormalTextRun
high acceptance of the optimized control of the EPOC® Boiler. div.awb-quote-content > p > span.TextRun > span.NormalTextRun
Maik Hawrylak div.review > div.author > span.company-name > strong
Head of Energy Supply, Egger Wismar div.review > div.author > span.company-name > span
Read the latest CONENGA blog posts here: div.fusion-layout-column > div.fusion-column-wrapper > div.fusion-text > h3.fusion-responsive-typography-calculated
Unsere Kunden div.fusion-column-content-centered > div.fusion-column-content > div.fusion-title > h3.fusion-title-heading
Auhofstraße 1/10, 1130 Vienna div.textwidget > ul.fusion-checklist > li.fusion-li-item > div.fusion-li-item-content
office@conengagroup.com ul.fusion-checklist > li.fusion-li-item > div.fusion-li-item-content > a
+43 1 23 500 32 div.textwidget > ul.fusion-checklist > li.fusion-li-item > div.fusion-li-item-content
+43 1 23 500 32–99 div.textwidget > ul.fusion-checklist > li.fusion-li-item > div.fusion-li-item-content
>  Imprint div.textwidget > ul > li > a
>  Privacy Policy div.textwidget > ul > li > a
COPYRIGHT 2026 CONENGA Group GmbH div.fusion-row > div.fusion-copyright-content > div.fusion-copyright-notice > div

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
Potential studies div.col > div.heading > a.heading-link > h6.content-box-heading
TSA Technology: Research Findings li.fusion-layout-column > div.fusion-column-wrapper > div.fusion-title > h5.fusion-title-heading

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.fusion-builder-row > div.fusion-layout-column > span.fusion-column-inner-bg > a.fusion-column-anchor div.fusion-builder-row > div.fusion-layout-column > span.fusion-column-inner-bg > a.fusion-column-anchor
div.swiper-slide > div.fusion-carousel-item-wrapper > div.fusion-image-wrapper > a div.swiper-slide > div.fusion-carousel-item-wrapper > div.fusion-image-wrapper > a
div.swiper-slide > div.fusion-carousel-item-wrapper > div.fusion-image-wrapper > a div.swiper-slide > div.fusion-carousel-item-wrapper > div.fusion-image-wrapper > a
div.swiper-slide > div.fusion-carousel-item-wrapper > div.fusion-image-wrapper > a div.swiper-slide > div.fusion-carousel-item-wrapper > div.fusion-image-wrapper > a
div.swiper-slide > div.fusion-carousel-item-wrapper > div.fusion-image-wrapper > a div.swiper-slide > div.fusion-carousel-item-wrapper > div.fusion-image-wrapper > a
div.swiper-slide > div.fusion-carousel-item-wrapper > div.fusion-image-wrapper > a div.swiper-slide > div.fusion-carousel-item-wrapper > div.fusion-image-wrapper > a
div.swiper-slide > div.fusion-carousel-item-wrapper > div.fusion-image-wrapper > a div.swiper-slide > div.fusion-carousel-item-wrapper > div.fusion-image-wrapper > 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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Testimonial Pagination div.fusion-column-wrapper > div.fusion-testimonials > div#fusion-testimonials-1 > a.activeSlide
Testimonial Pagination div.fusion-column-wrapper > div.fusion-testimonials > div#fusion-testimonials-1 > a
Testimonial Pagination div.fusion-column-wrapper > div.fusion-testimonials > div#fusion-testimonials-1 > a
Testimonial Pagination div.fusion-column-wrapper > div.fusion-testimonials > div#fusion-testimonials-1 > a
Testimonial Pagination div.fusion-column-wrapper > div.fusion-testimonials > div#fusion-testimonials-1 > a
Testimonial Pagination div.fusion-column-wrapper > div.fusion-testimonials > div#fusion-testimonials-1 > a
>  Imprint div.textwidget > ul > li > a
>  Privacy Policy div.textwidget > ul > li > a

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-*]` 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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●`[lang]` attributes have a valid value
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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.
○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.
○`<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
Landmark Structure
8 landmarks
PASS
8 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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 Menu" MAIN CONTENTINFO footer

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

A+
Heading Text Quality
All 27 heading(s) have substantive, well-formed text
PASS
All 27 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 110 images OK
PASS
All 110 images OK
Info::
6 decorative image(s) correctly marked
Info::
104 image(s) with good alt text
110 images 104 good alt text 6 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
ssearchSearch for:none
inputsubmitSearcharia-label
A+
Form Input Types
2 form control(s) checked, no type mismatches
PASS
2 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 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+
Tabindex Anti-Patterns
0 positive, 1 -1-on-focusable
PASS
0 positive, 1 -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.)
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Seite wurde nicht gefunden. - CONENGA Group ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
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