Skip to main content

WordPress plugin · for developers & agencies · WCAG 2.2 & EAA

Semanticality™ plugin for WordPress Gutenberg.

Take control of the HTML tags and attributes of your WordPress Gutenberg blocks and implement WCAG/EAA-relevant markup changes at render time in hours – instead of spending months rebuilding theme code*.

“We first built Semanticality™ for our own client projects. It saved us so much time that we now make it available to everyone.”

Dmitry Dugarev · Founder of Barrierenlos℠

Introduction · demo video

Why is real accessibility so hard in WordPress?

You know the feeling: A client loves the design of their new premium theme, but the HTML code generated by Gutenberg is a semantic minefield. This is where Semanticality™ comes in.

Demo video · 7 min · with subtitles

Genuine accessibility arises through correct, semantic HTML code – but this is exactly where developers quickly reach their limits with WordPress: There are hardly any ways to customize the code without completely reprogramming the theme.

Comparison between non-semantic and semantic HTML

Before

Classic WordPress Gutenberg block with incorrect HTML semantics

<div  class="wp-block-card">  <div    class="wp-block-card__title">    My card title  </div>  <div    class="wp-block-card__text">    Your content goes here.  </div>  <div    class="wp-block-card__link"    onclick="location='/mehr'">    Read more  </div></div>
  • No semantic HTML & WAI-ARIA.
  • No way to quickly skip the blocks with a screen reader.
  • It is not clear what is a heading and what is plain text here.
  • Violation of WCAG 2.2 success criteria 1.3.1, 2.4.4, 2.4.10 and 4.1.2 → EAA compliance not achieved***.

After

After customization with Semanticality™ Plugin

<article  class="wp-block-card"  aria-labelledby="card-title-1">  <h3    class="wp-block-card__title"    id="card-title-1">    My card title  </h3>  <p    class="wp-block-card__text">    Your content goes here.  </p>  <a    href="/mehr"    class="wp-block-card__link"    aria-label="Read more about 'My card title'">    Read more  </a></article>
  • Card marked up as article.
  • Identified as a landmark via aria-labelledby.
  • Content hierarchy established with h3 and p.
  • The WCAG 2.2 success criteria 1.3.1, 2.4.4, 2.4.10 and 4.1.2 are met → EAA compliance achieved***.

Especially in the context of the new EAA (BFSG), this is indispensable to meet the legal requirements. Semanticality™ is ideal for implementing the HTML-related measures in a few hours instead of months after an accessibility audit*.

  • The technical basis of your work

    With Semanticality™ you work directly on the HTML structure behind the Accessibility Object Model (AOM). In the Gutenberg block editor, you fix the code visually with rules. The rules are applied at render time.

    • WCAG 2.2 AA
    • EN 301 549
    • BITV 2.0
    • BFSG
    • EAA
    • ISO 40500:2012
    • WAI-ARIA
    • WHATWG HTML
    • ADA

    Accessibility standards you meet

    With Semanticality™ you lay the technical groundwork for key requirements of WCAG 2.2 / EN 301 549 / BITV 2.0 / EAA (BFSG) – wherever semantic HTML and ARIA are needed – without rebuilding your theme**.

  • A robust foundation. For every user.

    Adjust your Gutenberg blocks fast and optimize your website for accessibility** and EAA compliance*** in hours, not months*.

Comparison · overlays, attribute plugins, Semanticality™

More than just an attribute plugin. Granular control. Over every Gutenberg block.

Other plugins often only let you add simple attributes to the main wrapper of a Gutenberg block. Semanticality™ goes crucial steps further and gives you granular control over every single element within your WordPress Gutenberg blocks.

Overlay Widgets

Overlay widgets promise accessibility at the push of a button but are only a plaster. They do not change the underlying code and are usually not sufficient for genuine accessibility or compliance [1].

  • No semantic correction: A div that looks like a button remains a div – unusable for screen readers and not focusable.
  • Legal uncertainty: Since the actual deficiencies remain, overlays offer no guarantee of compliance with laws such as the EAA (BFSG). You risk your customers' compliance.
  • Performance & conflicts: Additional JavaScript slows down the page, causes script conflicts and degrades the user experience.

