[nbaddam]

Summary

Updates package to axe DevTools framework version 1.4.0.

This release of the axe DevTools framework (4.1.0) makes SupportsDynamicType
run automatically and it reports at CRITICAL impact. The
sample app uses fixed font sizes throughout, so every screen fails it and the existing
zero-critical check could never pass.

The check now allows that one rule by ID while still failing on anything else, so it
continues to demonstrate how you'd gate a build on accessibility. In your own app you'd
fix the fonts rather than allow the rule.

• RegressionUITests.assertNoCriticalResults()
• TargetedScanUITests.testHomeScreenHasNoCriticalIssues()

Also updated comments that referred to "the dashboard" to say DevHub, and clarified
where you can uncomment to post results.

Framework bump

Bumps the SPM dependency to 4.1.0.
Release: https://github.com/dequelabs/axe-devtools-ios/releases/tag/4.1.0

[Copilot]

Pull request overview

Updates the sample app’s UI tests to keep the “fail on CRITICAL accessibility issues” gate meaningful after the August axe DevTools release, by allowing the known CRITICAL SupportsDynamicType rule while still failing on any other unexpected CRITICAL results.

Changes:

• Adjusted CRITICAL-gating assertions to allow SupportsDynamicType while still failing on other CRITICAL failures.
• Refreshed test comments to refer to DevHub and clarified where to uncomment upload behavior.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
RegressionUITests/RegressionUITests.swift	Allows a known CRITICAL rule while keeping the regression gate for unexpected CRITICAL issues; updates scan/upload comments.
axe-devtools-ios-sample-appUITests/TargetedScan/TargetedScanUITests.swift	Updates targeted scan test messaging and gating to allow the known CRITICAL rule while failing on unexpected CRITICAL issues.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.