All articles

SMS code entry with a keyboard and screen reader

A row of attractive digit boxes can make life harder for someone using a keyboard or screen reader. If your interface uses messages obtained through SimAggregator in an authorized flow, test code-entry accessibility separately. The source of the SMS does not make the form usable.

Complete the screen without a mouse. Focus should be visible, navigation understandable, and pasting an entire code predictable. After an error, users should locate and correct the field without traversing the whole page again. Preserve leading zeros and avoid an unexpected submission after the last character.

Check how the label, hint, and result are announced. A changing timer should not constantly interrupt reading. A notification about a new code should make the event discoverable without unnecessarily announcing sensitive content to people nearby.

Start with synthetic values of different lengths. Record the browser, assistive technology, and input method used. A form checked only with a mouse at the developer's usual zoom level is not adequately assessed. Keep a reproducible scenario the team can repeat whenever the form changes.

Your first number in a minute

Signing up takes a minute, topping up a couple more, and the code arrives in 20 seconds.

Buy a number
No subscription feeCancel with a refund in the first hour