[RFC] Feature Proposal – sensory_friendly (Round 2)

@JPinAR and I have come up with a second round of the sensory_friendly proposal following feedback in previous RFC and voting periods! We welcome comments on this revised proposal here or on the talk page:

Proposal:Sensory - OpenStreetMap Wiki

Please, cross post this announcement on the tagging mailing list on my behalf by sending an email to: tagging@openstreetmap.org.

1 Like

This tag is very important to neurodivergent people, and as so i 100% approve it.

1 Like

The revised tagging scheme strongly recalls the wheelchair=* tagging scheme. That’s a good move, since wheelchair=* is so well-established and well-supported. The proposal should mention this relationship so voters less familiar with wheelchair=* will know to compare and contrast the two situations.

The new table of specific accommodations makes the proposal much more concrete. Thanks for researching the various accommodations and sensory disorders. Since amenity=quiet_room came along for the ride and you acknowledge that a quiet room isn’t necessarily for sensory needs, the proposal could call out explicitly that sensory_friendly:accommodation=* is only valid when it’s intentionally offered as an accommodation. Otherwise, some of these qualities are often present by coincidence, such as dimmed_lighting at a cinema or fine dining restaurant or refueling_assistance at any gas station in New Jersey. The “Subjectivity” section sort of addresses this issue, but I think this is a good place to reinforce the message.

The section on conditional tagging could be simpler. by_appointment is a well-established condition, but upon_request and listed_events are novel as far as I can tell. I’d suggest using the existing "comment" syntax for these cases, which would enable mappers to relay more details about when the accommodations are provided.

It looks like the previous vote got removed in favor of the reworked proposal. Would you mind archiving that vote on a subpage or moving the reworked proposal to a new proposal page? (After all, the proposed key hasn’t been sensory=* for a while now.) That would make it easier for participants in the previous round to tell what changed and what didn’t.

A use case for ‘upon_request’ is I went to a coffee shop with a friend today, they have sensory sensitivity and the music was too loud. Upon request, the shop happily and promptly lowered the volume to accommodate our need.

Additionally, many people I know that have sensitivity to sensory items also have some form of anxiety around asking for accommodation. I think it would be useful to tag that a place is particularly upon request instead of relegating it to a comment. That way if a data consumer wanted to list or filter places by default or request it would be possible.

Events I am not sure if there’s a more always to capture but would be open to feedback to anyone hosting / participating in such events!

1 Like