Skip to content
https://kriesi.at

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
D
Landmark Structure
Action
10 landmarks
FIX
10 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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.
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN (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

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

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

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
No navigation patterns
FIX
No navigation patterns
Info::
2 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
12 headings
REVIEW
12 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 We build EnfoldThe last WordPress theme you will ever need
  • H3 00+
  • H3 000,000
  • H3 00 / 0
  • H2 Enfold – a WordPress Theme that makes your life easier
  • H2 The Basics – what you get with Enfold
  • H2 Some of our most popular Demos
  • H3 Enfold Shop (e-Commerce)
  • H3 Enfold Modern (Multi Purpose Theme)
  • H3 Enfold Classic (Multi Purpose Theme)
  • H2 Stay updated on new theme releases. Subscribe to our Newsletter!
  • H2 What our Customers say about us

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

B
Form Accessibility
2 of 4 controls have issues
REVIEW
2 of 4 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <input type="text" name="avia_avia_username_1" id="avia_avia_username_1">
Info::
2 control(s) properly labeled
4 controls
2 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#avia_1_1textYour Name *for/id
#avia_0_1textYour Email *for/id
inputsubmit(none)none
#avia_avia_username_1text(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="submit">; <input type="text" name="avia_avia_username_1" id="avia_avia_username_1">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 5 fail WCAG AA
REVIEW

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

15 pass 5 fail WCAG AA 1 pass AA only
span Home
1.77:1
#000000
on
#552D17
needs 4.5:1 (normal text)
16px · top of page (header area)
span Demos
1.49:1
#000000
on
#472111
needs 4.5:1 (normal text)
16px · above the fold
span Blog
1.60:1
#000000
on
#3B2E21
needs 4.5:1 (normal text)
16px · above the fold
span About
1.17:1
#000000
on
#1B1611
needs 4.5:1 (normal text)
16px · above the fold
span Contact
1.02:1
#000000
on
#040303
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 We build21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The last WordPress t…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Enfold – a WordPre…18.93:13.0:1
#000000
#F3F3F3
Pass
h2 – what you get wit…18.93:13.0:1
#000000
#F3F3F3
Pass
h2 Some of our18.93:13.0:1
#000000
#F3F3F3
Pass
h2 Demos18.93:13.0:1
#000000
#F3F3F3
Pass
h2 Stay updated on new …18.93:13.0:1
#000000
#F3F3F3
Pass
h2 Subscribe to18.93:13.0:1
#000000
#F3F3F3
Pass
h2 What our Customers s…18.93:13.0:1
#000000
#F3F3F3
Pass
h3 Enfold Modern18.93:13.0:1
#000000
#F3F3F3
Pass
title Home - Kriesi.at - P…21.00:14.5:1
#000000
#FFFFFF
Pass
strong Kriesi.at21.00:13.0:1
#000000
#FFFFFF
Pass
strong Premium Themes21.00:13.0:1
#000000
#FFFFFF
Pass
span Home1.77:14.5:1
#000000
#552D17
Fail
span Demos1.49:14.5:1
#000000
#472111
Fail
span Blog1.60:14.5:1
#000000
#3B2E21
Fail
span About1.17:14.5:1
#000000
#1B1611
Fail
span Contact1.02:14.5:1
#000000
#040303
Fail
span Support5.88:14.5:1
#000000
#8E8682
Pass
span Search19.43:14.5:1
#000000
#F6F6F6
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.

A+
Alt Text Quality
All 11 images OK
PASS
All 11 images OK
Info::
10 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
11 images 1 good alt text 10 decorative
All images have appropriate alt text.
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 Scroll to top ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A
Lighthouse Accessibility Audits
Score 92/100 — 3 failing, 27 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
We build more than just Themes. We build User Experience for both, you and your… div.entry-content-wrapper > section.av_textblock_section > div.avia_textblock > p
6 principles section.av_textblock_section > div.avia_textblock > p > strong
Sometimes its best to let your work speak for you. Here are some of our most po… div.entry-content-wrapper > section.av_textblock_section > div.avia_textblock > p
(e-Commerce) header.entry-content-header > h3.grid-entry-title > a > span.portfolio-title-add
(Multi Purpose Theme) header.entry-content-header > h3.grid-entry-title > a > span.portfolio-title-add
View all Demos div.entry-content-wrapper > div.avia-button-wrap > a.avia-color-theme-color > span.avia_iconbox_title
OUR NEWSLETTER div.flex_column > div.av-special-heading > h2.av-special-heading-tag > strong
(We keep your Email address private and we do not spam – promised) div.flex_column > div.av-special-heading > div.av_custom_color > p
Fashion Label div.avia-testimonial_inner > div.avia-testimonial-meta > div.avia-testimonial-meta-mini > span.avia-testimonial-subtitle
Kapitan the Brand div.avia-testimonial_inner > div.avia-testimonial-meta > div.avia-testimonial-meta-mini > a.avia-testimonial-link
Web Designer div.avia-testimonial_inner > div.avia-testimonial-meta > div.avia-testimonial-meta-mini > span.avia-testimonial-subtitle
Philippfischer.at div.avia-testimonial_inner > div.avia-testimonial-meta > div.avia-testimonial-meta-mini > a.avia-testimonial-link
Owner div.avia-testimonial_inner > div.avia-testimonial-meta > div.avia-testimonial-meta-mini > span.avia-testimonial-subtitle
IrisEhrlich.at div.avia-testimonial_inner > div.avia-testimonial-meta > div.avia-testimonial-meta-mini > a.avia-testimonial-link
Video Productions div.avia-testimonial_inner > div.avia-testimonial-meta > div.avia-testimonial-meta-mini > span.avia-testimonial-subtitle
Paul Schuch Video div.avia-testimonial_inner > div.avia-testimonial-meta > div.avia-testimonial-meta-mini > a.avia-testimonial-link

These are opportunities to improve the legibility of your content.

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
Home div.avia3-menu > ul#avia3-menu > li#menu-item-1605 > a
Blog div.avia3-menu > ul#avia3-menu > li#menu-item-1606 > a
Newsletter div.avia3-menu > ul#avia3-menu > li#menu-item-3317 > a
Legal Information div.avia3-menu > ul#avia3-menu > li#menu-item-1607 > a
Privacy Policy div.avia3-menu > ul#avia3-menu > li#menu-item-3726 > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.html_stretched html.html_stretched

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
●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
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●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.
●`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
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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 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
○Buttons have an accessible name
○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 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.
○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
○`<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.
○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