Referer:
Issues:
37 Errors 8 Probable Errors 12 Warnings
DOCTYPE:
HTML5
Summary report > Page report
37 Errors
- 25 WCAG2 A
- 8 E956 - SC 4.1.2: The value of the 'role' attribute is not valid for this element. Elements can only have specific roles as defined by the ARIA specification. So, you may be better off using a more appropriate element for this role. See ARIA in HTML.
1 The value of the 'role' attribute is not valid for this element <img alt="" role="link" loading="lazy" width="0" height="0" decoding="async" data-nimg="1" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_mail.svg"/> 1 The value of the 'role' attribute is not valid for this element <img alt="" role="link" loading="lazy" width="0" height="0" decoding="async" data-nimg="1" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_facetime.svg"/> 1 The value of the 'role' attribute is not valid for this element <img alt="" role="link" loading="lazy" width="0" height="0" decoding="async" data-nimg="1" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_shop.svg"/> 71 The value of the 'role' attribute is not valid for this element <img alt="" role="link" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="Socials_logo__PDQjE" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_instagram.svg"/> 71 The value of the 'role' attribute is not valid for this element <img alt="" role="link" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="Socials_logo__PDQjE" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_facebook.svg"/> 71 The value of the 'role' attribute is not valid for this element <img alt="" role="link" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="Socials_logo__PDQjE" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_linkedin.svg"/> 71 The value of the 'role' attribute is not valid for this element <img alt="" role="link" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="Socials_logo__PDQjE" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_x-twitter.svg"/> 71 The value of the 'role' attribute is not valid for this element <img alt="" role="link" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="Socials_logo__PDQjE" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/04/lh_youtube.svg"/> - 1 E8661 - SC 1.1.1/1.3.1/3.3.2/4.1.2: User interface controls without a label should have an accessible name. Use the 'aria-label', 'aria-labelledby', or where appropriate 'value', attributes to label controls when the visual design cannot accommodate the label (for example, if there is no text on the screen that can be identified as a label) or where it might be confusing or not possible to use a label. User agents, including assisting technology, can use these attributes. See WCAG2 Failure F68.
1 User interface controls without a label should have an accessible name <button class="SearchInput_button__XVGZK"> - 7 E9081 - SC 2.5.3: The accessible name in 'aria-label' must contain the visible label text. The accessible name used by accessibility aids must contain the text displayed by the visible label. When choosing the text remember that both the name and the label may be read out aloud. See Understanding 2.5.3, and Accessibility API Mappings.
7 The accessible name in 'aria-label' must contain the visible label text: https://lanserhof.com <a aria-label="Visit lanserhof.com website" href="https://lanserhof.com"> 9 The accessible name in 'aria-label' must contain the visible label text: info.lans@lanserhof.com <a aria-label="Send email to Lanserhof Lans" href="mailto:info.lans@lanserhof.com"> 10 The accessible name in 'aria-label' must contain the visible label text: info.tegernsee@lanserhof.com <a aria-label="Send email to Lanserhof Tegernsee" href="mailto:info.tegernsee@lanserhof.com"> 11 The accessible name in 'aria-label' must contain the visible label text: info.sylt@lanserhof.com <a aria-label="Send email to Lanserhof Sylt" href="mailto:info.sylt@lanserhof.com"> 24 The accessible name in 'aria-label' must contain the visible label text: https://lanserhof.com <a aria-label="Visit lanserhof.com website" href="https://lanserhof.com"> 67 The accessible name in 'aria-label' must contain the visible label text: info@schlichtungsstelle-bgg.de <a aria-label="Send email to the arbitration office" href="mailto:info@schlichtungsstelle-bgg.de"> 68 The accessible name in 'aria-label' must contain the visible label text: www.schlichtungsstelle-bgg.de <a aria-label="Visit the arbitration office website" href="https://www.schlichtungsstelle-bgg.de"> - 8 E9542 - SC 4.1.2: Interactive elements are not allowed here. When using ARIA roles there are additional rules where interactive elements may appear. This error may also be caused by incorrectly nesting tags, missing end tags, or similar structural issues. So if it is not obvious what is wrong, fix any structural issues first. See ARIA in HTML.
1 Interactive elements are not allowed here <img alt="" role="link" loading="lazy" width="0" height="0" decoding="async" data-nimg="1" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_mail.svg"/> 1 Interactive elements are not allowed here <img alt="" role="link" loading="lazy" width="0" height="0" decoding="async" data-nimg="1" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_facetime.svg"/> 1 Interactive elements are not allowed here <img alt="" role="link" loading="lazy" width="0" height="0" decoding="async" data-nimg="1" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_shop.svg"/> 71 Interactive elements are not allowed here <img alt="" role="link" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="Socials_logo__PDQjE" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_instagram.svg"/> 71 Interactive elements are not allowed here <img alt="" role="link" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="Socials_logo__PDQjE" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_facebook.svg"/> 71 Interactive elements are not allowed here <img alt="" role="link" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="Socials_logo__PDQjE" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_linkedin.svg"/> 71 Interactive elements are not allowed here <img alt="" role="link" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="Socials_logo__PDQjE" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_x-twitter.svg"/> 71 Interactive elements are not allowed here <img alt="" role="link" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="Socials_logo__PDQjE" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/04/lh_youtube.svg"/> - 1 E9591 - SC 1.3.1: The value of the attribute must match an 'id' in the same document. Each of the ids listed for this aria attribute must match elements elsewhere in the document. See ARIA 1.3.
1 The value of 'aria-controls' must match an 'id' in the same document <button class="Hamburger_hamburger__6VuUc" aria-label="Opens and closes the main menu." aria-controls="navbar-main" aria-expanded="false">
- 8 E956 - SC 4.1.2: The value of the 'role' attribute is not valid for this element. Elements can only have specific roles as defined by the ARIA specification. So, you may be better off using a more appropriate element for this role. See ARIA in HTML.
- 2 WCAG2 AA
- 2 E913 - SC 2.4.6: Form control labels must be unique. Use unique labels so that users can distinguish between form controls on the same page when read out aloud. Alternatively, place them within different <fieldset> with unique <legend> labels, because the legend text is read out along with the label text. See WCAG2 Success Criterion 2.4.6.
1 The form control label 'en' is not unique <button class="Listbox_listbox-button___3oOv " id="headlessui-listbox-button-:Rqiv6:" type="button" aria-haspopup="listbox" aria-expanded="false" data-headlessui-state=""> 1 The form control label 'en' is not unique <button class="Listbox_listbox-button___3oOv " id="headlessui-listbox-button-:Rq7iv6:" type="button" aria-haspopup="listbox" aria-expanded="false" data-headlessui-state="">
- 2 E913 - SC 2.4.6: Form control labels must be unique. Use unique labels so that users can distinguish between form controls on the same page when read out aloud. Alternatively, place them within different <fieldset> with unique <legend> labels, because the legend text is read out along with the label text. See WCAG2 Success Criterion 2.4.6.
- 10 HTML
- 7 E622 - An attribute does not have a valid value. The HTML specification being tested against defines certain valid values for each attribute. Usually a list of valid values will be displayed when you see this message. Note that many values must be in lower case in XHTML, including the 'x' in numeric hex entity references. Also note that what values are allowed varies from standard to standard.
71 The 'id' attribute does not have a valid value: It does not contain a valid ID. It must contain at least one character and must not contain any space characters <section class="Section_section__oHlmj undefined has-grey-bg is-gapless-top-bottom section" id=""> 71 The 'id' attribute does not have a valid value: It does not contain a valid ID. It must contain at least one character and must not contain any space characters <section class="Section_section__oHlmj undefined has-grey-bg is-gapless-top-bottom section" id=""> 71 The 'id' attribute does not have a valid value: It does not contain a valid ID. It must contain at least one character and must not contain any space characters <section class="Section_section__oHlmj undefined has-grey-bg is-gapless-top-bottom section" id=""> 71 The 'id' attribute does not have a valid value: It does not contain a valid ID. It must contain at least one character and must not contain any space characters <section class="Section_section__oHlmj undefined has-grey-bg is-gapless-top-bottom section" id=""> 71 The 'id' attribute does not have a valid value: It does not contain a valid ID. It must contain at least one character and must not contain any space characters <section class="Section_section__oHlmj undefined has-grey-bg default section" id=""> 71 The 'id' attribute does not have a valid value: It does not contain a valid ID. It must contain at least one character and must not contain any space characters <section class="Section_section__oHlmj undefined has-grey-bg is-gapless-top-bottom section" id=""> 71 The 'id' attribute does not have a valid value: It does not contain a valid ID. It must contain at least one character and must not contain any space characters <section class="Section_section__oHlmj undefined has-grey-bg is-gapless-top-bottom section" id=""> - 2 E668 - Missing value for 'content' attribute. If either 'name', 'http-equiv', 'property' or 'itemprop' is specified, then the 'content' attribute must have a value.
1 Missing value for 'content' attribute <meta name="description"/> 1 Missing value for 'content' attribute <meta property="og:description"/> - 1 E6091 - A tag or some content is not allowed. There are strict rules as to what tags may be nested within others, as well as the order and number of tags allowed. This error may also be caused by incorrectly nesting tags, missing end tags, or similar structural issues. So if it is not obvious what is wrong, fix any structural issues first.
1 This tag or content is not allowed here. One of the following was expected: A phrasing content element except for interactive content. See the HTML Living Standard. <div class="Hamburger_hamburger-icon__Rk6CS" style="opacity:0;will-change:opacity,transform;transform:scale(0.9)">
- 7 E622 - An attribute does not have a valid value. The HTML specification being tested against defines certain valid values for each attribute. Usually a list of valid values will be displayed when you see this message. Note that many values must be in lower case in XHTML, including the 'x' in numeric hex entity references. Also note that what values are allowed varies from standard to standard.
8 Probable Errors
- 8 WCAG2 A
- 8 P871 - SC 1.1.1/2.4.4/2.4.9: Link text is missing. Describe the purpose of a link by providing descriptive text as the content of the element, or provide an 'aria-label' or 'aria-labelledby' attribute. The description lets a user distinguish this link from other links in the Web page and helps the user determine whether to follow the link. The URL of the destination is generally not sufficiently descriptive. See WCAG2 HTML Technique H30.
1 Link text is missing <img alt="" role="link" loading="lazy" width="0" height="0" decoding="async" data-nimg="1" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_mail.svg"/> 1 Link text is missing <img alt="" role="link" loading="lazy" width="0" height="0" decoding="async" data-nimg="1" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_facetime.svg"/> 1 Link text is missing <img alt="" role="link" loading="lazy" width="0" height="0" decoding="async" data-nimg="1" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_shop.svg"/> 71 Link text is missing <img alt="" role="link" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="Socials_logo__PDQjE" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_instagram.svg"/> 71 Link text is missing <img alt="" role="link" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="Socials_logo__PDQjE" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_facebook.svg"/> 71 Link text is missing <img alt="" role="link" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="Socials_logo__PDQjE" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_linkedin.svg"/> 71 Link text is missing <img alt="" role="link" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="Socials_logo__PDQjE" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_x-twitter.svg"/> 71 Link text is missing <img alt="" role="link" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="Socials_logo__PDQjE" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/04/lh_youtube.svg"/>
- 8 P871 - SC 1.1.1/2.4.4/2.4.9: Link text is missing. Describe the purpose of a link by providing descriptive text as the content of the element, or provide an 'aria-label' or 'aria-labelledby' attribute. The description lets a user distinguish this link from other links in the Web page and helps the user determine whether to follow the link. The URL of the destination is generally not sufficiently descriptive. See WCAG2 HTML Technique H30.
12 Warnings
- 10 WCAG2 A
- 5 W868 - SC 2.4.4: Different adjacent links with same link text. If you have adjacent links to different places, but with the same link text (when read aloud), it can be confusing to the user. So, you should either change the link text or add a unique 'aria-label' or 'aria-labelledby' attribute to each link. See Understanding 2.4.4.
71 Different adjacent links with the same link text 'socials-link' <a class="social" aria-label="socials-link" rel="noopener noreferrer" target="_blank" id="social-0" href="https://www.instagram.com/lanserhof/"> 71 Different adjacent links with the same link text 'socials-link' <a class="social" aria-label="socials-link" rel="noopener noreferrer" target="_blank" id="social-1" href="https://www.facebook.com/LanserhofDE/"> 71 Different adjacent links with the same link text 'socials-link' <a class="social" aria-label="socials-link" rel="noopener noreferrer" target="_blank" id="social-2" href="https://www.linkedin.com/company/lanserhof-gmbh/"> 71 Different adjacent links with the same link text 'socials-link' <a class="social" aria-label="socials-link" rel="noopener noreferrer" target="_blank" id="social-3" href="https://twitter.com/lanserhof"> 71 Different adjacent links with the same link text 'socials-link' <a class="social" aria-label="socials-link" rel="noopener noreferrer" target="_blank" id="social-4" href="https://www.youtube.com/channel/UCvwF4uQmURR_iEZ-V1WZOrw"> - 1 W874 - SC 2.4.1: Add a skip navigation link as the first link on the page. If your document has structure then you should add a skip navigation link to make it easier for accessible users to get to the page's content. To ensure detection, skip navigation links should point to a <main> element, or an element with role='main'. See Understanding 2.4.1, and Skip Navigation.
- 1 W877 - SC 1.3.1: Distinguish between navigation groups using an ARIA label. When the <nav> element is employed more than once on a page, distinguish between the navigation groups by using an 'aria-label' or 'aria-labelledby' attribute. See WCAG2 HTML Technique H97.
1 Distinguish between navigation groups using an ARIA label <nav id="navbar" class="Navbar_navbar__W_ouQ navbar"> - 2 W885 - SC 1.1.1/2.4.4/2.4.9: Do not use the URL as link text. Describe the purpose of a link by providing descriptive text as the content of the <a> element. This description lets a user distinguish this link from other links in the Web page and helps the user determine whether to follow the link. The URL of the destination is generally not sufficiently descriptive. See WCAG2 HTML Technique H30.
7 Do not use the URL as link text <a aria-label="Visit lanserhof.com website" href="https://lanserhof.com"> 24 Do not use the URL as link text <a aria-label="Visit lanserhof.com website" href="https://lanserhof.com"> - 1 W891 - SC 4.1.2: Avoid using fallback accessible names created from 'placeholder'. An accessible name generated from 'placeholder' typically yields a low quality accessible name, which may not always be supported. Instead use the recommended way of setting the accessible name for this element. See Avoid Fallback, and Accessible Name Computation.
1 Avoid using fallback accessible names created from 'placeholder' <input type="text" name="searchbar" placeholder="Search term" autoComplete="off"/>
- 5 W868 - SC 2.4.4: Different adjacent links with same link text. If you have adjacent links to different places, but with the same link text (when read aloud), it can be confusing to the user. So, you should either change the link text or add a unique 'aria-label' or 'aria-labelledby' attribute to each link. See Understanding 2.4.4.
- 2 HTML
- 2 W619 - Unrecognised value for the 'name' attribute. The 'name' attribute in the <meta> element is restricted to values documented in the HTML5 specification with extensions in the WHATWG Wiki. Note that Lanserhof will not recognise changes to the wiki after its release date. So, you will have to wait until the next release of Lanserhof before new names are recognised, or (Pro version only) use the 'Edit meta names' option to add them yourself. See Meta Extensions.
1 Unrecognised value for the 'name' attribute <meta name="twitter_card" content="summary_large_image"/> 1 Unrecognised value for the 'name' attribute <meta name="next-head-count" content="20"/>
- 2 W619 - Unrecognised value for the 'name' attribute. The 'name' attribute in the <meta> element is restricted to values documented in the HTML5 specification with extensions in the WHATWG Wiki. Note that Lanserhof will not recognise changes to the wiki after its release date. So, you will have to wait until the next release of Lanserhof before new names are recognised, or (Pro version only) use the 'Edit meta names' option to add them yourself. See Meta Extensions.
0 
W874WCAG2 A 2.4.1: Add a skip navigation link as the first link on the page
If your document has structure then you should add a skip navigation link to make it easier for accessible users to get to the page's content. To ensure detection, skip navigation links should point to a <main> element, or an element with role='main'. See Understanding 2.4.1, and Skip Navigation.
1 <!DOCTYPE html>
1 <html lang="en">
1 <head>
1 <noscript>
1 <link rel="stylesheet" href="/no-js.css"/>
1 </noscript>
1 <link rel="dns-prefetch" href="https://api.lanserhof.com/"/>
1 <link rel="preconnect" href="https://api.lanserhof.com/"/>
1 <link rel="preconnect" href="https://api.lanserhof.com/" crossorigin="anonymous"/>
1 <title>
1 Accessibility Information - Lanserhof
1 </title>
1 <meta charSet="UTF-8"/>
1 <meta name="viewport" content="width=device-width, initial-scale=1"/>
1 E668HTML: Missing value for 'content' attribute
If either 'name', 'http-equiv', 'property' or 'itemprop' is specified, then the 'content' attribute must have a value.
<meta name="description"/>
1 <meta name="robots" content="index,follow,max-image-preview:large,max-snippet:-1,max-video-preview:-1"/>
1 <meta property="og:locale" content="en_US"/>
1 <meta property="og:type" content="article"/>
1 <meta property="og:title" content="Accessibility Information - Lanserhof"/>
1 E668HTML: Missing value for 'content' attribute
If either 'name', 'http-equiv', 'property' or 'itemprop' is specified, then the 'content' attribute must have a value.
<meta property="og:description"/>
1 <meta property="og:url" content="https://lanserhof.com/en/accessibility-information/"/>
1 <meta property="og:site_name" content="Lanserhof"/>
1 <meta property="article:modified_time" content="2025-06-30T14:18:29+00:00"/>
1 <link rel="canonical" href="https://lanserhof.com/en/accessibility-information/"/>
1 W619HTML: Unrecognised value for the 'name' attribute
The 'name' attribute in the <meta> element is restricted to values documented in the HTML5 specification with extensions in the WHATWG Wiki. Note that Lanserhof will not recognise changes to the wiki after its release date. So, you will have to wait until the next release of Lanserhof before new names are recognised, or (Pro version only) use the 'Edit meta names' option to add them yourself. See Meta Extensions.
<meta name="twitter_card" content="summary_large_image"/>
1 <link rel="alternate" hrefLang="en" href="https://lanserhof.com/en/accessibility-information/"/>
1 <link rel="alternate" hrefLang="de" href="https://lanserhof.com/de/barrierefreiheit/"/>
1 W619HTML: Unrecognised value for the 'name' attribute
The 'name' attribute in the <meta> element is restricted to values documented in the HTML5 specification with extensions in the WHATWG Wiki. Note that Lanserhof will not recognise changes to the wiki after its release date. So, you will have to wait until the next release of Lanserhof before new names are recognised, or (Pro version only) use the 'Edit meta names' option to add them yourself. See Meta Extensions.
<meta name="next-head-count" content="20"/>
1 <link data-next-font="size-adjust" rel="preconnect" href="/" crossorigin="anonymous"/>
1 <link rel="preload" href="/_next/static/css/63adddc7b06b0ca3.css" as="style"/>
1 <link rel="stylesheet" href="/_next/static/css/63adddc7b06b0ca3.css" data-n-g=""/>
1 <link rel="preload" href="/_next/static/css/f9ed539b02f61655.css" as="style"/>
1 <link rel="stylesheet" href="/_next/static/css/f9ed539b02f61655.css" data-n-p=""/>
1 <link rel="preload" href="/_next/static/css/8c79a87a95d3bafd.css" as="style"/>
1 <link rel="stylesheet" href="/_next/static/css/8c79a87a95d3bafd.css" data-n-p=""/>
1 <link rel="preload" href="/_next/static/css/3966c38bb998cb33.css" as="style"/>
1 <link rel="stylesheet" href="/_next/static/css/3966c38bb998cb33.css" data-n-p=""/>
1 <link rel="preload" href="/_next/static/css/82e2f706c89777ab.css" as="style"/>
1 <link rel="stylesheet" href="/_next/static/css/82e2f706c89777ab.css"/>
1 <noscript data-n-css="">
1 </noscript>
1 <script defer="" nomodule="" src="/_next/static/chunks/polyfills-42372ed130431b0a.js">
1 </script>
1 <script defer="" src="/_next/static/chunks/6498.245093e2bf1e1fa4.js">
1 </script>
1 <script src="/_next/static/chunks/webpack-2d82902f679cb991.js" defer="">
1 </script>
1 <script src="/_next/static/chunks/framework-b0ec748c7a4c483a.js" defer="">
1 </script>
1 <script src="/_next/static/chunks/main-90d3efdc923b9c8a.js" defer="">
1 </script>
1 <script src="/_next/static/chunks/pages/_app-27196396652b94f5.js" defer="">
1 </script>
1 <script src="/_next/static/chunks/94726e6d-00317ae994f4f689.js" defer="">
1 </script>
1 <script src="/_next/static/chunks/26770aaf-787165cce7b5fafa.js" defer="">
1 </script>
1 <script src="/_next/static/chunks/5966-de81237dcf9e7535.js" defer="">
1 </script>
1 <script src="/_next/static/chunks/238-8fe680e2b82a3e83.js" defer="">
1 </script>
1 <script src="/_next/static/chunks/7247-a1aede3b2cd4cb41.js" defer="">
1 </script>
1 <script src="/_next/static/chunks/pages/%5B%5B...dynamicRoute%5D%5D-7a076e0de942c264.js" defer="">
1 </script>
1 <script src="/_next/static/eUoTcHg2TzlCbedKziswk/_buildManifest.js" defer="">
1 </script>
1 <script src="/_next/static/eUoTcHg2TzlCbedKziswk/_ssgManifest.js" defer="">
1 </script>
1 </head>
1 <body>
1 <div id="__next">
1 <header>
1 W877WCAG2 A 1.3.1: Distinguish between navigation groups using an ARIA label
When the <nav> element is employed more than once on a page, distinguish between the navigation groups by using an 'aria-label' or 'aria-labelledby' attribute. See WCAG2 HTML Technique H97.
<nav id="navbar" class="Navbar_navbar__W_ouQ navbar">
1 <a class="Navbar_navbar-text-wrapper__B93F_" target="_self" href="/en/">
1 <span>
1 <strong>
1 LANSERHOF.
1 </strong>
1 World’s Best Longevity Clinic
1 </span>
1 </a>
1 <div class="Navbar_language-wrapper__oyLyJ">
1 <div data-pos-top="false" data-color="black" class="Listbox_listbox__B2I19">
1 <div class="is-relative">
1 E913WCAG2 AA 2.4.6: The form control label 'en' is not unique
Use unique labels so that users can distinguish between form controls on the same page when read out aloud. Alternatively, place them within different <fieldset> with unique <legend> labels, because the legend text is read out along with the label text. See WCAG2 Success Criterion 2.4.6.
<button class="Listbox_listbox-button___3oOv " id="headlessui-listbox-button-:Rqiv6:" type="button" aria-haspopup="listbox" aria-expanded="false" data-headlessui-state="">
1 <span class="Listbox_listbox-selected__m1_C1">
1 en
1 </span>
1 <span class="Listbox_listbox-chevron__Y1n4I ">
1 <svg xmlns="http://www.w3.org/2000/svg" width="1em" height="1em" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" viewBox="0 0 24 24">
1 <path d="m6 9 6 6 6-6">
1 </path>
1 </svg>
1 </span>
1 </button>
1 </div>
1 </div>
1 </div>
1 <div class="QuickNavMenu_quick-nav-menu__NVGNn">
1 <div class="QuickNavMenu_language-toggle-wrapper__wpZ0b" style="opacity:0;will-change:opacity">
1 <div data-pos-top="true" data-color="black" class="Listbox_listbox__B2I19">
1 <div class="is-relative">
1 E913WCAG2 AA 2.4.6: The form control label 'en' is not unique
Use unique labels so that users can distinguish between form controls on the same page when read out aloud. Alternatively, place them within different <fieldset> with unique <legend> labels, because the legend text is read out along with the label text. See WCAG2 Success Criterion 2.4.6.
<button class="Listbox_listbox-button___3oOv " id="headlessui-listbox-button-:Rq7iv6:" type="button" aria-haspopup="listbox" aria-expanded="false" data-headlessui-state="">
1 <span class="Listbox_listbox-selected__m1_C1">
1 en
1 </span>
1 <span class="Listbox_listbox-chevron__Y1n4I ">
1 <svg xmlns="http://www.w3.org/2000/svg" width="1em" height="1em" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" viewBox="0 0 24 24">
1 <path d="m6 9 6 6 6-6">
1 </path>
1 </svg>
1 </span>
1 </button>
1 </div>
1 </div>
1 </div>
1 <div class="is-hidden-touch">
1 <div class="SearchInput_search-input-desktop__L4kYP">
1 <div class="SearchInput_icon__AakeJ">
1 <svg xmlns="http://www.w3.org/2000/svg" data-name="Ebene 1" viewBox="0 0 24 24" width="24" height="24">
1 <path d="M10.771 19.219a8.6 8.6 0 1 0-3.851-2.226l-4.986 4.986" style="fill:none;stroke:#2d2f38;stroke-linecap:round;stroke-linejoin:round;stroke-width:1.20000004768372px">
1 </path>
1 <path d="M18.827 10.906a5.868 5.868 0 0 1-11.736 0" style="fill:none;stroke:#2d2f38;stroke-linecap:round;stroke-linejoin:round;stroke-width:.699999988079071px">
1 </path>
1 </svg>
1 </div>
1 <span>
1 Search
1 </span>
1 </div>
1 <div class="SearchInput_search-input-desktop-input-wrapper__8Hj5W ">
1 W891WCAG2 A 4.1.2: Avoid using fallback accessible names created from 'placeholder'
An accessible name generated from 'placeholder' typically yields a low quality accessible name, which may not always be supported. Instead use the recommended way of setting the accessible name for this element. See Avoid Fallback, and Accessible Name Computation.
<input type="text" name="searchbar" placeholder="Search term" autoComplete="off"/>
1 E8661WCAG2 A 1.1.1/1.3.1/3.3.2/4.1.2: User interface controls without a label should have an accessible name
Use the 'aria-label', 'aria-labelledby', or where appropriate 'value', attributes to label controls when the visual design cannot accommodate the label (for example, if there is no text on the screen that can be identified as a label) or where it might be confusing or not possible to use a label. User agents, including assisting technology, can use these attributes. See WCAG2 Failure F68.
<button class="SearchInput_button__XVGZK">
1 <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 27.053 27.053" width="32" height="32">
1 <circle cx="13.527" cy="13.527" r="13.027" style="fill:none;stroke:#fff;stroke-miterlimit:10">
1 </circle>
1 <path d="m12.296 16.406 3.162-2.85-2.85-3.161" data-name="e" style="fill:none;stroke:#fff;stroke-linecap:round;stroke-miterlimit:10">
1 </path>
1 </svg>
1 </button>
1 </div>
1 </div>
1 <div data-is-hidden-mobile="false" class="QuickNavMenu_quick-nav-menu-item__1IRUs">
1 <a class="QuickNavMenu_quick-nav-menu-link__9HNcy" aria-label="MAIL" target="_blank" href="mailto:info.tegernsee@lanserhof.com">
1 <div data-is-last="false" class="QuickNavMenu_icon-wrapper__qRiwR">
1 E9542WCAG2 A 4.1.2: Interactive elements are not allowed here
When using ARIA roles there are additional rules where interactive elements may appear. This error may also be caused by incorrectly nesting tags, missing end tags, or similar structural issues. So if it is not obvious what is wrong, fix any structural issues first. See ARIA in HTML.
E956WCAG2 A 4.1.2: The value of the 'role' attribute is not valid for this element
Elements can only have specific roles as defined by the ARIA specification. So, you may be better off using a more appropriate element for this role. See ARIA in HTML.
P871WCAG2 A 1.1.1/2.4.4/2.4.9: Link text is missing
Describe the purpose of a link by providing descriptive text as the content of the element, or provide an 'aria-label' or 'aria-labelledby' attribute. The description lets a user distinguish this link from other links in the Web page and helps the user determine whether to follow the link. The URL of the destination is generally not sufficiently descriptive. See WCAG2 HTML Technique H30.
<img alt="" role="link" loading="lazy" width="0" height="0" decoding="async" data-nimg="1" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_mail.svg"/>
1 </div>
1 <span>
1 MAIL
1 </span>
1 </a>
1 </div>
1 <div data-is-hidden-mobile="false" class="QuickNavMenu_quick-nav-menu-item__1IRUs">
1 <a class="QuickNavMenu_quick-nav-menu-link__9HNcy" aria-label="CONTACT" target="_blank" href="/de/kontakt/">
1 <div data-is-last="false" class="QuickNavMenu_icon-wrapper__qRiwR">
1 E9542WCAG2 A 4.1.2: Interactive elements are not allowed here
When using ARIA roles there are additional rules where interactive elements may appear. This error may also be caused by incorrectly nesting tags, missing end tags, or similar structural issues. So if it is not obvious what is wrong, fix any structural issues first. See ARIA in HTML.
E956WCAG2 A 4.1.2: The value of the 'role' attribute is not valid for this element
Elements can only have specific roles as defined by the ARIA specification. So, you may be better off using a more appropriate element for this role. See ARIA in HTML.
P871WCAG2 A 1.1.1/2.4.4/2.4.9: Link text is missing
Describe the purpose of a link by providing descriptive text as the content of the element, or provide an 'aria-label' or 'aria-labelledby' attribute. The description lets a user distinguish this link from other links in the Web page and helps the user determine whether to follow the link. The URL of the destination is generally not sufficiently descriptive. See WCAG2 HTML Technique H30.
<img alt="" role="link" loading="lazy" width="0" height="0" decoding="async" data-nimg="1" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_facetime.svg"/>
1 </div>
1 <span>
1 CONTACT
1 </span>
1 </a>
1 </div>
1 <div data-is-hidden-mobile="true" class="QuickNavMenu_quick-nav-menu-item__1IRUs">
1 <a class="QuickNavMenu_quick-nav-menu-link__9HNcy" aria-label="SHOP" target="_blank" href="https://shop.lanserhof.com/">
1 <div data-is-last="true" class="QuickNavMenu_icon-wrapper__qRiwR">
1 E9542WCAG2 A 4.1.2: Interactive elements are not allowed here
When using ARIA roles there are additional rules where interactive elements may appear. This error may also be caused by incorrectly nesting tags, missing end tags, or similar structural issues. So if it is not obvious what is wrong, fix any structural issues first. See ARIA in HTML.
E956WCAG2 A 4.1.2: The value of the 'role' attribute is not valid for this element
Elements can only have specific roles as defined by the ARIA specification. So, you may be better off using a more appropriate element for this role. See ARIA in HTML.
P871WCAG2 A 1.1.1/2.4.4/2.4.9: Link text is missing
Describe the purpose of a link by providing descriptive text as the content of the element, or provide an 'aria-label' or 'aria-labelledby' attribute. The description lets a user distinguish this link from other links in the Web page and helps the user determine whether to follow the link. The URL of the destination is generally not sufficiently descriptive. See WCAG2 HTML Technique H30.
<img alt="" role="link" loading="lazy" width="0" height="0" decoding="async" data-nimg="1" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_shop.svg"/>
1 </div>
1 <span>
1 SHOP
1 </span>
1 </a>
1 </div>
1 E9591WCAG2 A 1.3.1: The value of 'aria-controls' must match an 'id' in the same document
Each of the ids listed for this aria attribute must match elements elsewhere in the document. See ARIA 1.3.
<button class="Hamburger_hamburger__6VuUc" aria-label="Opens and closes the main menu." aria-controls="navbar-main" aria-expanded="false">
1 <span class="Hamburger_menu-label__3wNgV" style="opacity:0;will-change:opacity,transform;transform:scale(0.9)">
1 MENU
1 </span>
1 E6091HTML: This tag or content is not allowed here. One of the following was expected: A phrasing content element except for interactive content
There are strict rules as to what tags may be nested within others, as well as the order and number of tags allowed. This error may also be caused by incorrectly nesting tags, missing end tags, or similar structural issues. So if it is not obvious what is wrong, fix any structural issues first. See the HTML Living Standard.
<div class="Hamburger_hamburger-icon__Rk6CS" style="opacity:0;will-change:opacity,transform;transform:scale(0.9)">
1 <img alt="" loading="lazy" width="0" height="0" decoding="async" data-nimg="1" style="color:transparent;width:100%;height:auto" src="/images/navbar/menu-open.svg"/>
1 </div>
1 </button>
1 </div>
1 </nav>
1 </header>
1 <main id="accessibility-information" class=" ">
1 <section class="Section_section__oHlmj TextHeader_header-text__6_TOk has-grey-bg is-clipped section">
1 <div class="container ">
1 <div class="columns is-desktop is-multiline">
1 <div class="column is-12 mb-6 is-hidden-mobile" style="opacity:0">
1 <nav aria-label="Breadcrumbs" class="column is-12 is-hidden-mobile Breadcrumbs_breadcrumbs__0II_j pl-0">
1 <ul>
1 <li>
1 <a class="Breadcrumbs_breadcrumbs-path__fU4Zz" target="_self" href="/en/">
1 Lanserhof
1 </a>
1 <span class="Breadcrumbs_separator__etls7">
1 <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 7.877 14.751">
1 <path d="m.5 14.251 6.877-6.876L.5.5" data-name="l" style="fill:none;stroke:#2d2f38;stroke-linecap:round;stroke-linejoin:round">
1 </path>
1 </svg>
1 </span>
1 </li>
1 <li aria-current="page">
1 <span class="Breadcrumbs_breadcrumbs-title__Hp5vF">
1 Accessibility Information
1 </span>
1 </li>
1 </ul>
1 </nav>
1 </div>
1 <div class="column is-4-desktop">
1 <h1 class="mb-6" style="opacity:0;transform:translateY(100px)">
1 Accessability Information
1 </h1>
1 </div>
1 <div class="column is-8-desktop">
1 <div data-headlineover="" class="TextHeader_content__R3Xng" style="opacity:0;transform:translateY(100px)">
1 <p>
1
1 </p>
2 <h2>
2 General Service Description
2 </h2>
3 <p>
3 The Lanserhof Group operates several health resorts with a focus on holistic health, prevention, and regeneration. This includes hotel operations, an outpatient facility in Austria, and two private clinics in Germany.
3 </p>
4 <p>
4 On our website
4 <a aria-label="Visit lanserhof.com website" href="https://lanserhof.com">
4 lanserhof.com
4 </a>
4 , we provide information about our resorts, treatments, and booking options.
4 </p>
5 <p>
5 You can reach us at:
5 </p>
6 <p>
6 Lanserhof Management GmbH
6 <br>
7 Website:
7 E9081WCAG2 A 2.5.3: The accessible name in 'aria-label' must contain the visible label text: https://lanserhof.com
The accessible name used by accessibility aids must contain the text displayed by the visible label. When choosing the text remember that both the name and the label may be read out aloud. See Understanding 2.5.3, and Accessibility API Mappings.
W885WCAG2 A 1.1.1/2.4.4/2.4.9: Do not use the URL as link text
Describe the purpose of a link by providing descriptive text as the content of the <a> element. This description lets a user distinguish this link from other links in the Web page and helps the user determine whether to follow the link. The URL of the destination is generally not sufficiently descriptive. See WCAG2 HTML Technique H30.
<a aria-label="Visit lanserhof.com website" href="https://lanserhof.com">
7 https://lanserhof.com
7 </a>
7
7 </p>
8 <p>
8 Contact our resorts:
8 <br>
9 Lanserhof Lans:
9 E9081WCAG2 A 2.5.3: The accessible name in 'aria-label' must contain the visible label text: info.lans@lanserhof.com
The accessible name used by accessibility aids must contain the text displayed by the visible label. When choosing the text remember that both the name and the label may be read out aloud. See Understanding 2.5.3, and Accessibility API Mappings.
<a aria-label="Send email to Lanserhof Lans" href="mailto:info.lans@lanserhof.com">
9 info.lans@lanserhof.com
9 </a>
9 <br>
10 Lanserhof Tegernsee:
10 E9081WCAG2 A 2.5.3: The accessible name in 'aria-label' must contain the visible label text: info.tegernsee@lanserhof.com
The accessible name used by accessibility aids must contain the text displayed by the visible label. When choosing the text remember that both the name and the label may be read out aloud. See Understanding 2.5.3, and Accessibility API Mappings.
<a aria-label="Send email to Lanserhof Tegernsee" href="mailto:info.tegernsee@lanserhof.com">
10 info.tegernsee@lanserhof.com
10 </a>
10 <br>
11 Lanserhof Sylt:
11 E9081WCAG2 A 2.5.3: The accessible name in 'aria-label' must contain the visible label text: info.sylt@lanserhof.com
The accessible name used by accessibility aids must contain the text displayed by the visible label. When choosing the text remember that both the name and the label may be read out aloud. See Understanding 2.5.3, and Accessibility API Mappings.
<a aria-label="Send email to Lanserhof Sylt" href="mailto:info.sylt@lanserhof.com">
11 info.sylt@lanserhof.com
11 </a>
11
11 </p>
12 <p>
12
12 </p>
13 <h2>
13 Using Our Online Services
13 </h2>
14 <p>
14 Our website offers you:
14 </p>
15 <ul>
16 <li>
16 Information about our resorts and locations
16 </li>
17 <li>
17 Overview of treatments and programs
17 </li>
18 <li>
18 Contact options and inquiries
18 </li>
19 <li>
19 Booking options for stays
19 </li>
20 </ul>
21 <p>
21 Navigation is possible via the main menu and the footer. All essential information is accessible within a maximum of three clicks.
21 </p>
22 <p>
22
22 </p>
23 <h2>
23 Accessibility Requirements
23 </h2>
24 <p>
24 This accessibility statement refers to our website at
24 E9081WCAG2 A 2.5.3: The accessible name in 'aria-label' must contain the visible label text: https://lanserhof.com
The accessible name used by accessibility aids must contain the text displayed by the visible label. When choosing the text remember that both the name and the label may be read out aloud. See Understanding 2.5.3, and Accessibility API Mappings.
W885WCAG2 A 1.1.1/2.4.4/2.4.9: Do not use the URL as link text
Describe the purpose of a link by providing descriptive text as the content of the <a> element. This description lets a user distinguish this link from other links in the Web page and helps the user determine whether to follow the link. The URL of the destination is generally not sufficiently descriptive. See WCAG2 HTML Technique H30.
<a aria-label="Visit lanserhof.com website" href="https://lanserhof.com">
24 https://lanserhof.com
24 </a>
24 .
24 </p>
25 <p>
25 The legal basis for accessibility is the German Accessibility Enhancement Act (BFSG) and its corresponding regulation (BFSGV), which refer to the Harmonized European Standard (EN) 301 549, version 3.2.1, based on the Web Content Accessibility Guidelines (WCAG) version 2.1, levels A and AA.
25 </p>
26 <p>
26
26 </p>
27 <h2>
27 Level of Compliance
27 </h2>
28 <p>
28 Current status: Under review
28 </p>
29 <p>
29 We are currently undergoing a comprehensive accessibility audit to assess the current state of our website and evaluate compliance with WCAG 2.1, level AA.
29 </p>
30 <p>
30 The audit is expected to be completed by August 2025. Only after the results are available can we:
30 </p>
31 <ul>
32 <li>
32 Determine the exact level of compliance
32 </li>
33 <li>
33 Identify specific improvement measures
33 </li>
34 <li>
34 Create a detailed timeline for implementation
34 </li>
35 </ul>
36 <p>
36
36 </p>
37 <h2>
37 Audit Status
37 </h2>
38 <p>
38 The accessibility audit covers all WCAG criteria, including:
38 </p>
39 <ul>
40 <li>
40 Perceivability
40 </li>
41 <li>
41 Operability
41 </li>
42 <li>
42 Understandability
42 </li>
43 <li>
43 Robustness
43 </li>
44 </ul>
45 <p>
45 After the audit is completed, we will update this accessibility information and:
45 </p>
46 <ul>
47 <li>
47 Document the actual level of compliance
47 </li>
48 <li>
48 List identified barriers transparently
48 </li>
49 <li>
49 Publish a binding action plan with a timeline
49 </li>
50 </ul>
51 <p>
51 We are aware of our responsibility and are actively working to make our digital services accessible to all people.
51 </p>
52 <p>
52
52 </p>
53 <h2>
53 Date and Method
53 </h2>
54 <p>
54 This statement was created on June 25, 2025.
54 </p>
55 <p>
55 A professional accessibility audit is currently being conducted and is expected to be completed by August 2025. Once the results are available, this statement will be updated accordingly.
55 </p>
56 <p>
56
56 </p>
57 <h2>
57 Feedback and Contact
57 </h2>
58 <p>
58 We aim to make our website accessible to everyone. Have you encountered any barriers or need assistance?
58 </p>
59 <p>
59 Please contact us:
59 <br>
60 Email:
60 <a aria-label="Send email to marketing@lanserhof.com, subject Accessibility lanserhof.com" href="mailto:marketing@lanserhof.com?subject=Accessibility%20lanserhof.com">
60 marketing@lanserhof.com
60 </a>
60
60 </p>
61 <p>
61 We will respond within 5 business days and work with you to find a solution.
61 </p>
62 <p>
62
62 </p>
63 <h2>
63 Enforcement Procedure
63 </h2>
64 <p>
64 If you are not satisfied with our response to your feedback, you may contact the arbitration office:
64 </p>
65 <p>
65 <strong>
65 Arbitration Office under the Equal Opportunities for Persons with Disabilities Act
65 </strong>
65 <br>
66 Phone:
66 <a aria-label="Phone number of the arbitration office: 030 18 527 2805" href="tel:+4930185272805">
66 030 18 527-2805
66 </a>
66 <br>
67 Email:
67 E9081WCAG2 A 2.5.3: The accessible name in 'aria-label' must contain the visible label text: info@schlichtungsstelle-bgg.de
The accessible name used by accessibility aids must contain the text displayed by the visible label. When choosing the text remember that both the name and the label may be read out aloud. See Understanding 2.5.3, and Accessibility API Mappings.
<a aria-label="Send email to the arbitration office" href="mailto:info@schlichtungsstelle-bgg.de">
67 info@schlichtungsstelle-bgg.de
67 </a>
67 <br>
68 Website:
68 E9081WCAG2 A 2.5.3: The accessible name in 'aria-label' must contain the visible label text: www.schlichtungsstelle-bgg.de
The accessible name used by accessibility aids must contain the text displayed by the visible label. When choosing the text remember that both the name and the label may be read out aloud. See Understanding 2.5.3, and Accessibility API Mappings.
<a aria-label="Visit the arbitration office website" href="https://www.schlichtungsstelle-bgg.de">
68 www.schlichtungsstelle-bgg.de
68 </a>
68
68 </p>
69 <p>
69 The arbitration office will inform you about the procedure of a dispute resolution process.
69 </p>
70 <p>
70 We are continuously working to make our digital offerings accessible to everyone. Your feedback helps us improve.
70 </p>
71 </div>
71 <div style="opacity:0;transform:translateY(100px)">
71 </div>
71 </div>
71 </div>
71 </div>
71 </section>
71 E622HTML: The 'id' attribute does not have a valid value: It does not contain a valid ID. It must contain at least one character and must not contain any space characters
The HTML specification being tested against defines certain valid values for each attribute. Usually a list of valid values will be displayed when you see this message. Note that many values must be in lower case in XHTML, including the 'x' in numeric hex entity references. Also note that what values are allowed varies from standard to standard.
<section class="Section_section__oHlmj undefined has-grey-bg is-gapless-top-bottom section" id="">
71 <div class="container container">
71 <div class="columns is-multiline">
71 <div class="column is-hidden-touch is-4-desktop">
71 </div>
71 <div class="column is-12-tablet is-8-desktop">
71 <div class="is-hidden-desktop">
71 </div>
71 <div class="is-clipped">
71 <div class=" is-clipped">
71 </div>
71 </div>
71 </div>
71 </div>
71 </div>
71 </section>
71 E622HTML: The 'id' attribute does not have a valid value: It does not contain a valid ID. It must contain at least one character and must not contain any space characters
The HTML specification being tested against defines certain valid values for each attribute. Usually a list of valid values will be displayed when you see this message. Note that many values must be in lower case in XHTML, including the 'x' in numeric hex entity references. Also note that what values are allowed varies from standard to standard.
<section class="Section_section__oHlmj undefined has-grey-bg is-gapless-top-bottom section" id="">
71 <div class="container container">
71 <div class="columns is-multiline">
71 <div class="column is-hidden-touch is-4-desktop">
71 </div>
71 <div class="column is-12-tablet is-8-desktop">
71 <div class="is-hidden-desktop">
71 </div>
71 <div class="is-clipped">
71 <div class=" is-clipped">
71 </div>
71 </div>
71 </div>
71 </div>
71 </div>
71 </section>
71 E622HTML: The 'id' attribute does not have a valid value: It does not contain a valid ID. It must contain at least one character and must not contain any space characters
The HTML specification being tested against defines certain valid values for each attribute. Usually a list of valid values will be displayed when you see this message. Note that many values must be in lower case in XHTML, including the 'x' in numeric hex entity references. Also note that what values are allowed varies from standard to standard.
<section class="Section_section__oHlmj undefined has-grey-bg is-gapless-top-bottom section" id="">
71 <div class="container container">
71 <div class="columns is-multiline">
71 <div class="column is-hidden-touch is-4-desktop">
71 </div>
71 <div class="column is-12-tablet is-8-desktop">
71 <div class="is-hidden-desktop">
71 </div>
71 <div class="is-clipped">
71 <div class=" is-clipped">
71 </div>
71 </div>
71 </div>
71 </div>
71 </div>
71 </section>
71 E622HTML: The 'id' attribute does not have a valid value: It does not contain a valid ID. It must contain at least one character and must not contain any space characters
The HTML specification being tested against defines certain valid values for each attribute. Usually a list of valid values will be displayed when you see this message. Note that many values must be in lower case in XHTML, including the 'x' in numeric hex entity references. Also note that what values are allowed varies from standard to standard.
<section class="Section_section__oHlmj undefined has-grey-bg is-gapless-top-bottom section" id="">
71 <div class="container container">
71 <div class="columns is-multiline">
71 <div class="column is-hidden-touch is-4-desktop">
71 </div>
71 <div class="column is-12-tablet is-8-desktop">
71 <div class="is-hidden-desktop">
71 </div>
71 <div class="is-clipped">
71 <div class=" is-clipped">
71 </div>
71 </div>
71 </div>
71 </div>
71 </div>
71 </section>
71 E622HTML: The 'id' attribute does not have a valid value: It does not contain a valid ID. It must contain at least one character and must not contain any space characters
The HTML specification being tested against defines certain valid values for each attribute. Usually a list of valid values will be displayed when you see this message. Note that many values must be in lower case in XHTML, including the 'x' in numeric hex entity references. Also note that what values are allowed varies from standard to standard.
<section class="Section_section__oHlmj undefined has-grey-bg default section" id="">
71 <div class="container container">
71 <div class="columns is-multiline">
71 <div class="column is-hidden-touch is-4-desktop">
71 </div>
71 <div class="column is-12-tablet is-8-desktop">
71 <div class="is-hidden-desktop">
71 </div>
71 <div class="is-clipped">
71 <div class=" is-clipped">
71 </div>
71 </div>
71 </div>
71 </div>
71 </div>
71 </section>
71 E622HTML: The 'id' attribute does not have a valid value: It does not contain a valid ID. It must contain at least one character and must not contain any space characters
The HTML specification being tested against defines certain valid values for each attribute. Usually a list of valid values will be displayed when you see this message. Note that many values must be in lower case in XHTML, including the 'x' in numeric hex entity references. Also note that what values are allowed varies from standard to standard.
<section class="Section_section__oHlmj undefined has-grey-bg is-gapless-top-bottom section" id="">
71 <div class="container container">
71 <div class="columns is-multiline">
71 <div class="column is-hidden-touch is-4-desktop">
71 </div>
71 <div class="column is-12-tablet is-8-desktop">
71 <div class="is-hidden-desktop">
71 </div>
71 <div class="is-clipped">
71 <div class=" is-clipped">
71 </div>
71 </div>
71 </div>
71 </div>
71 </div>
71 </section>
71 E622HTML: The 'id' attribute does not have a valid value: It does not contain a valid ID. It must contain at least one character and must not contain any space characters
The HTML specification being tested against defines certain valid values for each attribute. Usually a list of valid values will be displayed when you see this message. Note that many values must be in lower case in XHTML, including the 'x' in numeric hex entity references. Also note that what values are allowed varies from standard to standard.
<section class="Section_section__oHlmj undefined has-grey-bg is-gapless-top-bottom section" id="">
71 <div class="container container">
71 <div class="columns is-multiline">
71 <div class="column is-hidden-touch is-4-desktop">
71 </div>
71 <div class="column is-12-tablet is-8-desktop">
71 <div class="is-hidden-desktop">
71 </div>
71 <div class="is-clipped">
71 <div class=" is-clipped">
71 </div>
71 </div>
71 </div>
71 </div>
71 </div>
71 </section>
71 <div class="RetreatButton_retreat-button-wrapper__JCYkL retreat-button-wrapper" style="--bg-desktop:#96bdcd;--bg-hover-desktop:#2c2f38;will-change:transform">
71 <a class="RetreatButton_retreat-button__8J1LU retreat-button" aria-label="Booking request" target="_self" href="/en/plan-your-stay/">
71 <div class="RetreatButton_arrow__XbWgr">
71 <div class="RetreatButton_icon-wrapper__IJnBa">
71 <img alt="" loading="lazy" width="0" height="0" decoding="async" data-nimg="1" class="RetreatButton_touch-arrow__vvyDA" style="color:transparent;width:100%;height:auto" src="/images/retreat-btn/lh_arrow_right_white.svg"/>
71 <img alt="" loading="lazy" width="0" height="0" decoding="async" data-nimg="1" class="RetreatButton_desktop-arrow__Yevik" style="color:transparent;width:100%;height:auto" src="/images/retreat-btn/lh_arrow-cyrcle.svg"/>
71 </div>
71 </div>
71 <span class="RetreatButton_title___9DZ4">
71 Booking request
71 </span>
71 </a>
71 </div>
71 </main>
71 <footer class="Footer_footer__OYoYH has-dark-grey-bg" aria-label="footer" id="kontakt">
71 <section class="Section_section__oHlmj pb-2 pt-6 section">
71 <div class="container py-0">
71 <span class="Footer_instagram-title__aMV8U mb-6">
71 Lanserhof on Instagram
71 </span>
71 <div class="insta socials no-padding-bottom has-text-centered undefined">
71 <div class="feed-wrapper">
71 <div>
71 <p>
71 Zurzeit sind keine Instagram Posts verfügbar
71 </p>
71 </div>
71 </div>
71 </div>
71 <div class="is-flex is-justify-content-center">
71 <a class="btn primary Button_btn__1Gtek Button_primary__ivjK_ Footer_follow-button__E5PHc" target="_blank" href="https://www.instagram.com/lanserhof">
71 <span class="Button_children__ngKoL">
71 <strong>
71 Follow
71 </strong>
71 us
71 </span>
71 </a>
71 </div>
71 <div class="Socials_socials__g1jWB">
71 W868WCAG2 A 2.4.4: Different adjacent links with the same link text 'socials-link'
If you have adjacent links to different places, but with the same link text (when read aloud), it can be confusing to the user. So, you should either change the link text or add a unique 'aria-label' or 'aria-labelledby' attribute to each link. See Understanding 2.4.4.
<a class="social" aria-label="socials-link" rel="noopener noreferrer" target="_blank" id="social-0" href="https://www.instagram.com/lanserhof/">
71 E9542WCAG2 A 4.1.2: Interactive elements are not allowed here
When using ARIA roles there are additional rules where interactive elements may appear. This error may also be caused by incorrectly nesting tags, missing end tags, or similar structural issues. So if it is not obvious what is wrong, fix any structural issues first. See ARIA in HTML.
E956WCAG2 A 4.1.2: The value of the 'role' attribute is not valid for this element
Elements can only have specific roles as defined by the ARIA specification. So, you may be better off using a more appropriate element for this role. See ARIA in HTML.
P871WCAG2 A 1.1.1/2.4.4/2.4.9: Link text is missing
Describe the purpose of a link by providing descriptive text as the content of the element, or provide an 'aria-label' or 'aria-labelledby' attribute. The description lets a user distinguish this link from other links in the Web page and helps the user determine whether to follow the link. The URL of the destination is generally not sufficiently descriptive. See WCAG2 HTML Technique H30.
<img alt="" role="link" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="Socials_logo__PDQjE" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_instagram.svg"/>
71 </a>
71 W868WCAG2 A 2.4.4: Different adjacent links with the same link text 'socials-link'
If you have adjacent links to different places, but with the same link text (when read aloud), it can be confusing to the user. So, you should either change the link text or add a unique 'aria-label' or 'aria-labelledby' attribute to each link. See Understanding 2.4.4.
<a class="social" aria-label="socials-link" rel="noopener noreferrer" target="_blank" id="social-1" href="https://www.facebook.com/LanserhofDE/">
71 E9542WCAG2 A 4.1.2: Interactive elements are not allowed here
When using ARIA roles there are additional rules where interactive elements may appear. This error may also be caused by incorrectly nesting tags, missing end tags, or similar structural issues. So if it is not obvious what is wrong, fix any structural issues first. See ARIA in HTML.
E956WCAG2 A 4.1.2: The value of the 'role' attribute is not valid for this element
Elements can only have specific roles as defined by the ARIA specification. So, you may be better off using a more appropriate element for this role. See ARIA in HTML.
P871WCAG2 A 1.1.1/2.4.4/2.4.9: Link text is missing
Describe the purpose of a link by providing descriptive text as the content of the element, or provide an 'aria-label' or 'aria-labelledby' attribute. The description lets a user distinguish this link from other links in the Web page and helps the user determine whether to follow the link. The URL of the destination is generally not sufficiently descriptive. See WCAG2 HTML Technique H30.
<img alt="" role="link" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="Socials_logo__PDQjE" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_facebook.svg"/>
71 </a>
71 W868WCAG2 A 2.4.4: Different adjacent links with the same link text 'socials-link'
If you have adjacent links to different places, but with the same link text (when read aloud), it can be confusing to the user. So, you should either change the link text or add a unique 'aria-label' or 'aria-labelledby' attribute to each link. See Understanding 2.4.4.
<a class="social" aria-label="socials-link" rel="noopener noreferrer" target="_blank" id="social-2" href="https://www.linkedin.com/company/lanserhof-gmbh/">
71 E9542WCAG2 A 4.1.2: Interactive elements are not allowed here
When using ARIA roles there are additional rules where interactive elements may appear. This error may also be caused by incorrectly nesting tags, missing end tags, or similar structural issues. So if it is not obvious what is wrong, fix any structural issues first. See ARIA in HTML.
E956WCAG2 A 4.1.2: The value of the 'role' attribute is not valid for this element
Elements can only have specific roles as defined by the ARIA specification. So, you may be better off using a more appropriate element for this role. See ARIA in HTML.
P871WCAG2 A 1.1.1/2.4.4/2.4.9: Link text is missing
Describe the purpose of a link by providing descriptive text as the content of the element, or provide an 'aria-label' or 'aria-labelledby' attribute. The description lets a user distinguish this link from other links in the Web page and helps the user determine whether to follow the link. The URL of the destination is generally not sufficiently descriptive. See WCAG2 HTML Technique H30.
<img alt="" role="link" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="Socials_logo__PDQjE" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_linkedin.svg"/>
71 </a>
71 W868WCAG2 A 2.4.4: Different adjacent links with the same link text 'socials-link'
If you have adjacent links to different places, but with the same link text (when read aloud), it can be confusing to the user. So, you should either change the link text or add a unique 'aria-label' or 'aria-labelledby' attribute to each link. See Understanding 2.4.4.
<a class="social" aria-label="socials-link" rel="noopener noreferrer" target="_blank" id="social-3" href="https://twitter.com/lanserhof">
71 E9542WCAG2 A 4.1.2: Interactive elements are not allowed here
When using ARIA roles there are additional rules where interactive elements may appear. This error may also be caused by incorrectly nesting tags, missing end tags, or similar structural issues. So if it is not obvious what is wrong, fix any structural issues first. See ARIA in HTML.
E956WCAG2 A 4.1.2: The value of the 'role' attribute is not valid for this element
Elements can only have specific roles as defined by the ARIA specification. So, you may be better off using a more appropriate element for this role. See ARIA in HTML.
P871WCAG2 A 1.1.1/2.4.4/2.4.9: Link text is missing
Describe the purpose of a link by providing descriptive text as the content of the element, or provide an 'aria-label' or 'aria-labelledby' attribute. The description lets a user distinguish this link from other links in the Web page and helps the user determine whether to follow the link. The URL of the destination is generally not sufficiently descriptive. See WCAG2 HTML Technique H30.
<img alt="" role="link" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="Socials_logo__PDQjE" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lh_x-twitter.svg"/>
71 </a>
71 W868WCAG2 A 2.4.4: Different adjacent links with the same link text 'socials-link'
If you have adjacent links to different places, but with the same link text (when read aloud), it can be confusing to the user. So, you should either change the link text or add a unique 'aria-label' or 'aria-labelledby' attribute to each link. See Understanding 2.4.4.
<a class="social" aria-label="socials-link" rel="noopener noreferrer" target="_blank" id="social-4" href="https://www.youtube.com/channel/UCvwF4uQmURR_iEZ-V1WZOrw">
71 E9542WCAG2 A 4.1.2: Interactive elements are not allowed here
When using ARIA roles there are additional rules where interactive elements may appear. This error may also be caused by incorrectly nesting tags, missing end tags, or similar structural issues. So if it is not obvious what is wrong, fix any structural issues first. See ARIA in HTML.
E956WCAG2 A 4.1.2: The value of the 'role' attribute is not valid for this element
Elements can only have specific roles as defined by the ARIA specification. So, you may be better off using a more appropriate element for this role. See ARIA in HTML.
P871WCAG2 A 1.1.1/2.4.4/2.4.9: Link text is missing
Describe the purpose of a link by providing descriptive text as the content of the element, or provide an 'aria-label' or 'aria-labelledby' attribute. The description lets a user distinguish this link from other links in the Web page and helps the user determine whether to follow the link. The URL of the destination is generally not sufficiently descriptive. See WCAG2 HTML Technique H30.
<img alt="" role="link" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="Socials_logo__PDQjE" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/04/lh_youtube.svg"/>
71 </a>
71 </div>
71 <div class="Footer_divider__bfFrr my-6">
71 </div>
71 <div class="columns">
71 <div class="column is-2-tablet is-3-desktop is-2-widescreen is-hidden-mobile">
71 <img alt="" loading="lazy" width="1" height="1" decoding="async" data-nimg="1" class="Footer_logo__oqoeK" style="color:transparent" src="https://api.lanserhof.com/wp-content/uploads/2024/03/lanserhof-logo.svg"/>
71 </div>
71 <div class="column is-10-tablet is-9-desktop is-10-widescreen">
71 <div class="columns is-multiline Footer_main-menu__48BNz">
71 <div class="column is-6-tablet is-3-widescreen">
71 <div class="is-flex is-flex-direction-column">
71 <div class="is-flex is-justify-content-space-between is-align-items-center">
71 <span class="Footer_main-menu-title__ZRXUB">
71 LANSERHOF
71 </span>
71 </div>
71 <div class="is-flex is-flex-direction-column is-clipped" style="opacity:0;height:0px;will-change:opacity">
71 <a href="/en/lanserhof-concept/">
71 Lanserhof Concept
71 </a>
71 <a href="/en/services/">
71 Our range of services
71 </a>
71 <a href="/en/gallery/">
71 Gallery
71 </a>
71 <a href="/en/blog/">
71 Health Guide
71 </a>
71 </div>
71 </div>
71 </div>
71 <div class="column is-6-tablet is-3-widescreen">
71 <div class="is-flex is-flex-direction-column">
71 <div class="is-flex is-justify-content-space-between is-align-items-center">
71 <span class="Footer_main-menu-title__ZRXUB">
71 RESORT
71 </span>
71 </div>
71 <div class="is-flex is-flex-direction-column is-clipped" style="opacity:0;height:0px;will-change:opacity">
71 <a href="/en/lanserhof-tegernsee/">
71 Lanserhof Tegernsee
71 </a>
71 <a href="/en/lanserhof-lans/">
71 Lanserhof Lans
71 </a>
71 <a href="/en/lanserhof-sylt/">
71 Lanserhof Sylt
71 </a>
71 </div>
71 </div>
71 </div>
71 <div class="column is-6-tablet is-3-widescreen">
71 <div class="is-flex is-flex-direction-column">
71 <div class="is-flex is-justify-content-space-between is-align-items-center">
71 <span class="Footer_main-menu-title__ZRXUB">
71 FURTHER LOCATIONS
71 </span>
71 </div>
71 <div class="is-flex is-flex-direction-column is-clipped" style="opacity:0;height:0px;will-change:opacity">
71 <a href="https://lhtac.com/">
71 Lanserhof at The Art Club London
71 </a>
71 <a href="https://lansmedicum.de/">
71 Lans Medicum Hamburg
71 </a>
71 <a href="https://lansphysio.de/">
71 Lans Physio Hamburg
71 </a>
71 </div>
71 </div>
71 </div>
71 <div class="column is-6-tablet is-3-widescreen">
71 <div class="is-flex is-flex-direction-column">
71 <div class="is-flex is-justify-content-space-between is-align-items-center">
71 <span class="Footer_main-menu-title__ZRXUB">
71 CONTACT | CAREER
71 </span>
71 </div>
71 <div class="is-flex is-flex-direction-column is-clipped" style="opacity:0;height:0px;will-change:opacity">
71 <a href="/en/contact/">
71 Contact
71 </a>
71 <a href="/en/newsletter/">
71 Newsletter
71 </a>
71 <a href="https://jobs.lanserhof.com/">
71 Career
71 </a>
71 </div>
71 </div>
71 </div>
71 </div>
71 </div>
71 </div>
71 <div class="Footer_legal-menu__EdlZ3">
71 <div id="legal-menu" role="menubar" aria-label="legal-menu" class="LegalMenu_legal-menu__NiQAK">
71 <a class="legal menu-item" role="menuitem" id="menuitem-0" href="/en/legal-information/">
71 Legal Information
71 </a>
71 <span class="LegalMenu_divider__Yf_T6">
71 |
71 </span>
71 <a class="legal menu-item" role="menuitem" id="menuitem-1" href="/en/accessibility-information/">
71 Accessibility Information
71 </a>
71 <span class="LegalMenu_divider__Yf_T6">
71 |
71 </span>
71 <a class="legal menu-item" role="menuitem" id="menuitem-2" href="/en/privacy-policy/">
71 Privacy policy
71 </a>
71 <span class="LegalMenu_divider__Yf_T6">
71 |
71 </span>
71 <a class="legal menu-item LegalMenu_consent__oFrmR" role="menuitem" id="menuitem-privacysettings">
71 Privacy Settings
71 </a>
71 </div>
71 </div>
71 <div class="Footer_divider__bfFrr my-3">
71 </div>
71 <div class="Footer_bottom__KuoWZ">
71 <p class="Footer_copyright__1ODhL">
71 <span>
71 Copyright
71 </span>
71 <span>
71 2025
71 ,
71 </span>
71 <span>
71 Lanserhof
71 </span>
71 </p>
71 <div class="Footer_webdesign__UZPW_">
71 <div>
71 Webdesign & Development by
71 <a target="_blank" href="https://www.aleksundshantu.com/">
71 ALEKS & SHANTU
71 </a>
71 </div>
71 </div>
71 </div>
71 </div>
71 </section>
71 </footer>
71 </div>
71 <script id="__NEXT_DATA__" type="application/json">
71 </script>
71 </body>
71 </html>