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

Responsive Profile Page

accessibility
Abdulrahmon Ogunwale•100
@moyinoluwa001
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 most proud of the clean and responsive design of the profile page. The layout is simple yet effective, and it looks great across various screen sizes. I also took care to make the design user-friendly, with a focus on easy navigation and an aesthetic color scheme. The use of flexbox for centering the content and ensuring the layout adapts well to different screen sizes was a key decision.

What would you do differently next time? Next time, I would focus on enhancing the accessibility of the page, particularly by ensuring that all images have descriptive alt text. I’d also make sure that interactive elements like the "Follow" button are more accessible by adding proper keyboard navigation and screen reader support. I might also consider adding animations or transitions to make the page feel more dynamic and engaging.

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

One of the challenges I faced was ensuring the profile layout remained responsive on different screen sizes. Initially, I wasn't sure how to balance the elements (profile picture, cover image, and profile info) in a way that looked good on both desktop and mobile screens.

To overcome this, I relied on flexbox for centering the content and adjusted the image sizes using relative units like percentages and vh (viewport height) for the cover image. I also used the border-radius property to give the profile picture a circular shape and applied margins to make sure the elements were properly spaced. I tested the layout across multiple devices using the browser's developer tools, which helped me fine-tune the design.

Another challenge was ensuring the "Follow" button was visually appealing and functional. Initially, I struggled with making the button stand out without being too flashy. To solve this, I chose a blue color for the button that complements the overall design, with a subtle hover effect that improves user experience.

Overall, the challenge was mainly related to design adjustments for responsiveness and visual appeal, which I overcame through careful CSS styling.

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

I would like help with the following areas:

1.Improving Accessibility: While I made sure the page works well visually, I would love to get some advice on how to improve its accessibility further. Specifically, ensuring that the profile page is fully navigable with a keyboard and adding more descriptive alt text for the images.

2.Enhancing Responsiveness: While I used flexbox to make the layout responsive, I’m curious about the best practices for handling complex layouts on mobile screens, especially when elements like images overlap or get too small on narrower devices. I would appreciate some tips on how to refine the responsiveness for smaller screens.

3.Interactivity Features: I would like suggestions on adding interactive features that could improve user engagement, such as hover effects on the profile info or more dynamic elements like a dropdown for additional actions (e.g., viewing more details or connecting with the user).

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Pedro Henrique Jordão•40
    @vargasneto
    Posted 6 months ago

    great!

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