In #42524, the iPadOS keyboard regression was caught by exactly the right exchange — mdo asked coliff to re-test on hardware he didn't have, and coliff confirmed it the next day. That worked well. The only reason it didn't happen a week earlier on #42500 is that nothing in the process prompted anyone to ask.

Would the team be open to one optional section in .github/PULL_REQUEST_TEMPLATE.md?

Accessibility verification (if this PR changes rendered output)

• Verified with assistive technology or a real device — name it, plus OS/browser and what you observed
• Not yet — requesting a reviewer with access to verify before merge
• Not applicable — no rendered output affected

The middle option is the one doing the work: it turns "I can't check this myself" from a private problem into a visible, routable request. It blocks nothing, adds no review stage, and needs no accessibility expertise from reviewers.

Asking first per the contributing guidelines rather than opening a PR unannounced. Happy to open one if it's welcome, and equally happy to drop it — template changes touch every contributor, so it's your call.

Context, if useful: this came out of reading seven accessibility PR threads across four projects, four of them Bootstrap's — earlier discussion here: https://github.com/orgs/twbs/discussions/42779