Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
13
Comments
2

Drishti Saraf

@drishti1920India130 points

Web Developer in training

Latest solutions

  • Social Proof Section

    #pure-css

    Drishti Saraf•130
    Submitted 3 months ago

    0 comments
  • Coming Soon Page


    Drishti Saraf•130
    Submitted 7 months ago

    I'd like help with refining the image layout, especially ensuring that the images scale well and remain visually appealing across different screen sizes. While I've made progress in setting the image to be responsive using CSS techniques like object-fit: cover and object-position: top, there are still some areas where the image might not appear as intended on certain screen resolutions or aspect ratios. I would appreciate suggestions on how to make the image layout more adaptable and ensure that it doesn't get cropped or distorted on smaller devices.


    0 comments
  • 3 column layout


    Drishti Saraf•130
    Submitted 7 months ago

    1 comment
  • Preview Card Component


    Drishti Saraf•130
    Submitted 8 months ago

    I’d like guidance on making the project more accessible for users relying on assistive technologies. While I’ve used semantic HTML, I’m unsure if I’ve covered all accessibility best practices, such as proper ARIA roles or enhanced keyboard navigation.


    1 comment
  • Order Summary Component


    Drishti Saraf•130
    Submitted 8 months ago

    While I’ve made the layout responsive, I’d like feedback on how I can improve the design for smaller screens. Are there any best practices I missed or additional tweaks I can make to improve usability on mobile devices?


    0 comments
  • NFT Card Component


    Drishti Saraf•130
    Submitted 8 months ago

    Although I’ve added some basic accessibility features, such as semantic HTML tags and alt text for images, I’m not entirely confident in how well the component will be understood by screen readers. I would appreciate advice on best practices for improving accessibility for users who rely on screen readers, especially with interactive elements like the hover effect and icons.


    2 comments
View more solutions

Latest comments

  • Kedar Gavali•670
    @Kedar37
    Submitted 8 months ago
    What are you most proud of, and what would you do differently next time?

    suggestions welcome

    FAQ accordion solution

    1
    Drishti Saraf•130
    @drishti1920
    Posted 8 months ago
    1. Event Targeting You're correct that adding the event listener to the entire .subtitle div (instead of just .question) would improve the user experience. It ensures users can toggle the accordion by clicking anywhere on the question's container, not just the text.

    2. Improper id Usage Using the same id="answer" for all <p> elements is invalid since IDs must be unique within the document. Use classes instead.

    3. Font Family Issue In the body rule: font-family: '', sans-serif; The font-family is empty. Include the correct font.

  • Carlos Gómez•110
    @CarlosLDC
    Submitted 8 months ago

    QR code component

    #pure-css
    1
    Drishti Saraf•130
    @drishti1920
    Posted 8 months ago

    Ensure proper use of ARIA roles and attributes. Add descriptive alt text for images and ensure color contrast ratios meet WCAG guidelines.

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