Promotions are where accessibility failures cluster on casino sites. A welcome package, a weekly reload code, a prize drop banner: each one combines a form, a deadline, a set of terms and a call to action, and each element can exclude users if it is built carelessly. Meeting WCAG 2.1 AA for promos is not about a compliance badge. It is about making sure a screen-reader user can claim the same offer as everyone else, on the same terms, without emailing support. This guide walks through the practical fixes, using a real operator setup as the worked example.

Build the claim path so assistive technology can follow it

Start with the mechanics of a claim. On the Lady Luckmore casino, the promo code field is the first point of failure worth auditing. A text input needs a programmatically associated label, not just placeholder text that vanishes on focus and is inconsistently announced. The label should say what the field expects, for example “Promo code (letters and numbers, no spaces)”, and any validation error must be announced through an ARIA live region rather than signalled by a red border alone. Colour-only error states fail WCAG 2.1 AA under success criterion 1.4.1, and they fail real users every day.

Take the MEGA code as a test case: MEGA grants 10 spins for a £10 slots wager. Walk that journey with a screen reader and a keyboard only. Can the user reach the code field, paste the code, read the confirmation, and find the wagering requirement without leaving the flow? If the confirmation is an image, or the requirement sits in a linked PDF, the journey breaks. The same applies to the Lady Luckmore bonus code entry on mobile, where focus order often drifts because promo banners are injected above the form after page load.

Prize drop mechanics need the same treatment. Sweetest Slots prize drops run on selected slot games, and the opt-in control is usually a toggle or a button with no accessible name. Give it a clear label, expose its state (opted in or not) through ARIA, and make sure the countdown to the next drop is not the only indication that a drop is live. A screen reader should hear “Prize drop active, 14 minutes remaining” as text, not infer it from a ticking animation.

Publish bonus terms in plain text and plain English

The single highest-impact change most operators can make is retiring the PDF terms sheet. Bonus terms must exist as HTML text on the page, selectable, resizable to 200 percent without loss of content, and readable by a screen reader in document order. WCAG 2.1 AA criterion 1.4.4 covers resize, 1.4.10 covers reflow, and a scanned PDF fails both. Plain text also means plain English: short sentences, defined terms, and the key numbers stated up front.

Be explicit about the constraints that catch people out. The 25 percent max bet rule applies to bonus play, so say so in the terms body, not a footnote: no single stake above 25 percent of the bonus value while wagering. State the withdrawal cap, the eligible slot games, and the contribution rates for each. A user with a cognitive disability benefits from a summary table of the headline terms above the full text, and from consistent wording across every promotion so the rules do not appear to change shape each week.

Identity verification and withdrawal rules belong in the same plain-text block. If a withdrawal is held pending verification, the user needs to know before they deposit, not after. Pair the terms with visible links to GamCare, BeGambleAware and GamStop, and keep the responsible gambling section in the same accessible format as everything else. A promotion page that routes vulnerable users to a PDF help sheet has not met the brief.

Design deadlines and timed offers for cognitive accessibility

Timed offers are the least discussed accessibility problem in casino marketing. WCAG 2.1 AA criterion 2.2.1 requires that any time limit set by content can be turned off, adjusted, or extended, with exceptions for real-time events. A weekly reward that expires at a fixed hour is arguably a real-time event, but the claim window around it is not. Give users a way to extend the window, or at minimum warn them well in advance and let them set a reminder, and make sure the details are easy to find, for example at https://ladyluckmore-casino.uk/promotions/. Users with cognitive disabilities, attention difficulties or caring responsibilities are disproportionately excluded by hard cut-offs.

Apply the same logic to the recurring schedule. Weekly Rewards awards 10 free spins for a £25 deposit and wager, and 20 free spins for a £50 deposit and wager. Those weekly rewards spins are credited by 17:00 every Monday. Publish that deadline as text in the promotion block, with the time zone stated, and send a reminder that is readable by screen readers and not buried in an image-based email. If the credit is delayed, say so on the page rather than leaving users to guess.

Seasonal codes follow the same pattern. A code such as SANTA or BOOST50 should carry its expiry in plain text next to the field, and the expiry should be extendable where the offer allows. The operator behind Lady Luckmore, Grace Media (Gibraltar) Limited, holds UK Gambling Commission licence 057869-R-334655-008, and the UKGC expects licensees to treat fair and transparent terms as a condition of the licence, not a marketing nicety. Accessibility and fairness overlap heavily here.

Two more points worth auditing. Lady Luckmore does not publish no deposit bonuses, which removes one common accessibility trap: the no-deposit claim flow that hides verification behind a timed pop-up. And the site hides the welcome package until registration, so the terms must be reachable from the registration screen itself, in plain text, before the user commits. Test payment steps too: PayPal and Google Pay flows should be operable by keyboard and announced correctly, and any Megaways or Big Bass game tiles used in promo banners need alt text that describes the offer, not the artwork.

Run a short audit before the next promotion goes live. Check every code field for a proper label and announced errors, move all terms from PDF to HTML with a plain-English summary at the top, and add an extendable deadline to any timed claim window. Then test the whole journey with a screen reader, keyboard only, and at 200 percent zoom. Build those three checks into your sign-off process and accessibility stops being a project and becomes a habit.