Betsson Casino is a dense, commercially-driven interface — the kind where promotions, live-casino strips, a large game grid, account controls, and compliance content all fight for the same screen. I reviewed it the way a first-time player meets it: through the core, high-intent journeys, looking for the specific places where clarity, accessibility, and task completion could be strengthened without fighting the category it belongs to.
The challenge
High-density casino lobbies are hard to scan by design — the business wants everything visible at once. But when promotions, discovery, account flows, and regulatory content all shout at the same volume, the interface stops guiding and starts competing with itself. A person arrives with a goal (find a game, check a balance, make a deposit) and has to do the work the layout should be doing for them. Layered on top of that are accessibility risks that a sighted, mouse-using reviewer can miss unless they deliberately go looking: low-contrast text, focus states that vanish, grids that a keyboard cannot sensibly traverse, and touch targets packed too tightly for a thumb.
- Promotions and discovery compete at the same visual volume, so nothing reads as primary
- Account, balance, and deposit controls are harder to locate than their intent warrants
- Text and UI contrast that appears to fall below WCAG AA in several sampled states
- Focus visibility and keyboard operability gaps across game tiles and filters
- Dense mobile grids with touch targets and spacing below comfortable guidance
- No native way to test improvements — findings needed to become concrete, testable concepts
Discovery & research
A public-only audit built from the interface itself — no analytics, no session recordings, no insider data. Six findings, each carrying its observed behaviour, the criterion it maps to, and the evidence that substantiates it.
The lobby competes with itself for attention
Promotions and live-casino strips carry the heaviest visual weight on the page, while the two things a player most often arrives to do — discover a game and reach their account or balance — read as secondary. There is no clear priority ladder, so the eye has no obvious first stop and scanning becomes a search task. My concept establishes an explicit hierarchy that keeps the promotional energy but demotes it beneath discovery and account access.
EvidenceZone-by-zone hierarchy map plus a squint test: at reduced acuity the promotional blocks dominate and the primary nav, search, and account controls recede.
Contrast appears to fall below AA in several states
Sampled foreground/background pairs — secondary text, muted metadata, and some promotional and disabled states — appear to fall below the 4.5:1 threshold for normal text under SC 1.4.3, with some UI-boundary pairs also thin against SC 1.4.11. The fix is a palette-level adjustment to the affected roles rather than a per-component patch.
EvidenceMeasured with a WCAG contrast checker against sampled foreground/background pairs taken from the live interface; several returned ratios under 4.5:1 for normal-size text.
Focus visibility and keyboard operability break down in the grid
Traversing the game grid and its filters with a keyboard alone, the focus indicator is easy to lose and the traversal order does not always match the visual layout, so a keyboard or switch user cannot reliably tell where they are or predict where they will land next. This touches SC 2.1.1 (Keyboard), 2.4.7 (Focus Visible), and 2.4.11 (Focus Not Obscured). The concept restores a high-contrast focus ring and a logical, layout-matching tab order.
EvidenceKeyboard-only traversal of the lobby, game tiles, and filter controls, noting where focus disappeared or jumped out of visual order.
Dense mobile grids push targets below comfortable size
On narrow viewports the game grid packs tiles and controls tightly, leaving several interactive targets and their spacing below comfortable thumb-reach guidance (SC 2.5.8 Target Size, and general mobile ergonomics). This raises mis-tap risk exactly where the interface is busiest. The concept relaxes grid density and enforces a minimum target and gap on touch.
EvidenceMeasured interactive target dimensions and spacing on a mobile-width capture against the 24×24 CSS-px minimum and common 44px comfort guidance.
Errors and states lean on colour alone
In the account and deposit-adjacent surfaces reachable publicly, validation and status appear to be communicated largely through colour, with generic messaging, which risks failing SC 1.4.1 (Use of Colour) and SC 3.3.1 (Error Identification) for colour-blind and low-vision users. The concept pairs every state with an icon and specific, actionable text so meaning never rides on hue alone.
EvidenceWalkthrough of the publicly reachable sign-up and deposit-entry surfaces, noting where state was signalled by colour without a text or icon equivalent.
Discovery taxonomy overlaps and reads inconsistently
Categories, filters, and search cover overlapping ground, and category naming is not always consistent with the filters that refine it, so a player has more than one route to the same games and no clear model of how the routes relate. This is cognitive load, not a defect — but it slows the core discovery task. The concept reconciles the visible taxonomy into one coherent model with consistent labels.
EvidenceA lightweight card-sort of the visible categories, filters, and search scopes, surfacing duplicated and inconsistently-named paths to the same content.
How I approached it
I ran the audit as a pipeline rather than a single sweep, so each pass fed the next. A heuristic and WCAG 2.2 AA pass over each surface produced raw observations; a keyboard-only traversal and a contrast-sampling pass stress-tested the surfaces most likely to exclude people; a zone-by-zone hierarchy map turned "it feels busy" into a specific account of which regions are over- or under-weighted relative to a user's goal. Only then did I rank — by how many people a finding touches and how much it costs them, not by how easy it is to fix — and translate the ranked findings into design concepts framed as hypotheses to test, never as wins to claim.
Scoped the review to the core, high-intent journeys a new player meets first
Ran a heuristic and WCAG 2.2 AA pass over each surface
Traversed the key flows keyboard-only and sampled contrast with a checker
Mapped interface hierarchy and CTA competition zone by zone
Ranked findings by user impact and reach, not by ease of fix
Translated the ranked findings into testable design concepts
Trade-offs
The hard part was reviewing a mature commercial product without pretending its constraints away. A casino lobby is dense because density sells; recommending a calm, minimal grid would be both naive and useless to the team that owns it. The recommendations had to respect the category — keep the promotional energy, keep the breadth of discovery — while still carving a clear priority ladder through it. The second challenge was epistemic: with no analytics and no user sessions, I had to be disciplined about the difference between what I observed and what I inferred, and label the two honestly throughout.
- Respecting a dense commercial category instead of flattening it
- Separating observed behaviour from reviewer inference, explicitly
- Making accessibility fixes concrete enough to hand to a build team
- Avoiding generic audit language in favour of criterion-linked findings
- Framing every projected gain as a hypothesis to test, not an outcome achieved
Final direction
The deliverable is a structured UX and accessibility audit: a ranked friction map, a set of findings each tied to a WCAG 2.2 AA criterion or usability heuristic with the evidence that substantiates it, and a companion set of design concepts. The concepts target the highest-leverage moments — establishing a clear visual priority ladder in the lobby so discovery and account actions stop losing to promotions; raising sampled contrast and non-text contrast to AA; restoring a visible, logical focus order across tiles and filters; loosening dense mobile grids toward comfortable target sizes; and making errors legible without relying on colour alone. Each concept is written to be prototyped and tested rather than shipped on my say-so.
Outcomes
I want to be precise about this: no live metrics were available to me, so there is no measured outcome to report and none is claimed. The value is review value. The audit takes a product that is diffusely "busy and a bit hard to use" and turns it into a ranked, criterion-linked backlog — a specific list of what to change, why it matters, who it affects, and how a team could validate the fix. Every projected gain is written as a hypothesis to test, not a result achieved. In other words, the output is a starting point for design and experimentation, deliberately structured so the next step is a prototype and an A/B test, not a slide.
Clarity is not decoration. It is the shortest path between a person's intent and the control that serves it — and accessibility is how you keep that path open for everyone.
Accessibility and clarity turn out to be the same problem seen twice. The interface change that lets a keyboard or screen-reader user find the deposit button is the same change that helps everyone else find it faster — and that shared clarity is the quiet thing conversion tends to depend on. You do not have to choose between an accessible casino and a commercial one; the more legible version is usually both.