Accessibility ≠ Overlay: an accessibility menu does not make a website accessible
A website does not become accessible because an icon appears in a corner. Larger text, colour changes or text-to-speech can be useful, but they do not replace accessible implementation.
The visible button is not accessibility
WCAG concerns the content and how it works. A menu is only one possible interface; it does not prove that structure, keyboard use, focus, forms or alternatives are accessible.
Larger text does not replace zoom support
W3C says text must be resizable to 200% without loss of content or functionality and that scaling is primarily a user-agent responsibility. An “A+” button can complement, not replace, proper browser zoom.
Colour controls do not replace sufficient contrast
WCAG requires sufficient contrast in the default presentation. A high-contrast mode may help, but it does not make initially insufficient contrast acceptable.
Text-to-speech is not a screen reader
W3C distinguishes text-to-speech software from screen readers. Screen readers use semantics to communicate structure, roles, states and controls and support navigation and interaction.
What a menu does not repair
Incorrect headings, unlabelled fields, controls without accessible names, focus problems or poor structure are not repaired simply by adding a floating toolbar.
What about Blind Reader?
Blind Reader should be described as assistive technology that helps the person directly, not as an overlay that certifies WCAG or automatically repairs a website. The website remains responsible for its own accessibility.