Essential CSS
JavaScript Roadmap
Learn JavaScript
Mastering Web Typography
Practical Astro
Understanding Async JS
Unorthodox Tailwind
API Masterclass
Build and Deploy
The Beginner Freelancer
Real World Node
Profile Billing Logout
Learn JavaScript
Lesson Plan
  1. JavaScript and its ecosystem
    1. Welcome to Learn JavaScript!
    2. What is JavaScript used for?
    3. The JavaScript ecosystem
    4. Varying versions of JavaScript
  2. JS Basics
    1. Linking your JavaScript file
    2. Preparing your text editor
    3. The Console
    4. Comments
    5. On semicolons
    6. Strings, numbers and booleans
    7. Understanding Variables
    8. Understanding Functions
    9. The Flow of a Function
    10. Arrow functions
    11. Intro to objects
    12. If/else statements
    13. Comparing Objects
    14. The NOT operator
    15. Null and Undefined
    16. The BOM and the DOM
    17. Selecting an Element
    18. Changing Classes
    19. Listening to events
    20. Callbacks
  3. Building simple components
    1. How to think like a developer
    2. Starter files and Source codes
    3. Do this for every component
    4. ๐Ÿ›  Off-canvas menu: Building an off-canvas menu
    5. ๐Ÿ›  Modal: Building a Modal
    6. Lessons from the building process
    7. Debugging errors
    8. How to use a linter
  4. Arrays and loops
    1. Introduction to Arrays
    2. Array methods
    3. For loops
    4. The forEach loop
    5. Selecting multiple elements
    6. Nodes vs Elements
    7. ๐Ÿ›  Accordion: Building an accordion
  5. Dom basics
    1. Id, classes, attributes, and tags
    2. Changing CSS with JavaScript
    3. Getting CSS with JavaScript
    4. Changing Attributes
    5. Finding an element's size and position
    6. DOM Traversals
    7. ๐Ÿ›  Tabby: Building Tabby (A Tabbed component)
    8. ๐Ÿ›  Carousel: HTML and CSS
    9. ๐Ÿ›  Carousel: Switching slides with JavaScript
    10. ๐Ÿ›  Carousel: Working the dots
    11. ๐Ÿ›  Carousel: Positioning slides with JavaScript
  6. Events deep dive
    1. The listening element
    2. Default Behaviors
    3. Event propagation
    4. Event delegation
    5. Removing Event Listeners
    6. ๐Ÿ›  Modal: Closing the modal
    7. ๐Ÿ›  Accordion: Event delegation
    8. ๐Ÿ›  Tabby: Event delegation
    9. ๐Ÿ›  Carousel: Event delegation
  7. Transitions and Animations
    1. CSS Transitions
    2. CSS Animations
    3. Silky-smooth animations
    4. Integrating CSS transitions and animations with JavaScript
    5. Animating with JavaScript
    6. GreenSock Animation API (GSAP)
    7. ๐Ÿ›  Off-canvas menu: Animations
    8. ๐Ÿ›  Modal: Animating the modal
    9. ๐Ÿ›  Modal: Animating the pointing hand
    10. ๐Ÿ›  Modal: Animating the waving hand
    11. ๐Ÿ›  Modal: Wave hand animation with JavaScript (using GSAP)
    12. ๐Ÿ›  Accordion: Animations
    13. ๐Ÿ›  Carousel: Animations
  8. Useful JS features
    1. Ternary operators
    2. AND and OR operators
    3. Early returns
    4. Template Literals
    5. Destructuring
    6. Default parameters
    7. Enhanced Object Literals
    8. Rest and Spread
    9. Useful array methods
    10. Looping through objects
    11. Returning objects with implicit return
    12. ๐Ÿ›  Accordion: Using useful JavaScript features
    13. ๐Ÿ›  Tabby: Using useful JavaScript features
    14. ๐Ÿ›  Carousel: Useful JavaScript features
  9. JS Best practices
    1. Write declarative code
    2. Functions with a purpose
    3. Manage scope
    4. Reduce state changes
    5. Don't reassign
    6. Don't mutate
    7. Preventing Objects from mutating
    8. Preventing Arrays from mutating
    9. Write pure functions
    10. ๐Ÿ›  Accordion: Refactor
    11. ๐Ÿ›  Carousel: First refactor
    12. ๐Ÿ›  Carousel: Refactoring the dots part
    13. ๐Ÿ›  Carousel: Previous and next buttons
    14. ๐Ÿ›  Carousel: Second refactor
  10. Manipulating text and content
    1. Changing Text and HTML
    2. Creating HTML Elements
    3. Adding multiple elements to the DOM
    4. Removing Elements from the DOM
    5. ๐Ÿ›  Carousel: Creating dots with JavaScript
    6. ๐Ÿ› ๏ธ Calculator: HTML and CSS
    7. ๐Ÿ› ๏ธ Calculator: Happy Path
    8. ๐Ÿ› ๏ธ Calculator: Testing the Happy Path
    9. ๐Ÿ› ๏ธ Calculator: Easy Edge Cases
    10. ๐Ÿ› ๏ธ Calculator: Difficult Edge Cases
    11. ๐Ÿ› ๏ธ Calculator: Refactoring
    12. The switch statement
    13. ๐Ÿ› ๏ธ Calculator: Refactoring (Part 2)
    14. ๐Ÿ› ๏ธ Popover: Making one popover
    15. ๐Ÿ› ๏ธ Popover: Making four popovers
    16. ๐Ÿ› ๏ธ Popover: Making popovers with JavaScript
  11. Handling Forms
    1. Intro to forms
    2. Selecting form fields with JavaScript
    3. Form fields and their events
    4. Sanitize your output
    5. Generating unique IDs
    6. ๐Ÿ› ๏ธ Popover: Dynamic ID
    7. ๐Ÿ› ๏ธ Todolist: The HTML and CSS
    8. ๐Ÿ› ๏ธ Todolist: Creating tasks with JavaScript
    9. ๐Ÿ› ๏ธ Todolist: Deleting tasks with JavaScript
    10. ๐Ÿ› ๏ธ Typeahead: The HTML and CSS
    11. ๐Ÿ› ๏ธ Typeahead: Displaying predictions
    12. ๐Ÿ› ๏ธ Typeahead: Selecting a prediction
    13. ๐Ÿ› ๏ธ Typeahead: Bolding search terms
  12. Handling Dates
    1. The Date object
    2. Getting a formatted date
    3. Getting the time
    4. Local time and UTC Time
    5. Setting a specific date
    6. Setting a date with Date methods
    7. Adding (or subtracting) date and time
    8. Comparing Dates and times
    9. ๐Ÿ› ๏ธ Datepicker: HTML and CSS
    10. ๐Ÿ› ๏ธ Datepicker: Building the calendar
    11. ๐Ÿ› ๏ธ Datepicker: Building the datepicker with JavaScript
    12. ๐Ÿ› ๏ธ Datepicker: Previous and Next buttons
    13. ๐Ÿ› ๏ธ Datepicker: Selecting a date
    14. ๐Ÿ› ๏ธ Datepicker: Positioning the datepicker
    15. ๐Ÿ› ๏ธ Datepicker: Showing and hiding
    16. Formatting a date with toLocaleString
    17. setTimeout
    18. setInterval
    19. ๐Ÿ› ๏ธ Countdown timer: HTML and CSS
    20. ๐Ÿ› ๏ธ Countdown timer: JavaScript
    21. ๐Ÿ› ๏ธ Countdown timer: Counting Months
    22. ๐Ÿ› ๏ธ Countdown timer: Daylight Saving Time
    23. ๐Ÿ› ๏ธ Countdown timer: Counting Years
  13. Async JS
    1. Introduction to Ajax
    2. Understanding JSON
    3. The Fetch API
    4. Possible data types
    5. JavaScript Promises
    6. Requests and responses
    7. Sending a POST request
    8. Authentication
    9. Handling errors
    10. Viewing response headers
    11. CORS and JSONP
    12. XHR vs Fetch
    13. Using an Ajax library
    14. Reading API documentation
    15. Understanding curl
    16. ๐Ÿ› ๏ธ Todolist: The Todolist API
    17. ๐Ÿ› ๏ธ Todolist: Fetching tasks
    18. ๐Ÿ› ๏ธ Todolist: Creating tasks
    19. ๐Ÿ› ๏ธ Todolist: Editing tasks
    20. ๐Ÿ› ๏ธ Todolist: Deleting tasks
    21. ๐Ÿ› ๏ธ Todolist: Creating tasks with Optimistic UI
    22. ๐Ÿ› ๏ธ Todolist: Handling Optimistic UI errors
    23. ๐Ÿ› ๏ธ Todolist: Editing tasks with Optimistic UI
    24. ๐Ÿ› ๏ธ Todolist: Deleting tasks with Optimistic UI
    25. ๐Ÿ› ๏ธ Todolist: Refactor
    26. ๐Ÿ› ๏ธ Typeahead: How to add Ajax
    27. ๐Ÿ› ๏ธ Typeahead: Adding Ajax
    28. ๐Ÿ› ๏ธ Typeahead: Handling errors
    29. ๐Ÿ› ๏ธ Google Maps Clone: Creating your first Google Map
    30. ๐Ÿ› ๏ธ Google Maps Clone: Fetching JSONP via JavaScript
    31. ๐Ÿ› ๏ธ Google Maps Clone: Drawing directions
    32. ๐Ÿ› ๏ธ Google Maps Clone: Driving directions
    33. ๐Ÿ› ๏ธ Google Maps Clone: Handling errors
    34. ๐Ÿ› ๏ธ Google Maps Clone: Adding stopovers
    35. ๐Ÿ› ๏ธ Google Maps Clone: Refactor
  14. Advanced Async JS
    1. Requesting many resources at once
    2. Asynchronous functions
    3. Handling multiple awaits
    4. Asynchronous loops
    5. ๐Ÿ› ๏ธ Dota Heroes: Listing heroes
    6. ๐Ÿ› ๏ธ Dota Heroes: Filtering heroes (Part 1)
    7. ๐Ÿ› ๏ธ Dota Heroes: Filtering heroes (Part 2)
    8. ๐Ÿ› ๏ธ Dota Heroes: Refactoring
    9. ๐Ÿ› ๏ธ Dota Heroes: Hero Page
    10. ๐Ÿ› ๏ธ Dota Heroes: Making the hero page robust
    11. ๐Ÿ› ๏ธ Dota Heroes: Heroes page refactor
  15. Handling Keyboard Events
    1. Keyboard users
    2. Handling commonly used keys
    3. Keyboard events
    4. Understanding Tabindex
    5. Detecting the focused element
    6. Directing focus
    7. Preventing people from tabbing into elements
    8. How to choose keyboard shortcuts
    9. Creating single-key shortcuts
    10. ๐Ÿ› ๏ธ Off-canvas: Adding keyboard interaction
    11. ๐Ÿ› ๏ธ Modal: Adding keyboard interaction
    12. ๐Ÿ› ๏ธ Accordion: Adding keyboard interaction
    13. ๐Ÿ› ๏ธ Tabby: Adding keyboard interaction
    14. ๐Ÿ› ๏ธ Tabby: Refactoring
    15. ๐Ÿ› ๏ธ Carousel: Adding keyboard interaction
    16. ๐Ÿ› ๏ธ Carousel: Displaying help text
    17. ๐Ÿ› ๏ธ Calculator: Adding keyboard interaction
    18. ๐Ÿ› ๏ธ Popover: Keyboard
    19. ๐Ÿ› ๏ธ Popover: Refactor
    20. Keyboard shortcuts with Command and Control modifiers
    21. ๐Ÿ› ๏ธ Todolist: Keyboard
    22. ๐Ÿ› ๏ธ Typeahead: Keyboard
    23. ๐Ÿ› ๏ธ Typeahead: Selecting a prediction with the keyboard
    24. ๐Ÿ› ๏ธ Google Maps Clone: Keyboard
    25. ๐Ÿ› ๏ธ Dota Heroes: Keyboard
    26. ๐Ÿ› ๏ธ Datepicker: Tabbing in and out
    27. ๐Ÿ› ๏ธ Datepicker: Keyboard shortcuts
  16. Screen reader accessibility
    1. What is accessibility?
    2. How to use a screen reader
    3. Using NVDA
    4. Using Voiceover
    5. Aria roles
    6. Landmark roles
    7. Document structure roles
    8. Live region roles
    9. Widget roles
    10. Window and Abstract roles
    11. Accessible names and descriptions
    12. Hiding content
    13. ARIA properties and ARIA states
    14. ARIA for expandable widgets
    15. ๐Ÿ› ๏ธ Off-canvas: Accessibility
    16. ARIA for modal dialogs
    17. ๐Ÿ› ๏ธ Modal: Screen reader accessibility
    18. ๐Ÿ› ๏ธ Accordion: Screen reader accessibility
    19. ARIA for Tabbed components
    20. ๐Ÿ› ๏ธ Tabby: Screen reader accessibility
    21. ๐Ÿ› ๏ธ Tabby: Refactor
    22. ๐Ÿ› ๏ธ Carousel: Screen reader accessibility
    23. Roles that trigger Forms and Application modes
    24. What's next for accessibility?
  17. Handling Scroll
    1. The Scroll event
    2. ๐Ÿ› ๏ธ Auto-hiding Sticky-nav: HTML and CSS
    3. ๐Ÿ› ๏ธ Auto-hiding Sticky-nav: JavaScript
    4. ๐Ÿ› ๏ธ Auto-hiding Sticky-nav: Natural reveal
    5. Intersection Observer API
    6. Intersection Observer Options
    7. ๐Ÿ› ๏ธ Slide & Reveal
    8. ๐Ÿ› ๏ธ Slide & Reveal: Always fade-in when you scroll down
    9. ๐Ÿ› ๏ธ Slide & Reveal: Fine-tuning the animation
    10. ๐Ÿ› ๏ธ Infinite Scroll: Anatomy
    11. ๐Ÿ› ๏ธ Infinite Scroll: Infinite load
    12. ๐Ÿ› ๏ธ Infinite Scroll: Refactor
    13. ๐Ÿ› ๏ธ Infinite Scroll: Implementing the Infinite Scroll
  18. Mouse, Touch, and Pointer events
    1. Mouse Events
    2. ๐Ÿ› ๏ธ Spinning Pacman: HTML and CSS
    3. ๐Ÿ› ๏ธ Spinning Pacman: JavaScript
    4. Touch events
    5. Pointer events
    6. Touch-action
    7. ๐Ÿ› ๏ธ Spinning Pacman: Supporting Touch
    8. Cloning elements
    9. ๐Ÿ› ๏ธ DragDrop: HTML and CSS
    10. ๐Ÿ› ๏ธ DragDrop: JavaScript
    11. ๐Ÿ› ๏ธ DragDrop: Creating a drop preview
    12. ๐Ÿ› ๏ธ DragDrop: Sortable drop preview
    13. ๐Ÿ› ๏ธ DragDrop: Robustness
    14. ๐Ÿ› ๏ธ DragDrop: Refactor
  19. Object Oriented Programming
    1. Before we begin
    2. What is Object Oriented Programming?
    3. Four Flavours of Object Oriented Programming
    4. Inheritance
    5. This in JavaScript
    6. Call, bind, apply
    7. Creating Derivative Objects
    8. Composition vs Inheritance
    9. Polymorphism
    10. Encapsulation
    11. Closures
    12. Encapsulation in Object Oriented Programming
    13. Getters and Setters
    14. What OOP flavour to use
    15. When to use Object Oriented Programming
  20. Writing reusable code
    1. Creating reusable code by writing libraries
    2. Two Types of libraries
    3. Including libraries with Script tags
    4. Including libraries with ES6 Modules
    5. Dynamic imports
    6. ๐Ÿ› ๏ธ Off Canvas: Building a Library
    7. ๐Ÿ› ๏ธ Modal: Library setup
    8. ๐Ÿ› ๏ธ Modal: Opening the Modal
    9. ๐Ÿ› ๏ธ Modal: Closing the modal
    10. ๐Ÿ› ๏ธ Modal: Inheritance and Polymorphism
    11. ๐Ÿ› ๏ธ Modal: Resolving differences between subclasses
    12. ๐Ÿ› ๏ธ Modal: Exposing properties and methods
    13. ๐Ÿ› ๏ธ Accordion: Building a library
    14. ๐Ÿ› ๏ธ Tabby: Building a library
    15. ๐Ÿ› ๏ธ Carousel: Building a library
    16. ๐Ÿ› ๏ธ Calculator: Library
    17. ๐Ÿ› ๏ธ Calculator: Fixing the Clear Key
    18. ๐Ÿ› ๏ธ Calculator: Handling other keys
    19. ๐Ÿ› ๏ธ Calculator: State
    20. ๐Ÿ› ๏ธ Popover: Library
    21. ๐Ÿ› ๏ธ Popover: Adding event listeners
    22. ๐Ÿ› ๏ธ Typeahead: Library
    23. ๐Ÿ› ๏ธ DatePicker: Library
  21. Going from Vanilla JS to JS Frameworks
    1. ๐Ÿ› ๏ธ Building a Tiny framework
    2. ๐Ÿ› ๏ธ Tiny: Add event listeners
    3. ๐Ÿ› ๏ธ Tiny: Updating state
    4. ๐Ÿ› ๏ธ Tiny: Rendering Child Components
    5. ๐Ÿ› ๏ธ Tiny: Changing Parent State
    6. ๐Ÿ› ๏ธ Tiny: Passing Props
    7. ๐Ÿ› ๏ธ Tiny: Multiple Props
    8. ๐Ÿ› ๏ธ Tiny: Passing values from sibling components
    9. ๐Ÿ› ๏ธ Tiny: Mounting
    10. ๐Ÿ› ๏ธ Tiny: Passing props to descendants
    11. ๐Ÿ› ๏ธ Tiny: A tiny refactor
  22. Single Page Apps
    1. What is a Single Page App?
    2. Simple SPA using only CSS
    3. The Location Interface
    4. The History Interface
    5. Minimum viable server for a SPA
    6. ๐Ÿ› ๏ธ Dota SPA: Introduction
    7. ๐Ÿ› ๏ธ Dota SPA: Building The Heroes List
    8. ๐Ÿ› ๏ธ Dota SPA: Building the filters
    9. ๐Ÿ› ๏ธ Dota SPA: Filtering heroes
    10. ๐Ÿ› ๏ธ Dota SPA: Displaying filtered heroes
    11. ๐Ÿ› ๏ธ Dota SPA: Getting Ready to build the Hero Page
    12. ๐Ÿ› ๏ธ Dota SPA: Building the hero page
    13. ๐Ÿ› ๏ธ Dota SPA: Lore and abilities
    14. ๐Ÿ› ๏ธ Dota SPA: Routing for Single-page apps

๐Ÿ› ๏ธ Carousel: Adding keyboard interaction

Users can Tab through every element of the carousel. By this definition, our carousel is already keyboard accessible.

Tabbing through all elements.

Even though users can Tab through a carousel, they wonโ€™t know it unless they see a focus style.

Showing a focus style

Each slide has a focus style. We donโ€™t see the focus because the focus got hidden by overflow: hidden.

/* This is the culprit */
.carousel__contents-container {
overflow: hidden;
}

We can see the focus if we removed overflow: hidden from .carousel__contents-container.

Removed overflow hidden property to show the default focus style.

However, we cannot remove overflow: hidden from .carousel__contents-container. Thatโ€™s the property we used to hide other slides. We need overflow: hidden to remain.

We need another way to show focus on each slide. There are two choices:

  1. Use an inset box shadow on each focused slide
  2. Add a box shadow to .carousel__contents-container when children elements get focus

Both methods work. Weโ€™ll go with the second one because the focus looks way better when we change slides.

We can detect when children element gets focus with :focus-within. Weโ€™ll use this pseudo-class to display the focus.

.carousel__contents-container:focus-within {
box-shadow: 0 0 0 0.5rem lightskyblue;
}
Modified focus style.

Imagine using a website with this carousel. You need to get past the carousel with a keyboard. To get past the carousel, you need to hit Tab 9 times.

This is a frustrating experience. (And the frustration increases with the number of slides).

It takes 9 tabs to get through a carousel with 3 slides

The best way to allow users to move past the carousel is to remove the ability to Tab through all slides, buttons, and dots. If we do this, users can get through the carousel in 2 Tabs.

Allows the user to tab through the carousel in 2 tabs.

To do this, we have to set tabindex to -1 for the previous and next buttons.

<section class="carousel">
<button class="carousel__button previous-button" hidden tabindex="-1">
...
</button>
<div class="carousel__contents-container">...</div>
<button class="carousel__button next-button" tabindex="-1">...</button>
</section>

We also need to set tabindex for slides to -1.

But since we want users to Tab into the current slide, we will NOT add tabindex="-1" to the current slide.

<ul class="carousel__contents">
<li class="carousel__slide is-selected">
<a href="#"> ... </a>
</li>
<li class="carousel__slide">
<a href="#" tabindex="-1"> ... </a>
</li>
<li class="carousel__slide">
<a href="#" tabindex="-1"> ... </a>
</li>
</ul>

Finally, we set tabindex for each dot to -1.

function createDots(slides) {
// ...
slides.forEach(slide => {
const dot = document.createElement('button')
dot.classList.add('carousel__dot')
dot.setAttribute('tabindex', -1)
// ...
})
// ...
}

