Accessibility Widget needs improvements

  • Resolved mikeknappe

    (@mikeknappe)


    6 months ago

    Hello everyone,

    first of all, thank you so much for this plugin – it’s fantastic to have such a good plugin on the market, and it doesn’t load any libraries from the OneTab server, unlike other major accessibility plugins like Elementor, which access their server – making GDPR compliance impossible.

    During the use of the plugin, several suggestions arose on how this plugin could be improved.

    1. Please use the current CSS properties of “flex” to move the toolbar options if the toolbar is smaller or wider than 500 pixels. (Perfectly floating options within the toolbar regardless of the toolbar width)
    2. Please do not use a fixed width for the toolbar. Try to find a percentage that works well for all devices (PC, tablet, smartphone). Alternatively, the user can decide this via an option in the backend. A full-screen view might be better on mobile devices.
    3. Prevent the HTML/body area from overflowing during configuration and re-enable it when the user is finished. Otherwise, the user currently has two scroll areas in one view – this could confuse some people with disabilities. (Maybe also an option for the backend.)
    4. Please use the WordPress page functionality to create the accessibility statement, just as WordPress does with the privacy policy, for example. Furthermore, a ‘tag’ would be great for quicker access to the page in the page view. The advantage: An administrator doesn’t have to manage the text field in the plugin and a separate WordPress page containing the same information.
    5. Currently, the entire toolbar is reloaded every time the website is accessed. However, it is primarily needed by people with disabilities, and even then, probably only occasionally. This means the website’s TTFB (Time To First Byte) and First Contentful Paint (FCP) performance is unnecessarily degraded. Try loading the toolbar only when it’s truly needed: when the user clicks the accessibility button. You are able to implement this within WordPress thanks to its built-in jQuery framework.
    6. Consider whether you can implement additional features for people with visual impairments. Currently, only contrast options and monochrome are available. Someone with, for example, red-green color blindness wouldn’t want to use the monochrome view on every website. Take a look at this project:
      https://github.com/oftheheadland/Colorblindly/blob/master/LICENSE
      It’s a Chrome add-on. You can find the underlying functionality in the Git repository. The developers are creating a SVG with a color matrix and include it in the CSS filter of the <HTML> tag. This is a good and easy-to-implement approach and it is licensed under the MIT License. And definitely boost your plugin to the next level. (Yeah, you need to develop a counter matrix.)

    Happy coding!
    ~Mike

Viewing 1 replies (of 1 total)
  • Plugin Author onetapsupport

    (@onetapsupport)

    6 months ago

    Hi @mikeknappe

    thank you so much for sharing such detailed feedback — this kind of community input is extremely valuable to us.

    We’ll discuss each of your points internally with our development team and evaluate them carefully as part of our ongoing roadmap. Your suggestions are appreciated, and it’s great to see such thoughtful engagement with the plugin.

    Thanks again for taking the time to contribute 😊
    If you ever have more insights or ideas, feel free to reach out anytime.

    Warm regards,
    The OneTap Team

Viewing 1 replies (of 1 total)

The topic ‘Accessibility Widget needs improvements’ is closed to new replies.