Add additional information to country support table#709
Add additional information to country support table#709zachmargolis merged 5 commits intomargolis-country-supportfrom
Conversation
The ISO country code could be useful in the meantime (until we improve the translation experience).
Could you share why you think it isn't needed? Does listing ISO country code suffice?
If including dialing codes, at least consider having those in a separated column. In this case, I think it'd be helpful to have them described explicitly. Also, from a screen reader user standpoint, I think receiving a dialing code number without any context to anchor it might be confusing to them. |
In my mind for the typical workflow to see if a country is supported, I would just try to cmd-f by the country name, falling back to the abbreviation, typically I don't refer to the dialing code. But maybe somebody else would? |
Hmm, for a French or Spanish user in this case, is it the translation experience reliable w/r/t country code? If not, could there be cases where dialing code might be helpful here? |
It probably wouldn't hurt to add it. One issue is that sometimes countries share a dialing code (ex both the US and Canada use +1) Also for reference here is AWS Pinpoint's page with a similar table, they include dialing code: https://docs.aws.amazon.com/pinpoint/latest/userguide/channels-sms-countries.html |
|
Updated to have dialing code in its own column (06baa4b) |
|
Looking to be in the right direction. 👍🏼 |
|
Cool! Will merge to include this in the main PR |

We have some additional data that we could render, but may be one of those "just be cause you can doesn't mean you should kind of things", so I'm just throwing this out there as a possibility
We could make these separate columns in the table if we wanted, but I worry that would add even more visual noise.