terrysimpson99

We use: 'Address line 1' 'Address line 2' 'Address line 3 (optional)' 'Address line 4 (optional)' 'Postcode' This has several advantages: * Each field has a label * Eliminates the...

One of the advantages of the above 'Address line 1' format is it works equally well for UK and non-UK addresses. The only issue is with the postcode field. You...

Guidance currently refers to two scenarios 1. If the input uses characters that are not allowed and you know what the characters are 2. If the input uses characters that...

I support the statement: - _"The inline documentation is the only Yes/No example on the guidance, it has been misconstrued as the default, or preferred approach, for yes/no questions."._ I've...

I support the statements by @davehaigh where he says "allow spaces, dashes" in sort code and account number. The guidance on postcodes (`https://design-system.service.gov.uk/patterns/addresses/`) says to allow * "additional spaces at...

I'm glad to see the MOJ example has the sort code before the account number. This matches the sequence used in the IBAN and also matches the ‘general to specific’...

@ladine-cook We remove all unwanted characters prior to validation. It's an extra step in the software but simple enough. We're considering this as almost a default style to apply to...

https://github.com/alphagov/govuk-design-system-backlog/issues/214 'Asking for at least one thing' might be relevant

Thanks. Issues that I think are relevant: * Time estimates add content. If the content does not add significant value then it might just be clutter. * Hypothesis: time estimates...

The hypothesis appears to be: * "Completion rate is greater if a time estimate is given compared with no time estimate". Has anybody done an AB test for that? Does...