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

submit a message using pure-css

pure-css
Chame "Guigui-chan"•290
@Guilherme-Porto-Silva
A solution to the Contact form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

I had trouble setting up the border radius, the containers would aways look distorted. Overcame it by uploading the desktop-design.jpeg on Google Gemini and asking it to write a list of values I should put. It gave me a smaller and a less small value for each container, so, I decided to put the less small ones in the media querie. The values it gave were like "2px", I was previously using like "5%", so, no wander why the containers were looking like skate parks.

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

Reading this learning path articles was the very first time I came across the name "W.C.A.G.", so, I am as new I as could possibly be in this world. If anyone knows aria proprietys I should have used and did not, tell me, and etc.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Muhamad Rukhul Kirom•380
    @rukhulkirom
    Posted 4 months ago

    Hello there 👋. Good job on completing the challenge!

    I have some suggestions about your code that might interest you.

    1. Improve Label Association

    Your labels don't have for attributes pointing to inputs properly. Example:

    <input type="radio" name="QueryType" id="GeneralEnquiryInput">
    <label for="GeneralEnquiryInput">General Enquiry</label>
    
    1. Your fieldset doesn't have a legend, making it less accessible for screen readers.
    <fieldset>
      <legend>Query Type</legend>
      <label for="GeneralEnquiryInput">
        <input type="radio" name="QueryType" id="GeneralEnquiryInput"> General Enquiry
      </label>
      <label for="SupportRequestInput">
        <input type="radio" name="QueryType" id="SupportRequestInput"> Support Request
      </label>
    </fieldset>
    

    I hope you find it useful! Above all, the solution you submitted is great!

    Happy coding!

    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 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.

Oops! 😬

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

Log in with GitHub