Switching slides with arrow keys

We destroyed keyboard accessibility when we prevent users from Tabbing into the slides. We need to provide users an alternate way to access the slides.

The best way is to let them switch slides with arrow keys. They can:

  1. Go to the next slide with โ†’
  2. Go to the previous slide with โ†

First, we need to listen for arrow keys.

The best way to listen for arrow keys normally is to add the event listeners on focusable elements (the <a> tags for the carousel).

slides.forEach(slide => {
const a = slide.querySelector('a')
a.addEventListener('keydown', event => {
console.log(event.key)
})
})

But, in this case, we can use the event delegation pattern on a parent element like .carousel__contents.

We can do this because each <a> tag covers the same area as .carousel__contents. Users will not be able to click on a space between <a> and .carousel__contents.

contents.addEventListener('keydown', event => {
// ...
})

We want to switch slides if the user presses the Left or Right arrow keys. The simplest way to do this is:

  1. Click nextButton if user presses โ†’
  2. Click previousButton if user presses โ†
contents.addEventListener('keydown', event => {
const { key } = event
if (key === 'ArrowLeft') previousButton.click()
if (key === 'ArrowRight') nextButton.click()
})
Switching slides with arrow keys.

Focusing on the correct slide

Users should be able to interact with each slide. If they press Enter when the second slide is shown, they should navigate to the link the second slide points to.

