Magento 2 Accessibility Statement for the BFSG: Maintain and Publish
SKU: ACCESSIBILITYSTATEMENT1
- structured form for conformance level and limitations
- feedback contact, review date and version per store view
- footer link and checkout hint added automatically
- reminder for regular reviews
Einmaliger Kauf · inkl. 12 Monate Updates · zzgl. MwSt.
Magento 2 Accessibility Statement: mandatory details in structured fields, not a wall of text
With the Magento 2 Accessibility Statement from Mironsoft you maintain the accessibility information of your shop in a guided admin form. Conformance level, known limitations, review method, review date and feedback contact sit in fixed fields and are output as a clean, semantic page. Every change creates a version, every store view gets its language version, and the footer link appears by itself. The module runs on Alpine.js in the Hyvä theme without an extra library. Which content your shop must provide is for you and your legal adviser to decide.
Guided form
Fields for conformance level, limitations, method and date prevent mandatory points from being forgotten.
Known limitations
Capture every inaccessible spot with a description, a reason and an alternative.
Feedback contact
Name, email, phone and the usual response time appear prominently on the page.
Versions and date
Each change stores a version with a change note, and the review date is output automatically.
Per store view
German and English versions are kept apart, each with its own URL key and matching links.
Accessible output
The page uses a heading hierarchy, lists and sufficient contrast, so it meets accessibility needs itself.
Why online shops need a Magento 2 Accessibility Statement
Since 28 June 2025 the German Accessibility Strengthening Act (BFSG) applies. Among other things it covers services in electronic commerce with consumers, which includes many online shops. Micro-enterprises can fall under an exemption that depends on headcount and turnover. Whether your shop is affected is something to check with your legal adviser. Affected providers must inform consumers about the accessibility of their offer, and in practice this is often done with an accessibility statement. Merchants therefore search for Magento 2 Accessibility Statement, Magento 2 BFSG or Magento 2 accessibility mandatory information.
Magento ships no template for this. Many shops create a CMS page, copy text from a sample and forget the review date or the feedback contact. With the Magento 2 Accessibility Statement as a module you get a repeatable process: fill in, publish, review regularly. The module is not legal advice and does not replace an accessibility audit of your shop.
Fill in the Magento 2 Accessibility Statement: conformance level and limitations
The admin form guides you through the statement step by step. You choose the conformance level, the applied standard, such as WCAG 2.1 level AA or EN 301 549, and the review method, for example self-assessment or external audit. After that you capture each known limitation as its own row with description, reason and a possible alternative.
- Conformance level and standard from selection lists
- Limitations as repeatable rows with an alternative
- Review method and reviewing body freely named
Feedback contact and enforcement notes on the page
Visitors must be able to report barriers. The module outputs the feedback contact prominently: name, email address, phone and optionally the usual response time. You can also store a note about the competent body for complaints, which you agree with your legal adviser. Incoming mail goes to your normal mailbox; the module stores no visitor data.
- Contact block with email, phone and response time
- Free field for a note on the competent body
- No visitor data stored in the module
Versions, review date and reminder for the Magento 2 Accessibility Statement
Every save creates a new version with a change note and the editor’s name, so you can later trace when which detail changed. You enter the date of the last review yourself, while the creation date stays fixed. If you like, an admin message reminds you after a configurable number of months to review the statement, for instance after a relaunch or a theme update.
- Version history with change note and editor
- Creation date fixed, review date editable
- Reminder after a configurable number of months
A language version per store view and automatic linking
Each store view receives its own version with its own URL key. The module places the link in the footer and optionally in the checkout and the customer account, so the statement can be reached from any page. The output is semantic HTML with headings, lists and sufficient contrast. Hreflang links between the language versions are set by your existing SEO module or the theme.
- Own URL key per store view
- Link in the footer, optionally in checkout and account
- Semantic output without extra script
Where the Magento 2 Accessibility Statement helps in everyday shop work
Typical situations in which a maintained statement brings order.
Shop before a relaunch
The state of accessibility is documented and updated after the relaunch with a new review date and version.
Several country stores
The Magento 2 Accessibility Statement gives each store view its version in the right language, without duplicating CMS pages by hand.
Agency with many shops
The structure is the same in every shop while the content differs, which speeds up handovers to clients.
Shop with known gaps
Limitations are described openly and paired with an alternative instead of being left out.
Magento 2 Accessibility Statement: CMS page or module compared
The difference between a copied page and maintained data.
| Topic | Without module | With Mironsoft Accessibility Statement |
|---|---|---|
| Mandatory points | Copied from a sample, quickly incomplete | Guided fields in a fixed order |
| Changes | Page overwritten, no trace | Version history with note |
| Review date | Forgotten or outdated | Own field and reminder |
| Languages | Duplicate CMS pages one by one | Version per store view |
| Linking | Footer link by hand | Automatic in the footer and optionally in checkout |
How we set up the Magento 2 Accessibility Statement for you
The process after you order.
Alignment
We clarify store views, languages and which details your legal adviser expects for your shop.
Installation
We install the module and set up the Magento 2 Accessibility Statement for your store views.
First fill
We enter your status, limitations and contact, or move your existing text into the fields.
Linking
We place the footer link and optionally the checkout hint to match your Hyvä theme.
Handover
Your team gets an introduction to versions, review date and reminder.
Scope compared to the accessibility toolbar and other legal modules
The Magento 2 Accessibility Statement documents the state of your shop. The Mironsoft accessibility toolbar is a control for visitors, for example for contrast and font size, and creates no statement. A toolbar replaces neither an accessible shop design nor the information about accessibility.
Both modules can be combined. The output uses Alpine.js in the Hyvä theme, without jQuery and without an extra library. Whether and to what extent your shop is affected is for the shop owner to assess; the module is not legal advice.
No download, but a personal setup
Accessibility Statement is not listed here as a ready-made download for self-installation. The purchase is an order for a service: after the purchase we contact you, install the module in your shop and agree fields, languages and linking with you.
Frequently asked questions
Everything important about mandatory details, versions, languages and how the purchase works.
How can I create an accessibility statement in Magento 2?
How can I show the accessibility feedback contact in Magento 2?
Does my shop need an accessibility statement?
How can I keep the Magento 2 Accessibility Statement up to date?
Can I publish the statement in several languages?
Is the footer link added automatically?
Does the Magento 2 Accessibility Statement make my shop accessible?
What is the difference to the accessibility toolbar?
Does the module work in the Hyvä theme?
Can I download it myself?
Recently Viewed Products
Magento 2 Accessibility Statement – Mironsoft