=== BitHub Accessibility ===
Contributors: bithub
Tags: accessibility, accessibility widget, usability, toolbar, saas
Requires at least: 6.4
Tested up to: 7.1
Stable tag: 1.0.2
Requires PHP: 7.4
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Connects WordPress to BitHub Accessibility and displays the widget configured for the authorized domain.

== Description ==

BitHub Accessibility integrates the widget provided by the BitHub Accessibility SaaS service into WordPress.

The plugin allows administrators to:

* enter the public key associated with their website;
* verify that the license is active for the WordPress domain;
* enable or disable the widget without modifying the theme;
* automatically use the color and position configured in the BitHub customer area.

The plugin is free and its source code is fully available under the GPL. It is a serviceware connector: the accessibility widget and its functionality are provided by the remote BitHub service rather than being premium features included and locked inside the plugin. Using the widget requires a BitHub Accessibility account and a website with an active license, which may require payment.

The widget is a tool that can help users access website content. Installing it does not automatically guarantee that the website complies with WCAG, the EAA, or any other legal requirement.

== External services ==

This plugin connects to the external BitHub Accessibility service, which is required for the plugin to work.

The connection is made only after an administrator has entered the key, explicitly accepted the use of the external service, and enabled the widget.

Services contacted:

* `https://licence.bithub.it/licence.aspx` verifies the public key and domain, then returns the public widget configuration and a temporary token;
* `https://licence.bithub.it/bithub-accessibility.js` provides the BitHub Accessibility widget code. This service-related JavaScript does not update the plugin or install or modify WordPress code.

During verification, the public key and domain name are transmitted. As with any HTTP request, the servers may receive technical data such as the IP address and user agent. The temporary token may be stored in the browser's `sessionStorage` to avoid repeated calls during the same session. Preferences selected by the user in the widget may be stored locally in the browser.

The service is provided by BitHub: https://www.bithub.it/

BitHub privacy policy: https://www.bithub.it/privacy-cookie/

The service terms are presented during registration and in the customer area: https://app.bithub.it/accessibility/

== Installation ==

1. Install and activate the plugin from the WordPress Plugins screen.
2. Go to Settings > BitHub Accessibility.
3. Enter the key assigned to the domain in the BitHub customer area.
4. Accept the connection to the external service and save the settings.
5. Click "Verify license".
6. Enable the widget and save the settings again.

The domain configured in WordPress must match the one registered in the BitHub customer area. The `www` prefix is normalized automatically.

== Frequently Asked Questions ==

= Is the license key a password? =

No. The key is published in the page source and is considered public. Authorization also depends on the domain, status, and expiration date registered with the BitHub service.

= Does the plugin modify content or the theme? =

No. It loads the widget on the frontend through standard WordPress APIs and does not modify theme files, posts, or pages.

= Does the widget automatically make the website compliant? =

No. It is a support tool for users. Accessibility and compliance also require technical, editorial, and organizational reviews of the website as a whole.

= What happens if the license is not valid? =

The widget is not loaded. The WordPress website continues to work normally.

= How can I request support? =

Email info@bithub.it or visit https://www.bithub.it/.

== Privacy ==

The plugin adds suggested text to the WordPress Privacy Policy Guide. The website owner must adapt it to their situation and include it in their own privacy policy.

The plugin does not create WordPress accounts, read posts, users, orders, or form data, and does not set its own cookies. It uses `sessionStorage` to store the license response temporarily. The remote widget may store the preferences selected by the user in the browser.

== Changelog ==

= 1.0.2 =

* The loader is added to the document head so it also works with custom themes that do not call `wp_footer()`.

= 1.0.1 =

* Fixed the license verification service address after separating the customer area from the widget server.

= 1.0.0 =

* First public release.
* Settings for the key, external service consent, and widget activation.
* Manual license verification.
* Loading of the widget and the configuration associated with the domain.
