Thank you John, I'll have a look at testing removing the initial Yes / No, it would certainly make the structure of the question simpler, my only reservation would be that for the Nos there wouldn't be any action required other than clicking the continue button, currently there aren't any other screens in the service where a response isn't required in order to progress (other than the start page) ... Gemma thanks for the link, exactly what I was looking for
Radio Button - Error handling
We have had comments on the sue of our radio button from accessibility. I have attached a screenshot below. When the user commits an error there is a skip link that reads as “Please answer this question.” When the user navigates out of context this link is not descriptive as the user is unaware of what question must be answered.
There should be an anchor link from inside the summary box (the big red bordered box that appears at the top of the page, with a heading in it stating there has been an error), to the field with an error - where there should be another error message, giving the context of the error.
We are working on a service for the MoJ where we need to ask citizens to provide a telephone number(s) so that they can be contacted if required. We are currently testing with;
Is there any guidance / research around the most appropriate labels to use when asking for telephone numbers? Very conscious that the labels - Mobile / Home / Work will not be relevant for everyone ... we are also looking to test with Main phone + other phone