BFSG 2025: Accessible E-Commerce for B2B Retailers

The BFSG defines accessibility requirements for products and services placed on the market or provided after June 28, 2025. For e-commerce, services in electronic commerce are particularly relevant: web stores selling goods or services to consumers must meet the requirements of the harmonized standard EN 301 549. This standard references the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as the minimum standard for web content.

The legal situation for pure B2B stores requires nuanced consideration. The BFSG primarily targets consumer transactions. A B2B store that sells exclusively to commercial customers and offers no consumer access formally falls outside the scope of the law. In practice, however, this distinction is problematic: many B2B stores are accessible to unregistered visitors, some operate hybrid models with B2C components, and market surveillance authorities have not yet communicated a clear boundary. From a risk management perspective, implementing accessibility is therefore strongly recommended for B2B retailers as well.

Independent of legal obligations, there are compelling business reasons for accessibility in B2B. Buyers with visual impairments, motor limitations, or age-related restrictions operate in the business customer environment as well. An accessible store opens up this user group and simultaneously improves overall usability for all users. According to a study by the German Retail Association, 15 percent of all online users directly benefit from accessibility measures (HDE, 2024).

The Web Content Accessibility Guidelines in the current version 2.2 constitute the international standard for accessible web content. Although the BFSG formally references WCAG 2.1, aligning with the newer version 2.2 is recommended as it includes additional success criteria for mobile interaction and cognitive accessibility. The WCAG is based on four fundamental principles that every element of a web store must satisfy.

WCAG 2.2 introduces several new success criteria compared to its predecessor that are directly relevant for e-commerce stores. Criterion 2.4.11 (Focus Not Obscured) requires that focused elements are not completely hidden by other content -- a common problem in stores with sticky headers, cookie banners, or overlay dialogs that can obscure form fields or buttons.

Criterion 2.5.7 (Dragging Movements) mandates that functions requiring drag movements must also be accessible via simple clicks. In the B2B context, this particularly affects quantity selection sliders, drag-and-drop sorting in order lists, and carousel elements in product presentations. An alternative interaction method must be available for every drag movement.

Particularly relevant for B2B stores with registration and ordering processes is criterion 3.3.7 (Redundant Entry). It requires that information a user has already entered is not requested again -- or that previously entered data is offered as a pre-selection. In checkout, this means: if the billing address has already been captured, the shipping address must be pre-selected as a copy and only changed when different.

An analysis by WebAIM shows that 96.3 percent of all examined homepages have at least one WCAG error (WebAIM, 2025). Certain deficiencies occur particularly frequently in B2B stores, as the complexity of the interface -- with extensive product filters, nested forms, and dynamically loaded content -- creates additional accessibility challenges.

The five most common problems in B2B stores are: missing or meaningless alternative text for product images, insufficient color contrast in navigation and action buttons, dropdown menus and filter bars not accessible via keyboard, missing form labels in checkout and registration processes, and inadequate ARIA markup for dynamically loaded content such as cart updates or search results.

Particularly critical in the B2B context are complex ordering processes. Quick-order forms with CSV upload, multi-level approval workflows, and order lists with hundreds of line items must be not only functional but also accessible to users with assistive technologies. A screenreader user must be able to understand which step of the ordering process they are in, which fields are required, and what actions buttons trigger.

Keyboard navigation is the single most important criterion for accessibility and simultaneously one of the most frequently violated standards. Every interactive element in the store -- links, buttons, form fields, dropdown menus, tabs, modal dialogs -- must be reachable via the Tab key. The focus order must be logical and correspond to the visual layout.

For B2B stores with complex product filters, implementation is particularly demanding. Filters with checkboxes, sliders, and nested categories must be keyboard operable without requiring the user to tab through dozens of steps to reach the desired filter. Skip links that jump directly to the main content or filter bar, and ARIA landmarks that semantically mark page regions, help here.

The focus indicator -- the visual highlight of the currently focused element -- must be clearly visible. WCAG 2.2 strengthens requirements for the focus indicator with the new success criterion 2.4.13: the focus indicator must have a minimum size and contrast to be recognizable even for users with limited vision. A subtle outline is often insufficient; a clearly visible focus ring with at least 2 pixel width and a 3:1 contrast ratio against the background is the recommended solution.

Accessible Rich Internet Applications (ARIA) supplements HTML with additional information for assistive technologies. In the context of a B2B store, ARIA attributes are particularly important for dynamic content that changes without page reload: cart updates, search results, filter changes, and status messages. Without ARIA live regions, a screenreader user does not notice these changes.

The golden rule with ARIA is: no ARIA is better than bad ARIA. Semantic HTML -- button instead of div with onclick, nav instead of div with role=navigation, input with label instead of placeholder text -- solves the majority of accessibility problems without additional ARIA attributes. ARIA comes into play when native HTML elements are insufficient, such as for tabs, accordions, tree views, and complex widgets.