Other plugins (e.g. Attributes for Blocks)

These plugins offer very limited customization and are not intended for accessibility. They are unsuitable for complex layouts or complete control.

  • Limited customization options: Changes only possible on the main wrapper of a block.
  • No control over nested elements: e.g. a link in a card.
  • HTML tags cannot be changed: e.g. a div cannot be converted into a button.
  • No global rules or dynamic variables: e.g. you can't create one rule for all buttons in a block.
  • Not fail-safe: Static values are saved in the content and can cause unpredictable errors if deactivated.

Semanticality™ Plugin for WordPress Gutenberg

With Semanticality™ you get granular control over the HTML output of every Gutenberg block – dynamically, securely and server-side. You define rules, Semanticality™ implements them automatically in the code. Here is the full range of functions:

  • Element addressing via CSS selector.
  • Change HTML tags (e.g. div to button).
  • Add & remove attributes.
  • Extend attributes (append, change, prepend, replace).
  • Global rules for block types.
  • Local rules for individual blocks.
  • The ability to define rules for child blocks within parent blocks (e.g. create a rule for all paragraphs in a group).
  • Copying and pasting of rules between blocks.
  • Access to WordPress meta fields.
  • Random IDs generated.
  • Live preview of rendered code directly in the block editor.

The result: Up to 10x faster project implementation*, predictable costs and a clear competitive advantage for you and your customers.

Screenshot of the Semanticality™ Rules Editor in the Gutenberg Block Editor

Compatibility · limits · self-check

Is Semanticality™ right for your project?

Anything that goes beyond the structure & semantics of the HTML has to be solved in design, content or JS, not in the markup – and therefore not with Semanticality™ either.

What Semanticality™ Plugin is not intended for:

  • Not a substitute for content work: Meaningful alt texts, clear language, error texts, understandable phrasing and information architecture must be provided editorially.
  • No color/contrast adjustments: Contrast values and non-text contrasts (e.g. 1.4.3, 1.4.11) require CSS/design.
  • No focus styling as such: Visible focus and focus appearance (2.4.7, 2.4.11–2.4.13) require CSS/interaction logic.
  • No layout/reflow handling: Responsive reflow, text spacing, target size (1.4.10, 1.4.12, 2.5.8) are styling topics.
  • No control over dynamic interactions: Solving keyboard traps, drag/drop alternatives, shortcut logic, overlay behavior (e.g. 2.1.2, 2.5.7) require JS.
  • Does not create media alternatives: Subtitles/AD/transcripts for time-based media (1.2.x) must be provided by you.
  • No control over automatic audio/timers: Autoplay control, pausing, timeouts & animations (1.4.2, 2.2.x, 2.3.x) lie outside the block HTML.

Self-check · 3 questions

Self-check: is Semanticality right for your project?

Question 1 of 3 · Prerequisites:

Does your project use Gutenberg blocks (not Elementor/Divi)?

Semanticality™ intervenes server-side in the final HTML output of the Gutenberg blocks. Page builders like Elementor/Divi are not compatible.

Semanticality™ is a Swiss Army knife for the semantics of your website. It helps you address many important WCAG 2.2 criteria that are based on correct HTML & ARIA**.

Use case · 4 steps · 3 rules

Case study: a div becomes an accessible section.

In a few clicks you convert a purely visual container into a semantically correct section with a landmark according to WCAG 2.2 techniques ARIA11 (opens in a new tab) and ARIA13 (opens in a new tab).

