Skip to content
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

Next / Back button placement #278

Open
guywillis opened this issue Oct 5, 2023 · 2 comments
Open

Next / Back button placement #278

guywillis opened this issue Oct 5, 2023 · 2 comments

Comments

@guywillis
Copy link
Contributor

Subject of the issue

The placement of the back and next buttons in the narrative hasn't changed for a while and am wondering whether a small change up to their positioning would help the buttons flow better with the user eyes as they read and scroll down the page.

Your environment

  • Master AT & FW

Expected behaviour

Aligning both buttons to the bottom right hand side of the image would help to concentrate the navigation to remove the potential for missing it and reduce issues with overlapping key areas of the narrative image responsively.

Mock as an example:
Screenshot 2023-10-04 at 11 08 20

Slightly more significant change to inverse the current display of image / text to text / image alongside button movement.
Screenshot 2023-10-05 at 11 49 47

@kirsty-hames
Copy link
Contributor

I like the buttons being positioned bottom right with the text remaining on the right. The user flow sits closer together, image text and buttons.

I often find the current position of the buttons consume a lot of the image, with white space having to be used to prevent the buttons obscuring the imagery. The bottom right position is an improvement.

@swashbuck
Copy link
Contributor

We could also position the controls outside of the component:

Then, for smaller screens, the controls would move inward and the slide area would shrink to prevent overlap.

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

No branches or pull requests

3 participants