Skip to content
https://www.voestalpine.com/welding/global-en/

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
78
GRADE
C
FIX
5
REVIEW
8
PASS
11
INFO
0
Checks
24
11 PASS 8 REVIEW 5 FIX
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
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ffffff
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 ModePartial Dark Mode
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.
B
Landmark Structure
6 landmarks
REVIEW
6 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Warning::
Skip link target(s) don't exist on page: #main
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 CONTENTINFO footer

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

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
Heading Hierarchy
20 headings
REVIEW
20 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H3 We need your consent to load the JW Player service!
  • H3 We need your consent to load the JW Player service!
  • H3 We need your consent to load the JW Player service!
  • H3 We need your consent to load the JW Player service!
  • H2 The Best for the Best - Our Product Portfolio
  • H3 We need your consent to load the JW Player service!
  • H2 The new CORE TIG is here.
  • H2 Our extensive High-Quality Portfolio is supported by three specialized Brands
  • H3 (empty)
  • H2 Discover our Latest News
  • H2 Martin Peruzzi elected Vice President of the European Welding Association
  • H2 Introducing EVOLUTION V80 Air - Welding helmets that perfectly match your needs
  • H2 100 Years Böhler Welding:Be part of our jouney and Lasting Connections
  • H2 Social Media News
  • H3 Contact
  • H3 Locations
  • H3 Distributor Finder
  • H4 voestalpine Böhler Welding
  • H4 Links
  • H4 voestalpine Group

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

B
Iframe Accessibility
2/2 iframe(s) missing title; 0 placeholder(s)
REVIEW
2/2 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://my.walls.io/voestalpine-boehler-welding")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
C
Tap Target Adequacy
Action
6 tap target(s) too small or too close together
REVIEW
6 tap target(s) too small or too close together
Warning::
6 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
404 Error Page
HTTP 404, custom page
REVIEW
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 - voestalpine ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
14 icon(s) detected
REVIEW
14 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, 4 fail WCAG AA
REVIEW

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

16 pass 4 fail WCAG AA
title voestalpine Böhler Welding - voestalpin…
4.24:1
#000000
on
#707070
needs 4.5:1 (normal text)
16px · top of page (header area)
span Drücken Sie Alt+1 für den Bildschirmle…
4.24:1
#000000
on
#707070
needs 4.5:1 (normal text)
16px · top of page (header area)
a Leitfaden für barrierefreie Bildschirml…
4.06:1
#000000
on
#6D6D6D
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to main content
3.94:1
#000000
on
#6B6B6B
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 The Best for the Bes…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our extensive High-Q…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Discover our Latest …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Martin Peruzzi elect…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Introducing EVOLUTIO…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 100 Years Böhler We…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Be part of our joune…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Social Media News21.00:13.0:1
#000000
#FFFFFF
Pass
h3 We need your consent…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 We need your consent…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 We need your consent…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 We need your consent…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 We need your consent…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Contact21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Locations21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Distributor Finder21.00:13.0:1
#000000
#FFFFFF
Pass
title voestalpine Böhler …4.24:14.5:1
#000000
#707070
Fail
span Drücken Sie Alt+1 f…4.24:14.5:1
#000000
#707070
Fail
a Leitfaden für barri…4.06:14.5:1
#000000
#6D6D6D
Fail
a Skip to main content3.94:14.5:1
#000000
#6B6B6B
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.

