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

Mobile-first responsive social link profile

accessibility, bem
haquanq•2,035
@haquanq
A solution to the Social links profile challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abdulgafar-Riro•250
    @Abdulgafar-Riro
    Posted 7 months ago

    Feedback for Haquanq's Social Links Profile Solution

    1. Semantic HTML

    Strengths:

    The project uses semantic tags such as <main>, <section>, <nav>, and <footer> effectively.

    Proper use of heading tags (<h1>, <h2>) makes the content structure logical.

    The use of aria-label on navigation links is commendable for improving accessibility.

    Suggestions for Improvement:

    Include a <header> tag if applicable to better represent the start of the content structure.

    Add <ul> or <ol> inside the <nav> to group the links semantically, especially since it's a list of social links.

    1. Accessibility

    Strengths:

    The color contrast between text and background meets accessibility standards.

    aria-label attributes enhance screen reader compatibility.

    Hover and focus states are clear and provide good feedback for interactive elements.

    Suggestions for Improvement:

    Include alt text for images that describe their content meaningfully (e.g., the avatar image could use a description like "Jessica Randall's profile picture").

    Add a skip navigation link for better keyboard navigation.

    Use rem or em for font sizes to respect user accessibility settings.

    1. Responsiveness

    Strengths:

    The layout adapts well to different screen sizes, maintaining good readability and spacing.

    The mobile-first workflow ensures smooth scalability.

    Suggestions for Improvement:

    On larger screens, consider increasing the max-width of the card for better use of space.

    Test the design on more screen widths to ensure no content appears cramped or stretched.

    1. Code Structure

    Strengths:

    The CSS is modular with custom properties (CSS variables), making it reusable and easy to maintain.

    The project adheres to a clear and consistent naming convention for classes.

    Suggestions for Improvement:

    Consider organizing CSS into separate files if the project scales (e.g., base.css, components.css).

    Use comments in the CSS file to group styles logically (e.g., typography, layout, utilities).

    1. Design Alignment

    Strengths:

    The design closely matches the original challenge's layout and style.

    Hover states align well with the design's intent, providing a good user experience.

    Suggestions for Improvement:

    Review spacing and alignment to ensure consistent padding and margins (e.g., between the avatar and name or between the links).

    Adjust the avatar size slightly for better balance in larger viewports.

    Overall Feedback

    This is a solid solution that effectively meets the challenge requirements. The semantic HTML and accessibility considerations are commendable. With minor adjustments to responsiveness, accessibility, and code organization, this project could be even more polished. Keep up the excellent work!

    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