Referer:
Issues:
22 Errors 8 Probable Errors 11 Warnings 1 Extra Info
DOCTYPE:
HTML5
Summary report > Page report
22 Errors
- 19 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"/> 12 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"/> 12 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"/> 12 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"/> 12 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"/> 12 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"> - 1 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.
1 The accessible name in 'aria-label' must contain the visible label text: MENÜ <button class="Hamburger_hamburger__6VuUc" aria-label="Öffnet und schließt das Hauptmenü" aria-controls="navbar-main" aria-expanded="false"> - 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"/> 12 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"/> 12 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"/> 12 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"/> 12 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"/> 12 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="Öffnet und schließt das Hauptmenü" 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 'de' 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 'de' 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.
- 1 HTML
- 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)">
- 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.
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"/> 12 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"/> 12 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"/> 12 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"/> 12 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"/> 12 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.
11 Warnings
- 9 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.
12 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/"> 12 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/"> 12 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/"> 12 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"> 12 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"> - 1 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.
10 Do not use the URL as link text <a target="_blank" rel="noopener" href="https://ec.europa.eu/consumers/odr/"> - 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="Suchbegriff" 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.
1 Extra Info
- 1 WCAG2 A
- 1 I885 - SC 2.4.3: When 'tabindex' is used the tab order may become incorrect. With 'tabindex', changes to the page can easily change the tab order such that it no longer follows logical relationships and sequences in the content. So, you should manually check any pages that use 'tabindex' to be sure they still make sense. See WCAG2 Failure F44.
0 
I885WCAG2 A 2.4.3: When 'tabindex' is used the tab order may become incorrect
With 'tabindex', changes to the page can easily change the tab order such that it no longer follows logical relationships and sequences in the content. So, you should manually check any pages that use 'tabindex' to be sure they still make sense. See WCAG2 Failure F44.
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="de">
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 Impressum | Lanserhof
1 </title>
1 <meta charSet="UTF-8"/>
1 <meta name="viewport" content="width=device-width, initial-scale=1"/>
1 <meta name="description" content="Impressum | Lanserhof"/>
1 <meta name="robots" content="index,follow,max-image-preview:large,max-snippet:-1,max-video-preview:-1"/>
1 <meta property="og:locale" content="de_DE"/>
1 <meta property="og:type" content="article"/>
1 <meta property="og:title" content="Impressum | Lanserhof"/>
1 <meta property="og:description" content="Impressum | Lanserhof"/>
1 <meta property="og:url" content="https://lanserhof.com/de/impressum/"/>
1 <meta property="og:site_name" content="Lanserhof"/>
1 <meta property="article:modified_time" content="2024-12-10T15:57:12+00:00"/>
1 <link rel="canonical" href="https://lanserhof.com/de/impressum/"/>
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="de" href="https://lanserhof.com/de/impressum/"/>
1 <link rel="alternate" hrefLang="en" href="https://lanserhof.com/en/legal-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="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 <noscript data-n-css="">
1 </noscript>
1 <script defer="" nomodule="" src="/_next/static/chunks/polyfills-42372ed130431b0a.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="/de/">
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 'de' 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 de
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 'de' 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 de
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 Suche
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="Suchbegriff" 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="KONTAKT" 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 KONTAKT
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.
E9081WCAG2 A 2.5.3: The accessible name in 'aria-label' must contain the visible label text: MENÜ
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.
<button class="Hamburger_hamburger__6VuUc" aria-label="Öffnet und schließt das Hauptmenü" 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 MENÜ
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="impressum" 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="/de/">
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 Impressum
1 </span>
1 </li>
1 </ul>
1 </nav>
1 </div>
1 <div class="column is-12-desktop is-4-fullhd">
1 <h1 class="mb-6" style="opacity:0;transform:translateY(100px)">
1 Impressum
1 </h1>
1 </div>
1 <div class="column is-12-desktop is-8-fullhd">
1 <div data-headlineover="" class="TextHeader_content__R3Xng" style="opacity:0;transform:translateY(100px)">
1 <p>
1 <strong>
1 Lanserhof Management GmbH
1 </strong>
1 <br>
2 Neue ABC-Straße 8
2 <br>
3 20354 Hamburg
3 <br>
4 Deutschland
4 </p>
5 <p>
5 <strong>
5 Telefon:
5 </strong>
5 +49 40 288 09 67 0
5 </p>
6 <p>
6 <strong>
6 Mail:
6 </strong>
6 <a target="_blank" rel="noopener" href="mailto:marketing@lanserhof.com">
6 marketing@lanserhof.com
6 </a>
6 </p>
7 <p>
7 <strong>
7 Geschäftsführer:
7 </strong>
7 Dr. Christian Harisch
7 </p>
8 <p>
8 <strong>
8 Handelsregister:
8 </strong>
8 Amtsgericht München, HRB 213099
8 </p>
9 <p>
9 <strong>
9 Umsatzsteuer-Identifikationsnummer:
9 </strong>
9 DE296812119
9 </p>
10 <p>
10 Die Europäische Kommission stellt eine Plattform zur Online-Streitbeilegung (OS) bereit, die Sie hier finden
10 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 target="_blank" rel="noopener" href="https://ec.europa.eu/consumers/odr/">
10 https://ec.europa.eu/consumers/odr/
10 </a>
10 . Wir sind bereit, an einem außergerichtlichen Schlichtungsverfahren vor einer Verbraucherschlichtungsstelle teilzunehmen.
10 </p>
11 <p>
11 Impressum erstellt mit dem
11 <a target="_blank" rel="noopener" href="https://legal.trustedshops.com/">
11 Trusted Shops
11 </a>
11 Rechtstexter in Kooperation mit
11 <a target="_blank" rel="noopener" href="https://foehlisch.com/">
11 FÖHLISCH
11 </a>
11 Rechtsanwälte.
11 </p>
12 </div>
12 <div style="opacity:0;transform:translateY(100px)">
12 </div>
12 </div>
12 </div>
12 </div>
12 </section>
12 <div class="RetreatButton_retreat-button-wrapper__JCYkL retreat-button-wrapper" style="--bg-desktop:#96bdcd;--bg-hover-desktop:#2c2f38;will-change:transform">
12 <a class="RetreatButton_retreat-button__8J1LU retreat-button" aria-label="Aufenthalt buchen" target="_self" href="/de/aufenthalt-planen/">
12 <div class="RetreatButton_arrow__XbWgr">
12 <div class="RetreatButton_icon-wrapper__IJnBa">
12 <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"/>
12 <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"/>
12 </div>
12 </div>
12 <span class="RetreatButton_title___9DZ4">
12 Aufenthalt buchen
12 </span>
12 </a>
12 </div>
12 </main>
12 <footer class="Footer_footer__OYoYH has-dark-grey-bg" aria-label="footer" id="kontakt">
12 <section class="Section_section__oHlmj pb-2 pt-6 section">
12 <div class="container py-0">
12 <span class="Footer_instagram-title__aMV8U mb-6">
12 Lanserhof auf Instagram
12 </span>
12 <div class="insta socials no-padding-bottom has-text-centered undefined">
12 <div class="feed-wrapper">
12 <div>
12 <p>
12 Zurzeit sind keine Instagram Posts verfügbar
12 </p>
12 </div>
12 </div>
12 </div>
12 <div class="is-flex is-justify-content-center">
12 <a class="btn primary Button_btn__1Gtek Button_primary__ivjK_ Footer_follow-button__E5PHc" target="_blank" href="https://www.instagram.com/lanserhof">
12 <span class="Button_children__ngKoL">
12 <strong>
12 Folgen
12 </strong>
12 Sie uns
12 </span>
12 </a>
12 </div>
12 <div class="Socials_socials__g1jWB">
12 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/">
12 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"/>
12 </a>
12 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/">
12 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"/>
12 </a>
12 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/">
12 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"/>
12 </a>
12 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">
12 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"/>
12 </a>
12 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">
12 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"/>
12 </a>
12 </div>
12 <div class="Footer_divider__bfFrr my-6">
12 </div>
12 <div class="columns">
12 <div class="column is-2-tablet is-3-desktop is-2-widescreen is-hidden-mobile">
12 <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"/>
12 </div>
12 <div class="column is-10-tablet is-9-desktop is-10-widescreen">
12 <div class="columns is-multiline Footer_main-menu__48BNz">
12 <div class="column is-6-tablet is-3-widescreen">
12 <div class="is-flex is-flex-direction-column">
12 <div class="is-flex is-justify-content-space-between is-align-items-center">
12 <span class="Footer_main-menu-title__ZRXUB">
12 LANSERHOF
12 </span>
12 </div>
12 <div class="is-flex is-flex-direction-column is-clipped" style="opacity:0;height:0px;will-change:opacity">
12 <a href="/de/lanserhof-concept/">
12 Lanserhof Concept
12 </a>
12 <a href="/de/leistungen/">
12 Leistungsangebot
12 </a>
12 <a href="/de/galerie/">
12 Galerie
12 </a>
12 <a href="/de/blog/">
12 Gesundheitsratgeber
12 </a>
12 <a href="/de/lanserhof-podcast/">
12 Lanserhof Podcast
12 </a>
12 </div>
12 </div>
12 </div>
12 <div class="column is-6-tablet is-3-widescreen">
12 <div class="is-flex is-flex-direction-column">
12 <div class="is-flex is-justify-content-space-between is-align-items-center">
12 <span class="Footer_main-menu-title__ZRXUB">
12 RESORT
12 </span>
12 </div>
12 <div class="is-flex is-flex-direction-column is-clipped" style="opacity:0;height:0px;will-change:opacity">
12 <a href="/de/lanserhof-lans/">
12 Lanserhof Lans
12 </a>
12 <a href="/de/lanserhof-sylt/">
12 Lanserhof Sylt
12 </a>
12 <a href="/de/lanserhof-tegernsee/">
12 Lanserhof Tegernsee
12 </a>
12 </div>
12 </div>
12 </div>
12 <div class="column is-6-tablet is-3-widescreen">
12 <div class="is-flex is-flex-direction-column">
12 <div class="is-flex is-justify-content-space-between is-align-items-center">
12 <span class="Footer_main-menu-title__ZRXUB">
12 WEITERE STANDORTE
12 </span>
12 </div>
12 <div class="is-flex is-flex-direction-column is-clipped" style="opacity:0;height:0px;will-change:opacity">
12 <a href="https://lhtac.com/">
12 Lanserhof at The Art Club London
12 </a>
12 <a href="https://lansmedicum.de/">
12 Lans Medicum Hamburg
12 </a>
12 <a href="https://lansphysio.de/">
12 Lans Physio Hamburg
12 </a>
12 </div>
12 </div>
12 </div>
12 <div class="column is-6-tablet is-3-widescreen">
12 <div class="is-flex is-flex-direction-column">
12 <div class="is-flex is-justify-content-space-between is-align-items-center">
12 <span class="Footer_main-menu-title__ZRXUB">
12 KONTAKT | KARRIERE
12 </span>
12 </div>
12 <div class="is-flex is-flex-direction-column is-clipped" style="opacity:0;height:0px;will-change:opacity">
12 <a href="/de/kontakt/">
12 Kontakt
12 </a>
12 <a href="/de/newsletter/">
12 Newsletter
12 </a>
12 <a href="https://jobs.lanserhof.com/">
12 Karriere
12 </a>
12 </div>
12 </div>
12 </div>
12 </div>
12 </div>
12 </div>
12 <div class="Footer_legal-menu__EdlZ3">
12 <div id="legal-menu" role="menubar" aria-label="legal-menu" class="LegalMenu_legal-menu__NiQAK">
12 <a class="legal menu-item" role="menuitem" id="menuitem-0" href="/de/datenschutzerklaerung/">
12 Datenschutzerklärung
12 </a>
12 <span class="LegalMenu_divider__Yf_T6">
12 |
12 </span>
12 <a class="legal menu-item" role="menuitem" id="menuitem-1" href="/de/barrierefreiheit/">
12 Barrierefreiheit
12 </a>
12 <span class="LegalMenu_divider__Yf_T6">
12 |
12 </span>
12 <a class="legal menu-item" role="menuitem" id="menuitem-2" href="/de/impressum/">
12 Impressum
12 </a>
12 <span class="LegalMenu_divider__Yf_T6">
12 |
12 </span>
12 <a class="legal menu-item LegalMenu_consent__oFrmR" role="menuitem" id="menuitem-privacysettings">
12 Persönliche Einstellungen
12 </a>
12 </div>
12 </div>
12 <div class="Footer_divider__bfFrr my-3">
12 </div>
12 <div class="Footer_bottom__KuoWZ">
12 <p class="Footer_copyright__1ODhL">
12 <span>
12 Copyright
12 </span>
12 <span>
12 2025
12 ,
12 </span>
12 <span>
12 Lanserhof
12 </span>
12 </p>
12 <div class="Footer_webdesign__UZPW_">
12 <div>
12 Webdesign & Development by
12 <a tabindex="2" target="_blank" href="https://www.aleksundshantu.com/">
12 ALEKS & SHANTU
12 </a>
12 </div>
12 </div>
12 </div>
12 </div>
12 </section>
12 </footer>
12 </div>
12 <script id="__NEXT_DATA__" type="application/json">
12 </script>
12 </body>
12 </html>