This improves orientation for screen reader users and is sufficient to meet WCAG 2.2 success criteria 1.3.1 "Info and Relationships" (opens in a new tab) and 2.4.1 "Bypass Blocks" (opens in a new tab)***.

  1. Open the Semanticality™ Rules Editor for the block

    Before you start, select the section in the Block Editor and open the Semanticality™ Rules Editor. The rules you define here only apply to this block, unless you save them as a global rule.

    1. Select a section in the Gutenberg Block Editor that you want to customize.
    2. Click the Semanticality™ button in the block toolbar.
    Semanticality™ Rules Editor button in the Gutenberg block editor
  2. Rule 1: div → section

    First, you turn the block wrapper from a div into a section. The Live Code Preview on the right shows the change straight away.

    1. In the Local Block Rules tab, click + Add Rule. To save the rule for all blocks of this type across the whole website, create it in the Global Block Rules tab instead.
    2. Select Change Tag as the Action.
    3. Enter the CSS selector of the block wrapper (e.g. .wp-block-group, with Mode set to First).
    Semanticality™ Rules Editor with a rule that changes a div into a section
  3. Rule 2: Heading ID

    Next, you give the heading a stable ID that you can reference later.

    1. Click + Add Rule again to add another rule.
    2. For Action, this time select Modify Attribute.
    3. Enter the CSS selector of the heading (e.g. h2, with Mode set to First).
    4. Select id as the attribute in the Attribute Name field.
    5. In the Insertion field, select Add / Replace.
    6. Enter the ID in the Value field. You can use a static ID such as hero-title or a dynamic ID such as {{ id_dein_label }}.
    Semanticality™ Rules Editor with rule to assign an ID to a heading
  4. Rule 3: aria-labelledby

    Finally, you add the aria-labelledby attribute to the block wrapper. It points to the ID of the heading.

    1. Click + Add Rule again to add another rule.
    2. For Action, this time select Modify Attribute.
    3. Enter the CSS selector of the section (e.g. section, with Mode set to First. Each rule assumes that the rules above it have already been applied. So here you can simply select section.)
    4. Select aria-labelledby as the attribute in the Attribute Name field.
    5. In the Insertion field, select Add / Replace.
    6. In the Value field, enter the ID you gave the heading.
    7. Click Save Block Local Rules to save the rules and apply them to the block.
    8. Save the page and test it on the front end. If you do not save the page, the rules are lost when you leave the editor.
    Semanticality™ Rules Editor with a rule that adds an aria-labelledby attribute to a section

Result: Screen readers recognize a named landmark, navigation is now more meaningful, and you meet WCAG 2.2: 1.3.1, 2.4.1 at the markup level - without touching the theme.

Target audiences

Who is the Semanticality™ plugin for?

We developed Semanticality™ for ourselves as accessibility experts and have successfully used it in numerous projects. Now we want to share this tool with other developers.

  • In-house developer teams

    Ensure your company website is accessible, even if you rely on a complex theme**.

  • Accessibility consultants and freelancers

    Put your recommendations into practice right away, without depending on the capacity of developer teams.

  • WordPress agencies

    Deliver websites to your clients that are technically flawless and accessible** – and boost your margin by simply skipping weeks of theme rework*.

Pricing · annual licenses · 14-day money-back*****

Choose your Semanticality™ plan – every plan has all features, the difference is sites and support.

An investment that pays off immediately. Compare the cost of an annual license with a developer's hourly rate (about €100). Save just 2–3 hours, and Semanticality™ has paid for the whole year*!

