New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update guidance about using type="email"
when asking users for an email address
#2187
Comments
Interestingly Accessibility Support seems to suggest that data entry is supported by Dragon but it looks like that was last tested in August 2019 with Chrome 76 and Dragon 15.30. I imagine things might have changed since then. Did DAC happen include the version of Dragon they were using, and what browser and browser version? |
Ooh, good question. They did:
|
Would a PR updating the guidance be useful to get this moving? |
I've done a little more digging into the spec and I think there are two other differences between
I'm not sure either of these should stop us from making this change, but we might want to consider whether any additional guidance is needed, especially if we want to publish any sort of communications encouraging users to make the change. We're working towards another audit of GOV.UK Frontend at the minute – hopefully we'll learn more about this then, either by testing the 'new version' or by looking out for this issue cropping up in the audit report. |
Related documentation
The documentation and code examples for on how to ask users for an email address (under ‘Help users to enter a valid email address’) states:
Suggestion
The
type
attribute is used to achieve 2 things:On the first point, the Design System recommends only adding client side validation:
type="email"
is recommended in this guidance in order to achieve the second point only.Modern browsers now support the
inputmode
attribute, which addresses this need explicitly:Evidence (where applicable)
Our service (Submit social housing lettings and sales data (CORE)) was recently audited by DAC. One of their assessors was using Dragon and found that the
type
attribute interfered with how they interacted with the input:Their recommendation was to use
type="text" inputmode="email"
overtype="email"
.The text was updated successfully, but these errors were encountered: