• do
InterCourses
CoursesBlogs
0
← DOM Manipulation with JavaScript
○The page is a tree○Exercise: follow the document reference○Load a script when the page is ready○Exercise: initialize a deferred script○Find one element by id or CSS selector○Exercise: select a notice and label○Compare DOM properties, HTML attributes, and node types○Exercise: inspect a room input and its nodes✦Module Quiz
○Find every match with querySelectorAll○Exercise: label every trail stop○Move from a child to its relatives○Exercise: trace a nested card○Check for missing elements and search within a card○Exercise: update only the chosen card○Compare a live HTMLCollection with a static NodeList○Exercise: safely expand a live collection✦Module Quiz
○Safe text and HTML○Exercise: render a safe notice○Read and change link attributes○Exercise: update an accessible link○Data attributes and conditional text○Exercise: announce session availability○Boolean attributes and DOM properties●Exercise: unlock a volunteer sign-up✦Module Quiz
○Add, remove, and check classes○Exercise: mark a favourite card○Toggle a panel accessibly○Exercise: toggle the help panel○Inline styles, classes, and hidden○Exercise: style and hide a notice○Change a CSS custom property from JavaScript○Exercise: change a workshop card accent✦Module Quiz
○Create and Append a Text Node○Exercise: Add a Reading List Item○Place Nodes Before and Between○Exercise: Order the Workshop Agenda○Remove, Replace, and Clear Safely○Exercise: Refresh a Museum Display○Clone a Card and Insert a Batch○Exercise: Clone Two Exhibit Cards✦Module Quiz
○Listen for Clicks with a Named Handler○Exercise: Check Library Hours○Event Target, Current Target, and Delegation○Exercise: Delegate Pantry Actions○Keyboard Events Without Trapping Keys○Exercise: Search the Recipe Box○Once, Remove, and Bubble○Exercise: Control Workshop Notifications✦Module Quiz
○Read a field while someone types○Build a live name preview○Handle submit without leaving the page○Validate a library request○Keep a selection in sync on change and reset○Sync a preference and its reset state○Read multiple checked values with FormData○Build a checkbox-based garden request✦Module Quiz
○Filter a list as someone types○Build a live trail finder○Toggle an accessible disclosure○Build a guide menu disclosure○Create and remove items with one delegated listener○Build a neighborhood task board○Sort a workshop table with accessible buttons○Build an accessible sortable resource table✦Module Quiz
○Read selectable cards and detail updates○Build directory cards and a selected profile○Trace live search and an empty state○Add live search to the community directory○Trace safe additions and delegated removal○Add and remove community directory cards✦Module Quiz
○Read and update a live itinerary○Build the workshop itinerary○Add a validated item through a form○Add a workshop session○Filter and remove live entries○Finish the workshop planner✦Module Quiz
○Fetch JSON and render safe text○Exercise: load recipe cards○Handle loading, empty, and failed responses○Exercise: handle alert states○Build a query with URLSearchParams○Exercise: search the catalog○Abort outdated requests○Exercise: keep the latest result✦Module Quiz
○Load a dashboard from an offline API fixture○Build an events dashboard○Query a dashboard with URLSearchParams○Add event search to the dashboard○Retry requests without stale results○Finish a resilient event dashboard✦Module Quiz

Exercise: unlock a volunteer sign-up

The tour demo used a consent checkbox to enable booking. Now a community kitchen needs a sign-up button that unlocks only when someone confirms they have read the shift details.

Transfer the idea

A boolean HTML attribute is true because it is present, not because its value spells "true". disabled="false" still disables a button. The DOM property .disabled is a real boolean and reflects changes to the button's attribute; .checked gives a checkbox's current on/off state after interaction without rewriting the original checked attribute. Do not read getAttribute("checked") to determine its live state. hasAttribute("disabled") checks whether the reflected attribute exists and returns true or false. On each checkbox change, recompute the button state from the checkbox rather than guessing whether to toggle it.

Here is the same technique on an unrelated equipment loan page, not the volunteer sign-up you will implement:

javascript
const terms = document.querySelector("#loan-terms");
const borrow = document.querySelector("#borrow-equipment");
function updateLoan() {
  borrow.disabled = !terms.checked;
  console.log(borrow.hasAttribute("disabled"));
}
terms.addEventListener("change", updateLoan);
updateLoan();

Notice the last call initializes the page before the first change event. In your starter, the HTML already has a labelled checkbox, a disabled button, and a status line. The supplied updateShift() function already computes the button's disabled state and is called on load. Edit script.js, then use the preview to check, uncheck, and check again. Submit to run the three checks.

Your Task

  1. Inside updateShift(), set #shift-status to Read the shift details first. for the initially unchecked checkbox.
  2. Listen for change on #shift-agreement by registering updateShift; checking the box should enable the button.
  3. Replace the fixed status message with one selected by joinShift.hasAttribute("disabled"): show Sign-up is ready. when enabled and the initial message when unchecked again.
Hint 1
1 / 2
HINT 1

Read the checkbox's current .checked value rather than its checked HTML attribute.

HINT 2

Assign a boolean to button.disabled, then inspect button.hasAttribute("disabled").

Take the Quiz →
Loading editor…
READY
intercourses
javascript