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

Contact form main using pure html,css and javascript responsive design

Mohamed Khairy•190
@mo7amed5hairy
A solution to the Contact form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

Well, am so proud because in this challenge i had to deal more with form validation using javascript and i learned a lot from that i gained good experience in dealing with forms, validating fields with different types using foreach and for loop and regex validation for mail , i think in next time i will learn how to be more professional when dealing with forms maybe writing more professional code than that i wrote in this project

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

many challenges actually first, i had to write the form components and i mean here with components fields like input , email,textarea and check and radio boxes with more organizing and professional manner that achieve the web accessibility such as dealing with aria and writing inputs with labels, grouping radion and checkbuttons with fieldset and using legend which are things that i didn't get used to do in previous , so i overcomed that with reading about arias with deploying what i read so i learned a lot from this challenge actually

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

i think all project parts and areas were very important for me but i can say that the most important part is javascript part because i had to focus in it when dealing with form inputs to make the write and clean code and to a chieve the goals of the challenge

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Crystalis89•440
    @Crystalis89
    Posted 5 months ago

    Looks about as close as mine visually. A few small things is:

    Maybe replace the divs with Semantic HTML, I used <section> but am unsure if there a better alternative. Semantic doesn't just improve accessibility but also helps the dev read the code and it's structure easier than compared to nested divs.

    https://developer.mozilla.org/en-US/blog/aria-accessibility-html-landmark-roles/

    And according to documentation <legend> is often used with <fieldset>

    "Legend is a broad label used for a group of objects. Label is used for labeling specific elements."

    https://accessibleweb.com/question-answer/what-is-the-difference-between-legend-and-label-elements/

    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