Bitron Right of Withdrawal vs Filikod – ALT Text Audit & Bulk Management

From 19 June 2026, EU member states require every consumer-facing online shop to provide an online withdrawal function — not just static information, but a continuously available electronic interface where the consumer can declare intent to withdraw, and from which the shop sends an automatic confirmation on a durable medium. In Hungary the same rule applies through the amendment of Government Decree 45/2014. Bitron Right of Withdrawal delivers exactly that, accessibly. What the plugin does A continuously available, accessible withdrawal form — embeddable via the [bitrow_form] shortcode or the Withdrawal Form Gutenberg block, so it drops into any classic-editor page, a block-built layout, or a page builder that handles either. Tight WooCommerce integration: the form is surfaced to logged-in customers as a Withdrawal item in their My Account menu, but only while they have at least one order still inside the window — so a customer with nothing eligible doesn’t see a dead link. A withdrawal link is automatically attached to WooCommerce’s customer order emails (processing, completed, invoice) while the window is open — a discreet text link (not a prominent button) to avoid accidental clicks. Its position in the email (top, after the order details, or bottom — bottom by default) and both the surrounding message text and the link label are configurable under Settings → Email. HTML and plain-text variants, with a filter to extend the list of carrier emails. Guest and logged-in customer paths. A logged-in customer sees a select of their own in-window orders. For guests, optional email verification: with the free OneCode Login plugin active, the guest proves they own their email with a one-time code, and the form then loads that email’s orders just like for a logged-in customer — closing the gap where anyone who knew an order number and the billing email could file on someone else’s behalf. When email verification is not in force, an unverified guest is never shown any order data: instead of looking up an order, they file a free-text withdrawal declaration (no order is matched server-side, no line items or totals are disclosed), which is recorded flagged as unverified for the shop to match by hand. Order data is therefore only ever shown to logged-in or email-verified customers. Item-level partial withdrawal. After the customer picks an order, they tick exactly which line items (and quantities) they want to withdraw from — the form is not all-or-nothing. Bank-account capture for non-card payments. When the original gateway can’t refund automatically (e.g. cash on delivery, bank transfer), the customer enters a Hungarian IBAN or domestic GIRO account number — validated client- and server-side with MOD-97 / CDV checks — so the shop has everything to wire the refund manually. Customizable form copy and brand colors. An optional intro paragraph above the form and the submit-button colors (background + text) are configurable from Settings → Form, with a live WCAG contrast meter that announces the ratio as you type so a custom brand color cannot quietly drop below AA. An “advanced” panel additionally exposes the form body text, wrapper background, and input/fieldset border colors for themes that need the form to blend in — these three are not contrast-checked and carry an explicit “you own the contrast” warning. The same values can be overridden per-instance through [bitrow_form] shortcode attributes or the block’s Inspector panel. Automatic confirmation email to the customer (durable medium) and notification to the shop admin, with editable subject and body templates for both — empty fields fall back to safe i18n defaults so the plugin is functional out of the box. The admin notification recipient is a configurable email address (defaults to the site administration email); leave it empty to switch admin notifications off. Optional business-customer exclusion: because the right of withdrawal is a consumer right, shops that also sell to VAT-registered businesses can switch the online form off for orders carrying a business marker (e.g. a VAT-number checkout field). Business buyers are shown a contact pointer instead; consumer orders are unaffected. It’s a technical filter, not legal advice. Per-product and per-category withdrawal exemptions for the CRD §16 / 45-2014 §29 carve-outs (perishables, custom-made, sealed digital downloads, etc.). The withdrawal form still shows exempted items inside an eligible order so the customer sees what they bought, but the quantity input is locked at zero with a visible “Not eligible for withdrawal” badge; orders that consist entirely of exempt items are blocked at step 1 with a contact pointer. A separate Settings → Exclusions tab manages the lists with searchable autocompletes. Exclusion type split — excluded by law vs waivable. The exclusion settings separate two legally distinct cases: “excluded by law” items (perishables, custom-made, opened sealed goods) where the right never applies and no customer action is involved, and “waivable” items where the right exists but the customer can expressly give it up. Each case has its own product and category pickers; existing exclusions keep behaving as “by law”. Checkout withdrawal waiver. For waivable goods (typically digital content), the shop can show a consent checkbox at checkout through which the customer expressly waives the right of withdrawal for the affected items. It appears only when the cart actually contains a waivable item, works on both the classic shortcode checkout and the block-based (Store API) checkout, can be optional or mandatory, and records the consent on the order as evidence (timestamp, IP, a fingerprint of the statement text, the covered products and the mode). Off by default; enable and word it under Settings → Exclusions. “Withdrawals” hub in the customer’s My Account area — a single durable, log-in-gated landing page for everything withdrawal-related: a one-click button to start a new declaration (when the form page is configured), plus the full list of past declarations submitted from the account (reference number, date, order link, items, refund preference, status). The menu item appears only when the customer has at least one past record OR an order still inside the withdrawal window; the list itself is privacy-scoped to the customer’s own account email and never reveals records filed under a different email. Minimal record-keeping with unique BITROW-XXXXXX references for evidentiary value, plus a per-record detail page in the admin. Admin can mark a record as closed (and reopen it) once the case is resolved, with timestamp and the closing user recorded — keeps the working list focused on what’s still pending. Withdrawal status on the order screen. When an order has an associated withdrawal, the WooCommerce order-edit screen shows a “Right of withdrawal” panel with the withdrawal’s status and a direct link to its record. Optional withdrawal column on the orders list. A Settings → General switch (off by default) adds a column to the WooCommerce orders list flagging which orders have a withdrawal and its status (a dash when none). HPOS- and legacy-orders compatible. WCAG 2.1 AA accessibility throughout — programmatic labels, focus management, live regions, sufficient contrast. GDPR integration with WordPress’ personal data export and erase tools, plus a suggested paragraph for the Privacy Policy Guide. Compatibility The plugin integrates with WooCommerce orders. It declares HPOS (High-Performance Order Storage) compatibility and uses the WooCommerce CRUD API throughout. WooCommerce is referenced for compatibility only — the trademark is not used in the plugin name or slug. Important — what this plugin does NOT do This is a technical tool, not legal advice, and does not by itself guarantee legal compliance. The plugin does not generate Terms of Service text, privacy-policy text, or other legal content — those must be prepared by your own lawyer. The confirmation email contains only a factual acknowledgement (received, when, with which ID, what content); any “what happens next” wording is the shop operator’s own policy and must come from you. The plugin records each withdrawal and notifies you, but it does not issue refunds automatically. Refunds remain a deliberate admin action through WooCommerce’s standard refund interface. Privacy The plugin stores only what is necessary to acknowledge and document the withdrawal: name, email, order reference, optional note, timestamps and a unique identifier. No IP address is stored in plain text. On plugin removal the stored records are kept by default (so an accidental deactivation cannot destroy evidence); a setting lets you opt in to deletion at uninstall. Pro version The free plugin covers the full legal compliance core on its own. Bitron Right of Withdrawal Pro adds a convenience and automation layer on top, for shops that process withdrawals regularly: One-click WooCommerce refund — issue the refund straight from the withdrawal record, instead of re-entering it by hand in WooCommerce. Status management and history — a richer status workflow (received, in progress, goods returned, refunded, rejected) with a full audit trail of who changed what and when. Automation rules — define rules that act on incoming withdrawals automatically (status transitions, notifications), so routine cases handle themselves. Custom form fields — add your own fields to the withdrawal form and store them on the record. Searchable admin + CSV export — find any declaration fast and export the list for accounting or reporting. Webhooks — push withdrawal events to your CRM, ERP or any external system in real time. REST API — read and manage withdrawal records programmatically from your own integrations. The Pro plugin is standalone: it contains the full compliance core plus the convenience layer, so you install it instead of the free plugin, not alongside it. Pro adds convenience, not extra compliance — the free plugin already makes you compliant. Learn more and see pricing

