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

Responsive social links profile

AllisonFavour•170
@AllisonFavour
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?

Same as always, i am proud and happy of not stopping halfway, i got it completed within few hours.

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

The only challenge i encountered was when i had to decide to either use a button tag and then nesting an anchor tag inside the button for the links or using an anchor tag directly and styling it to look like the button.

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

The part where they said we should ensure users can navigate the links using a keyboard, i need some clarity on that and how to go about it, although when i am chanced proper google search and a conversation with claude or chatgpt will give some insight which i will intime.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Martin Liesche•590
    @marliedev
    Posted 10 months ago

    Nice Job Allison. Code structure (HTML and CSS) is readable and looks clear and good. Maybe i wouldn't use a h2 for the location info.

    Regarding your question to the keyboard optimisation: You used anchor tags which is the best options. They don't need a aria-role or tabindex attribute. Navigation and highlighting (:focus, :focus-visible) works fine with these. You should have added a target:"_blank" attribute to the anchor-links. This is just a usability optimization.

    What you could have added is a screenreader optimisation in form of a "screenreader-only"-info that tells blind people a bit more about what will happen when they use the links.

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