Tag Info

New answers tagged

1

I am just going to throw that in there, as I cannot actually say any of this with confidence or base this on any factual knowledge. My guess is that they want to circumvent liability, that is, nowadays it is so common to skip these agreements that chances are (again I am not a lawyer, I am completely out of my depth here) somebody is actually going to be ...


0

Unless there is a regulatory reason to have a done button, don't have one at all, next should set your finished state. You can supplement this with skip ahead and/or mark place where skip functions like next without setting finished and mark place may or may not mark finished but lets your users pickup later (like after lunch)


1

Noting that the checkmark is an important but merely visual element, I can suggest that it only appears when the Done trigger button is clicked. Extending a strong theory... I wanted to show you this classy, simple UI solution (Kindle and tablet inspired.) Clicking on the ghost checkmark toggles the solid checkmark! In either case the state of ...


9

If a significant majority of users click Next after selecting Done you could design primarily for that workflow. Github does this with a combined button for commenting on a software bug with/without marking the bug as fixed: Without knowing your requirements, just marking a page could still be possible using Archive and next, followed by Previous or ...


0

I think option 3 is the best because the user's mouse is more likely to be on the right hand side of the screen moving downwards due to the positioning of the horizontal scroll bar. Additionally, the Guttenberg pattern and Z-pattern theories of eye movement suggest that the bottom right side of the page is the last point your user reaches on the page (last ...


8

For business software, design for workflow first, beauty second Design observations: Users tend to process text pages using the F-pattern, where the eye tends to use the left margin to anchor the visual flow down the page. Your workflow is, roughly: Read text Hit Done Hit Next Occasionally, the user may hit Previous instead. Also occasionally, the ...


0

Given that this seems to be more for e-Learning than simply checking boxes in a sequential web form, it is important to give learners an appropriate degree of control over their pace of completion. Learners need to be free to move back & forth within the content (at least within content they're immediately working on or have previously completed). It ...


0

By adding the check box your building in a constraint before they select the next button. You want to go with option 2 because it chunks the checkmark box with the content. Ideally you should "deactivate" the "Next" button until the user selects the checkmark. Also change your label from "Done" to "Agree" if this is a compliance business rule and move away ...


24

Why not merge the done and next buttons? This layout still allows a user to continue without being finished with the page, but requires less clicks.


7

This answer is based on these two comments from the original poster... They can see it in a menu to the left where they also can navigate between the pages. It is definately there to help the user remember what he has finished/hasn't finished. It could be an assignment of sorts. Navigating to another step does not mean you have finished the ...


0

I think this action button should be placed in its own row, so as to not confuse the user with navigation elements and to further avoid confusion make it stand out as the secondary activity confirmation (primary being reading the text, tertiary being going to the Next page). To do this perhaps offer a positive colour (green) with a big tick on confirm ...


15

Ideally from a pure UX perspective there shouldn't be such a checkbox at all. It is an unnecessary extra click. Users should be able to just click next and it is naturally assumed they are done. However, I assume that this is a box that exists for some sort of compliance reason? Its one of those "Yes I have read everything here and fully agree with it thus ...


0

I would go for the third option, as the Done button stays near to the Next button and, as far as I can see, seems logical that the normal flow for the user will be check the Done and then click the Next button. Why not the first option then? IMHO, when you have a row for navigation buttons, you shouldn't put buttons with other functionalities in the ...



Top 50 recent answers are included