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

Four card feature section

accessibility, pure-css
Sunil•370
@SunilBaghel002
A solution to the Four card feature section 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?

Next time, i would made more understandable website with better design

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

I encounter challenges while making website responsive and overcome using flexbox and grid in css.

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

I like fully responsiveness in this website

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mohit kulkarni•170
    @burningbeattle
    Posted 11 months ago

    Semantic HTML:

    Use <article> or <figure> for each card to enhance semantics. Provide descriptive alt text for images. Accessibility:

    Ensure color contrasts meet WCAG standards. Make sure all interactive elements (if any) are keyboard navigable. Use ARIA roles only when necessary. Responsive Layout:

    Adopt a mobile-first approach using min-width media queries. Test across various devices and screen sizes. Ensure consistent spacing and sizing across breakpoints. Code Structure:

    Implement BEM naming conventions for better scalability. Consolidate repetitive CSS rules. Organize CSS for readability, possibly using preprocessors. Adherence to Design:

    Ensure pixel-perfect accuracy in font sizes, spacing, and element dimensions. Implement design-specific interactivity like hover effects. Correct file path typos (assets instead of assests). Optimize font loading by using <link> instead of @import. Use relative units (rem, em) for better scalability. Add transitions and hover effects to improve user experience. By addressing these areas, your project will not only be more robust and maintainable but also provide a better user experience across different devices and for all users, including those relying on assistive technologies.

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