Letโ€™s add real links to each slide to test this out.

<ul class="carousel__contents">
<li class="carousel__slide is-selected">
<a href="https://en.wikipedia.org/wiki/1"> ... </a>
</li>
<li class="carousel__slide">
<a href="https://simple.wikipedia.org/wiki/Universe" ...tabindex="-1">
...
</a>
</li>
<li class="carousel__slide">
<a href="https://learnjavascript.today" tabindex="-1"> ... </a>
</li>
</ul>

Try going to the third slide with โ†’. Press Enter when you get to the third slide. Youโ€™ll notice you get directed to the first slideโ€™s link.

This is wrong. You should get directed to the third slideโ€™s link.

Carousels always link to the first slide

This happens because we only changed the slides visually. Focus still remains on the first slideโ€™s <a> element.

For keyboard accessibility to work properly, we need to focus on the correct slideโ€™s <a> too.

nextButton.addEventListener('click', event => {
// ...
// Focus on selected slide's anchor tag
const link = slides[nextSlideIndex].querySelector('a')
link.focus()
})

Unfortunately, the carousel breaks after adding the focus method.

Try clicking the right button (or hitting โ†’ once). You should see the second slide. But youโ€™ll see the third slide.

This happens because the focus method forces the browser to scroll to the focused element (both vertically and horizontally).

