The right tag for the job: why you should use semantic HTML

Re:The right tag for the job: why you should use semantic HTML by richardwhiuk on Sunday June 06, 2021 @03:32PM (#27415623)

Cost of ensuring a site is accessible is greater than the profit from the sales which you get in addition?

[ Parent | on HN ]

Re:The right tag for the job: why you should use semantic HTML by goto11 on Sunday June 06, 2021 @05:02PM (#27416293)

Yes but what is the the cost of accessibility? How much more expensive is it to use a <button> compared to a <div> with attached event handlers?

[ Parent | on HN ]

Re:The right tag for the job: why you should use semantic HTML by lmm on Sunday June 06, 2021 @11:01PM (#27418563)

The cost of doing accessibility is the cost of doing accessibility testing. If you're not actually testing your accessibility work, using a button instead of a div is pissing in the wind.

[ Parent | on HN ]

Re:The right tag for the job: why you should use semantic HTML by goto11 on Monday June 07, 2021 @05:50AM (#27420731)

Surely a button is more accessible than a div regardless?

[ Parent | on HN ]

Re:The right tag for the job: why you should use semantic HTML by lmm on Monday June 07, 2021 @11:18PM (#27430284)

Maybe, maybe not. ("Surely" using the browser's CSS animations would be more efficient than reimplementing them yourself in JavaScript - but if actually you benchmark it, the opposite is true). If you're not actually testing it, how could you possibly know?

[ Parent | on HN ]

Re:The right tag for the job: why you should use semantic HTML by slver on Sunday June 06, 2021 @07:42PM (#27417433)

If only it were so simple.

[ Parent | on HN ]

Re:The right tag for the job: why you should use semantic HTML by ctoth on Sunday June 06, 2021 @03:51PM (#27415761)

For what kind of site? If you just use semantic HTML as this article recommends, the cost is quite low for development, and your QA people should already know the basics of accessibility testing.

[ Parent | on HN ]