DOM and events · Lesson 9 of 10 · 7 minutes

DOM and events: Status announcements

Updating an existing live region can communicate a status without moving focus away from the user.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

Current edit

PreviewNo external resources

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Build status announcements
Build this first target: the JavaScript statements shown in the example, as executable-position code rather than a string or comment. Explain how the values and control flow implement this lesson’s concept; this browser lab checks structure without executing arbitrary JavaScript.
Hint & worked example
Updating an existing live region can communicate a status without moving focus away from the user.
The requested statements are present as code, not inside a string or comment. No arbitrary JavaScript is executed.
```
const status = document.querySelector("#status");
```
Common mistake to avoid: A string containing code executes automatically when it is assigned.
2
Extend the status announcements example
Extend your file to include: the JavaScript statements shown in the example, as executable-position code rather than a string or comment. Explain how the values and control flow implement this lesson’s concept; this browser lab checks structure without executing arbitrary JavaScript.
Hint & worked example
Updating an existing live region can communicate a status without moving focus away from the user.
The requested statements are present as code, not inside a string or comment. No arbitrary JavaScript is executed.
```
const status = document.querySelector("#status");
const message = "Saved locally";
```
Common mistake to avoid: A successful element lookup guarantees that the rest of an event handler is correct.
3
Verify the complete status announcements pattern
Finish the pattern with: the JavaScript statements shown in the example, as executable-position code rather than a string or comment. Explain how the values and control flow implement this lesson’s concept; this browser lab checks structure without executing arbitrary JavaScript.
Hint & worked example
Updating an existing live region can communicate a status without moving focus away from the user.
The requested statements are present as code, not inside a string or comment. No arbitrary JavaScript is executed.
```
const status = document.querySelector("#status");
const message = "Saved locally";
if (status) { status.textContent = message; }
```
Common mistake to avoid: A string containing code executes automatically when it is assigned.

Understand the pattern

Updating an existing live region can communicate a status without moving focus away from the user.

Misconceptions to reject

A string containing code executes automatically when it is assigned.
A successful element lookup guarantees that the rest of an event handler is correct.

This is a code-inspection lab, not a full JavaScript runtime.

Worked example and expected result

const status = document.querySelector("#status");
const message = "Saved locally";
if (status) { status.textContent = message; }

Updating an existing live region can communicate a status without moving focus away from the user.

Try a variation

Adapt the final example to a different project name while retaining its structure and relationships. A different context still needs a real browser and accessibility check.

Explain it

Which statement correctly explains status announcements?Updating an existing live region can communicate a status without moving focus away from the user.A string containing code executes automatically when it is assigned.A successful element lookup guarantees that the rest of an event handler is correct.

Apply it elsewhere

You reuse status announcements in a different project. What must still be verified?Nothing; passing a single exercise guarantees every future use.Only whether the source code has the same number of lines.The input values, element availability, and actual behavior in a real browser.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: DOM and events: DOM behavior checkpoint Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

MDN: JavaScript fundamentals