The community member posted a request for an accessibility button on their website, and they would like it to be ARIA standard. The comments suggest that the website already has native accessible buttons, and that adding ARIA labels can help describe content. However, some community members caution against using pre-built accessibility widgets, as they may not address underlying semantic issues, and improper use of ARIA can make a site less accessible. The consensus seems to be that the community member should focus on building an accessible website using WCAG standards, rather than relying on a pre-built accessibility button.
It looks like you mean a widget. Those are garbage. Most people needing special accessibility considerations know how to set them on their system by default. For a temporary disability (like you had eye surgery recently and are recovering), those might be of use... but very little. They aren't fixing any semantic issues a website might have.
Webstudio allows you to build accessible websites without that.
Ps. Doing bad aria, is worse than no aria. Don't add aria tags unless you know what you're doing, otherwise you might make your site less accessible.