Javascript vs Java Applet

A short, practical add-on to the thread (for @Cerberus and anyone landing here later): the right way to build a slideshow today is to treat it like a regular piece of content — semantic HTML first, small CSS for transitions, then unobtrusive JavaScript for controls/behaviour. That gives a robust baseline (works if scripts fail), keeps things indexable, and reduces long-term maintenance. (smashingmagazine.com) Progressive enhancement guide.

Make accessibility a design requirement, not an afterthought. Use a carousel container with a clear label and aria-roledescription="carousel", slides as groups with aria-roledescription="slide", native buttons for previous/next and a start/stop control for autoplay. Ensure auto-rotation pauses on focus and provide keyboard controls — the WAI-ARIA Authoring Practices explain the keyboard and labeling rules and include working examples. (w3.org) WAI-ARIA carousel pattern and examples

A minimal, copyable skeleton (semantic + accessible):

<div class="carousel" role="region" aria-roledescription="carousel" aria-label="Featured images">
  <div class="slides">
    <div class="slide" role="group" aria-roledescription="slide" aria-label="Slide 1 of 5">
      <img src="image-1.jpg" alt="..." />
    </div>
    <!-- more slides -->
  </div>

  <button class="prev" aria-label="Previous slide">‹</button>
  <button class="next" aria-label="Next slide">›</button>
  <button class="autoplay" aria-pressed="false" aria-label="Stop autoplay">Stop</button>
</div>

Make images responsive and fast: serve appropriate sizes with srcset/sizes or <picture>, defer off-screen assets with loading="lazy" (or IntersectionObserver where needed), and animate slides using transform/opacity (and will-change only when necessary) so animations stay smooth. These techniques reduce bandwidth and avoid repaint/layout jank. (developer.mozilla.org) Responsive images · Lazy loading guide · Animating for performance

If you prefer a finished library, pick a focused, actively maintained slider (for example, Swiper) that supports touch, lazy-loading and virtual slides — otherwise keep your script small and test on keyboard, screen readers and low-end devices. Balance features vs. maintenance: sometimes simple, well-tested custom code beats a heavy plugin. (swiperjs.com) Swiper (example)

Notes tied to earlier replies: the participants here raised the plugin-vs-JS question — the advice above gives a modern, accessible, and maintainable path that avoids plugin dependencies while addressing the practical needs a slideshow typically has.