We can prevent automatic scrolling by setting preventScroll to true.

nextButton.addEventListener('click', event => {
// ...
// Focus on selected slide's anchor tag
const link = slides[nextSlideIndex].querySelector('a')
link.focus({ preventScroll: true })
})
Carousel fixed. Hitting Enter on a slide goes to the correct page too.

Remember to add the focus code to previousButtonโ€™s and dotsContainerโ€™s event listeners as well.

previousButton.addEventListener('click', event => {
// ...
// Focus on selected slide's anchor tag
const link = slides[previousSlideIndex].querySelector('a')
link.focus({ preventScroll: true })
})
dotsContainer.addEventListener('click', event => {
// ...
// Focus on selected slide's anchor tag
const link = slides[targetSlideIndex].querySelector('a')
link.focus({ preventScroll: true })
})

Unfortunately, preventScroll is not supported on Safari and Edge yet.

preventScroll is not supported on Safari and Edge.

We need a fallback.

Fallback for preventScroll

When the browsers scrolls to the focused element, theyโ€™ll scroll the nearest scrollable ancestor element. In this case, the scrollable element is .contents__track-container.

You can detect the scroll by adding a transitionend event listener.

window.addEventListener('transitionend', event => {
console.log(contents.parentElement.scrollLeft)
})
Logs the scrolled amount in the console.