Try Semanticality™ for 14 days, 100% risk-free: if it does not convince you, you get your money back – no questions asked*****.

  • Solo LicenseFor freelancers, side projects and single websites.

    Solo License: €119 / year

    Price plus VAT. Renews automatically every year at the same price. Cancel any time before the renewal date.

    • License key for 1 simultaneous website activation (production + staging included).
    • Flexible transfer: move the license from an old project to a new one at any time.
    • All features: tag switching, attribute rules, global and local rules, live preview, meta fields, ID generator.
    • User manual and developer documentation.
    • After expiry → the plugin keeps working, but without updates and support****.
    • 1 year of updates & standard support (usual response ≤ 3 working days).
    • Support quota: max. 2 tickets / month (unused tickets expire at the end of the month).
    • Support scope: Installation, basic setup, day-to-day use and basic questions about digital accessibility (WCAG/EAA (BFSG)) in the context of the plugin. No individual project or legal advice, no fixes for third-party software.
    • Upgrade or downgrade at any time.
    • 14-day money-back guarantee, no questions asked.
    • Access to the partner program with 20% recurring commission per referral (for example, to your clients).

    The buy button becomes active as soon as you've confirmed your consent above.

  • Studio License · RecommendedFor small teams & agencies with multiple projects.

    Studio License: €249 / year

    Price plus VAT. Renews automatically every year at the same price. Cancel any time before the renewal date.

    • License key for 5 simultaneous website activations (production + staging included).
    • Flexible transfer: move licenses from old projects to new ones at any time.
    • All features: tag switching, attribute rules, global and local rules, live preview, meta fields, ID generator.
    • User manual and developer documentation.
    • After expiry → the plugin keeps working, but without updates and support****.
    • 1 year of updates and priority support (reply usually within 1 working day).
    • Support quota: max. 5 tickets / month (unused tickets expire at the end of the month).
    • Support scope: Installation, basic setup, everyday use and basic questions about digital accessibility (WCAG, EAA/BFSG) related to the plugin. No individual project or legal advice. No fixes for third-party software.
    • Upgrade or downgrade at any time.
    • 14-day money-back guarantee, no questions asked.
    • Access to the partner program with 20% recurring commission per referral (for example, to your clients).

    The buy button becomes active as soon as you've confirmed your consent above.

  • Agency LicenseFor agencies with an active project pipeline.

    Agency License: €499 / year

    Price plus VAT. Automatic annual renewal at the same price. Cancellation possible at any time before the renewal date.

    • License key for 25 simultaneous website activations (production and staging included).
    • Easy to transfer: move licenses from old to new projects at any time.
    • All Features: Tag-Switching, Attribute Rules, Global & Local Rules, Live Preview, Meta Fields, ID Generator.
    • User manual and developer documentation.
    • 1× 60-min onboarding call for the team.
    • After expiry → the plugin keeps working, but without updates and support****.
    • 1 year of updates and priority support (reply usually within 1 working day), with an escalation path.
    • Support quota: max. 10 tickets / month (unused tickets expire at the end of the month).
    • Support scope: Installation, basic setup, everyday use and basic questions about digital accessibility (WCAG, EAA/BFSG) related to the plugin. No individual project or legal advice. No fixes for third-party software.
    • Upgrade or downgrade at any time.
    • 14-day money-back guarantee, no questions asked.
    • Access to the partner program with 20% recurring commission per referral (for example, to your clients).

    The buy button becomes active as soon as you've confirmed your consent above.

  • Enterprise LicenseFor organizations with more than 50 sites and formal SLA requirements (Support, Security Review, DPO coordination).

    Enterprise License: upon request

    Custom quote based on your volume, support and SLA needs.

    • License key for 50+ sites (production and staging included).
    • Optional private builds.
    • Custom support and SLA package, by arrangement.
    • Custom quote and volume pricing.

Note: Payment processing and invoicing are handled by our partner Freemius, Inc. (USA), who acts as the Merchant of Record. The contractual partner for the plugin remains Dmitry Dugarev (barrierenlos.com). Automatic renewal annually at the full price without discount. Cancellation is possible at any time until the renewal date. Prices plus VAT, if applicable.

All licenses are based on simultaneous activations and are transferable at any time. Finish a client project, deactivate the license with one click, and use it for your next job. Perfect for a developer's daily work.

Explainer video · 3 min · with subtitles

Partner program · 20% recurring commission

Love Semanticality™? Spread the word!

Earn 20% commission on the first purchase and every renewal of the customers you refer – no minimum sales, no obligations. Sign up → recommend → earn.

Questions

Do you still have questions?

Semanticality™ is a WordPress plugin that gives you granular control over the HTML your Gutenberg blocks output. You can change HTML tags and add, edit or remove attributes. All changes happen dynamically at render time. Your theme files and the content stored in the database stay untouched. Visitors automatically get the adjusted code in the frontend.

