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

Responsive Portfolio Website Using HTML, CSS, and JavaScript

accessibility, parcel
Stephen Ikuomola•610
@stephenikuomola
A solution to the Single-page design portfolio 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?

Honestly, Implementing the slider functionality was not easy. I had to do loads of research before I could develop the solution. I made it possible for users to navigate the slider using the arrow key on their keyboard, as well as a mouse or trackpad. I am also happy to see the website being very responsive across all devices.

In the future, I might clean up my code and use a library to implement this slider functionality.

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

I encountered a challenge when building the slider. It is essential that sliders or carousels are accessible to all users and that navigating them is easy to implement. With the help of some resources, I was able to do that. I also better understood DOM traversing; I learned about events that I had never used before before this challenge. I also learnt some techniques that can be used when working with certain pseudo-classes and pseudo-elements.

Resources:

  • Working with focus states
  • Listening for when the window is resized
  • Working with debounce and throttle to control the execution rate of events handlers -MouseEvents, its properties and its methods
  • KeyboardEvents, its properties and its methods
  • TouchEvents, its properties and its methods
  • Prevent touch event handler from blocking
What specific areas of your project would you like help with?

I am always open to suggestions on how to improve this challenge and make my code cleaner and more efficient.

Thank You 🙏

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Stephen Ikuomola's solution.

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.