Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 9 months ago

blog-preview-card's solution Accessibility Friendly

accessibility, sass/scss
Ahmed Aziz•90
@Abo3bazez
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?

"This is my first time using rem and considering accessibility. I hope I used them correctly."

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

nothing really

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

"The use of rem and accessibility I think I did not use them the right way."

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Huy Phan•3,430
    @huyphan2210
    Posted 9 months ago

    Hi, @Abo3bazez,

    I reviewed your solution and have a few thoughts:

    • There aren’t strict rules when using rem, and I'm not sure what you meant by "accessibility" in that context.
    • While it’s technically fine to use decimal values like 0.91rem or 1.3rem, I wouldn't recommend it for consistency. Since rem is a relative unit based on the root html font size (which is usually 1rem = 16px unless modified), I personally prefer to stick with rounded numbers. If I use decimals, I go for values like 1.25rem, 1.5rem, or 1.75rem. If you feel that values like 0.91rem or 1.3rem work better, then using px might make more sense for precision.
    • Accessibility covers many areas. If you were referring to semantic HTML, you’ve done a good job, but there’s always room for improvement. You can draw inspiration from established design systems, like Google’s Material Design or Apple’s Human Interface Guidelines.

    Hope this helps!

    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
Frontend Mentor logo

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