We understand that operation is crucial. At the beginning of this page in the Introduction you will find a video demonstrating the user interface and workflow of Semanticality™.

Feel free to book a free demo session with us, where we will show you the plugin live and answer your questions: Book your free demo session now.

After purchase, you also get detailed documentation with instructions and best practices for using the plugin.

Semanticality™ works server-side and is optimized for performance. The impact on load time is minimal in typical setups.

With a large number of complex rules, it can help to optimize selectors and only make the changes you need.

Yes. Semanticality™ accesses the final HTML output of the Gutenberg blocks and is therefore generally theme-independent (Core, Kadence, GenerateBlocks, etc.). As long as a block outputs HTML, you can adjust it with Semanticality™.

Note: Very individual block implementations may require adapted selectors/rules.

Yes, Semanticality™ is compatible with Kadence Blocks. Kadence Blocks builds on the standard WordPress blocks. So you can apply Semanticality™ adjustments to these blocks too. Still, take the specific implementation details and requirements of Kadence Blocks into account to make sure all functions work as expected.

No, Semanticality™ is not compatible with Elementor. Elementor uses its own structure and widgets, which are not based on the standard WordPress blocks. So you cannot apply Semanticality™ adjustments to Elementor widgets.

No, Semanticality™ is not compatible with Divi. Divi uses its own structure and widgets, which are not based on the standard WordPress blocks. So you cannot apply Semanticality™ adjustments to Divi widgets.

Your rules stay in place. Most rules are based on the CSS classes of the WordPress core blocks. So they keep working after a theme change. If a new theme uses different classes, you can quickly adapt your selectors in the plugin.

Client-side scripts can overwrite the HTML output generated by the plugin because they run after rendering in the browser.

Recommendations:

  • Where possible, make changes server-side with Semanticality™ (this avoids conflicts).
  • Avoid JS that blindly overwrites global attributes. Use targeted selectors.
  • If you need JS, run it idempotent (add to values, never destroy them) and check existing values.
  • Document project-wide which attributes are "owned by JS" and which are "owned by Semanticality™".

Your website returns to its original state immediately. Semanticality™ makes no permanent changes to your content or theme files. So deactivating the plugin is 100% safe and reversible. It leaves no trace in your code or database.

A "Site" is a unique domain on which a license is activated. Our license model is based on the number of websites on which the plugin can be simultaneously active.

Staging sites:

Activation on a staging site consumes no license slot, provided it is on one of the following supported subdomains: dev.*, staging.*, stage.*, demo.*,preprod.*, qa.*, sandbox.*,preview.*, test.*. If your staging environment is on a different subdomain, it counts as a separate site and requires activation.

Localhost:

no license activation is required for local development on your computer. The plugin is fully functional on the following domains: localhost, 127.0.0.1, ::1, *.local.

Every sub-site project with independent output/branding counts as a separate site and requires activation.

Recommended: WordPress 6.4+, PHP 8.1+. Older versions may work, but we primarily test and support the current stable releases.

Multisite is supported. Popular block libraries (e.g. Core, Kadence, GenerateBlocks) are compatible. Highly custom implementations may need adapted selectors.

Yes. Since Semanticality™ adjusts the HTML output before delivery, it is generally compatible with page cache, OPCache, Minify/Combine and CDN.

Tip: clear the cache after you change rules. Do not set HTML minification to "aggressive" if your selectors depend on whitespace or formatting.

Yes. Rules affect the HTML output regardless of the language. You can define language-specific selectors/rules if necessary (e.g. via body classes).

Yes. After purchase, you get the plugin plus comprehensive user documentation. It helps you get the most out of the plugin and improve the semantics of your website.

It explains all plugin features in detail, with step-by-step instructions, best practices and tips for meeting accessibility requirements.

With Semanticality™ you can meet many of the WCAG 2.2 success criteria that are based on correct HTML, ARIA and clean structure. Here's a practical overview.

