Frequently asked questions

It provides visitors with a panel of controls for text size, contrast, font for dyslexia, text-to-speech, shut down animations, and other accessibility preferences.

No. No widget can guarantee compliance with WCAG. Real compliance requires semantic HTML, correct ARIA, keyboard navigation, alternative text, contrast and testing. The widget is complementary, not a replacement for fix.

We do not promise automatic compliance and do not use statements such as “AI fixes everything”.The widget provides controls of preference for the visitor; the remedy remains in code, design and content.

The ZebraByte widget script can be used without a subscription for the functions published in this version.

The widget is designed to run in the browser and keep local preferences. Always check the version of the script you implement and the applicable policy before publishing.

Added the script <script src='https://accesibilitate.zebrabyte.ro/dist/zbt.js' defer></script> before the </body>You can generate a custom configuration from the Customize page.

On sites that allow the upload of a JavaScript script: WordPress, Shopify, static sites and customized applications, depending on the CSP policies and site integration.

The ZebraByte configurator generates attributes for position, offset, size, color, icon and text-to-speech settings.

No. Preferences are applied client-side to the user. Permanent accessibility correction must be done separately in the application code.

Dev mode is activated with ?acc-dev=true and enables the use of integrated audit to identify problems that require investigation and correction.