Skip to content
Luc edited this page Nov 20, 2025 · 1 revision

Frequently Asked Questions (FAQ)

Common questions and answers about the Accessibility Widget.

General Questions

Q: Is this plugin free to use?

A: Yes! The Accessibility Widget is completely free to use and modify for any purpose. There are no licensing fees, usage restrictions, or hidden costs.

Q: Do I need to host the files myself?

A: No, you can use the CDN version which doesn't require hosting the files yourself. However, you can also download and host the files if you prefer.

Q: Does it work with WordPress?

A: Yes! The plugin works with WordPress. See the WordPress Integration guide for detailed instructions.

Q: Can I customize the appearance?

A: Yes! You can customize colors, position, styling, and more. See the Customization Guide for details.

Q: Does it work on mobile devices?

A: Yes! The plugin is fully responsive and works on all mobile devices including iOS and Android.

Q: Will it slow down my website?

A: No, the plugin is lightweight (< 50KB total) and has minimal performance impact. It's optimized for speed and efficiency.

Q: Does it comply with WCAG guidelines?

A: Yes, the plugin helps websites comply with WCAG 2.1 guidelines and accessibility best practices.

Q: Can I use it on multiple websites?

A: Yes, you can use it on as many websites as you want. There are no restrictions.

Q: Does it require server-side configuration?

A: No, it's completely client-side and requires no server configuration. It works on any web server.

Q: Can I modify the code?

A: Yes! The code is open source and you're free to modify it to suit your needs.

Installation Questions

Q: What files do I need?

A: You need three files:

  • accessibility-plugin.js (main plugin)
  • accessibility-plugin.css (styles)
  • accessibility-config.js (optional configuration)

You also need Boxicons CSS (loaded from CDN).

Q: Do I need to include all files?

A: The CSS and JS files are required. The config file is optional - if you don't include it, the plugin uses default settings.

Q: What order should I load the files?

A: Load in this order:

  1. Boxicons CSS
  2. Plugin CSS
  3. Config JS (optional)
  4. Plugin JS (must be last)

Q: Can I use a different icon library?

A: The plugin is designed to work with Boxicons. Using a different icon library would require modifying the code.

Feature Questions

Q: Does text-to-speech work in all browsers?

A: TTS works best in Chrome, Edge, and Safari. Firefox has limited TTS support. The plugin will gracefully handle browsers that don't support TTS.

Q: How many characters can TTS read?

A: The plugin can read up to 5000 characters at once. For longer content, users can select specific text to read.

Q: Do color blindness filters affect performance?

A: Color blindness filters use SVG filters which may have a slight performance impact on very large pages with many images. For most websites, the impact is negligible.

Q: Are settings saved permanently?

A: Settings are saved in browser localStorage and persist across page reloads and browser sessions. They are per-domain, so each website has its own settings.

Q: Can users reset their settings?

A: Yes, there's a reset button in the accessibility panel that restores all settings to defaults.

Technical Questions

Q: What browsers are supported?

A: The plugin works on all modern browsers:

  • Chrome 90+
  • Firefox 88+
  • Safari 14+
  • Edge 90+
  • Mobile browsers (iOS Safari, Chrome Mobile)

Q: Does it work with React/Vue/Angular?

A: Yes! The plugin is framework-agnostic and works with any JavaScript framework or vanilla HTML.

Q: Can I use it with TypeScript?

A: Yes, though you may need to add type definitions. The plugin is plain JavaScript but works fine with TypeScript projects.

Q: Does it conflict with other scripts?

A: The plugin is designed to avoid conflicts. It uses namespaced code and scoped CSS. However, if you encounter conflicts, check the Troubleshooting guide.

Q: Can I disable certain features?

A: Yes, you can customize which features are available via the configuration file or by modifying the code.

Customization Questions

Q: Can I change the button position?

A: Yes, you can set the position to 'bottom-left' or 'bottom-right' in the config file, or use CSS to position it anywhere.

Q: Can I change the button text?

A: Yes, set the buttonText option in the config file to any text you want.

Q: Can I change the colors?

A: Yes, you can customize colors via CSS. See the Customization Guide for examples.

Q: Can I add my own features?

A: Yes, but it requires modifying the JavaScript code. See the Development Setup guide.

Support Questions

Q: How do I report a bug?

A: Open an issue on GitHub with:

  • Description of the bug
  • Steps to reproduce
  • Browser and version
  • Screenshots if applicable

Q: How do I request a feature?

A: Open a feature request on GitHub describing the feature you'd like.

Q: Where can I get help?

A:

Q: Is there a community or forum?

A: Currently, support is provided through GitHub issues and email. A community forum may be added in the future.

License Questions

Q: What license does this use?

A: The plugin is free to use and modify for any purpose. There's no specific license - you can use it commercially, modify it, distribute it, etc.

Q: Do I need to credit the author?

A: Attribution is not required but appreciated! If you'd like to credit AirforceRP, that's great.

Q: Can I sell a product that includes this plugin?

A: Yes, you can include it in commercial products without restrictions.

Still Have Questions?

Getting Started

Documentation

Guides

Development

Support

Clone this wiki locally