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

Social links profile card using HTML and CSS

accessibility
Gustavo Gutiérrez•370
@gustavo2023
A solution to the Social links profile 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'm proud to say that I managed to build this project fairly quickly in comparison to the previous two challenges, especially considering that this time I didn't use the Figma design. From the structure of the HTML to the styling using CSS, everything went quite smoothly.

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

There wasn't any particular challenge, except making the elements clickable. I had to make the elements occupy the same space as the list items to solve that problem.

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

Feedback on any improvements I can make whether is in the HTML structure or the way I styled the elements is more than welcome. Any feedback on accessibility improvements or things I am missing currently would be useful as well.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Salva•290
    @salva-it
    Posted 11 months ago

    Your code is well written and well structured. I suggested that the <footer> tag should be placed inside the <main> tag in your code. The closing <footer> and <main> tags seem to be misplaced In general, your codes are very good, congratulations

    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