Issue:
Monzo.me got a new design, however, the Apple Pay button appears to be less WCAG 2.2 AAA-compliant, instead going for WCAG 2.2 AAAnt-compliance.
If you’re a 31337 XxX_ProSniper_360_XxX you might be able to aim your mouse just right, or, alternatively, if you know how to cascade the sheets of style, you can whack it into a more reasonable size, but good luck doing either on a phone.
I’ll never understand people who quote obscure guidelines as some sort of gotcha when it’s going to be absolutely nothing to do with it.
Delete the app. Restart device. Reinstall.
This happens when you request a payment from a transaction page, it doesn’t happen on the standard Monzo.me links
And you can’t uninstall a website @Revels
The joke is that WCAG AAA is a set of accessibility guidelines. WCAG AAAnt is something I made up as a bit more interesting take on the “what is this, an X for ants?” joke.
And I’ll never get why people repeat the “have you tried turning it off and on again” without actually reading any of the problem description, as some sort of catch-all solution to any technical issue. I tried it on 2 iPhones and on my Mac, where it happened on all 3 devices, so clearly, restarting the device wouldn’t help.
Seems to be specific to payment requests, not if you just visit a regular monzo.me/someone link.
How long have you been able to split bills with monzome links? I used to always just send my link with the amount, probably why I got frozen after a few
According to Bill splitting made simple, 6 years, or, about as long as the feature has existed
Wow, had no idea 
You dropped the moustache today.
The criticism was pretty obviously tongue in cheek (and I’m autistic!) and Monzo.me is not an app you can delete and reinstall. It’s a website.
Had to scroll really far back (it’s been longer than I thought) to find a transaction I could split the bill on, but yes, pay request links from bill splits is the only link that seems to result in this bug.
Voted on it now. Hopefully gets fixed. Should be a simple css fix.
Tried it today and it seems to be resolved!