We want to prevent this scrolling behavior from happening. To do this, we need to set .contents__track-container scroll back to 0 before the transition happens.

We need to use a setTimeout callback to do this.

nextButton.addEventListener('click', event => {
// ...
const link = slides[nextSlideIndex].querySelector('a')
link.focus({ preventScroll: true })
// Fallback for preventScroll
setTimeout(() => {
contents.parentElement.scrollLeft = 0
}, 0)
})
// Repeat fallback for previousButton and dotContainer event listeners

Safari and Edge should work fine now.

Fallback for preventScroll works on Safari.

Subsequent focus

Letโ€™s say a user Tabs out of the carousel from the second slide. A while later, the Tab back into the carousel. When they do this, we want focus to be on the second slide.

We can do this by swapping the tabindex values when we change slides.

nextButton.addEventListener('click', event => {
// ...
// Focus on selected slide's anchor tag
const nextLink = slides[nextSlideIndex].querySelector('a')
nextLink.focus({ preventScroll: true })
// Fallback for preventSrroll
setTimeout(() => {
contents.parentElement.scrollLeft = 0
}, 0)
// Roving tabindex
const currentLink = slides[currentSlideIndex].querySelector('a')
currentLink.setAttribute('tabindex', '-1')
nextLink.removeAttribute('tabindex')
})
previousButton.addEventListener('click', event => {
// ...
// Focus on selected slide's anchor tag
const previousLink = slides[previousSlideIndex].querySelector('a')
previousLink.focus({ preventScroll: true })
// Fallback for preventSrroll
setTimeout(() => {
contents.parentElement.scrollLeft = 0
}, 0)
// Roving tabindex
const currentLink = slides[currentSlideIndex].querySelector('a')
currentLink.setAttribute('tabindex', '-1')
previousLink.removeAttribute('tabindex')
})
dotsContainer.addEventListener('click', event => {
// ...
// Focus on selected slide's anchor tag
const targetLink = slides[targetSlideIndex].querySelector('a')
targetLink.focus({ preventScroll: true })
// Fallback for preventSrroll
setTimeout(() => {
contents.parentElement.scrollLeft = 0
}, 0)
// Roving tabindex
const currentLink = slides[currentSlideIndex].querySelector('a')
currentLink.setAttribute('tabindex', '-1')
targetLink.removeAttribute('tabindex')
})

