Familypark is committed to digital accessibility for people with disabilities.
We continuously improve the user experience for everyone and apply the appropriate accessibility standards.

To support this effort, we have commissioned Ipedis to conduct a comprehensive accessibility audit of our website, including both automated and manual testing.

Conformance Status

The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility for people with disabilities.
The Familypark website is not compliant with WCAG 2.2 Level AA.
“Not compliant” means that the content does not meet accessibility standards.

Technical Specifications

Technologies used in the creation of the website:

• HTML5
• CSS
• JavaScript

The website was tested using the following combinations of browsers and screen readers:

• Google Chrome
• NVDA

Accessibility testing tools used:

• Web Developer Toolbar
• WAVE
• WCAG Contrast Checker
• Accessible Color Picker
• Taba11y
• axe DevTools – Web Accessibility Testing
• Assistant RGAA
• PDF Accessibility Checker (PAC) 2024

Tested pages of the website:

• Homepage
• Attractions overview including filters
• Legal notice / General Terms and Conditions
• Contact
• Help / FAQ
• Party registration form
• Götterblitz (attraction detail page)
• Prices
• Opening hours
• Birthday party
• Online shop checkout

Our Commitment

Familypark strives for broad compliance with WCAG 2.2 Level AA. Improvements already achieved include:

• Content reading direction is correctly specified when needed.
• The website does not restrict screen orientation – both portrait and landscape view are supported.
• Texts can be enlarged up to 200% without loss of content or functionality.
• Content adjusts to different screen sizes (as narrow as 320 px) without information or functionality loss; horizontal scrolling is minimized.
• Moving, blinking, or scrolling content can be paused, stopped, or hidden by the user.
• Keyboard navigation follows a logical order that matches the visual layout.
• Keyboard focus is visible and has sufficient contrast.
• Actions triggered by long presses or swipes can be canceled or confirmed to prevent unintended execution.
• Visible voice command labels match programmatic names to enable effective voice control.
• The main language of each page is correctly declared to enable accurate screen reader interpretation.
• Repeated navigation elements are consistently placed across all pages.
• Elements with identical functionality are consistently presented.

Remaining Accessibility Limitations

Despite all efforts, some limitations remain that Familypark will continue to address:

• Some non-text content (e.g. images, icons, graphics) lacks appropriate alternative text.
• Video content is not always accompanied by transcripts or audio descriptions.
• Visual structures (e.g. lists) are not always correctly conveyed to assistive technologies.
• Some form fields do not support autocomplete due to missing attributes.
• Information is sometimes conveyed by color alone, without additional visual or textual indicators.
• Contrast between text and background is insufficient for some elements (e.g. secondary text, button labels).
• Some text is embedded as an image without an accessible alternative.
• Interactive elements (e.g. buttons, form fields) do not always meet minimum contrast requirements.
• Content that appears on hover or focus (e.g. calendars, menus) may not be operable or dismissible via keyboard.
• Some functions are not fully operable by keyboard alone.
• Users may become trapped in certain components without a way to navigate using only the keyboard.
• A “skip to main content” feature is partially missing.
• Page titles do not always reflect the actual page content.
• Link texts are unclear when taken out of context.
• Headings or form field labels are sometimes insufficiently descriptive.
• Focus on interactive elements is not always clearly visible.
• Foreign-language text is not always properly marked (e.g. missing “lang” attribute).
• Input errors are not always clearly indicated.
• Form fields may lack instructions or input labels.
• Suggestions for correcting input errors are often missing.
• Custom components may not correctly provide name, role, or value to assistive technologies.
• Status messages (e.g. form validation feedback) are not always announced automatically by screen readers.

Feedback and Contact

If you cannot access content or services, please contact us.
You will then receive an accessible alternative or the content in another form.

Contact: Familypark customer service
Email: [email protected]