Verify change on request
Description
This rule does not automatically validate anything. It simply reminds you to manually verify that changes of context are initiated only by user request or that a mechanism is available to turn off such changes. It is based on WCAG 2.2 Success Criterion 3.2.5 Change on Request (Level AAA).
A change of context
includes major disruptions such as opening a new window, moving focus to a different component, submitting a form, navigating to a new page, or substantially rearranging page content – any action that alters the user’s perceived environment. Under WCAG 3.2.5, these changes must only happen when the user explicitly triggers them (e.g., by clicking a button or link), or the page must provide a way for users to disable automatic context changes before they occur. The rule scans for interactive elements such as <button>, <a>, <input type="submit">, and elements with role="button" or role="link" and reports a reminder when any are present. No automated pass/fail determination is made.
Disabilities impacted
- Visual impairments – Screen reader users build a sequential mental model of page interaction. When a context change occurs automatically (e.g., a
<select>element navigates on change, or a new window opens without warning), the user’s position in the accessibility tree is suddenly disrupted. They may lose their reading position, miss critical announcements, or be disoriented about where they are on the page. This is especially disruptive for blind users who cannot visually confirm what just happened. - Cognitive disabilities – People with attention disorders, memory impairments, or learning disabilities rely on predictable navigation to avoid confusion and cognitive overload. Unexpected context changes – such as a page that auto-redirects, a form that submits after the last field is filled, or a popup that opens on page load – can cause disorientation, task abandonment, and anxiety. These users need a stable, predictable environment where they control the pace and sequence of interactions.
- Screen reader users – This group is specifically impacted because assistive technologies announce content in a linear, focused manner. When a context change fires without user activation, the screen reader may announce unexpected content, lose its virtual cursor position, or begin reading a completely new page without the user understanding why. Screen reader users who navigate by headings, landmarks, or links are particularly vulnerable to focus-redirect patterns that silently move them away from their intended target.
- Motor disabilities – People who use switch devices, eye-tracking systems, or speech-recognition software often navigate sequentially and with deliberate, effortful actions. An automatic context change (e.g., a timeout-based redirect or an
onchangehandler on a form field) may occur while the user is still in the process of navigating to or interacting with an element. The unexpected change forces them to re-orient, re-navigate, and expend additional physical effort to return to their intended task, causing fatigue and reducing task efficiency.
Why it matters
Predictable interaction behavior is a cornerstone of accessible web design. When users trigger a context change, they expect it; when it happens automatically, they are surprised. This distinction between user-initiated and automatic changes directly supports the WCAG Principle of Predictability (Guideline 3.2): Make Web pages appear and operate in predictable ways.
SC 3.2.5 extends this principle beyond form submission and focus changes (covered by SC 3.2.1 and 3.2.2) to all types of context changes, making it the broadest and most stringent criterion in the Predictable guideline.
Failing to meet this criterion can have legal, financial, and reputational consequences. Under the ADA, the European Accessibility Act (EAA), and Section 508 of the Rehabilitation Act, unpredictable context changes that prevent users with disabilities from effectively navigating a website can be cited as accessibility barriers. Beyond compliance, user trust erodes when people feel they have lost control over their browsing experience. A predictable, request-driven interface respects user autonomy and reduces cognitive friction for everyone.
Coding problems and solutions
Common coding problems
Since this rule is a manual-only reminder with no automated element validation, the following checklist describes what a human reviewer should manually verify when auditing for change-on-request compliance:
- Automatic redirects triggered on page load – Pages that use
<meta http-equiv="refresh">or client-sideglobalThis.locationredirects without user activation violate SC 3.2.5. A reviewer must check every page load (including login, checkout, and post-submission pages) for automatic URL changes that happen before the user interacts. - Select elements that navigate on change – Dropdowns (
<select>) with anonchangehandler that triggers navigation or form submission are a classic failure (WCAG Failure F36). The reviewer must test every<select>to verify that changing its value does not cause a context change without an explicit submit button. - New windows opened without user activation – Popup windows launched by
onload,onfocus, oroninputhandlers (WCAG Failures F52, F60, F22) catch users off guard. A reviewer must check that everyglobalThis.open()call is directly tied to a user click or keypress, not to page lifecycle events or text entry. - Automatic content updates that change page meaning – Carousels that auto-rotate, live regions that push major content shifts, or infinite scroll that reconstructs the page layout (WCAG Failure F61) can fundamentally alter what the user is reading. The reviewer must verify that auto-updating regions either provide a pause/stop control or do not constitute a change of context.
- Form auto-submission after the last field – Some forms automatically submit when the user completes the final input field (e.g., a search field that fires on keystroke delay, or a multi-step form that advances without a “Next” button). This is a context change not initiated by user request. The reviewer must test every form to confirm that submission requires an explicit activation step.
- Focus-triggered context changes – WCAG Failure F9 describes situations where removing focus from an element (e.g., via
onblur) causes a new window, form submission, or navigation. A reviewer must check that losing focus on any interactive element does not trigger an unexpected context change.
How to fix it
Replace auto-submitting selects with an explicit button
Dropdowns that navigate or submit on change are one of the most common violations. Require the user to press a separate button before any context change occurs. This approach also benefits keyboard-only and switch-device users who may overshoot their intended selection.
<label for="language-select">Choose language:</label>
<select id="language-select" name="language">
<option value="en">English</option>
<option value="fr">Français</option>
<option value="de">Deutsch</option>
</select>
<button type="button" id="go-button">Go</button>
<script>
document.getElementById('go-button').addEventListener('click', () => {
const select = document.getElementById('language-select');
globalThis.location.href = `/${select.value}/`;
});
</script><!-- Navigation fires immediately on selection change -->
<label for="language-select">Choose language:</label>
<select id="language-select" name="language"
onchange="globalThis.location.href = '/' + this.value + '/'">
<option value="en">English</option>
<option value="fr">Français</option>
<option value="de">Deutsch</option>
</select>Use server-side redirects instead of meta refresh or client-side timers
Automatic redirects should be performed on the server side (e.g., via HTTP 301/302 headers) whenever possible, so the browser never renders an intermediate page that could surprise the user. If a client-side redirect is unavoidable, provide clear warning text and a manual link as a fallback.
<!-- Server sends HTTP 301; this page is never rendered.
If server-side is not possible, provide manual fallback: -->
<p>You will be redirected shortly.
<a href="/new-location">Click here</a> if nothing happens.</p><!-- Auto-redirect without user consent or manual link -->
<meta http-equiv="refresh" content="0; url=/new-location">
<!-- Client-side auto-redirect on load -->
<script>
globalThis.setTimeout(() => {
globalThis.location.href = '/new-location';
}, 3000);
</script>Open new windows only on explicit user activation
Every call to globalThis.open() must be placed inside an event handler that fires in response to a user click or keypress. Never open windows from onload, onfocus, oninput, or timer callbacks without user intent. When a link opens a new window, always warn users with visible text or the aria-label attribute.
<!-- New window opens only on click, with a visible warning -->
<a href="/help" target="_blank" rel="noopener"
aria-label="Help documentation, opens in a new window">
Help <span aria-hidden="true">(opens new window)</span>
</a>
<!-- Programmatic open only from a click handler -->
<button type="button" id="open-help">Open help</button>
<script>
document.getElementById('open-help').addEventListener('click', () => {
globalThis.open('/help', '_blank', 'noopener');
});
</script><!-- New window opens on page load (F52) -->
<script>
globalThis.addEventListener('load', () => {
globalThis.open('/promo', '_blank');
});
</script>
<!-- New window opens when user types in a field (F60) -->
<input type="text" name="search"
oninput="globalThis.open('/results?q=' + this.value, '_blank')">
<!-- Link opens new window without warning -->
<a href="/terms" target="_blank">Terms of Service</a>Provide a mechanism to pause, stop, or hide auto-updating content
Carousels, live tickers, auto-refreshing feeds, and animated content that changes the page’s meaning must include a user-accessible control to pause, stop, or hide the updates. This allows users to consume content at their own pace without the page context shifting beneath them.
<section aria-label="Latest news" aria-roledescription="carousel">
<button type="button" id="pause-carousel"
aria-label="Pause auto-rotating news">⏸ Pause</button>
<ul id="news-list" aria-live="polite">
<li>Headline one</li>
<li>Headline two</li>
<li>Headline three</li>
</ul>
</section>
<script>
let intervalId = null;
const startCarousel = () => {
intervalId = globalThis.setInterval(() => {
const list = document.getElementById('news-list');
const first = list.firstElementChild;
if (first) {
list.appendChild(first);
}
}, 5000);
};
document.getElementById('pause-carousel').addEventListener('click', () => {
if (intervalId) {
globalThis.clearInterval(intervalId);
intervalId = null;
}
});
startCarousel();
</script><!-- Auto-rotating carousel with no pause control (F61) -->
<section aria-label="Latest news" aria-roledescription="carousel">
<ul id="news-list" aria-live="polite">
<li>Headline one</li>
<li>Headline two</li>
<li>Headline three</li>
</ul>
</section>
<script>
globalThis.setInterval(() => {
const list = document.getElementById('news-list');
const first = list.firstElementChild;
if (first) {
list.appendChild(first);
}
}, 5000);
</script>Avoid context changes on blur or focus events
Focus and blur are navigation events, not activation events. They should never trigger navigation, form submission, or new windows. Reserve context changes for click, keypress, or other explicit user-activation triggers. If validation on blur is needed, display an inline message; do not redirect or submit.
<!-- Blur triggers inline validation, not a context change -->
<label for="email">Email address:</label>
<input type="email" id="email" name="email"
aria-describedby="email-hint">
<span id="email-hint" role="alert" class="error" hidden></span>
<script>
document.getElementById('email')?.addEventListener('blur', () => {
const input = document.getElementById('email');
const hint = document.getElementById('email-hint');
const value = input.value.trim();
if (value.length === 0) {
hint.textContent = '';
hint.hidden = true;
return;
}
if (value.includes('@') === false) {
hint.textContent = 'Please enter a valid email address.';
hint.hidden = false;
} else {
hint.textContent = '';
hint.hidden = true;
}
});
// Submission requires explicit button click
document.getElementById('subscribe-btn')?.addEventListener('click', () => {
document.getElementById('email-form').submit();
});
</script><!-- Blur triggers new window (F9, F60) -->
<label for="email">Email address:</label>
<input type="email" id="email" name="email"
onblur="globalThis.open('/validate?email=' + this.value, '_blank')">
<!-- Focus triggers navigation -->
<a href="/products"
onfocus="globalThis.location.href = '/products'">View products</a>Known Limitations
- Manual-only verification – This rule performs no automated context-change detection. It cannot analyze whether a
selectelement navigates on change, whether a<meta>refresh tag exists, or whether a timer-based redirect will fire. It only reports a reminder whenever interactive elements are present on the page. The auditor must manually examine every interactive control and script. - Single-page applications (SPAs) – Client-side routing in frameworks like Angular, React, or Vue can produce context changes (view swaps, re-renders) that look identical to navigation but are implemented via the History API or virtual DOM. The rule cannot determine whether these transitions were triggered by the user or by programmatic logic such as route guards, timers, or state-change side effects.
- Shadow DOM – Interactive elements rendered inside shadow trees (e.g., inside custom Web Components) are not traversed by the rule’s selector, which operates on the light DOM only. Buttons, links, and other controls inside encapsulated components will not trigger the reminder, so entire sections of the UI may go unaudited.
- Asynchronously injected elements – Interactive controls added to the DOM after the initial page load (via
globalThis.fetch, third-party scripts, or lazy-loaded modules) may not be present when the rule evaluates the page. Context-change risks introduced by these late-arriving elements will be missed. - JavaScript event delegation and dynamic binding – The rule has no insight into JavaScript event listeners. A
<select>that appears safe in the markup could have anonchangenavigation handler attached viaaddEventListenerin a separate script file. The auditor must inspect all event bindings, not just inline attributes. - Third-party content and ads – Embedded widgets, ad iframes, social media embeds, and analytics scripts can trigger context changes (popups, redirects) outside of the site owner’s direct control. The rule cannot assess or flag these external behaviors because they operate in separate execution contexts.
Resources
- WCAG 2.2 Success Criterion 3.2.5 Change on Request – W3C
- Understanding SC 3.2.5 Change on Request – W3C WAI
- How to Meet WCAG 3.2.5 – W3C WAI Quick Reference
- WCAG Guideline 3.2 Predictable – MDN Web Docs
- Failure F36: Redirection on select change – W3C WAI
- Technique G76: Providing a mechanism to request an update – W3C WAI
Rule
- Audit: accessibility
- Standard: WCAG
- Level: AAA
- Success Criteria: 3.2.5
- Rule ID:
change-on-request