Keyboard navigation support in Angular - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is keyboard navigation support in Angular?

Keyboard navigation support means making your Angular app usable with a keyboard alone, so users can move through interactive elements using keys like Tab, Enter, and arrow keys.

beginner

Which Angular directive helps manage keyboard events easily?

The @HostListener decorator lets you listen to keyboard events like keydown or keyup on components or elements.

beginner

Why should you use tabindex in Angular templates?

tabindex controls the order in which elements receive focus when users press the Tab key, helping create a logical navigation flow.

intermediate

How does Angular's new control flow syntax help with keyboard navigation?

Angular 17+ introduces @if and @for which can dynamically show or hide elements, so you can update keyboard focus targets smoothly as UI changes.

beginner

What role does ARIA play in keyboard navigation support?

ARIA attributes provide extra info to assistive technologies, helping users understand focus states and element roles when navigating with a keyboard.

Which key is commonly used to move focus to the next interactive element?

A Tab

B Enter

C Escape

D Space

The Tab key moves focus forward through interactive elements.

In Angular, which decorator listens to keyboard events on a component?

A @Output

B @Input

C @HostListener

D @Injectable

@HostListener listens to events like keyboard presses on components.

What does setting tabindex="-1" on an element do?

A Makes element focusable by Tab key

B Highlights element visually

C Disables element completely

D Removes element from Tab order but allows programmatic focus

tabindex="-1" removes element from Tab order but lets scripts focus it.

Which ARIA attribute helps indicate the current focused item in a list?

A aria-selected

B aria-hidden

C aria-label

D aria-checked

aria-selected marks the focused or selected item in a list.

What Angular feature helps update focus targets when UI elements change dynamically?

A NgModules

B New control flow syntax (@if/@for)

C Standalone components

D Template-driven forms

The new @if and @for control flow lets you update UI and focus targets smoothly.

Explain how to implement basic keyboard navigation support in an Angular component.

Think about focus order, event listening, and accessibility.

Describe why keyboard navigation is important and how Angular features help improve it.

Consider accessibility and Angular tools.

Practice

1. What is the main purpose of adding keyboard navigation support in an Angular app?

easy

A. To allow users to navigate the app using keyboard keys

B. To improve the app's loading speed

C. To change the app's color scheme automatically

D. To add animations when clicking buttons

Solution

1. Step 1: Understand keyboard navigation

   Keyboard navigation lets users move through app elements using keys like arrows or tab.

2. Step 2: Identify the purpose in Angular apps

   Adding keyboard navigation improves accessibility and user experience by enabling key-based movement.

3. Final Answer:

   To allow users to navigate the app using keyboard keys -> Option A

4. Quick Check:

   Keyboard navigation = user key movement [OK]

Hint: Keyboard navigation means moving with keys, not visuals [OK]

Common Mistakes:

• Confusing keyboard navigation with app speed
• Thinking it changes colors or animations
• Assuming it only works with mouse clicks

2. Which Angular syntax correctly listens for the 'ArrowDown' key press on a button?

easy

A. Click

B. Click

C. Click

D. Click

Solution

1. Step 1: Recall Angular event binding syntax

   Angular uses parentheses for events and lowercase event names with dots for key names.

2. Step 2: Match correct key event syntax

   The correct syntax is (keydown.arrowdown) with lowercase and dot notation.

3. Final Answer:

   <button (keydown.arrowdown)="onArrowDown()">Click</button> -> Option B

4. Quick Check:

   Angular key event = (keydown.arrowdown) [OK]

Hint: Use lowercase and dot for key events in Angular [OK]

Common Mistakes:

• Using uppercase letters in event names
• Replacing dot with dash or camelCase
• Missing parentheses around event

3. Given this Angular snippet, what happens when the user presses the 'ArrowDown' key?

<button #btn1 (keydown.arrowdown)="focusNext(1)">One</button>
<button #btn2 (keydown.arrowdown)="focusNext(2)">Two</button>
<button #btn3>Three</button>

Assuming focusNext(index) sets focus to the button at that index, which button gets focused after pressing 'ArrowDown' on button 1?

medium

A. Button One again

B. Button Three

C. Button Two

D. No button gets focused

Solution

1. Step 1: Understand the event binding

   Pressing 'ArrowDown' on button 1 triggers focusNext(1), which focuses button at index 1 (button 2).

2. Step 2: Identify which button is at index 1

   Button Two is the second button, so it receives focus.

3. Final Answer:

   Button Two -> Option C

4. Quick Check:

   ArrowDown on btn1 focuses btn2 [OK]

Hint: Index 1 means second button, so focus moves there [OK]

Common Mistakes:

• Assuming index starts at 0 instead of 1
• Thinking focus stays on the same button
• Confusing button labels with indexes

4. You wrote this Angular code to move focus on 'ArrowDown', but it does not work:

@ViewChildren('btn') buttons: QueryList<ElementRef>;

focusNext(index: number) {
  this.buttons.toArray()[index].nativeElement.focus;
}

What is the error preventing focus from moving?

medium

A. Index should be zero-based, not one-based

B. Wrong decorator used instead of @ViewChild

C. QueryList does not support toArray() method

D. Missing parentheses after focus method call

Solution

1. Step 1: Check method call syntax

   The code uses nativeElement.focus without parentheses, so the focus method is not called.

2. Step 2: Understand method invocation

   To move focus, focus() must be called with parentheses to execute it.

3. Final Answer:

   Missing parentheses after focus method call -> Option D

4. Quick Check:

   Call focus() with () to move focus [OK]

Hint: Remember to call focus() with parentheses [OK]

Common Mistakes:

• Forgetting parentheses on method calls
• Confusing @ViewChild and @ViewChildren usage
• Assuming toArray() is invalid on QueryList

5. You want to create a keyboard navigation system in Angular where pressing 'ArrowDown' moves focus to the next item, and pressing 'ArrowUp' moves focus to the previous item in a list of buttons. Which approach correctly supports this behavior and handles edge cases (start and end of list)?

hard

A. Use @ViewChildren to get buttons, then in keydown handlers call focusNext(index) or focusPrev(index) with checks to wrap focus from last to first and vice versa

B. Use @ViewChild for each button separately and manually set focus without index checks

C. Use (keydown) event without specifying keys and call focus() on the first button always

D. Use native JavaScript event listeners outside Angular to manage focus without Angular bindings

Solution

1. Step 1: Understand Angular focus management

   @ViewChildren collects all buttons, allowing indexed access to manage focus programmatically.

2. Step 2: Handle keydown events with wrapping logic

   Using keydown handlers for ArrowUp and ArrowDown with index checks lets you move focus up/down and wrap from last to first or first to last.

3. Step 3: Compare options for correctness

   Use @ViewChildren to get buttons, then in keydown handlers call focusNext(index) or focusPrev(index) with checks to wrap focus from last to first and vice versa uses Angular patterns and handles edge cases correctly. Others miss index checks or Angular integration.

4. Final Answer:

   Use @ViewChildren to get buttons, then in keydown handlers call focusNext(index) or focusPrev(index) with checks to wrap focus from last to first and vice versa -> Option A

5. Quick Check:

   Indexed focus with wrapping = correct keyboard navigation [OK]

Hint: Use @ViewChildren and wrap focus indexes for smooth navigation [OK]

Common Mistakes:

• Not handling focus wrap at list ends
• Using @ViewChild for multiple elements incorrectly
• Ignoring Angular event bindings and using native listeners