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

[DEV-027] Footer #46

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from
Open

[DEV-027] Footer #46

wants to merge 2 commits into from

Conversation

DigestedLime
Copy link
Member

[DEV-027] Footer

Fixes: #27

  • Has the code been formatted?
  • Have dependencies/packages been added?

Changes

Made a responsive footer for the website, with text/design matching the Figma story.

Testing

  • Does the code have sufficient automated test coverage? If not, include a reasoning and steps required to manually QA

@DigestedLime DigestedLime added the frontend Work related to the frontend label Jan 7, 2021
@vercel
Copy link

vercel bot commented Jan 7, 2021

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/white-van/dialog/4o691o30h
✅ Preview: https://dialog-git-dev-027.white-van.vercel.app

Copy link
Member

@AipioxTechson AipioxTechson left a comment

Choose a reason for hiding this comment

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

Love it! Just one tiny fix~

Hello{" "}
</a>
</footer>
<Flex className={styles.footer}>
Copy link
Member

Choose a reason for hiding this comment

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

Suggestion: Since this component is used outside of the main component, we need a semantic sectional HTML element wrapping it, rather than a div. Can we wrap this in a footer?

Suggested change
<Flex className={styles.footer}>
<Flex className={styles.footer} as="footer">

Reference: https://www.w3.org/TR/wai-aria-practices/examples/landmarks/HTML5.html

Copy link
Member Author

Choose a reason for hiding this comment

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

Ah okay, just read up on the ARIA practices and accessible considerations! Does your fix automatically do the role="footer" tag onto the footer as well?

Copy link
Member

Choose a reason for hiding this comment

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

It doesn't automatically add a role="footer", rather it's a replacement to it!
It's recommended to use semantic html elements over adding roles to ambigious elements.
I believe just having it as a footer html element should be sufficient considering we're only using it at the end of the page, (if we're using footers in a different context then we'd have to specific what role it is!)

If I remember correctly, the default role of a footer is contentinfo, so the role would be that I think

Copy link
Contributor

@jcserv jcserv left a comment

Choose a reason for hiding this comment

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

Nothing else to add that @AipioxTechson did not say, so approving!

Oops I thought of something haha

@jcserv jcserv self-requested a review January 10, 2021 01:03
© 2020 White Van, Inc.
</Heading>
<Text fontSize="xs" color="white">
made with ❤ by pizza van
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we internationallize this + the footerLinks?

@@ -15,6 +18,8 @@ describe("Footer", () => {

it("Basic render functionality", () => {
const { queryByText } = render(<Footer />);
Copy link
Member

Choose a reason for hiding this comment

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

I realized this a bit late but -- can we use renderWrapped exported from the helpers.tsx file instead of render -- it's because renderWrapped has the appropriate providers wrapped and would give us a better picture on the actual component we're testing!

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

Successfully merging this pull request may close these issues.

Footer
4 participants