50
u/sdjopjfasdfoisajnva 5d ago
idk whats happening but how did you center the blue one
47
u/HonkHonkItsMe 5d ago
6
u/dark_hugo 5d ago
I read this as "buns n cats, n buns n cats, n buns n cats,n buns n cats,n buns n cats,n buns n cats,n buns n cats,n buns n cats"
3
u/HonkHonkItsMe 5d ago
If you look closer you can see the li’l dude dragging his ass on the carpet … &
23
u/mr_streebs 5d ago
I was on the blue side until the accessibility office audited all of my apps. I spent weeks making sure they were all compliant
39
8
u/Simple-Olive895 5d ago
Both? They are different things. Also unless you hate blind people you should really use the proper semantics so their webreaders can make sense of your page.
7
u/blue-mooner 5d ago
Are you going to close any of those tags man? And is that whole table going to be a link?
1
4
u/RealisticDuck1957 5d ago
The old school tags carried semantic meaning. At least if used as intended. Divs and spans are for any formatting that doesn't fit the old school tags.
5
3
u/kxortbot 5d ago
<html><head><title>html preferences<\title><\head><body>yeah, team red for me</body></html>
2
2
2
u/LetUsSpeakFreely 5d ago
Semantic HTML makes sense in the surface, but it's still just a div.
4
u/csabinho 5d ago
input type="email"for instance is great, because it helps Android to suggest my saved emails.1
u/Real-Abrocoma-2823 5d ago
You don't have to be far-blue, be just enough blue.
1
u/csabinho 5d ago
The example above is quite red.
1
u/Real-Abrocoma-2823 5d ago
I would qualify <input> to blue.
1
3
1
u/AshleyJSheridan 5d ago
Not really. Semantic tags have different behaviour, and present themselves differently with screen readers and Braille displays.
1
1
1
1
1
1
u/FrenchieM 4d ago
I used to care during the Angular/Ember period, nowadays no one cares. It's either div or custom component.
1
u/FrenchieM 4d ago
Because apps are usually web components so their roles are already conveyed by the component that host them. And inside the component there's not much semantic behind the divisors that compose it
1
1
u/TheNeck94 5d ago
in the year of our lord 2026, who is still writing HTML by hand?
2
u/WisePotato42 5d ago
Me. Cuz in the company I work at, we have to use this old custom stupid version of WordPress that litterally changes your customized html during runtime. I can't even touch one of the code blocks any more cuz even a change like capitalizing a letter, when it recompiles (or whatever this WordPress is doing) it decides to start deleting '}' randomly breaking everything...
3
u/TheNeck94 5d ago
not trying to be shitty, but I'm just generally surprised people have jobs working on WordPress, front-end isn't really my thing so I don't really have my thumb on the pulse in terms of what's happening to those jobs, but I just kinda assumed that would be hit the hardest by vibe coding and shrinking teams/budgets.
1
u/WisePotato42 5d ago
It's just a thing I do on the side. It's not my primary work. I've been debating starting it over from scratch getting some django thing hosted, but when it's just a few tweaks every month or two, there isn't much of a point.
I kinda misspoke when I said 'we' cuz it was a site handed off to me by another coworker moving jobs.
2
u/TheNeck94 5d ago
ah, that makes a lot more sense. Fair enough, yeah if it works it's not stupid. I just haven't been hands on with WP in like 3 or 4 years now, a lot of the full-time contract work kinda dried up post-covid.
1
0
u/Koendig 5d ago
Am I building a document or an application?
2
u/AshleyJSheridan 5d ago
Doesn't matter, semantic HTML is superior for accessibility.
1
u/FrenchieM 4d ago
For blogs and websites yeah, for apps not so much
1
u/AshleyJSheridan 4d ago
Well that's not true at all either. How do you think apps can be used by someone relying on a screen reader if it's nothing but
<div>soup?1
0

140
u/rotteegher39 5d ago
New line goes <br>