Tracking Page Accessibility: A 2026 Guide to WCAG, ADA Demand Letters and the Post-Purchase Journey

Tracking page accessibility means that a post-purchase tracking page, its notifications and its reschedule and returns flows can be used by people who rely on screen readers, keyboards, voice control or magnification. In the United States the exposure comes mainly from private lawsuits under Title III of the Americans with Disabilities Act, and there is no federal regulation that sets a technical standard for private-sector websites. In practice, the Web Content Accessibility Guidelines (WCAG) are the benchmark that the Department of Justice’s guidance points to, so a tracking page that meets WCAG 2.1 or 2.2 Level AA is the safest working target.

Why Tracking Page Accessibility Matters: The Business Case

Tracking pages are among the most visited pages a retailer owns after checkout, and they are built by vendors, which makes accessibility easy to assume and hard to prove.

• Seyfarth’s ADA Title III blog counted 3,117 federal website cases in 2025, up from 2,452 in 2024, and said website cases were 36% of all federal ADA Title III suits.
• UsableNet, which sells accessibility testing, reported more than 5,000 lawsuits in 2025 across federal courts and New York and California state courts, with e-commerce 70% of them.
• The Department of Justice’s 2022 web guidance says that it does not have a regulation setting detailed standards, and that businesses have flexibility in how they comply.
• The W3C published WCAG 2.2 as a Recommendation on 12 December 2024 and states that it does not deprecate or supersede 2.0 or 2.1.
• Ontario’s rules require public websites of covered organizations to meet WCAG 2.0 Level AA, and they apply to businesses and non-profits with 50 or more employees.

Courts are not uniform on whether a website needs a connection to a physical place to be covered by Title III, and a Minnesota district court held in 2025 that web-only businesses are covered. The two counts also use different methods, since Seyfarth counts federal cases and UsableNet adds state courts, so quote each with its source.

How to Make a Tracking Page Accessible in Six Steps

The six steps cover the whole post-purchase journey and not only the page that carries the logo.

1. Inventory the journey

List every post-purchase surface: the tracking page, the map, the reschedule and cancel flows, email and SMS notifications, the returns portal and the support links. Accessibility failures hide in flows that were added later.

2. Choose the conformance target

Set WCAG 2.2 Level AA as the target, with 2.1 Level AA as the floor. If you serve Ontario, the provincial rule names WCAG 2.0 Level AA, which 2.2 also satisfies.

3. Test automatically and manually

Run an automated scan to catch contrast, missing labels and broken structure, then test by hand with a keyboard and a screen reader. Automated tools cannot judge whether a reschedule flow makes sense to a person using assistive technology.

4. Prioritize by traffic and severity

Rank defects by how many customers meet the page and how badly each defect blocks a task. A reschedule form that cannot be used with a keyboard outranks a decorative image without alternative text.

5. Fix at the template and in the contract

Fix problems in the shared template and brand theme once, and require the vendor to fix defects in its own components within a stated period, with conformance re-tested after each release.

6. Publish a statement and a feedback route

Publish an accessibility statement that names the standard you target and gives a way to report a problem. A reachable feedback channel gives customers an alternative to a demand letter and gives you early warning.

Automated Scan, Manual Audit, Assistive-Technology Testing and Vendor Reports: Key Differences

What to Look for in a Tracking Page Platform

A current conformance report

Ask for an accessibility conformance report that names the WCAG version and level, the date and the components tested, and then verify it with your own test of your configured page.

Accessible branding controls

White-label themes let you set colors, and a tracking platform should flag or prevent color combinations that fall below 4.5:1 contrast for normal text.

Keyboard and screen-reader support in task flows

The reschedule, cancel and slot-selection flows should work with a keyboard alone and should announce status changes without moving focus, which WCAG 2.2 covers under status messages.

Accessible notifications

Email and SMS should carry plain-text alternatives, meaningful link text and the same information as the page, so a notification is not the only place a fact appears.

A release and remediation process

Look for a vendor commitment to retest after each release and to fix reported defects within a stated period.

Tracking Page Accessibility in Action: Real-World Results

A worked contrast example. WCAG 2.2 success criterion 1.4.3 requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text. Status badges and buttons are where brand colors most often fail, so check them first.

Three other WCAG 2.2 criteria deserve a place in every audit of a tracking page. Criterion 2.1.1 requires all functionality to be operable through a keyboard, which covers calendar pickers and slot lists in reschedule flows. Criterion 4.1.3 requires status messages such as “Your driver is 3 stops away” to be programmatically determinable without taking focus. Criterion 2.5.8 sets a minimum pointer target size of 24 by 24 CSS pixels, which matters for small action links on a phone.

