Editorial team ·

Where should a bookmaker explain that the displayed price changed?

Editorial cover: Where should a bookmaker explain that the displayed price changed?
AI-generated illustration.

On a demo slip, the price beside Owls starts at 2.05. By the time you reach the review screen it reads 1.95. If the only clue is a flash of colour, you can miss the change while reading the other details. Put the explanation next to the price and make it available from the review controls.

Show the change where someone checks the selection

In the example, a message below the selection says “Price changed from 2.05 to 1.95.” The review screen keeps the selected event and choice visible. Anyone checking the details can see which number changed and which number is now shown.

Try the example in a test environment with keyboard and screen reader. If the update appears while focus stays on a control, check whether an appropriate status message gets announced. Then read the nearby text again to see whether the information remains available.

If a confirmation is requested, test the decision screen with its actual wording. The user should be able to tell which price the decision concerns and go back to review or remove the choice. Use test data so the exercise ends at the interface.

Record whether the update interrupted or displaced the task. A notice that pushes the active button under another panel, or repeats every second, can introduce trouble even when the words are good.

A price change on an imaginary review screen
Point in the demo Displayed information
Selection added Owls to win, 2.05
Price refresh Price changed from 2.05 to 1.95
Review Owls to win, current displayed price 1.95

Test what happens while the person is reading

  1. Trigger the update in the demo
    • Note the original price and focused control.
    • Let the simulated change occur while reading the review.
  2. Check the new state
    • Read the change and identify the choice it belongs to.
    • Find the current price and test going back without submitting.

Questions and answers

Is a red price enough to signal the change?
Use words or another cue that explains the change. Colour can reinforce the message.
Should focus jump to every automatic update?
A status message can communicate updates without moving focus. Check the right behaviour for the type of notice.
What belongs in an issue report?
Include the demo state, both prices, input method, and the place where you expected to find or hear the explanation.

W3C WCAG 2.2: Status Messages

W3C WCAG 2.2: Use of Color