Skip to main content

    Does Your Website Need an Accessibility Menu?

    What accessibility menus and widgets can do, what they cannot, and how to build one properly.

    The short answer

    An accessibility or preferences menu can help visitors personalize how a page looks. It is not required by WCAG, and it does not make an inaccessible site compliant.

    Our position is simple: the underlying website should be designed and coded to work accessibly without relying on the menu. If the site is solid, a menu is a thoughtful extra. If it is not, a menu is a sticker on a leaking boat.

    What is an accessibility menu?

    It is a small control, often a button in a corner of the page, that opens a panel of display options: larger text, different contrast, more spacing, highlighted links and a reset button. Different products call it an accessibility widget, toolbar or display preferences panel.

    Good ones change only presentation, on the current website. They do not claim to detect and repair accessibility problems, which is what separates a preferences menu from an overlay (more on that below).

    Why some visitors value text, contrast and spacing controls

    W3C notes that people may need to personalize font size, spacing, colours and other presentation properties. Someone with low vision may want larger text. Someone sensitive to glare may want a darker palette. Someone who finds dense paragraphs hard to track may want more line spacing. A parent on a phone in a waiting room may just want it bigger.

    Not everyone knows their browser can do this already, and a visible control tells them it is welcome here.

    Browser and device settings already exist

    W3C also notes that browsers and assistive technologies already provide many personalization functions, and that a website widget to change text and colour is not itself an accessibility requirement. A widget affects the current website only. Browser-level preferences follow the person across every site.

    That is why a site menu must never fight the browser: it should not block zoom, ignore the system's reduced-motion setting, or override the person's own text size.

    These controls let you personalize how this website is displayed. They are an additional option and do not replace your browser, device, or assistive-technology accessibility settings.

    Try a display preferences demo

    This is an isolated demo, not a sitewide feature. It changes only the preview box so you can see what the controls do. Everything uses real buttons, shows its state, works with the keyboard and can be reset.

    100%

    Book a first appointment

    Tell us a little about what you are looking for and we will reply within two business days. You can also read how our intake process works before you decide.

    A gentle pulse, off if you ask for reduced motion.

    This demo changes the preview box only. Your browser, device and assistive-technology settings are not touched, and nothing is saved.

    Why the underlying code still matters

    A person using a screen reader does not need a text-size button. They need headings that make sense, forms that are labelled and buttons that are buttons. A person who navigates by keyboard needs visible focus. No preferences panel adds those after the fact.

    It also works the other way. A menu's "high contrast" mode must not become an excuse for low-contrast default text. The default design should already meet the applicable contrast requirements, and the alternate mode should be tested too, so borders and icons do not vanish when colours change.

    Which controls are actually useful

    • Increase and decrease text size. The most-used control.
    • Alternate contrast. A high-contrast or darker presentation.
    • More line and text spacing. Helps some people track lines.
    • Highlight links. Links should already be distinguishable; this reinforces them.
    • Reduce or pause motion. Respect the system setting by default, and offer a manual one too.
    • Reset preferences. Always.

    An alternate readable font is optional. We avoid labelling any font a "dyslexia mode", because font preference is individual and the evidence for a single font helping everyone is not strong enough to promise it.

    Name it plainly: "Accessibility Preferences" or "Display and Accessibility". Not "AODA Widget" or "Compliance Widget", because the name should not imply a legal certification.

    How to build the menu so it is accessible too

    The menu is part of your website, so it has to pass the same tests. It should:

    • Be operable by keyboard, with an accessible name and real buttons or form controls.
    • Expose each option's state (on or off, selected size) to assistive technology.
    • Show a visible focus indicator and never trap keyboard focus.
    • Not cover important content, and not break at zoom or on mobile.
    • Have a clear reset, and leave browser and OS accessibility settings alone.
    • Store preferences in the visitor's browser where possible, with no account needed, and respect privacy.
    • Avoid heavy third-party scripts unless there is a good reason.

    If you store preferences, mention the storage in your privacy or cookie approach where that applies. Keep it simple.

    What an accessibility menu cannot fix

    • Semantic structure: headings, lists, landmarks and real buttons and links.
    • Keyboard access, logical focus order and visible focus.
    • Form labels, instructions and useful error messages.
    • Sufficient default colour contrast.
    • Alt text and accessible names for controls.
    • Reflow and zoom support.
    • Captions and transcripts.
    • Accessible dialogs, menus and third-party widgets.
    • Robust HTML and sensible use of ARIA.

    Accessibility menus versus automated overlays

    A preferences menu hands control to the visitor: you pick the text size. An automated overlay is usually a third-party script that claims to scan your site and fix accessibility problems on its own, often with a promise of compliance.

    W3C is clear that tools cannot automatically check all accessibility aspects, and fixing is harder than checking. Be cautious about any product that promises compliance, adds a heavy script to every page, or interferes with the way assistive technology already works on your site.

    How we approach personalization

    Accessibility preferences, plus an accessible underlying design, plus testing. That is the package. We can provide an accessibility preferences menu as an additional usability feature, built natively into the site rather than loaded from an overlay vendor.

    It is especially meaningful for therapy centres, clinics, community services and businesses serving families or older adults, where the website is part of how people reach the service. It is not a way to claim AODA compliance, and we will not describe it as one. See our website design and development service, or the practical accessibility guide for the foundations.

    Want personalization controls without relying on a third-party overlay?

    Ask about an accessibility preferences menu built into your website.

    Ask about a preferences menu

    Questions people ask about accessibility menus

    Is an accessibility menu required by AODA?

    No. Ontario's website requirement is about meeting WCAG 2.0 Level AA, with listed exceptions, for organizations it applies to. It does not require an accessibility menu or widget.

    Does an accessibility widget make a website WCAG compliant?

    No. A preferences menu can change how a page looks for the current visitor, but it cannot repair missing labels, keyboard traps, poor structure or inaccessible third-party tools. W3C also says a website widget for changing text and colour is not itself an accessibility requirement. In April 2025 the U.S. Federal Trade Commission finalized an order requiring overlay vendor accessiBe to pay $1 million and barring it from claiming its automated products can make any website WCAG-compliant without evidence.

    Should people change font size through the website or their browser?

    Browser and device settings are the better default, because they work across every site and with assistive technology. A site menu is a convenience for people who do not know those settings exist. It should never get in the way of the browser's own controls.

    Can a website remember accessibility preferences?

    Yes. A small script can save preferences in the visitor's browser so they do not need an account. Provide a clear reset control and mention the storage in your privacy or cookie approach if it applies.

    Will an accessibility menu change my site's design?

    Only for visitors who turn something on. The default design stays as you built it. That is also why the default has to be accessible already: the menu is an extra, not a repair.

    What is the difference between an accessibility menu and an accessibility overlay?

    An overlay is usually a third-party script that claims to detect and fix accessibility problems automatically. A preferences menu only lets visitors change presentation, such as text size or spacing. Automated fixes cannot fix every problem, so be cautious about any product promising compliance.

    Sources

    Continue the Toolkit