ACCESIBILIDAD ≠ OVERLAY · 44
Buttons that answer to their visible name
📅 19 November 2026 · ⏱ 6 min read
You see an ‘Add to basket’ button and ask your voice tool to activate it. Nothing happens. The button works with a mouse and keyboard, but its accessible name is ‘Buy product’. The shopper is speaking the words the shop presents. To understand the problem, compare the visible label with the name the browser exposes to assistive technology. This article follows that check from a product page to the basket, including repeated buttons, product variations and translated pages.
01. Start with what the shopper sees
On a simple product page, the button’s own text can supply its accessible name. A button element containing ‘Add to basket’ will usually provide those words without an additional label. Start by recording the complete text shown before activation, including any information that changes with a selected variation. If the control says ‘Reserve’, someone opening a screen reader’s button list should be able to recognise that word. The same reference helps a person move between looking, listening and using voice input. Include links styled as buttons and calls to action in product cards. Their appearance can be similar while their markup and names come from different sources.
02. Inspect the name the browser calculates
Locate the control in the browser’s accessibility tree and find its computed name. Compare it with the visible text. An aria-label can override the name supplied by the button’s content. An aria-labelledby attribute can instead take text from other elements identified by their ids. Check those references individually. A reference to the wrong product title can produce a meaningful-looking name for the wrong action. Then listen to the control with a screen reader. This second check confirms what reaches the person and can reveal a nearby duplicate control. Record the label and name as a pair so another editor can reproduce the discrepancy on the same product page.
03. Add context while retaining the visible words
On a listing page, several jackets may have an ‘Add to basket’ button. An accessible name such as ‘Add to basket, blue jacket’ can provide the product context while retaining the visible label. Putting the visible words first helps people recognise them. WCAG 2.2 criterion 2.5.3 requires the name to contain the text shown in a visible text label or image of text. Choose the extra context using the actual product card. A colour alone might be insufficient if several blue products appear together. Check whether the name distinguishes the intended item when someone navigates through a list of controls, without having to inspect each card’s surrounding layout.
04. Follow the button through its states
Select a size, change the colour and return to the purchase control. Verify that any product context reflects the chosen variation. If the button is disabled until a choice is made, the instructions should explain what is missing. After activation, inspect its waiting state and its name after the server responds. A visible change to ‘Adding’ needs a comprehensible equivalent for someone listening. The outcome also needs perceptible feedback, as covered in the previous article. Record each state separately to distinguish a naming problem from an operation that is still pending. Finally, verify that you can continue to the basket and recognise the product and quantity that were actually added.
05. Check the output of the Divi template
A WordPress button module can combine its visible text with attributes added by a theme, extension or customisation. Inspect the published product page to see the final result. The editor helps locate the source, while the browser’s computed name shows how those sources interact. Review an old aria-label to determine whether its extra information is needed and whether it includes the current visible label. Where the button’s own text is sufficient, using it as the source of the name reduces the number of strings that need updating. Include mobile templates, related products and offer cards in the review, since they may use separate modules with similar styling.
06. Test each language as a complete journey
A translation can change the visible label while leaving an aria-label in another language. The control still has a name, but the shopper sees and hears different references. Open each shop language, select a product and compare both names. Check the document language as well, since it helps the screen reader pronounce the text appropriately. Review waiting messages and added product context alongside the original label. If several editors maintain the catalogue, document where attributes are translated so a later change can update all relevant strings together. Keep one simple product and one variable product as repeatable samples, including the exact options selected during the test.
07. Try voice input with Blind Reader
Blind Reader supports voice navigation and a guided shopping journey in WooCommerce, PrestaShop and Odoo. In Chrome or Edge, enable voice control and consult the help for the commands available on the current page. Try finding the product, choosing its options and reaching the purchase action. The tool’s help tells you which commands it recognises, while inspecting the accessible name checks the shop itself. Record both observations because voice tools can use different commands and selection methods. Repeat the action using a keyboard and screen reader. Confirm that the person can identify the same product and continue to review the quantity in the basket.
08. Leave a repeatable record
Choose a product page and record its address, language, variation and window width. Write down the visible button text, computed name and screen reader announcement. Include the voice command used and the action that actually occurred. Repeat on a listing containing several buttons with the same label so you can check whether the added context selects the intended product. Automated checks can reveal some discrepancies, while the shopping task verifies the resulting action. Reuse the same samples after a Divi update, a translation change or a Blind Reader integration update. Finish by checking that the shopper recognises the control, activates the intended action and can verify the item added.
09. Check the complete product reference
In a listing, listen to each button’s full name before activation. If it includes a size, confirm that the size matches the current selection. Repeat after sorting the results or moving to another page of the listing. A reused card can retain a reference to an earlier identifier. Record the item that actually reached the basket and compare it with the one you intended to choose. This helps the editor locate whether the discrepancy concerns the label, the name reference or the action attached to the module.

