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

Semantic HTML5 form with JS validation

Dmitry•375
@dmitrymitenkoff
A solution to the Intro component with sign-up form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This has been a great challenge for me to practise creating semantic forms using HTML5 and JS. While I completed the challenge, I feel I'd like to learn more about current best practice for creating web forms. I've read through a lot of online resources and couldn't find anything more or less definitive on this point. Cheers

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dmitry•375
    @dmitrymitenkoff
    Posted almost 4 years ago

    Hey Teegamtee, thanks for your feedback.

    You're quite right to comment on the lack of responsiveness, I've added a breakpoint for a tablet view as well. I originally ignored adding other breakpoints simply because this particular design is just a component and I thought following the provided figma designs would suffice. But I can see how it could've been upsetting to have a mobile view displayed on a large screen.

    In terms of responsiveness in general, I thought it was more than just having a number of breakpoints but rather using relative units, min and max values, mobile first, web safe fonts, etc.. Please feel free to share any resources or point me in the right direction if I should incorporate other features of responsive design in the future - I'd be keen to learn more!

    Cheers and have a lovely day

  • Account deletedPosted almost 4 years ago

    Hi,

    Your solution looks ok at 1440px, and then anything below that is mobile view.

    • 1440px looks good but I was quite shocked to have mobile view literally starting 1px below 1440px, and all that white empty space it comes with on the sides don't look good.

    • This way I wouldn't say it's responsive because you only have it catered for two screens, 1440px and 375px, & in the styles guide that you are given, the 1440px for desktop and 375px for mobile they are to simply give you a picture of how big your site is to be in relation to the screen width, they are not telling you to only have your solution working on those two screen width but also in between.

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

Oops! 😬

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

Log in with GitHub