Responsive Web Design - Survey Form feedback

Code Feedback
1

This is a plain and simple survey form. Tell me how it is and if you have any suggestions please tell me.

[https://codepen.io/Computer_Coach12345/full/MWJGbBd

2

Welcome to the forums @swarnodip.sinha. Your form looks good. Some things to revisit;

  • Keep the test script when forking the pen (<script src="https://cdn.freecodecamp.org/testable-projects-fcc/v1/bundle.js"></script>)
    • The test script, with all tests passing, should be included when you submit your projects.
    • Your page passes 1/17 user stories. Click the red button to see which test(s) are failing and text to help you correct the issue.
    • Be sure and read more than just the first line of the failing message. The ability to read and comprehend error messages is a skill you’ll need to acquire as a developer. Ask questions on what you don’t understand.
  • Run your HTML code through the W3C validator.
    • There are HTML syntax/coding errors you should be aware of and address.
    • Since copy/paste from codepen you can ignore the first warning and first two errors.
  • Codepen provides validators for HTML, CSS and JS. Click on the chevron in the upper right of each section and then click on the respective ‘Analyze’ link.
    • The one for CSS is good. Use it and address the issue(s). (Be careful of overwriting yourself)
    • (The one for HTML misses things which is why I recommend W3C)
  • Keep all your styling external. Do not use in-line styling)
  • Change the cursor to a pointer when hovering over the submit button

On a side note, placeholder text should not mirror the label. Rather it should show the format of the expected input.

1 Like
3

Thank you so much. I have fixed the issues.

4

It’s getting better @swarnodip.sinha. Not all issues have been resolved. Some things to revisit;

  • The test script, with all tests passing, should be included when you submit your projects.
    • Your page passes 14/17 user stories. Click the red button to see which test(s) are failing and text to help you correct the issue.
    • Be sure and read more than just the first line of the failing message. The ability to read and comprehend error messages is a skill you’ll need to acquire as a developer. Ask questions on what you don’t understand.
  • As previously mentioned, run your HTML though the W3C validator.
    • There are HTML syntax/coding errors you should be aware of and address.
  • As previously mentioned, codepen provides validators for HTML, CSS and JS. Click on the chevron in the upper right of each section and then click on the respective ‘Analyze’ link.
    • The one for CSS is good. Use it and address the issue(s). (Be careful of overwriting yourself. You may have to run it more than once.)
    • (The one for HTML misses things which is why I recommend W3C)
  • As previously mentioned, keep all your styling external. Do not use in-line styling).
5

This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.