Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Blog Preview Card using HTML & CSS w/ hover & focus states

Andi•140
@AStombaugh
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I got the design pretty close and the hover and focus states seem to work

What challenges did you encounter, and how did you overcome them?

Mostly just trying to get the design as close as possible on desktop and mobile. I used a media query to tweak the mobile version just a little bit to match the image.

What specific areas of your project would you like help with?

Ensuring that I got the accessibility portion correct this time, as I did not do that on the first project. I think the code is sound though.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alex•3,130
    @Alex-Archer-I
    Posted about 1 year ago

    Hi!

    It seems that you put a lot of effort to make your work accessible! That's cool, but I'm afraid you did a bit of unnecessary work.

    At first, semantic tags and their text content usually provides enough information for accessibility gadgets. Attributes like role and related to them, like aria-roledescription, override initial roles of the elements, therefore they should be used only in a very rare cases when you can't use relevant tags. For example, when you work with some tricky custom elements or... mmm... your crazy boss have weird superstition about a tag, but you still need to explicit that element have link role. Sorry, a can't make up a serious example right now, but they exist =)

    Second, there is no need to wrap every tag in the section. It'll make your code more complex, less readable and could be cause of optimization problem. h1, p, img and the others already have all the necessary semantic information and could be styled directly.

    But, really, that's cool that you tried to implement all this (I'd be too lazy =))

    Oh, and since I'm already all chatty here, I can give you a couple advices:

    • Use rem for font sizes. This value depends on user's font size settings and it's their primal purpose.
    • Keep styles and HTML in separate files. The bigger your project become, the less convenient it will be to maintain all like this.
    • Try not to hardcode height and width of your container. It's better when the height depends on content (it's default auto value) and for width you can use this trick:
    main {
        width: 95%;
        max-width: 24rem;
    }
    

    That way main will keep 24rem width on the big screens and will become 95% on the small ones.

    Well, I hope it could help =) You are doing great, good luck =)

    Marked as helpful

Join 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

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub