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

HTML,CSS , BOOSTRAP

bootstrap
Kamlesh•40
@kamlesh2407
A solution to the Social links profile challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Newton Ombese•180
    @nejidevelops
    Posted over 1 year ago

    Good work there, try fixing the following the suggestions and you will have the best of it.

    1. Semantic HTML: The HTML structure is somewhat semantic, as it uses appropriate tags like <header>, <footer>, <h1>, <p>, etc. However, there are some improvements that could be made. For instance, instead of using a <div> with a class of "bio" and "profession", you could use semantic HTML elements like <section>, <article>, or <aside> to represent different sections of the content.

    2. Accessibility: The accessibility of the code can be improved. The image of Jessica should have an alt attribute that describes the image. Alt text is important for users who cannot see the image, such as those using screen readers. Additionally, the buttons should have descriptive text or labels inside them, not just "Github" or "LinkedIn", to improve accessibility for screen reader users. Also, ensure there is sufficient color contrast for text elements to improve readability for users with visual impairments.

    3. Code structure, readability, and reusability: The code structure is relatively simple, but it could be improved for better readability and reusability. CSS classes could be more clearly named to reflect their purpose, making it easier for others to understand and modify the code. Additionally, consider consolidating repetitive CSS rules to enhance code reusability and maintainability.

    Here are some specific suggestions for improvement:

    • Use semantic HTML elements appropriately.
    • Provide descriptive alt attributes for images.
    • Improve color contrast for better readability.
    • Make the layout more responsive using relative units in CSS.
    • Refactor CSS classes for better readability and reusability.
    • Consider adding labels to buttons for better accessibility.
    • Consider increasing the width of the card as yours seems a little bit small
    • Consider also increasing the width of the button and make them links. You can add your links to the href.
    • Consider also adding the hover effects to the buttons and also try using the provided Hexadecimal colors you can find the color codes in the style guide markdown file.

    By implementing these suggestions, you can enhance the accessibility, responsiveness, and maintainability of your code.

    If you have any issues don't hesitate am here to help you anytime. My email is newtonombese1@gmail.com

    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