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

Users expected cursor to apprear in the 1st box and / or auto-forward #323

Open
GWSunderland opened this Issue Apr 11, 2017 · 8 comments

Comments

8 participants
@GWSunderland

GWSunderland commented Apr 11, 2017

issue2

@joanneSouthern

This comment has been minimized.

Show comment
Hide comment
@joanneSouthern

joanneSouthern Apr 11, 2017

we have been talking about this, it would be really good especially if you are not used to using a mouse

joanneSouthern commented Apr 11, 2017

we have been talking about this, it would be really good especially if you are not used to using a mouse

@petegale

This comment has been minimized.

Show comment
Hide comment
@petegale

petegale Apr 11, 2017

Collaborator

@GWSunderland @joanneSouthern We follow the GDS Design pattern on this that recommends not auto forwarding date fields as being the least problematic approach overall. I've added a link to this page to the page where this design pattern is discussed so if you have any more specific observations on this topic, please add them, as they will help inform this design pattern. We won't respond to this issue immediately, but we should add to the evidence collected across government projects.

Collaborator

petegale commented Apr 11, 2017

@GWSunderland @joanneSouthern We follow the GDS Design pattern on this that recommends not auto forwarding date fields as being the least problematic approach overall. I've added a link to this page to the page where this design pattern is discussed so if you have any more specific observations on this topic, please add them, as they will help inform this design pattern. We won't respond to this issue immediately, but we should add to the evidence collected across government projects.

@Becktacular

This comment has been minimized.

Show comment
Hide comment
@Becktacular

Becktacular Apr 12, 2017

Not having the auto forward function is a minor inconvenience to sighted users. But in terms of accessibility, for people using a screen reader and keyboard to move around a screen (e.g. visually impaired), having the cursor auto-forward to the next field is unexpected behaviour and can make it almost impossible for them to complete the fields.

Becktacular commented Apr 12, 2017

Not having the auto forward function is a minor inconvenience to sighted users. But in terms of accessibility, for people using a screen reader and keyboard to move around a screen (e.g. visually impaired), having the cursor auto-forward to the next field is unexpected behaviour and can make it almost impossible for them to complete the fields.

@petegale

This comment has been minimized.

Show comment
Hide comment
@petegale

petegale Apr 13, 2017

Collaborator

@Becktacular I thought that was the case. It's interesting though that the current pattern causes so many usability issues with this audience - especially those older users with poor motor skills, who struggle when they then have to edit the text they've entered into tiny input fields. I wonder if there is a solution out there can address both sets of needs?

Collaborator

petegale commented Apr 13, 2017

@Becktacular I thought that was the case. It's interesting though that the current pattern causes so many usability issues with this audience - especially those older users with poor motor skills, who struggle when they then have to edit the text they've entered into tiny input fields. I wonder if there is a solution out there can address both sets of needs?

@timpaul

This comment has been minimized.

Show comment
Hide comment
@timpaul

timpaul Apr 18, 2017

Contributor

Thanks for sharing this - it's an interesting example of the needs of two groups conflicting with each other. I also think this is one of those things we'll need to keep an eye on, as it's affected by users expectations, which can shift over time.

Contributor

timpaul commented Apr 18, 2017

Thanks for sharing this - it's an interesting example of the needs of two groups conflicting with each other. I also think this is one of those things we'll need to keep an eye on, as it's affected by users expectations, which can shift over time.

@EUzkuraityte

This comment has been minimized.

Show comment
Hide comment
@EUzkuraityte

EUzkuraityte Apr 21, 2017

Collaborator

Evidence from Bucks user research:

image
image

image
image

image
image

Collaborator

EUzkuraityte commented Apr 21, 2017

Evidence from Bucks user research:

image
image

image
image

image
image

@EUzkuraityte

This comment has been minimized.

Show comment
Hide comment
@EUzkuraityte

EUzkuraityte Jun 12, 2017

Collaborator

more evidence from Sunderland

image

Collaborator

EUzkuraityte commented Jun 12, 2017

more evidence from Sunderland

image

@EUzkuraityte EUzkuraityte changed the title from Users expected cursor to auto-forward to Users expected cursor to apprear in the 1st box and / or auto-forward Jun 16, 2017

@EUzkuraityte

This comment has been minimized.

Show comment
Hide comment
@EUzkuraityte

EUzkuraityte Jun 16, 2017

Collaborator

@sanjaypoyzer I assign this to you in case anything can be done to at least have the cursor located in the 1st box of the page by default.
screen shot 2017-06-16 at 15 51 12

Collaborator

EUzkuraityte commented Jun 16, 2017

@sanjaypoyzer I assign this to you in case anything can be done to at least have the cursor located in the 1st box of the page by default.
screen shot 2017-06-16 at 15 51 12

@EUzkuraityte EUzkuraityte moved this from Is this a real need? to PP issues (ready to do) in Alpha board Jul 3, 2017

@ingasiler ingasiler removed this from PP issues (ready to do) in Alpha board Jul 20, 2017

@ingasiler ingasiler added this to PP ready to do in Beta board Jul 20, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment