This site has limited support for your browser. We recommend switching to Edge, Chrome, Safari, or Firefox.

Holistic organic anti-aging treatments for professional use

Accessibility

Document created with the help of the sample letter assistant of HB Legal Tech GmbH


Preliminary remarks:
From June 29, 2025, the legal information requirements regarding accessibility in online shops must be met.
Shop operators must then have a separate button in the central shop navigation that provides a clear
label such as “Accessibility”, a statement on the current status of accessibility of their
Provide shops.
Note: This template was prepared conscientiously and with the utmost legal care. It makes no claim
for completeness and accuracy and does not replace legal advice. It offers assistance for
the creation of an accessibility statement and is to be understood as a proposal for possible regulations.
Independent testing and adjustment by the user is recommended.
Document created with the help of the sample letter assistant of HB Legal Tech GmbH


Accessibility Statement


Introduction
We strive to make our website www.beauetal.com in accordance with the Accessibility Strengthening Act
(BFSG) and the Ordinance on the Accessibility Strengthening Act (BFSGV). Our
The aim is to provide all users, especially people with disabilities, with easy and unrestricted
to enable use.
This statement describes the accessibility status of our website, the measures taken to eliminate
Barriers and opportunities for contact and complaint.
Scope of this declaration
This accessibility statement applies to the website www.beauetal.com.
Service description
On this website we offer the following services:
Were
Services: Consulting for beauty salons, training for treatments and products,
Management consulting
digital content: e-books
In addition, this website contains a blog .

Frequently asked questions and answers are also included on this website.

Status of compliance with the requirements
Our website partially meets the requirements of the BFSG in conjunction with the BFSGV, the applicable technical
Standards of the European standard EN 301 549 and the Web Content Accessibility Guidelines WCAG 2.1. WCAG conformance corresponds to level AA.
Measures implemented to remove barriers
The accessibility requirements on our website are met in particular by the following measures:
Clearly recognizable font sizes and strong color contrasts
Navigability via mouse and keyboard
Document created with the help of the sample letter assistant of HB Legal Tech GmbH


Alternative texts for images
Subtitles and audio descriptions in videos
Easy-to-read and understandable language
Additional text instructions when mandatory input fields are not filled in
Compatibility with all common screen readers (screen reading aids)
Customizable display options for different devices (smartphones, tablets, desktop computers, etc.)
Non-accessible content
Despite our efforts, the following content is not accessible:
1. Missing semantic main heading (H1) Problem: On the homepage there is no clearly defined H1
marked element present – ​​the page name or claim is not correctly marked as H1.
This leaves screen reader users without a central orientation element. Standard/Requirement: WCAG 2.1 AA
1.3.1 (Info and Relationships); DIN EN 301 549 5.2.2 Reasonableness: Yes. Effort: HTML template to create a
Add H1 marking in the header (approx. 0.5–1 hour of development time). 2. Insufficient labeling of
Form elements Problem: The search field (“Search”) and the newsletter registration do not have
correctly with linked label text (Label for/ID), but only placeholder texts. Screen readers can thus
The function of the field cannot be reliably output. Standard/Requirement: WCAG 2.1 AA 1.3.1; WCAG 2.1 AA
4.1.2 (Name, Role, Value); DIN EN 301 549 5.3.1 Reasonableness: Yes. Effort: Labels in the Shopify theme
Add or supplement aria-label (approx. 1 hour of development work). 3. Incomplete alternative texts for images
Problem: Many product and advertising images contain only generic text like "Image" or lack an alt attribute. As a result, visually impaired users receive no description of the image content. Standard/Requirement:
WCAG 2.1 AA 1.1.1 (Non-Text Content); DIN EN 301 549 5.4.1 Reasonableness: Yes. Effort: Product and
Provide content images with meaningful, short alt texts (approx. 2–5 minutes per image). 4. Missing visible
Focus indicators Problem: After pressing the Tab key, there is no focus indicator on interactive elements (buttons, links).
clearly visible frame or background change recognizable – many custom styles set outline: none.
Keyboard-only users become disoriented. Standard/Requirement: WCAG 2.1 AA 2.4.7 (Focus Visible);
DIN EN 301 549 5.2.4 Reasonableness: Yes. Effort: Adapt CSS to use standard focus or custom styles with
high contrast (approx. 1 hour). 5. Insufficient color contrast in navigation texts Problem:
Navigation elements (e.g. menu item “Knowledge”) and footer links appear in light grey on white
Background with a contrast ratio below 4.5:1. Difficult to read for visually impaired users. Standard/Requirement:
WCAG 2.1 AA 1.4.3 (Contrast Minimum); DIN EN 301 549 5.3.2 Reasonableness: Yes. Effort: Font color in
Change CSS to a darker color value (approx. 0.5 hours). 6. Missing ARIA landmarks and roles Problem: The page
does not use role="banner", role="navigation", role="main" or role="contentinfo". Screen reader users
cannot jump using quick navigation. Standard/Requirement: WCAG 2.1 AA 1.3.1; DIN EN 301 549 5.2.1
Reasonableness: Yes. Effort: Add ARIA landmarks to the HTML template (approx. 0.5 hours). 7. Keyboard Navigability of the Mega Menu Problem: The drop-down main menu (e.g., "Products") can be navigated via
Mouse opens, but does not respond consistently to keyboard events (e.g., Enter/Space, arrow keys), and ariaexpanded attributes are missing. Standard/Requirement: WCAG 2.1 AA 2.1.1 (Keyboard); WCAG 2.1 AA 4.1.2; DIN EN
301 549 5.2.2 Reasonableness: Yes. Effort: Add JavaScript event handlers and ARIA attributes to
to ensure full keyboard support (approx. 4–6 hours). 8. hCaptcha without an accessible alternative
Problem: The hCaptcha widget in the newsletter form is difficult to use for screen readers and hides
Often audio or visual testing tasks without accessible alternatives. Standard/Requirement: WCAG 2.1 AA 1.4.11
Document created with the help of the sample letter assistant of HB Legal Tech GmbH
(Non-Text Contrast for visual testing tasks); WCAG 2.1 AA 4.1.2; DIN EN 301 549 5.5.3 Reasonableness:
No. Reason: Changing provider or implementing a barrier-free alternative requires
in-depth licensing negotiations or expensive custom development (estimated at several thousand euros). 9. No
Subtitles for embedded videos Problem: If videos are embedded on the product pages, there are currently
There are no subtitles or descriptions. Hearing-impaired users cannot understand the content.
Standard/Requirement: WCAG 2.1 AA 1.2.2 (Captions); DIN EN 301 549 5.4.2 Reasonableness: No. Reason:
Professional subtitling for external video productions can cost several hundred euros per video. 10.
Missing adjustment to screen magnification Problem: At 200% browser zoom,
Overlaps in navigation and product lists due to fixed layout widths. Standard/Requirement:
WCAG 2.1 AA 1.4.4 (Resize Text); DIN EN 301 549 5.1.2 Reasonableness: No. Reason: Comprehensive
Switching to fluid, responsive grid layouts requires a major theme overhaul (estimated 20–30 hours).
Development costs). Summary of economically unreasonable points for small businesses
hCaptcha alternative / License costs (point 8) Professional subtitling of videos (point 9) Extensive
Theme revision for Zoom/Responsive (point 10)
We are continuously working to identify and eliminate existing barriers.
We will endeavor to provide an adapted version or accessible alternatives as soon as possible.
Non-accessible content due to economic unreasonableness
Some barriers on our website cannot be removed in the short term due to economic unreasonableness
These include:
Complex interactive applications and special features on our website require significant
financial and human resources to make them fully accessible. We continuously review
Opportunities for improvement, but due to the disproportionately high costs, not all
Remove barriers immediately. This applies to the following applications and functions: 8. hCaptcha without accessible
alternative
Problem: The hCaptcha widget in the newsletter form is difficult to use for screen readers and hides
often audio or visual testing tasks with no accessible alternative.
Standard/Requirement: WCAG 2.1 AA 1.4.11 (Non-Text Contrast for Visual Inspection Tasks); WCAG 2.1 AA 4.1.2;
DIN EN 301 549 5.5.3
Reasonableness: No.
Reason: Changing provider or implementing a barrier-free alternative requires in-depth
License negotiations or expensive individual development (estimated at several thousand euros).
9. No subtitles for embedded videos
Problem: If videos are embedded on the product pages, there are currently no subtitles or
Descriptions are provided. Hearing-impaired users cannot understand the content.
Standard/Requirement: WCAG 2.1 AA 1.2.2 (Captions); DIN EN 301 549 5.4.2
Reasonableness: No.
Reason: Professional subtitling of external video productions can cost several hundred euros per video
cost.
Document created with the help of the sample letter assistant of HB Legal Tech GmbH
10. Lack of adaptation to screen magnification
Problem: At 200% browser zoom, there are overlaps in navigation and product lists because fixed
Layout widths are used.
Standard/Requirement: WCAG 2.1 AA 1.4.4 (Resize Text); DIN EN 301 549 5.1.2
Reasonableness: No.
Reason: Comprehensive conversion to fluid, responsive grid layouts requires major theme overhaul (estimated 20-30 hours of development effort).
Summary of economically unreasonable points for small businesses
hCaptcha alternative / license costs (point 8)
Professional subtitling of videos (point 9)
Extensive theme revision for Zoom/Responsive (point 10)
1. Missing semantic main heading (H1)
Problem: There is no clearly marked H1 element on the homepage – the page name or
Claim is not correctly marked as H1. This means that screen reader users are missing a central
Orientation element.
Standard/Requirement: WCAG 2.1 AA 1.3.1 (Info and Relationships); DIN EN 301 549 5.2.2
2. Insufficient labeling of form elements
Problem: The search field (“Search”) and the newsletter registration do not have a correctly
linked label text (Label for/ID), but only placeholder texts. Screen readers can thus use the function
of the field cannot be reliably output.
Standard/requirement: WCAG 2.1 AA 1.3.1; WCAG 2.1 AA 4.1.2 (Name, Role, Value); DIN EN 301 549 5.3.1
3. Incomplete alternative texts for images
Problem: Many product and advertising images contain only generic text like "Image" or lack an alt attribute. This means visually impaired users cannot access a description of the image content.
Standard/Requirement: WCAG 2.1 AA 1.1.1 (Non-Text Content); DIN EN 301 549 5.4.1
4. Missing visible focus indicators
Problem: After pressing the Tab key, there is no clearly visible
Frame or background change recognizable – many custom styles set outline: none. Keyboard-only users
lose their orientation.
Standard/Requirement: WCAG 2.1 AA 2.4.7 (Focus Visible); DIN EN 301 549 5.2.4
5. Insufficient color contrast in navigation texts
Problem: Navigation elements (e.g. menu item “Knowledge”) and footer links appear in light gray
on a white background with a contrast ratio below 4.5:1. Difficult to read for visually impaired users.
Standard/Requirement: WCAG 2.1 AA 1.4.3 (Contrast Minimum); DIN EN 301 549 5.3.2
Document created with the help of the sample letter assistant of HB Legal Tech GmbH
6. Missing ARIA landmarks and roles
Problem: The page does not use role="banner", role="navigation", role="main" or role="contentinfo".
Screen reader users cannot jump using quick navigation.
Standard/Requirement: WCAG 2.1 AA 1.3.1; DIN EN 301 549 5.2.1
7. Keyboard navigation of the mega menu
Problem: The drop-down main menu (e.g. “Products”) can be opened with the mouse, but does not respond
consistent on keyboard events (e.g. Enter/Space, arrow keys), and aria-expanded attributes are missing.
Standard/Requirement: WCAG 2.1 AA 2.1.1 (Keyboard); WCAG 2.1 AA 4.1.2; DIN EN 301 549 5.2.2
Report barriers, feedback and contact details
If you encounter any barriers on our website or need assistance using the website, please feel free
Please do not hesitate to contact us. We look forward to your feedback and will endeavour to address the reported barriers within
to resolve the problem as quickly as possible within the limits of technical and economic possibilities. You can contact us via the following
contact:
BEAUÉTAL UG ) limited liability) & Co. KG
Maximilianstraße 2, 80539 Munich
hello@beauetal.com
Phone: +49 89 20 500 8 57 18
If you do not receive a satisfactory response to your accessibility notifications or requests,
You should contact the relevant market surveillance authority.
Competent market surveillance authority
MLBF (under construction)
c/o Ministry of Labour, Social Affairs, Health and Equality Saxony-Anhalt
PO Box 39 11 55
39135 Magdeburg
Phone: 0391 567-4530
Email: MLBF@ms.sachsen-anhalt.de
Creation process of this declaration
This statement was created through internal testing.
Methods for testing accessibility:
Document created with the help of the sample letter assistant of HB Legal Tech GmbH
ChatGPT


Updating this statement
This declaration has been prepared with the greatest care and is regularly reviewed and updated to reflect the
to meet current requirements and standards.
Last updated: June 27, 2025
Source: https://www.haendlerbund.de