For the checkout process of a B2B store, an ARIA stepper implementation is recommended that communicates to the screenreader user the current step, total number of steps, and completion status of each step. Required fields must be marked with aria-required=true, and validation errors must be linked to corresponding error messages via aria-describedby.

Reliable accessibility testing combines automated testing tools with manual tests. Automated accessibility tests and browser developer tools detect approximately 30 to 40 percent (project experience) of all WCAG violations (W3C/WAI): missing alt text, contrast issues, missing form labels and invalid ARIA attributes. These tests should be integrated into the CI/CD pipeline to automatically detect regressions with every deployment.

The remaining 60 to 70 percent (project experience) of issues require manual testing. This includes: keyboard navigation through the entire ordering process, testing with the screen readers available on Windows, macOS and iOS, checking logical reading order, evaluating the clarity of error messages, and contextual review of ARIA attributes. Additionally, user testing with people with disabilities is recommended, as it uncovers usability problems that even experienced auditors may miss.

WCAG 2.2 Level AA requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text (from 18pt or 14pt bold). For non-text elements such as icons, form borders, and focus indicators, a minimum contrast of 3:1 applies. Many B2B stores use corporate colors that do not meet these requirements -- such as light gray text on white backgrounds or colored buttons with white text on too-light backgrounds.

Adapting the color palette to WCAG requirements often requires balancing corporate design with accessibility. In practice, most color conflicts can be resolved by choosing text colors one to two shades darker and slightly lightening background colors. For B2B, red-green differentiation is also relevant: status indicators and inventory traffic lights should not be coded exclusively through color but additionally through icons or text labels.

Shopware in its current version already includes some accessibility features, particularly semantic HTML in the default theme, keyboard navigation for the main navigation, and language declaration. However, gaps remain in practice that must be closed through theme customizations or plugins. The checkout process, product filters, and custom Shopping Experiences typically require manual remediation.

A systematic approach to BFSG implementation in Shopware comprises four phases: First, a WCAG audit that documents the current state and prioritizes deficiencies. Second, theme adaptation -- color contrast, focus indicators, font sizes. Third, template overhaul -- semantic HTML, ARIA attributes, form labeling. And fourth, implementing automated accessibility tests in the deployment pipeline to prevent regressions with future updates.

Violations of the BFSG can be penalized with fines of up to 100,000 euros. Market surveillance is the responsibility of state authorities, which can conduct both proactive inspections and complaint-driven reviews. Beyond the fine risk, competitors or consumer protection associations may issue cease-and-desist notices, asserting BFSG violations as unfair competition under the UWG.

Companies must also provide an accessibility statement on their website that describes conformance status, identifies known limitations, and offers a feedback mechanism. This statement must be reachable from every page of the store and regularly updated. The absence of the statement constitutes a standalone BFSG violation.

Enforcement practice is currently evolving dynamically. Market surveillance authorities of the federal states have begun systematically reviewing e-commerce offerings. Initial spot checks focus on companies with high revenue volumes and publicly accessible stores. Organizations such as the Federal Centre for Accessibility offer guidance but also act as complainants in cases of violations. For B2B retailers relying on the legal gray area, this creates an increasing risk as authorities gradually specify their interpretation of the scope of application.

When implementing BFSG compliance, a risk-based prioritization is recommended. Not all WCAG criteria have the same urgency. Critical deficiencies that block access to core functionality should be fixed immediately: missing keyboard navigation in checkout, inaccessible required forms, and missing language declaration. In a second phase, deficiencies that restrict usage but do not completely prevent it follow: insufficient contrasts, missing alt text, and inadequate focus indicators. Cosmetic improvements and advanced ARIA optimizations form the third phase.

Independent of legal requirements, accessibility is a quality standard that improves usability for all users. Semantic HTML and well-designed keyboard navigation benefit every user, not just people with disabilities. In the B2B context, where efficiency and speed in ordering are decisive, accessible design leads to measurably higher user satisfaction and faster task completion.

Investing in accessibility pays off in the long run: the initial effort for a WCAG audit and implementation of prioritized measures for a typical B2B store ranges from 5,000 to 20,000 euros depending on complexity and starting state. Compared to potential fines, reputational risk, and missed business opportunities, this is a manageable investment with lasting value.

The growing importance of ESG criteria in supplier selection reinforces this trend: large procurement organizations already assess whether their suppliers provide accessible digital offerings. A B2B store that is WCAG 2.2 compliant positions itself as a responsible and forward-thinking business partner.

From an SEO perspective as well, accessibility brings measurable benefits. Search engines positively evaluate semantically correct HTML, meaningful alt text, and clear page structure. Google considers Core Web Vitals, which can be directly improved with accessible, performant code. Accessible stores typically load faster, have better internal linking through skip links and ARIA landmarks, and offer search engine crawlers a clearer content structure. These synergies between accessibility and search engine optimization make the investment doubly valuable.