An illustrative audit scorecard. The findings below are invented to show how to rank work, and they are not from a real page.

A leading ASEAN apparel retailer. The retailer’s last-mile delivery runs through several carriers, and Locus harmonizes carrier statuses into one standard set, computes accurate delivery dates at checkout and tracks deliveries and returns against the promise. Where-is-my-order and returns queries dropped by more than 40%. The result shows how much volume a tracking page carries, and it is not an accessibility result. Read the ASEAN apparel case study.

A Canadian grocery brand. The brand delivers fresh food to homes in more than 30 cities through several carriers, with a unified tracking dashboard replacing carrier-by-carrier checking. After automation, it reported a 33% faster order-ready-to-delivered cycle time and a 15% reduction in fulfillment costs. Again, this shows the scale of the post-purchase journey and not accessibility performance. Read the Canadian grocery case study.

Common Tracking Page Accessibility Mistakes to Avoid

Assuming the vendor has handled it. A vendor’s components may conform while your brand colors, content and custom scripts do not, so test the configured page.

Testing only the tracking page. Reschedule, cancel, returns and notification flows carry the tasks that block people, so include them.

Relying on an automated scan alone. Scans cannot tell whether a task can be completed, so add manual and assistive-technology testing.

Treating the Title II rule as your deadline. The Department of Justice’s Title II rule, whose compliance dates were extended by an interim final rule in April 2026, covers state and local governments and not private retailers. Private-sector exposure comes from Title III suits and state laws.

How Locus Approaches Tracking Pages and Delivery Notifications

Locus, the world’s first Decision-Intelligent, Agentic TMS, gives retailers a white-label tracking page that centralizes order status across owned and outsourced deliveries, sends alerts by SMS, email or push, lets customers reschedule or cancel, and keeps a consistent brand experience on third-party carriers.

Recognized by analysts and selected after evaluation. Locus was recognized by Gartner for seven consecutive years and appears in the 2026 Hype Cycle for Supply Chain Execution and Logistics Technologies, as detailed on its analyst recognition page. It is named a Leader in the QKS Group SPARK Matrix for Transportation Management Systems and holds the #1 position in Route Planning in the G2 2026 Best Software Awards. In October 2025, Ingka Investments, the investment arm of Ingka Group, the world’s largest IKEA retailer, acquired Locus. Ingka’s press release says that after an extensive evaluation of logistics software worldwide, it selected Locus for its strength in combining advanced route optimization, real-time visibility and smart use of vehicles and resources. Locus continues to operate independently.

What this means for accessibility. Locus has optimized 1.5B+ deliveries for 360+ enterprise customers across 30+ countries, and its agents and governance controls keep delivery status and exceptions consistent across carriers, which gives your tracking page reliable data to present. The accessibility of the page itself depends on how it is configured and tested.

What to confirm. Locus’s public pages do not state WCAG conformance for the tracking page, the reschedule flow or the notifications. Ask for an accessibility conformance report, the WCAG version and level it covers, and the process for fixing reported defects, and run your own keyboard and screen-reader test of your configured page.

To review your own tracking page and notification journey with a Locus specialist, schedule a demo.

For retailers asking how to make a tracking page accessible, Locus offers a white-label tracking page, multi-channel alerts and reschedule flows in one platform, so the accessibility target can be set and tested across the whole post-purchase journey.

Frequently Asked Questions

Are tracking pages covered by the ADA? Courts disagree on how Title III applies to websites, and no federal regulation sets a technical standard for private websites. Lawsuits against retail sites are common, so most retailers treat a tracking page as in scope. Ask counsel about your situation.

Which WCAG version should a tracking page meet? Target WCAG 2.2 Level AA, which also satisfies 2.0 and 2.1. The Department of Justice’s guidance names WCAG as helpful, and Ontario’s rule specifies WCAG 2.0 Level AA.

How many accessibility lawsuits are filed? Seyfarth counted 3,117 federal website cases in 2025, and UsableNet counted more than 5,000 across federal and New York and California state courts, with about 70% against e-commerce. The counts use different methods.

Do delivery notifications need to be accessible? Treat them as part of the journey. Email and SMS should carry plain-text content, meaningful link text and the same information as the page, so no fact appears only in an inaccessible format.

Does the Title II rule apply to retailers? No. The Department of Justice’s Title II rule covers state and local governments, and its compliance dates were extended in April 2026. Retail exposure comes from Title III and state laws.

Does Locus state that its tracking page meets WCAG? Locus’s public pages do not state WCAG conformance. Ask for an accessibility conformance report and test your configured page.