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

Banner accessibility - refactor moment template #781

Draft
wants to merge 19 commits into
base: main
Choose a base branch
from

Conversation

KaliedaRik
Copy link
Contributor

@KaliedaRik KaliedaRik commented Nov 1, 2022

What does this change?

We need to refactor the Moment Template component to make it amenable for our planned banner accessibility fix

Screenshots (generic banner with image)

Mobile
Screenshot 2022-11-09 at 13 41 38
Screenshot 2022-11-09 at 13 41 54
Screenshot 2022-11-09 at 13 42 07
Screenshot 2022-11-09 at 13 42 20
Screenshot 2022-11-09 at 13 42 36

Tablet and wider
Screenshot 2022-11-09 at 13 42 54
Screenshot 2022-11-09 at 13 43 09
Screenshot 2022-11-09 at 13 43 22
Screenshot 2022-11-09 at 13 43 40
Screenshot 2022-11-09 at 13 43 51

Additional parts of the banner exposed
Screenshot 2022-11-09 at 13 44 11
Screenshot 2022-11-09 at 13 50 23

@KaliedaRik KaliedaRik marked this pull request as draft November 1, 2022 14:39
reminderTracking,
separateArticleCount,
includeSignIn,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this a new feature you're adding to the moment banner?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, but ... the more I think about it, the less I like it. We do need asignIn attribute which will include the sign-in copy and CTA line, which appears in some existing Banners, either following the body copy or following the CTA buttons.

This fix would allow us to add a dropdown to the RRCP banner variants form for Marketing to add the sign-in line (= easy A/B testing). But I'm now thinking that this is more of a design choice and we should probably set the signIn attribute in the JSON that gets fed into the Moment template. If Marketing want banner variations with/without the sign-in line then engineers can create two banners from the template and make them available in the RRCP banner dropdown.

Thoughts?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if the moment template banner doesn't currently support the feature then I'm not sure how it relates to the accessibility task?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed. Will fix when we refactor existing banners which use the sign-in link to use the Moment template

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

Successfully merging this pull request may close these issues.

2 participants