Directly achievable (via correct HTML/ARIA)

  • 1.1.1 Non-text Content (A): alt for images, aria-hidden for decorative images, suitable roles.
  • 1.3.1 Info and Relationships (A): real headings (h1…h6), lists, table structure, labels, landmarks (header, main, nav,footer, aside or role).
  • 1.3.2 Meaningful Sequence (A): semantic order instead of purely visual arrangement.
  • 2.1.1 Keyboard (A): interactive elements as real controls (e.g. div → button/a).
  • 2.4.1 Bypass Blocks (A): skip link(s) + landmarks.
  • 2.4.3 Focus Order (A): clean DOM structure and real controls, plus tabindex="0" where needed.
  • 2.4.4 Link Purpose (In Context) (A): meaningful link text, plus aria-label/aria-labelledby.
  • 2.4.6 Headings and Labels (AA): consistent heading hierarchy, precise labels.
  • 2.5.3 Label in Name (A): visible button/link text included in the accessible name (e.g. via aria-label).
  • 3.3.1 Error Identification (A): error messages via aria-describedby, role="alert" or similar.
  • 3.3.2 Labels or Instructions (A): explicit labels, help text and required-field hints, linked semantically.
  • 1.3.5 Identify Input Purpose (AA): autocomplete for personal data fields.
  • 3.1.2 Language of Parts (AA): set lang at section or inline level (e.g. for quotes).
  • 3.1.1 Language of Page (AA): correct html lang (if the project lets you control it).
  • 2.4.10 Section Headings (AAA): content-relevant section headings.

Needs additional CSS/JS (Semanticality™ lays the groundwork)

  • 2.4.2 Page Titled (A): is set in the document head (theme/head, not block HTML).
  • 2.4.7 Focus Visible (AA): visual focus styles come from CSS. Semanticality™ provides real interactive elements.
  • 2.4.11 Focus Appearance (AA) & 2.4.12/2.4.13 Focus Not Obscured (AA/AAA): mostly CSS/interaction logic.
  • 2.5.7 Dragging Movements (AA) & 2.5.8 Target Size (AA): require interaction logic/styling; semantics helps with basic operability.
  • 2.4.5 Multiple Ways (AA): semantic navigation and structure are supported. Alternative ways to the content are an editorial task.

Practical mapping examples with Semanticality™

  • Skip link & landmarks (2.4.1, 1.3.1): add a skip link, mark up main/nav/footer correctly.
  • Buttons instead of clickable divs (2.1.1, 4.1.2): div → button, meaningful attributes (type, aria-pressed,aria-expanded).
  • Heading fixes (1.3.1, 2.4.6, 2.4.10): make incorrect heading levels consistent (e.g. h4 → h2).
  • Form associations (1.3.1, 3.3.1, 3.3.2, 1.3.5): label for, aria-describedby to help text/error, autocomplete="email".
  • Link Purpose (2.4.4): add aria-label where visible text alone is not enough.
  • Language of Parts (3.1.2): lang="en" for foreign-language snippets, technical terms and quotes.

Note: Some criteria depend on Design/JS (e.g. visible focus, target sizes). Semanticality™ provides the semantic foundation for them (real controls, correct roles/relationships); you add the visual and behavioral implementation in CSS/JS.

No. Semanticality™ does not make your website accessible automatically. It is a tool that helps developers make their content more accessible. They use it to create and optimize semantic HTML. Accessibility remains the developer's responsibility. The developer must use these tools to make sure the website meets accessibility standards.

The Agency license covers up to 25 sites (Prod + Staging incl.). For 26–49 sites, you can combine multiple Agency licenses. From 50+ sites we recommend Enterprise (individual offer, SLA, if necessary Private Builds).

Are you unsure what suits you? Simply book a short free consultation appointment via Enterprise consultation.

As an agency, you can use your license (e.g. Studio or Agency) to build a client project. When you hand the project over to the client, deactivate your license for that website in your client area or in the plugin settings. This frees up a slot. The client then needs their own license to keep the functionality and get future updates.