Refactoring

We did these 5 things in nextButtonโ€™s, previousButtonโ€™s, and dotContainerโ€™s event listeners:

  1. Switch to the correct slide
  2. Highlight dot
  3. Show/hide arrow buttons
  4. Focus on the slideโ€™s link
  5. Corrected each slideโ€™s tabindex attribute

Since we need to do all five things each time we switch a slide, we might as well group them into switchSlide.

function switchSlide(currentSlideIndex, targetSlideIndex) {
const currentSlide = slides[currentSlideIndex]
const targetSlide = slides[targetSlideIndex]
// Switches to the correct slide
const destination = getComputedStyle(targetSlide).left
contents.style.transform = `translateX(-${destination})`
currentSlide.classList.remove('is-selected')
targetSlide.classList.add('is-selected')
// Highlights the correct dot
const currentDot = dots[currentSlideIndex]
const targetDot = dots[targetSlideIndex]
currentDot.classList.remove('is-selected')
targetDot.classList.add('is-selected')
// Show/hide arrow buttons accordingly
if (targetSlideIndex === 0) {
previousButton.setAttribute('hidden', true)
nextButton.removeAttribute('hidden')
} else if (targetSlideIndex === dots.length - 1) {
previousButton.removeAttribute('hidden')
nextButton.setAttribute('hidden', true)
} else {
previousButton.removeAttribute('hidden')
nextButton.removeAttribute('hidden')
}
// Focus on selected slide's anchor tag
const currentLink = slides[currentSlideIndex].querySelector('a')
const targetLink = slides[targetSlideIndex].querySelector('a')
targetLink.focus({ preventScroll: true })
// Fallback for preventScroll
setTimeout(() => {
contents.parentElement.scrollLeft = 0
}, 0)
// Roving tabindex
currentLink.setAttribute('tabindex', '-1')
targetLink.removeAttribute('tabindex')
}

If we do this, we can simplify our event listeners use only switchSlide.

nextButton.addEventListener('click', event => {
const currentSlideIndex = getCurrentSlideIndex()
const nextSlideIndex = currentSlideIndex + 1
switchSlide(currentSlideIndex, nextSlideIndex)
})
previousButton.addEventListener('click', event => {
const currentSlideIndex = getCurrentSlideIndex()
const previousSlideIndex = currentSlideIndex - 1
switchSlide(currentSlideIndex, previousSlideIndex)
})
dotsContainer.addEventListener('click', event => {
const dot = event.target.closest('button')
if (!dot) return
const currentSlideIndex = getCurrentSlideIndex()
const targetSlideIndex = dots.findIndex(d => d === dot)
switchSlide(currentSlideIndex, targetSlideIndex)
})

We can also delete highlightDot and showHideArrowButtons.

Thatโ€™s it!