To Unterwössen along Tiroler Ache and Richard-Strauss Höhenweg )
Valley hike from Marquartstein to Unterwössen and back.
Valley hike from Marquartstein to Unterwössen and back.
distance
duration
highest point
meters upwards
meters downwards
Difficulty
easy
From the car park at the town hall in Marquartstein we follow the B307 towards Reit im Winkl, then we walk along the B305 over the bridge towards Unterwössen. We walk along the B305 next to the main road, then turn right and go downhill a little but still follow the B305. At the next signpost we turn right onto the Achendamm circular trail over a stream and continue next to the Tiroler Ache through the sparse trees. At the next signpost we follow the circular trail towards the centre of Unterwössen along the Wössner Bach. To the right the view opens up to wide open spaces and the back of the Hochplatte. We reach Unterwössen, cross the B305 and continue walking towards the Richard Strauss high trail, slightly uphill past meadows. When we arrive at the Kapellenweg there are signs again pointing to the high trail, but we do not choose the slightly shorter route “via Altweg” but walk towards Grub-Point and at the first fork turn left along the ridge. At the next signpost, we turn sharply left towards the Richard Strauss high trail. The wide forest path climbs slightly and we enter a high forest, walking past the turnoff to Neugrabenalm and Grub-Point. Shortly after the turnoff, a path leads to Berghof Altweg, but we stay on the high trail. We can see the Hochplatte, somewhat obscured by the sparse trees. As we continue on, we also see the Berghof Schlecht guesthouse below the high trail. At the next turnoff, which leads right to Grub-Point and Neugrabenalm, we turn left onto a forest path that leads downhill to a fork. We walk straight on, slightly uphill, and see the Berghof Schlecht guesthouse in front of us. From here, we walk downhill, enter the forest, and eventually reach the B305. Turning right, we reach the next signpost, which shows us the way to the underpass that runs beneath the B305. Then we continue to the right and after a short time we are back at the start of the hike, the starting point at the town hall in Marquartstein
Einkehrmöglichkeit
Parkplatz Rathaus
Achental - Chiemsee-Chiemgau holiday region
We firmly believe that the internet should be available and accessible to anyone, and are committed to providing a website that is accessible to the widest possible audience, regardless of circumstance and ability.
To fulfill this, we aim to adhere as strictly as possible to the World Wide Web Consortium’s (W3C) Web Content Accessibility Guidelines 2.1 (WCAG 2.1) at the AA level. These guidelines explain how to make web content accessible to people with a wide array of disabilities. Complying with those guidelines helps us ensure that the website is accessible to all people: blind people, people with motor impairments, visual impairment, cognitive disabilities, and more.
This website utilizes various technologies that are meant to make it as accessible as possible at all times. We utilize an accessibility interface that allows persons with specific disabilities to adjust the website’s UI (user interface) and design it to their personal needs.
Additionally, the website utilizes an AI-based application that runs in the background and optimizes its accessibility level constantly. This application remediates the website’s HTML, adapts Its functionality and behavior for screen-readers used by the blind users, and for keyboard functions used by individuals with motor impairments.
If you’ve found a malfunction or have ideas for improvement, we’ll be happy to hear from you. You can reach out to the website’s operators by using the following email
Our website implements the ARIA attributes (Accessible Rich Internet Applications) technique, alongside various different behavioral changes, to ensure blind users visiting with screen-readers are able to read, comprehend, and enjoy the website’s functions. As soon as a user with a screen-reader enters your site, they immediately receive a prompt to enter the Screen-Reader Profile so they can browse and operate your site effectively. Here’s how our website covers some of the most important screen-reader requirements, alongside console screenshots of code examples:
Screen-reader optimization: we run a background process that learns the website’s components from top to bottom, to ensure ongoing compliance even when updating the website. In this process, we provide screen-readers with meaningful data using the ARIA set of attributes. For example, we provide accurate form labels; descriptions for actionable icons (social media icons, search icons, cart icons, etc.); validation guidance for form inputs; element roles such as buttons, menus, modal dialogues (popups), and others. Additionally, the background process scans all the website’s images and provides an accurate and meaningful image-object-recognition-based description as an ALT (alternate text) tag for images that are not described. It will also extract texts that are embedded within the image, using an OCR (optical character recognition) technology. To turn on screen-reader adjustments at any time, users need only to press the Alt+1 keyboard combination. Screen-reader users also get automatic announcements to turn the Screen-reader mode on as soon as they enter the website.
These adjustments are compatible with all popular screen readers, including JAWS and NVDA.
Keyboard navigation optimization: The background process also adjusts the website’s HTML, and adds various behaviors using JavaScript code to make the website operable by the keyboard. This includes the ability to navigate the website using the Tab and Shift+Tab keys, operate dropdowns with the arrow keys, close them with Esc, trigger buttons and links using the Enter key, navigate between radio and checkbox elements using the arrow keys, and fill them in with the Spacebar or Enter key.Additionally, keyboard users will find quick-navigation and content-skip menus, available at any time by clicking Alt+1, or as the first elements of the site while navigating with the keyboard. The background process also handles triggered popups by moving the keyboard focus towards them as soon as they appear, and not allow the focus drift outside it.
Users can also use shortcuts such as “M” (menus), “H” (headings), “F” (forms), “B” (buttons), and “G” (graphics) to jump to specific elements.
We aim to support the widest array of browsers and assistive technologies as possible, so our users can choose the best fitting tools for them, with as few limitations as possible. Therefore, we have worked very hard to be able to support all major systems that comprise over 95% of the user market share including Google Chrome, Mozilla Firefox, Apple Safari, Opera and Microsoft Edge, JAWS and NVDA (screen readers).
Despite our very best efforts to allow anybody to adjust the website to their needs. There may still be pages or sections that are not fully accessible, are in the process of becoming accessible, or are lacking an adequate technological solution to make them accessible. Still, we are continually improving our accessibility, adding, updating and improving its options and features, and developing and adopting new technologies. All this is meant to reach the optimal level of accessibility, following technological advancements. For any assistance, please reach out to