Application – UX/UI Designer

win2day • Casinos Austria & Austrian Lotteries Group

View CV Read cover letter
  • End‑to‑End UX/UI (web & apps)
  • Figma & design systems (tokens, variants, components)
  • WCAG 2.1 AA • Jira workflow • Data‑informed (e.g., Glassbox)

UX/UI Examples

Mini cases (keyboard‑friendly, no fake numbers). Each case shows: problem → hypothesis → solution → measurement plan.

Storytelling & impact metrics

Case 01 – Registration: reduce friction, increase trust

Problem
Drop‑off in account creation (too many fields, unclear errors, missing transparency).
Hypothesis
Progressive disclosure + clear helper/error text + visible privacy/compliance hints reduce drop‑off and support load.
Solution
3‑step flow, clear field states, inline validation, password checklist, accessible errors with focus management.
Measurement plan
  • Conversion (start→finish)
  • Drop‑off per step
  • Form error rate
  • Time‑to‑complete
  • Support tickets (registration)
  • Trust signals (micro survey)

Case 02 – Deposits/withdrawals: clarity & error tolerance

Problem
Errors and abandonment due to unclear limits, fees or missing status feedback.
Hypothesis
If status, limits and “what happens next” are explicit, errors drop and completion rises.
Solution
Status stepper, clear confirmation screens, crisp copy for limits/fees, optional “save method”, robust empty/error states.
Measurement plan
  • Error rate
  • Retries
  • Time‑to‑task
  • Abandonment
  • Payment‑related tickets
  • Self‑service success rate

Case 03 – Accessibility audit: WCAG 2.1 AA by default

Problem
Inconsistent focus order, contrast risks, missing semantics and motion without alternatives.
Hypothesis
A systematic audit plus design system fixes reduces bug cost and improves usability for everyone.
Solution
Audit checklist, contrast tokens, standard focus ring, skip link, ARIA for live updates, reduced motion, keyboard‑only test pass.
Measurement plan
  • WCAG findings (count/severity)
  • Fix lead time
  • Bug reopen rate
  • Keyboard‑only task success
  • Support feedback

Case 04 – Design system: tokens, variants & Jira fit

Problem
UI inconsistency and high implementation effort because variants/states are missing.
Hypothesis
With well‑defined tokens + variants, dev questions drop and time‑to‑implement improves.
Solution
Tokens (color/type/space), component API, states, spec snippets, Jira tickets with acceptance criteria & DoD.
Measurement plan
  • Design‑to‑dev cycle time
  • Dev questions per ticket
  • UI defect rate
  • Component reuse rate
  • Velocity stability

Interactive mini cases

All mini cases are accessible: keyboard support, visible focus, ARIA live updates, reduced‑motion support.

Mini Case Game 01: Draw a card (feedback & states)

Draw a card: states, subtle motion (reducible) and a screenreader live update.

Mini Case Game 02: Funnel Fix (form UX)

Choose the best next improvement. Each decision explains UX reasoning and measurement.

Scenario: Step 2/3 of a registration flow has high drop‑off. What do you do next?

Mini Case Game 03: Accessibility Check (keyboard‑only)

Test focus order and ARIA feedback in a small component.

Keyboard only: tab through the controls. Live feedback confirms focus order.

Link