Expecting all devs to test their sites with screen readers is unrealistic.
I disagree with this but its not what we're talking about. You said output is useless and I'm saying its obviously not. There's zero cost to using it instead of a div so the only reason not to use it is to purposefully screw users who need accessibility features.
All those other elements give some benefit apart from accessibility
Maybe for label but p and h1 - h6 only differ from div in styles, which is another argument in my favor. If you're willing to swap a div for one of those for visual users, swapping a div for output should be just as easy of a change.
There’s zero cost to using it instead of a div so the only reason not to use it is to purposefully screw users who need accessibility features.
No, the main reason is because people don't know about it, because it's an extra thing to remember for little benefit. Same reason other semantic-only tags like article get very little use.
only differ from div in styles
Err yeah the "only" do a really useful thing that lots of people want.
If output came with some nice styling and maybe animations... maybe a built in copy-to-clipboard option... then people would have used it.
the main reason is because people don't know about it
But you know about it now and you're still arguing against it.
it's an extra thing to remember for little benefit
the "only" do a really useful thing that lots of people want.
The benefit you see in those tags is the same level of benefit that users who use accessibility features get from output and other semantic tags. But your argument seems to boil down to "I dont need accessibility features so i don't care about enabling them for ppl who do". That's very disappointing and continuing this debate seems pointless so i'm gonna stop here
What do you mean by "instead of watching"? OP links to a text article.
I still prefer your MDN link though. Concise, and a more readable layout. Dunno why OP felt the need to increase the font size that much into a wide layout.
13 Comments
FizzyOrange@programming.dev · 21 pts · 300d
Less "best kept secret" more "not very useful so nobody cared to learn about it".
0x1C3B00DA@fedia.io · 1 pts · 298d
Nearly every web app that uses an
inputcalculates and displays some result based on those inputs. It's clearly useful.FizzyOrange@programming.dev · 1 pts · 297d
You can do that with a div. Its only use is slightly improved default accessibility behaviour.
0x1C3B00DA@fedia.io · 1 pts · 297d
Yes exactly. Which is reason enough to use it, unless you purposefully want worse accessibility.
You could make the same argument about
p,h1-h6,label, etc.FizzyOrange@programming.dev · 1 pts · 296d
All those other elements give some benefit apart from accessibility which is why they are universally used and
outputisn't.Expecting all devs to test their sites with screen readers is unrealistic.
0x1C3B00DA@fedia.io · 1 pts · 296d
I disagree with this but its not what we're talking about. You said
outputis useless and I'm saying its obviously not. There's zero cost to using it instead of a div so the only reason not to use it is to purposefully screw users who need accessibility features.Maybe for
labelbutpandh1-h6only differ fromdivin styles, which is another argument in my favor. If you're willing to swap adivfor one of those for visual users, swapping adivforoutputshould be just as easy of a change.FizzyOrange@programming.dev · 1 pts · 296d
No I said it's not very useful.
No, the main reason is because people don't know about it, because it's an extra thing to remember for little benefit. Same reason other semantic-only tags like
articleget very little use.Err yeah the "only" do a really useful thing that lots of people want.
If
outputcame with some nice styling and maybe animations... maybe a built in copy-to-clipboard option... then people would have used it.0x1C3B00DA@fedia.io · 1 pts · 296d
But you know about it now and you're still arguing against it.
The benefit you see in those tags is the same level of benefit that users who use accessibility features get from
outputand other semantic tags. But your argument seems to boil down to "I dont need accessibility features so i don't care about enabling them for ppl who do". That's very disappointing and continuing this debate seems pointless so i'm gonna stop heretreadful@lemmy.zip · 14 pts · 300d
I've been writing HTML since like '98 and am just learning about this tag now.
ZTechnical@programming.dev · 12 pts · 299d
If you prefer reading instead of watching:
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/output
Kissaki@programming.dev · 6 pts · 299d
What do you mean by "instead of watching"? OP links to a text article.
I still prefer your MDN link though. Concise, and a more readable layout. Dunno why OP felt the need to increase the font size that much into a wide layout.
ZTechnical@programming.dev · 5 pts · 298d
I have no idea why I thought it was a video.
cupcakezealot@piefed.blahaj.zone · 9 pts · 299d
htmls best kept secret; the marquee tag