Most WordPress sites have broken ALT text, and most site owners have no way to measure it. Missing, generic, duplicated or too-short ALT text quietly hurts your accessibility score and your image SEO. The problem stays invisible until it is too late. Filikod scans your entire media library, gives you an ALT Quality Score from 0 to 100%, and gives you the tools to fix everything in bulk, directly inside WordPress. No external API. No credits to buy. No complex setup. You write the ALT text. You stay in control. Full documentation and guides on filikod.com Who is Filikod for? Filikod is built for: SEO professionals who want ALT text treated as a measurable ranking signal, not an afterthought Accessibility-focused teams who need a structured audit to meet WCAG guidelines Content managers with large media libraries who need to fix issues fast, in bulk Agencies managing multiple WordPress sites who need a repeatable quality process Anyone who wants full control over their ALT text quality at scale, without external services or paid credits ALT Text Audit and Quality Score Filikod scans your entire media library and instantly flags: Missing ALT: images with no ALT attribute at all Generic ALT: meaningless values like “image”, “photo”, “logo”, “thumbnail”, “untitled” Too Short ALT: descriptions too brief to be useful for accessibility or SEO Duplicated ALT: the same ALT text reused across multiple images You get a clear ALT Quality Score from 0 to 100% plus a breakdown by issue type, so you always know exactly what to fix first. This turns ALT text from a vague, invisible problem into a measurable system you can actually improve, like a health score for your media library. Bulk ALT Management Editing ALT text one image at a time is the reason most people never finish. Filikod lets you: Filter images by issue type (missing, generic, short, duplicated) Edit ALT text inline, directly from the audit view Save instantly without leaving the page Fix dozens or hundreds of images in minutes Built for real media libraries with thousands of images, not tidy demos with five. Context-Based Editing Good ALT text requires context. What is this image actually about on this page? Filikod shows you where each image is used (which post or page) so you can jump directly to the content and write accurate, relevant ALT text. No guesswork. Native Media Library (Media > Library) See ALT health where you already work: Filikod adds ALT Status badges directly in Media > Library, in both list and grid views. List view: a dedicated ALT Status column with one badge per issue, or a green Alt: OK when everything is fine Grid view: badges as an overlay on each thumbnail so you can scan your entire library at a glance Attachment details: an ALT Status field that updates live as you type, so you see the result before saving Multiple badges can appear on the same image when several issues apply. The cache refreshes automatically whenever ALT text is changed anywhere in WordPress. Optional Automation For teams who need to process large volumes, Filikod includes optional automation tools, all disabled by default: Generate ALT from filename (only for images that have no ALT yet) Remove special characters from ALT text (slashes, dashes, underscores) Remove title attribute from images (reduces redundancy, improves accessibility) Bulk process your entire existing media library in one click Execution order is always enforced: generate ALT from filename, clean special characters, then remove title. Predictable. Consistent. Always yours to control. How Filikod Compares Most ALT text plugins do one thing: auto-generate ALT on upload, often using a paid credit system. Filikod is an ALT audit and bulk management system. It works on your existing library, gives you a measurable quality score, and lets you fix issues at scale with full editorial control. What only Filikod does: ALT Quality Score (0 to 100%) across your entire library ALT Status badges in the native Media Library (list column, grid overlay, attachment details) with live updates after save Detects generic ALT values like “photo”, “image”, “logo” Detects duplicated ALT text reused across multiple images Detects ALT text that is too short to be useful Bulk filtering by issue type (missing, generic, short, duplicated) Works on images already in your media library No external API, no credits, no subscription required Full editorial control: you write and validate every ALT text If you want full visibility and control over your ALT text quality at scale, Filikod is exactly that. Compatibility Works with any theme Compatible with Elementor, Divi, Gutenberg, WPBakery and most major page builders Single site and multisite supported No external services required, runs entirely inside WordPress Learn more at filikod.com