It is widely acknowledged that accessibility complements usability and there are very few examples where they conflict. But I have found one…

The national lottery results checker available on their website used to work really well for me. It used to move focus to the next field once you had input your number for the current field automatically. I’d have my ticket in my left hand while inputting with my right – it was a real annoyance to move my right hand to the left side of keyboard to tab across or worse change focus by using the mouse. Due to accessibility guidelines this has now been changed so that there is no automatic change of focus – you have to activate the change by pressing tab or click. So I feel I have quite an awkward experience.

There must be a solution that works well for both. The WCAG 2 guidelines 3.2 says you have to make web pages appear and operate in predictable ways and I think the preference is for the user to activate any change, which is perfectly feasible for search controls or dropdown selection boxes. However, thinking about how many will use this control it may be appropriate to follow the alternative advice stated in the success criteria, if an onchange event occurs is there an explanation of what will happen when the control is changed available prior to the controls activation.

My solution therefore is to ensure that the user is informed that the control will change focus once they have entered a valid number for a field. This therefore meets the guidelines and works for me. Does this work well in practice for people using screen readers or alternative technologies? I would be glad to get any thoughts on this.