Why ‘Edit Text’ Fails Your Bonus Accessibility Checklist

Screen reader users hit a specific wall on casino signup pages: the promo code input often has no accessible name. The field exists, it accepts text, and it works with a mouse or a finger. But a screen reader announces it as “edit text” and nothing else, so the player has no idea where to type WELCOME2026 or which field belongs to the bonus. This article is a checklist for auditing bonus accessibility on Canadian casino sites, with the promo input as the first test case.

Why “edit text” is a failing grade on a bonus page

An accessible name is the label a screen reader speaks when focus lands on a form control. On a well-built deposit or registration form, that name is something like “Promo code” or “Bonus code (optional)”. When the name is missing, browsers and assistive technology fall back to the control’s role. For a text input, the role is “edit text”. The player hears the role, hears nothing about the purpose, and has to guess.

This matters more on bonus pages than on ordinary forms because the promo field is the one control that decides whether the player gets the welcome package at all. A player who cannot identify the field either skips it or types the code into the wrong box, such as the deposit amount or the email confirmation. Either way, the qualifying deposit goes through without the tracking tag attached, and the free spins package or multi-deposit bonus does not activate.

Our audit of TonyBet Ontario’s mobile site found exactly this failure. The WELCOME2026 input on tonybet.ca renders without a element and without an aria-label or aria-labelledby attribute. Screen readers announce it only as “edit text”. The field is functional and the code works when entered, but the accessible name is absent, which means a blind player relying on speech output cannot find the promo field with confidence.

A working checklist for bonus term accessibility

Treat accessibility as part of bonus term compliance, not a separate design concern. The checklist below is ordered by how often each item fails in practice. Run it on the registration form, the cashier deposit screen, and the promotions page, because promo fields appear in more than one place and each instance needs its own accessible name.

Form controls and the promo field

• Every input has a programmatic label: a element with a matching for attribute, or an aria-label on the input itself. Placeholder text alone does not count because it disappears on typing and is inconsistently announced.
• The promo field’s name states its purpose and its status, for example “Promo code, optional” or “Bonus code, enter WELCOME2026 if you have one”.
• Required fields are marked in text, not by color or an asterisk alone, and the marking is part of the accessible name.
• Error messages after a failed submission are announced and tied to the field they concern, so a player who mistypes the signup code knows which box to fix.
• The opt-in checkbox for the welcome offer has its own label and sits close to the promo field, so the relationship between the code and the opt-in is clear from the reading order.
• Deposit amount fields announce the minimum qualifying deposit, so a player knows the C$20 per tier threshold before submitting rather than after.

Test each item with at least two screen readers, one on mobile and one on desktop, because announcement behavior differs between platforms. A field that speaks correctly in one combination can still fail in another.

Terms text that survives being read aloud

Bonus terms are dense by nature, and screen reader users get them as a single stream of speech with no visual skimming. Structure carries the meaning. Headings should mark each clause group, paragraphs should stay short, and lists should be real lists rather than lines broken with manual spacing. Wagering requirements, maximum bet rules, game contribution percentages, and expiry windows each deserve their own heading so a player can jump between them.

Watch for the usual traps: terms rendered as images of text, which screen readers skip entirely; tables used for layout rather than data; and collapsed accordions that hide key conditions from the accessibility tree. If the house rules on maximum bet or game weighting are only reachable by hovering, they are not reachable for a large share of players. The promo code at https://tonybet-casino-online.ca/promo-code/ itself does not bypass minimum deposit limits or house wagering rules, and a player who cannot read those rules cannot make an informed decision about claiming the offer.

Jurisdiction, eligibility, and the code itself

Accessibility checks sit alongside the eligibility checks that any bonus audit should include. TonyBet OÜ operates the main site for players outside Ontario, while TonyBet Ontario operates at tonybet.ca under provincial oversight and does not advertise welcome packages. That split matters for the checklist: the WELCOME2026 field on the Ontario-facing site is a functional input, but the promotional framing differs by jurisdiction, and a player reading the page with a screen reader should be able to tell which entity they are dealing with and what applies to them.

Age rules also belong in the same pass. Players in Alberta, Manitoba, and Quebec must be at least 18 years old, and players in the rest of Canada must be at least 19. Where the site states these limits, the statement needs to be in text, in the accessibility tree, and near the registration form rather than buried in a footer image. A player using speech output should hear the 18+ or 19+ requirement before submitting, not after.

For reference, the welcome package offered through tonybet-casino-online.ca runs to up to C$2,500 plus 225 free spins, with a minimum deposit of C$20 per tier. The promo code WELCOME2026 is entered in the registration form or the cashier deposit field, and the code is a tracking tag rather than a key that unlocks anything on its own. None of that is discoverable to a player who cannot identify the input, which is why the accessible name check belongs at the top of the list rather than in an appendix.

Build the audit into your release process. Before any bonus campaign goes live, run a screen reader pass over the registration form and the cashier, confirm the promo field announces its purpose by name, confirm the opt-in and the qualifying deposit minimum are spoken, and confirm the terms are structured with headings and real lists. Fix the label first, then retest with the code entered and with it left blank, and keep the results with the campaign documentation so the next promotion starts from a known baseline.