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

Helen Chong

@helenclxMalaysia190 points

I am a web developer with 8 years of working experience as a graphic designer.

Latest solutions

  • Advice generator app with vanilla JavaScript

    #fetch#accessibility

    Helen Chong•190
    Submitted about 1 year ago

    0 comments
  • FAQ accordion with HTML, CSS and no JavaScript

    #accessibility

    Helen Chong•190
    Submitted over 1 year ago

    1 comment
  • Responsive newsletter sign-up form using vanilla JavaScript

    #accessibility

    Helen Chong•190
    Submitted almost 2 years ago

    0 comments
  • Responsive Ping coming soon page with vanilla JavaScript

    #accessibility

    Helen Chong•190
    Submitted almost 2 years ago

    0 comments
  • FAQ accordion card without JavaScript


    Helen Chong•190
    Submitted almost 2 years ago

    2 comments
  • Responsive profile card component using Flexbox


    Helen Chong•190
    Submitted almost 2 years ago

    0 comments
View more solutions

Latest comments

  • khalagai•370
    @khalagai
    Submitted 11 months ago
    What are you most proud of, and what would you do differently next time?

    Being able to select a rating independently.

    What challenges did you encounter, and how did you overcome them?
    • Having to select a rating independently. Opted to add the onclick property to each rating.

    Interactive Component rating

    2
    Helen Chong•190
    @helenclx
    Posted 10 months ago

    Good work in completing the project. There are ways that you can improve your solution:

    Use semantic HTML to convey the meaning and purpose of different parts of your page, including to assistive technologies, by using the <main> tag for your main container and using the <footer> tag for your attribution. You can check out these links to learn more about semantic HTML and why to use them:

    • Semantic by MDN Web Docs
    • Why Use Semantic HTML?

    You may remove the white borders and make your background colour cover the entire page, by adding a margin: 0 to your body element's CSS.

    Code this rating component as a form, by using <form> with a fieldset of radio <inputs>, instead of <div> elements with multiple <button>s, since this is challenge is a practice of creating a rating form.

    This will involve rewriting much of your HTML and JavaScript, and you will need to look up how to accessibly style them as well. Modern CSS has an article for this: Pure CSS Custom Styled Radio Buttons. Using a <form> element allows your JavaScript to just listen to the submit event when the form data is submitted.

    Happy coding.

  • Santiago Quintero•160
    @SantiRock
    Submitted almost 2 years ago

    Frontend Mentor | Qr code component

    1
    Helen Chong•190
    @helenclx
    Posted almost 2 years ago

    Congratulations on completing your first challenge!

    You may use different semantic HTML elements for various parts of your page, such as <main> for your main content and <footer> for the attribution. For more about Semantic HTML and why to use them:

    • Semantics
    • Why Use Semantic HTML?

    To improve the responsiveness of your web page, use relative units like rem or em instead of px which is an absolute unit. You can read more about CSS units, including relative units and absolute units here: Learn CSS Units – Em, Rem, VH, and VW with Code Examples

    Happy coding!

    Marked as helpful
  • amaar09•240
    @amaar09
    Submitted almost 2 years ago

    Results-summary-compo

    2
    Helen Chong•190
    @helenclx
    Posted almost 2 years ago

    Hi, the images are not visible in your live site because in your HTML, you set the images' relative paths as /, which represents the root directory, meaning when you deployed your files, the deployed site is trying to look for images located at https://amaar09.github.io/assets/images/icon-reaction.svg, ignoring your Results-summary-component folder.

    On the other hand, the images were visible in your PC might be because Results-summary-component is a root folder in your PC.

    To solve this issue, try changing the paths of your images to ./, by adding a dot before the slash, which represents current working directory, for example ./assets/images/icon-memory.svg. This should make your deployed site look for the image files in your Results-summary-component folder.

    You can read more about HTML file paths here: HTML File Paths

    Marked as helpful
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