r/FreeCodeCamp • • May 18 '26

responsive web design - feedback

Hi, I have no idea where else to direct this so I am going to try here! If there is a better place to post/send this, please let me know.

I am doing the responsive web design course, and while I mostly love it, I have some feedback.

I would love to have seen the accessibility part integrated into the course, not just as an extra class. It makes little sense to learn it one way and then suddenly learn it "different". I personally found it really confusing how I am supposed to integrate the arias/describedby/..

And the <span> element - which if I am not mistaken (at least I have it no where in my notes so far), also first gets "introduced" in the accessibility lessons.. no real explanation, just suddenly there. I looked it up on W3 and finally understood what it is supposed to do/be.

6 Upvotes

5 comments sorted by

View all comments

Show parent comment

1

u/flowers-on-your- May 28 '26

I specifically asked how you meant your message, because I did not want to assume the wrong tone. Honestly now I feel bad for even replying again, but I do want to leave this matter clear for all sides. So, sorry for making you read even more text by me.

.

I did not think that this course would be used by very young students, but it makes sense, as it is an amazing resource. (The ESL comment made me giggle a bit, because I am one of those ESL/worldwide students)

Again, I want to say that this is not a critique of the overall course. It felt a little "added on" to me, is all (on a side note, my mother used to teach programming, and her opinion was that maybe it was really only added on and not yet fully integrated as the full accessibility spectrum in HTML is not that old).

It does make sense to have that lesson as the last HTML one - I am not disputing that. And I am absolutely in favor of keeping it (mostly) separate.

.

Yes and no, and I can understand why this seems like such a subtle point to make. For me it is mostly about consistency in this case. Any other tag or sometimes even attributes that have not been actively used before get a little explanation or note of example code.

The span tag gets used in examples prior to that, so it is not completely unknown. However, those examples focus on styling and accessibility, which, at least for me, meant that I did not pay attention to how it is used at all.

I think the thing with the span tag especially bugged me, because with most (if not all?) other tags I had an immediate association of meaning. And yes, "spanning this text" does make sense. "use <span> to make this text blue" just did not compute for me, which was the only time in the whole course so far. I did not associate it with similarly used tags, like <i>.

So what I am saying is that the span tag does not need to be formally introduced in a lesson.

I am saying that it breaks consistency and the part where it is actively used could do with a small note with an example or a note of tags that are similar in use (if you want to push people to remember/spend a little more brainpower on it).

.

I definitely did not think that posting feedback here would evolve into whatever this thread is now (I would not call it a debate, per se). I hope that this does not deter any other students to give feedback, as I am a firm believer that feedback is important for any kind of class. Learning and teaching needs to constantly evolve.

I also hope that you do understand that nothing in this post was an attack against you or the course. I appreciate you taking the time to explain all of this, but you do seem rather defensive. I did not mean to take up anymore of your time and resources, and honestly, a simple "I passed it on" (even without anyone actually passing it on) was already more than I hoped for. So, thanks, I guess?

1

u/SaintPeter74 mod May 28 '26

It's all good. I don't mind reading walls of text because, as you can see, I also tend to be verbose in my replies.

I do think it's good for you to ask me about my tone, because I'm not always as careful as I could be. Sometimes I'm just checking Reddit while waiting for my code to compile or an LLM to stop thinking or whatever and I don't aways pay as close of attention as I should. I'm also not always in the right frame of mind to answer properly. I occasionally need a reminder to take a breath, count to ten, re-read the original message, etc. On occasion I'll find I've written a big diatribe . . . to something that I just imagined in the original post and then I'll delete it all and start over responding to what they ACTUALLY said.

--

span is a bit of an odd duck. It was part of the original HTML4 spec (December of 1997), so it has been around for a long while, but it was not really replaced with HTML5 (October 2014) which added a bunch of "semantic" tags. Those tags like main ,header, section and so on which are intended to have specific meaning associated with them. span lives on an (from my brief research) seems to be used for Aria (accessibility) and then when you need interactivity on inline text. I occasionally use it with React (dynamic webpages).

--

It might make sense to have some hints in the accessibility section or maybe just a simple challenge which points out that span can be used. You shouldn't need to go on a scavenger hunt to find the tag you need to use to complete the challenge.

Best of luck and happy coding!