Next.js 13 - Hackdot

Re:Next.js 13 by lghh on Tuesday October 25, 2022 @02:49PM (#33334624)

I'd rather spend a literal 6-character burden (alt="") to put an empty string in my little hobby projects than live in a world where non-hobby projects can skip adding alt.

It should be very clear by just looking around on the internet that, when given the choice, accessibility will take a back seat.

[ Parent | on HN ]

Re:Next.js 13 by latchkey on Tuesday October 25, 2022 @03:00PM (#33334762)

I'm curious why you think that forcing people to write alt="" is going to improve accessibility?

[ Parent | on HN ]

Re:Next.js 13 by randomguy0 on Tuesday October 25, 2022 @03:55PM (#33335350)

Because that’s how screen readers know the image is decorative. It literally is/improves accessibility.

[ Parent | on HN ]

Re:Next.js 13 by lghh on Tuesday October 25, 2022 @05:18PM (#33336302)

Additionally, the developer is more likely to actually write alt text when it's not decorative.

[ Parent | on HN ]

Re:Next.js 13 by Vinnl on Wednesday October 26, 2022 @02:48AM (#33340562)

Although I must admit, I've also seen such rules leading to developers writing alt text for decorative images, and I'm not sure if that's much better.

[ Parent | on HN ]