Alternatively, you can leave your license key with the client if you keep maintaining the project and include the license cost in your agency fees. In your client area, you can switch on white-label mode for this website. The client then cannot see your license details.

Tip: Become our Partner! If your client buys their own license through your partner link, you earn a 20% recurring commission.

Yes. You can remove a site from your license and add another one (e.g. at launch). For a full handover, the client needs their own license for updates and support.

Yes, you can upgrade or downgrade your plan at any time. Our payment provider Freemius prorates the billing to the day.

A subscription enables ongoing compatibility updates, continuous further development and reliable support. The WordPress ecosystem changes quickly – a one-time price would not cover this in the long run.

  1. Compatibility: Ongoing adjustments to WordPress, themes and block plugins.
  2. More value over time: New features, better workflows, performance improvements.
  3. Direct support: Help from the development team, prioritized by plan.

In short: every year you invest in a well-maintained professional tool that saves you time, risk and money.

We offer direct developer support. Response time depends on the plan, and each subscription has a monthly ticket quota:

  • Solo: Standard support, response usually ≤ 3 working days, max. 2 tickets/month.
  • Studio: Prioritized support, response usually ≤ 1 working day, max. 5 tickets/month.
  • Agency: Prioritized support with escalation path, response usually ≤ 1 working day, max. 10 tickets/month, plus 1× 60-min onboarding call.

Scope: Installation, basic setup, day-to-day use and basic questions about digital accessibility (WCAG/EAA (BFSG)) in the context of the plugin. Not included: individual project consulting, legal advice, general WordPress consulting or fixing conflicts with third-party software (available as a separate order).

Quotas: Unused tickets expire at the end of the month.

Please email support requests to our team. You will find the address in the order confirmation and in the documentation.

Within 14 days from the date of purchase you can revoke without giving reasons. Simply send us a brief message (details in the order confirmation). Enterprise agreements are excluded.

Semanticality™ works server-side inside your WordPress instance and by default does not send any content data to external services.

For license checks, checkout and invoicing, we use the payment provider Freemius. Freemius acts as the merchant of record. It processes all payments in line with the GDPR, based on standard contractual clauses.

Currently not yet. Export/import is planned (prioritized for Studio/Agency). Until then, you can copy and paste rules between blocks.

We communicate major milestones (e.g. export/import) in the release notes. You can submit feature requests at any time via support – we prioritize according to user impact and feasibility.

Our license model is based on the number of websites on which the plugin can be simultaneously active.

  • Solo license allows 1 simultaneous website activation.
  • Studio license allows 5 simultaneous website activations.
  • Agency license allows 25 simultaneous website activations.

You can remove (deactivate) a license from one website at any time and activate it on another. The number of activations therefore determines how many projects you can manage in parallel.

If your license expires after one year and is not renewed:

  • The plugin remains fully functional on the website where it is activated.
  • You will no longer receive updates or support.
  • You can no longer transfer the expired license to another website.
  • Important: If you accidentally deactivate an expired license in your customer account, the activation expires permanently. The plugin stops working and cannot be reactivated without a new, valid license.

Yes! If Semanticality™ has won you over, recommend it to your network and earn from it. Our fair partner program gives you:

  • 20% recurring commission on all sales and annual renewals.
  • exclusive discount that you can offer to your customers or community.

The program is ideal for agencies, freelancers and content creators who promote high-quality web solutions. All information and free registration can be found on our partner page.

Yes. The plugin source code of Semanticality™ is under the GNU GPL (2.0-or-later). You are allowed to use, study, change and share the code.

The payment refers not to the GPL rights to the code, but to additional contracted services: 1 year updates, support (incl. A11y questions in the context of the plugin, with ticket quota depending on the plan) and if necessary optional cloud/API services. After expiry, the installed code remains usable, but you will not receive any new updates/support.

Details can be found in our EULA and the terms and conditions (AGB).

BFSG entry into force ·

Act now.

Semanticality™ is the pragmatic solution to make your clients' WordPress Gutenberg websites accessible at markup level and protect them from fines of up to €550,000 for BFSG violations***.