Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
18
Comments
18
P

Aakash Dasgupta

@a-d14360 points

I’m a mysterious individual who has yet to fill out my bio. One thing’s for certain: I love writing front-end code!

Latest solutions

  • Responsive News Page using CSS Grid


    P
    Aakash Dasgupta•360
    Submitted 10 days ago

    I would like someone to check my website for accessibility and tell me if I missed something. I think the hamburger menu should be good (followed a video for that) but the rest of the website might need a little work.


    1 comment
  • Contact Form with ARIA Labels


    P
    Aakash Dasgupta•360
    Submitted about 2 months ago

    I would like someone to check the accessibility of my form. Since this is my first time learning about accessibility I would like to get some feedback on what I should change/improve on.


    1 comment
  • FAQ Accordion


    P
    Aakash Dasgupta•360
    Submitted 2 months ago

    1 comment
  • Interactive Rating Component


    P
    Aakash Dasgupta•360
    Submitted 2 months ago

    1 comment
  • Quiz Application using HTML, SASS and JS Template Literals


    P
    Aakash Dasgupta•360
    Submitted 3 months ago

    1 comment
  • Password Generator using JS


    P
    Aakash Dasgupta•360
    Submitted 3 months ago

    1 comment
View more solutions

Latest comments

  • P
    GeraASM•410
    @GeraASM
    Submitted 10 days ago
    What are you most proud of, and what would you do differently next time?

    The next time I'll start with the menu

    add new concept with events

    1
    P
    Aakash Dasgupta•360
    @a-d14
    Posted 9 days ago

    You have issues with accessiobility in your hamburger menu.

    • you should label your nav and the hamburger icon button like so :
    <span id="nav-label" hidden>Navigation</span>
    
    // For the open button
    <button id="btnOpen" class="nav__open" aria-expanded="false" aria-labelledby="nav-label">...
    
    // for the nav manu
    <nav class="nav__menu" role="dialog" aria-labelledby="nav-label">...
    
    • if you noticed, I labelled the open button with aria-expanded false and the added role='dialog' to the nav. This is to make an accessible dialog. A dialog is an element that contains extra information that comes into view when a control, in this case a button, is pressed.

    • when the menu is opened, you want to make the rest of the website inaccessible to keyboard and screen readers. To do that, use the HTML's inert property.

    • similarly when the hamburger menu is closed, you want the items in the menu to be inaccessible as well. This must only happen on mobile devices. You can do this used JS. You can detect if a user is on a mobile device using the matchmedia method on the window object.

    Marked as helpful
  • Vedant Agrawal•600
    @vedantagrawal524
    Submitted about 2 months ago

    Contact Form

    1
    P
    Aakash Dasgupta•360
    @a-d14
    Posted about 2 months ago

    Looks good

  • P
    Koxone•580
    @Koxone
    Submitted 4 months ago

    CSS Grid Areas, Flex, JavaScript

    1
    P
    Aakash Dasgupta•360
    @a-d14
    Posted 2 months ago

    nice job! However, your images should be inside a button element as it is better for accessibility and would be more semantic HTML. This would also satisfy the criteria given in the problem statement - user should be able to navigate using keyboard.

  • P
    Koxone•580
    @Koxone
    Submitted 4 months ago

    CSS Grid Areas, Flex, JavaScript

    1
    P
    Aakash Dasgupta•360
    @a-d14
    Posted 2 months ago

    There is a small issue with your project. When you select a rating, the box of the corresponding rating should turn orange. You can implement this by adding a class to the element using JS and in CSS, you can add a declaration under the class selector that turns the background color to orange.

  • guardianprime•260
    @guardianprime
    Submitted 3 months ago
    What are you most proud of, and what would you do differently next time?

    Building with react was good. i even did the darkmode toggle thing that looked hard at first but a little reasearch and i did it.

    what would i do differently? well i would use context api and even the usereducer hook and simplify state handling.

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

    allowing the user to use keyboard as navigation in the app and also the option logic. like how the user sees if the option selected is correct or not instead of just seeing everything that is not correct.

    responsive frontend quiz using react

    1
    P
    Aakash Dasgupta•360
    @a-d14
    Posted 3 months ago

    You need to fix your progress bar, it does not work properly.

  • P
    gkilasonia•270
    @gkilasonia
    Submitted 3 months ago

    password-generator-app

    1
    P
    Aakash Dasgupta•360
    @a-d14
    Posted 3 months ago

    looks good!

View more comments
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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub