Lee Carré (2021-07-02 20:13:06+00:00): “crazy details”
Gosh, I'd forgotten about this one.

This was one of the cooperative places. A bunch of answers were apparent just from looking carefully, which helped, so I thought it more worthwhile to try 20 questions to go for completeness, while I was there anyway (and they had barely opened, still prepping, without any customers yet, so was perfect timing for the opportunity; that's sometimes why I only add a few things to others, because they're clearly busy selling and it's not a time when they'll be receptive to questions).

“the list of not-supported payment modes excessive (except maybe the more common ones like american express)”
Ah, yeah, I had to think back to why. Unless it was simply because I didn't tick those boxes in the UI widget, I think it may have been because they made clear that none but payment:apple_pay is accepted, so since I had the info it seemed better to mark them explicitly instead of leaving them remain ambiguous (as if undetermined).

Notice that when entire categories aren't accepted (like cryptocurrencies) I only set the generic key, rather than each individual sub-type. In this case, it was only because one (crApple) was accepted, but definitely no others, that I (probably) decided to do it that way.

One use case would be for tourists bringing foreign cards or whatever, since Jersey is still something of a tourist spot.

To my understanding tags aren't intended to be for (direct) human-reading. So, I was probably also thinking of machine-readability and the context of running some query to find places that accept one's favourite payment:*. American Express might be the convenient example; some places are all ‘oh, yes, of course, we accept everything’ while others are adamantly ‘no, AE charges too high fees, …’ while gladly accepting the likes of Visa & MC. So, for AE card-holders, the tag not being set would be ambiguous.
Another might be payment:delta which I've seen at a few places, but (so far) not many.

“I wouldn't add microbrewery=no”
I did debate myself over that one, especially for this type of establishment. A brewery (micro or otherwise) would obviously be far more of a pub type thing.

I'll probably not bother in future, unless there's a reasonable chance that they might actually have one.

“The detailed infos for wheelchair users are very useful. Great that you remember to look for this!”
Well, Vespucci & presets help a lot. Once I'm sure the thing is tagged to match the right preset, I then have it add keys (including optional ones), along with common sets like payment:*, and start going through them.

I avoided wheelchair* for a while, since I didn't feel qualified to make that determination. But, then realised that some info is better than none, and people on wheels aren't gonna go somewhere which could dmdwtp being a waste of time, nor are many gonna survey unknown places. There's just too much involved for them (I know some people who're affected one way or another, which is part of my motivation).

The one I do keep forgetting, is disability:* (or disabled:*, whichever it is). Or I only remember after submitting & closing the changeset.
Obvious ones would be the blind and/or deaf, which have a bunch of different difficulties. Others are not obvious but just as life-altering.

I'm a fan of buyers making the most of their market influence, as a means to persuade sellers to adapt in order to remain in the market. So, in this context, if those on wheels know that one place is more accessible than another, and more / enough decide to favour that place either for convenience or principle, then less accessible competitors will soon have strong incentive to adapt in order to survive.
Thus, by giving the wheel-enhanced the info to make such decisions, I'm helping that process.
If not, and it's ignored, then no harm done.