C
Lighthouse Accessibility Audits
Action
Score 78/100 — 7 failing, 25 passed
REVIEW
78

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#centercontainer > article > div.tilesSlider > button.tiles-toggle div#centercontainer > article > div.tilesSlider > button.tiles-toggle

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section > div.sdp-wrapper > div#sdp-874b47fc-122a-11f1-8566-0260681a7a34 > iframe.deferred section > div.sdp-wrapper > div#sdp-874b47fc-122a-11f1-8566-0260681a7a34 > iframe.deferred

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
nav.stickyBar__nav > ul.stickyBar__itemlist > li.stickyBar__item > a.stickyBar__itemContent nav.stickyBar__nav > ul.stickyBar__itemlist > li.stickyBar__item > a.stickyBar__itemContent
nav.stickyBar__nav > ul.stickyBar__itemlist > li.stickyBar__item > a.stickyBar__itemContent nav.stickyBar__nav > ul.stickyBar__itemlist > li.stickyBar__item > a.stickyBar__itemContent
nav.stickyBar__nav > ul.stickyBar__itemlist > li.stickyBar__item > a.stickyBar__itemContent nav.stickyBar__nav > ul.stickyBar__itemlist > li.stickyBar__item > a.stickyBar__itemContent

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.

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
100 YEARS BÖHLER WELDING - ANNIVERSARY BUNDLE div.fullstage__themeTile > section.fullstage__themeTile__content > p.tile-headline > span
Our promotional bundle combines our powerful TERRA NX 400 PME with the Guardian… article.slide > div.fullstage__themeTile > section.fullstage__themeTile__content > p
FIND A DISTRIBUTOR article.slide > div.fullstage__themeTile > section.fullstage__themeTile__content > a.btn
Welding and Brazing Consumables div.col-xxs-60 > div.inner-container > section > a.btn
Welding Equipment div.col-xxs-60 > div.inner-container > section > a.btn
PPE & Accessories div.col-xxs-60 > div.inner-container > section > a.btn
More Info & Settings div#uc1792155323285 > div.uc-embedding-wrapper > div.uc-embedding-buttons > button.uc-embedding-more-info
Accept Cookies & continue div#uc1792155323285 > div.uc-embedding-wrapper > div.uc-embedding-buttons > button.uc-embedding-accept
Discover more div.col-xxs-60 > div.inner-container > section > a.btn
Read more div.inner-container > section > div.content > a.btn
Read more div.inner-container > section > div.content > a.btn
Read more div.inner-container > section > div.content > a.btn
Support & Service section > ul.plain > li > a
Career section > ul.plain > li > a
Terms & Conditions section > ul.plain > li > a
Code of Conduct section > ul.plain > li > a
Compliance section > ul.plain > li > a
Data Protection & Privacy section > ul.plain > li > a
Cookie settings section > ul.plain > li > a
Legal Notice div.row > div.col-xs-60 > span.imprint > a
Accept only essential cookies div.sc-bmzYkS > div.sc-dtBdUo > div.sc-iHGNWf > button.sc-gsFSXq
Save settings div.sc-bmzYkS > div.sc-dtBdUo > div.sc-iHGNWf > button.sc-gsFSXq

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Legal Notice div.row > div.col-xs-60 > span.imprint > a

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
Links div.row > div.col-xs-30 > section > h4.footer-headline

These are opportunities to improve keyboard navigation in your application.

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
Career section > ul.plain > li > a
Terms & Conditions section > ul.plain > li > a
Code of Conduct section > ul.plain > li > a
Compliance section > ul.plain > li > a
Data Protection & Privacy section > ul.plain > li > a
Cookie settings section > ul.plain > 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
●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.
●Select elements have associated label elements.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●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
○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
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○Uses ARIA roles only on compatible elements
○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.
A+
Heading Text Quality
All 20 heading(s) have substantive, well-formed text
PASS
All 20 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 22 images OK
PASS
All 22 images OK
Info::
1 decorative image(s) correctly marked
Info::
21 image(s) with good alt text
22 images 21 good alt text 1 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q" id="query">
Info::
1 control(s) properly labeled
2 controls
1 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#languageSwitchselectLanguagefor/id
#querytext(Search)placeholder only

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

<input type="text" name="q" id="query">

Why this matters

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

Learn more ▾

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

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "q" should use type="search" (currently type="text")
Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
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"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
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+
Mobile-Readable Font Sizes
All 20 visible text node(s) render at >= 12 CSS pixels
PASS
All 20 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::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback