Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Next.js 13

nextjs.org

Post reply on HN
Print view View original

101–106 of 106 posts

Re: Next.js 13

#101

Post by krono »

chrisco255 wrote: post #88
krono wrote: post #81

Earlier quoted context omitted.

Which of these tags you should use and what they should contain is entirely context dependant. That said, the use of empty alt tags is generally discouraged and not even allowed together with the ARIA presentation role in most cases. This decision of theirs will steer developers towards non-compliant/asemantic code. It's really stupid. https://html.spec.whatwg.org/multipage/images.html#alt https://w3c.github.io/aria/…

That second link from W3C gives this very example: https://w3c.github.io/aria/#example-13 "In the following code sample, the containing img and is appropriately labeled by the caption paragraph. In this example the img element can be marked as presentation because the role and the text alternatives are provided by the containing element." So empty alt tags are not discouraged.

Hence the generally discouraged - as in not recommended in the majority of situations but exceptions exist (such as the one you provided).

Re: Next.js 13

#102

Post by klipilicica »

chrisco255 wrote: post #68
calvin wrote: post #13

Earlier quoted context omitted.

You should still be able to use alt="" to indicate that it is "decorative" and not meaningful imagery for a visually-impaired user.

Instead use the ARIA tag role="presentation": https://developer.mozilla.org/en-US/docs/Web/Accessibility/A... to indicate when an element has no semantic meaning and is purely visual.

"presentation" is the default role for an element when the "alt" attribute is an empty string.

Re: Next.js 13

#103

Post by Vinnl »

googlryas wrote: post #100
Vinnl wrote: post #98

Earlier quoted context omitted.

The fix for no a11y is to add a11y. In many cases (i.e. the "often" specified by GP), images contain no extra information, in which case you should indicate that by adding alt="". In other cases, you should add an actual description.

I meant the "fix" of people not caring about a11y(which is why I put it in quotes) and just trying to get their code to compile. If people don't care about a11y, they aren't going to start devoting time to it because a tool puts a slight roadblock in their way - they're just going to try to bypass the tool.

Sure, but it doesn't really matter what you do for those people; their projects will be inaccessible anyway. For the rest of us, it's a useful reminder.

Re: Next.js 13

#104

Post by ConsoleTVs »

halfmatthalfcat wrote: post #65
nightski wrote: post #25

Earlier quoted context omitted.

Actually it tells me that the javascript ecosystem fails to build software that can adapt to change. The culture is to throw everything out and start fresh every time they want to do something different. It's terrible engineering.

Thankfully that's just your opinion. I appreciate all the innovation and experimentation that's happening. Nobody is dictating you or anyone else use these tools.

It's not an opinion. It's common sense. Do you think Rust or Swift would exist if LLVM would have stopped its development long ago in favour of ?

Not only in software, if we keep renewing rather than perfecting software, we won't go anywhere.

Re: Next.js 13

#105

Post by Old_Thrashbarg »

elforce002 wrote: post #78

I started my journey with Vue, then Nuxt (of course),then switched to React and last year started to use Nextjs. So far I have no complains (at least no big ones). With new frameworks poping out (qwik, remix, fresh, etc...), it's getting really interesting and tiresome at the same time. We're migrating all our platforms to React/Next and we couldn't be happier. Is it perfect? Nothing really is. Next is good enough, t…

I'm curious why you decided to migrate from Vue to React.

Re: Next.js 13

#106

Post by tr1ll10nb1ll »

Joeri wrote: post #61
pastor_bob wrote: post #46

Earlier quoted context omitted.

>On an application with 3,000 modules, Turbopack takes 1.8 seconds to boot up, while Vite takes 11.4 seconds. How many apps are dealing with 3,000+ modules?

At the pace the javascript ecosystem is going, by next year it will be almost all of them. Create react app for a new default project pulls in 1400 packages, 300 MB in size, just to put a hello world page on a screen. That nobody thinks this is absolutely bonkers drives me absolutely bonkers.

Informed developers don't use CRA anymore.
Post reply on HN