This section of the curriculum is broken

This section of the curriculum is broken. I have entered in the exact line of code a 1/2 dozen times and it is not accepted. I have watched the video and written the code to specification. Watch the video provided for the video & compare my code. This is extremely frustrating!

Your code so far


<h2>CatPhotoApp</h2>
<main>
<p>Click here to view more <a href="#">cat photos</a>.</p>

<a href="#"><img src="https://bit.ly/fcc-relaxing-cat" alt="A cute orange cat lying on its back."></a>

<p>Things cats love:</p>
<ul>
  <li>cat nip</li>
  <li>laser pointers</li>
  <li>lasagna</li>
</ul>
<p>Top 3 things cats hate:</p>
<ol>
  <li>flea treatment</li>
  <li>thunder</li>
  <li>other cats</li>
</ol>
<form action="/submit-cat-photo">
  <input id="indoor"> type="radio" name="indoor-outdoor">
  <label for="indoor">Indoor</label>
  <input id="outdoor"> type="radio" name="indoor-outdoor">
  <label for="outdoor">Outdoor</label>
  <button type="submit">Submit</button>
</form>
</main>

Your browser information:

User Agent is: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0.

Challenge: Create a Set of Radio Buttons

Link to the challenge:

Hello and welcome to the FCC community~!

You have an extra > after your id, which is causing the tests to fail. :slight_smile:

I removed the extra > after id, but I am still getting an error message that says " Each of your two radio button elements should be nested in its own label element."

Everything else seems to be correct. Any advice. Thank you for respoding to my question.

The failing test now says

Each of your two radio button elements should be nested in its own label element.

You need to follow the written example and nest your radio button elements inside of their corresponding labels.

Example from challenge description:

It is considered best practice to set a for attribute on the label element, with a value that matches the value of the id attribute of the input element. This allows assistive technologies to create a linked relationship between the label and the child input element. For example:

<label for="indoor"> 
  <input id="indoor" type="radio" name="indoor-outdoor">Indoor 
</label>
2 Likes

It is unfortunate that the video has not been updated to reflect the requirements. I did try (here is the issue) to get it updated but it never happened. I might ping the issue again just to give it one last go.

Anyway, you can’t use the code in the video to pass the test for the nested inputs. So do what @JeremyLT said to do.

That video really does need to be changed. I’m sure it has confused a number of students. Thank you all for your help. Joy…Screenshot from 2020-08-13 18-55-35

I have mixed opinions on the video being slightly different. Yeah, we want our videos to be accurate, but at some point developers need to transition from videos to written documentation. The transition is rough but must occur at some point. I don’t mind explaining this point over and over to help that transition.

1 Like

I think having incorrect code in the video is worse than not having a video at all.

At least unless it is made very clear that the video is just an example and can not be used for the solution. Otherwise, it’s just confusing that suddenly one video is not showing the correct code.

It’s technically a bug with the curriculum when a challenge is changed and the video is not updated to reflect the changes.

Again, I don’t mind there not being a “solution” video, but it should be made more clear then.

2 Likes

That I can agree with. I don’t think that the videos should be character for character walk-throughs of the solutions but rather instructional aids to help students think about and understand the material. If they give character for character solutions, then they defeat their purpose and encourage students to engage with the material less.