Keyboard navigation basics in HTML - Performance & Optimization

Performance: Keyboard navigation basics

MEDIUM IMPACT

This affects user interaction responsiveness and accessibility, impacting how quickly users can navigate and interact with page elements using the keyboard.

Making interactive elements accessible and navigable by keyboard

HTML

<button onclick="doSomething()">Click me</button>

Uses semantic button element which is focusable and operable by keyboard by default.

📈 Performance GainImproves INP by enabling instant keyboard interaction without extra scripting.

Making interactive elements accessible and navigable by keyboard

HTML

<div onclick="doSomething()">Click me</div>

Non-semantic element without keyboard focus or keyboard event handlers, so keyboard users cannot interact.

📉 Performance CostBlocks keyboard users, increasing interaction time and causing poor INP.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Non-semantic clickable div without keyboard support	Low	0	Low	[X] Bad
Semantic button element with native keyboard support	Low	0	Low	[OK] Good
Using tabindex="-1" to remove focusable elements	Low	0	Low	[X] Bad
Natural DOM order with no tabindex manipulation	Low	0	Low	[OK] Good

Rendering Pipeline

Keyboard navigation affects the browser's event handling and focus management stages, influencing how quickly user input is processed and reflected visually.

→Event Handling

→Composite

⚠️ BottleneckEvent Handling when non-semantic elements require extra scripting for keyboard support

Core Web Vital Affected

INP

This affects user interaction responsiveness and accessibility, impacting how quickly users can navigate and interact with page elements using the keyboard.

Optimization Tips

1Use semantic HTML elements like <button> for interactive controls.

2Avoid removing elements from keyboard focus order unless necessary.

3Keep DOM order logical to ensure predictable keyboard navigation.

Performance Quiz - 3 Questions

Which HTML element is best for keyboard accessible clickable items?

A <div>

B <button>

C <span>

D <section>

DevTools: Elements and Performance

How to check: Use Elements panel to inspect focusable elements and their tabindex attributes. Use Performance panel to record keyboard interaction and check event handling delays.

What to look for: Ensure interactive elements are focusable and keyboard events are handled quickly without delays.

Practice

1. What is the main purpose of keyboard navigation on a webpage?

easy

A. To allow users to move through the page using only the keyboard

B. To enable mouse clicks on buttons

C. To change the page colors automatically

D. To load images faster

Solution

1. Step 1: Understand keyboard navigation concept

   Keyboard navigation means using keys like Tab to move focus between elements without a mouse.

2. Step 2: Identify the purpose

   This helps users who cannot or prefer not to use a mouse to access all parts of a webpage.

3. Final Answer:

   To allow users to move through the page using only the keyboard -> Option A

4. Quick Check:

   Keyboard navigation = move with keyboard only [OK]

Hint: Keyboard navigation means moving focus without a mouse [OK]

Common Mistakes:

• Confusing keyboard navigation with mouse actions
• Thinking it changes page colors
• Assuming it speeds up loading

2. Which HTML attribute is used to control the order of keyboard focus on elements?

easy

A. onclick

B. alt

C. href

D. tabindex

Solution

1. Step 1: Recall HTML attributes related to focus

   The tabindex attribute sets the order in which elements receive keyboard focus.

2. Step 2: Eliminate unrelated attributes

   onclick is for mouse clicks, alt is for images, href is for links.

3. Final Answer:

   tabindex -> Option D

4. Quick Check:

   Focus order attribute = tabindex [OK]

Hint: Use tabindex to set keyboard focus order [OK]

Common Mistakes:

• Choosing onclick instead of tabindex
• Confusing alt with focus control
• Thinking href controls keyboard navigation

3. Consider this HTML snippet:

<button>Save</button>
<div tabindex="0">Info</div>
<a href="#">Link</a>

When pressing Tab repeatedly, which element will receive focus second?

medium

A. The <div> with tabindex="0"

B. The <button> element

C. The <a> link element

D. No element will receive focus second

Solution

1. Step 1: Understand default tab order

   By default, focus moves to interactive elements like buttons and links in source order.

2. Step 2: Consider tabindex="0" effect

   Adding tabindex="0" makes the <div> focusable and places it in the natural tab order after the button.

3. Final Answer:

   The <div> with tabindex="0" -> Option A

4. Quick Check:

   tabindex="0" adds element to tab order [OK]

Hint: tabindex="0" makes non-focusable elements focusable [OK]

Common Mistakes:

• Assuming div cannot get focus
• Thinking link comes second instead of div
• Ignoring tabindex effect

4. This HTML code is intended to make a <div> focusable for keyboard users:

<div tabindex="-1">Menu</div>

Why might this cause a problem for keyboard navigation?

medium

A. tabindex='-1' makes the element invisible

B. tabindex='-1' removes the element from tab order, so it can't be reached by Tab key

C. tabindex='-1' causes a syntax error in HTML

D. tabindex='-1' makes the element focusable twice

Solution

1. Step 1: Understand tabindex="-1" meaning

   tabindex="-1" makes an element focusable only by script, not by keyboard Tab key.

2. Step 2: Identify keyboard navigation impact

   Because it is skipped in tab order, keyboard users cannot reach it by pressing Tab.

3. Final Answer:

   tabindex='-1' removes the element from tab order, so it can't be reached by Tab key -> Option B

4. Quick Check:

   tabindex="-1" excludes element from Tab focus [OK]

Hint: tabindex="-1" excludes element from keyboard tab focus [OK]

Common Mistakes:

• Thinking tabindex="-1" causes syntax error
• Believing it makes element invisible
• Assuming it makes element focusable twice

5. You want to create a custom interactive widget using a <div> that keyboard users can access in a logical order after a button and a link. Which is the best way to ensure correct keyboard navigation?

hard

A. Add tabindex="-1" to the <div> so it is skipped by keyboard

B. Add tabindex="1" to the <div> to place it first in tab order

C. Add tabindex="0" to the <div> and place it after the button and link in HTML

D. Do not add tabindex; keyboard users cannot access <div> anyway

Solution

1. Step 1: Understand tabindex values and order

   tabindex="0" places element in natural tab order based on HTML position; positive tabindex values change order but can confuse users.

2. Step 2: Choose best practice for accessibility

   Using tabindex="0" and placing the <div> after button and link in HTML ensures logical, predictable keyboard navigation.

3. Final Answer:

   Add tabindex="0" to the <div> and place it after the button and link in HTML -> Option C

4. Quick Check:

   tabindex="0" + correct HTML order = best keyboard navigation [OK]

Hint: Use tabindex="0" and HTML order for logical tab sequence [OK]

Common Mistakes:

• Using positive tabindex values which confuse tab order
• Using tabindex="-1" which skips element
• Assuming div is never focusable without tabindex