ghost
commented
5 years ago These are mostly used by Tables (DataTable) which hide the Previous until the user leaves page 1.
I would argue that it should be the left button, but the style guide could be updated with "Should not be visible when user is on first page".
Also the 'Next' button should also have "Should not be visible when user is on the last page".
http://wet-boew.github.io/wet-boew-styleguide/v4/design/buttons-en.html I would argue against the recommendation regarding the position of the Previous/back link first in a context of a form or multi-steps process as a general recommendation -Previous: "Make it the left button".
Having the back/previous button first may create confusion for the users submitting a form and it is of disadvantage for someone with low vision given that the expected call for action is to click “next/submit/register”. More info : See Derek’s simulation for someone by mistake, get tripped and went to previous because it is placed first https://youtu.be/gf_BrfCZT7c?t=591
Our developers follow this recommendation and it creates a lot of usability concerns e.g. users go back then use the browser next and lose all the input they put in a form.
Suggestion: I propose that the recommendation on the position of the previous button be adjusted e.g. specify that this is in a case of a manual etc. OR add another recommendation for "Order of buttons to start with the call for action in a context of a form or web app".