Design comparison
Solution retrospective
The only thing I really wanted to achieve which I knew would be a bit difficult to grasp was harnessing a media query that would adjust the bottom 'LUXURY' card to turn its width into the width of both the 'SUVS' and 'SEDANS' cards above it while being viewed on a tablet sized viewport.
Any best practices feedback is always welcome! I am still getting into the how to even start refining my process, but it is coming along faster than I thought. This community so far is AWESOME.
Community feedback
- @PhoenixDev22Posted about 2 years ago
Hi Liz,
Well done! I have some suggestions regarding your solution if you don't mind:
- Use the
<main>
lndmark to wrap the.container
the body main content,<footer>
for the attribution.
- About
<h1>
it is recommended not to have more than one h1 on the page. Multiple<h1>
tags make using screen readers more difficult, decreasing your site’s accessibility. In this challenge, as it’s not a whole page, you can have<h1>
visually hidden withsr-only
. Then you can swap those<h1>
with<h2>
.
- In this challenge, what would happen when the user click those learn more? In my opinion, clicking those "learn more" would likely trigger navigation not do an action so button elements would not be right. So you should use the
<a>
. For future use , it's a good habit of specifying the type of the button to avoid any unpredictable bugs.
- Add
border-radius
andoverflow hidden
to the main container that wraps the three cards so you don't have to setborder-radius
to individual corners.
- In this challenge, the svgs are much likely to be decorative. For any decorative svgs, each svg tag should have
aria-hidden="true"
andfocusable=”false”
attributes to make all web assistive technologies such as screen reader ignore those svgs .
- Remember a modern css reset on every project that make all browsers display elements the same.
- Don't capitalize in html, let css text transform take care of that. Remember screen readers won't be able to Read capitalized text as they will often read them letter by letter thinking they are acronyms.
Aside these, great job on this one! Hopefully this feedback helps.
Marked as helpful0 - Use the
Please log in to post a comment
Log in with GitHubJoin our Discord community
Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!
Join our Discord