Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 3 years ago

Ecommerce Product Page w/ SvelteKit, Tailwind & Typescript.

accessibility, svelte, tailwind-css, typescript
Antoine C•1,240
@mattari97
A solution to the E-commerce product page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello everyone.

This was a very nice project where i took the time to think about accessibility.

I tried to give to the user the possibility so navigate with keyboard only. Using Shift, Shift+Tab, Enter & Escape keys.

Please test it yourself and and let me know if i missed something.

One thing i wonder is how does it feels to use a screen reader. It would be an amazing experience if i could try one but i have no idea how it works, or how to setup one and if there is an open-source screen reader.

Anyway, feel free to share you thoughts on my design/code.

Have a nice day/night. Peace

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Clarence Onumajulu•400
    @clarencejulu
    Posted almost 3 years ago

    Hi Antoine, Your project is really impressive and looks so good to say the least. It's clear you put in a lot of time and effort. I really like what you did with the accessibility and it makes me want to add that to my future projects.

    Can I know how you added those sliding lines to your menu items by the way :)

    Keep up the good work man!

    Marked as helpful
  • Elaine•11,360
    @elaineleung
    Posted almost 3 years ago

    Hi Antoine, this looks really well done, and I'm glad you built with this accessibility in mind, as that is also something I've been doing. I can see you put a lot of work and thought into this!

    I did test it out, and like you, I also wish there's a screen reader I can use to test out code; I tried with my OS but I don't think I know how to operate it well yet. Anyway, here are some things I noted when testing this out with the tab key:

    1. It works well in going between the thumbnails, which is good!
    2. When I hit back tab on the first thumbnail, I got taken to the main full size image; the problem was, I couldn't tab out of it, so I was stuck there 😅
    3. When tabbing to the number input for adding quantities, it would help if the focus style could be right on the buttons. Right now I can only see a blue line, which was a bit confusing to me at first
    4. Adding quantities to the cart worked well with the tab key, which is important

    I had to build a slider recently for a challenge, and here are some links that I found in my research that might be of use to you:

    How to build a more accessible carousel or slider, by Jason Webb

    If you must use a carousel, make it accessible, by Alison Walden

    Well done, and keep building! 🙂

    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 1st-party linked stylesheets, and styles within <style> tags.

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.

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