| 开发者 | studiomeyerio |
|---|---|
| 更新时间 | 2026年7月21日 06:11 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
No tool can guarantee that. The scanner finds the machine-detectable part of WCAG problems (roughly a third), and the generator produces a statement covering the mandatory elements of Anlage 3 BFSG. Manual testing and, where needed, legal review remain your responsibility. The plugin is explicit about this distinction throughout.
No. All checks run in PHP on your own server using the WordPress HTML API. The only HTTP request the plugin makes is a loopback to your own homepage for the site-level checks — the same pattern WordPress Site Health uses.
Broadly: businesses offering products or services to consumers in the EU digitally (e.g. online shops, booking systems) fall under the BFSG since 28 June 2025. Micro-enterprises providing services (fewer than 10 employees and at most €2 million annual turnover) are exempt from the service obligations. When in doubt, ask a lawyer — the plugin ships this hint in the statement UI too.
German, English and Spanish. The plugin admin UI itself is available in English, German and Spanish (full bundled translations).
Yes. If WooCommerce is active, published products are included in the scan scope by default — configurable in the settings.
The scanner checks the rendered content of your posts (blocks and shortcodes are processed). Content injected exclusively by theme templates or builder frontend scripts is covered by the homepage site-level checks only.