You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
International brands may choose to "latinize" their domain names (or offer alternatives) as an accommodation for users unfamiliar with how to access extra-language characters on their keyboards. The domain should still have the ability to announce with the correct brand/company pronunciation.
Abbreviations and Concatenations
Many domains choose to use abbreviated words for their domain or concatenations with thier TLD which is intended to be read as part of the "name". Pronunciation standard could reduce confusion when the page uses a "correctly" pronounced word or phrase that doesn't seem to match the domain.
Security (Homograph attack)
Is it worth mentioning in the use cases document that homograph attacks in domain names could be an attack vector for AT users?
Similar to how homoglyph attacks target sighted users. I see correct pronunciation as an additional layer of protection (albeit easily reproduced) where a user depends on AT to announce link resolution/page loading.
The text was updated successfully, but these errors were encountered:
Latinized Names
International brands may choose to "latinize" their domain names (or offer alternatives) as an accommodation for users unfamiliar with how to access extra-language characters on their keyboards. The domain should still have the ability to announce with the correct brand/company pronunciation.
Abbreviations and Concatenations
Many domains choose to use abbreviated words for their domain or concatenations with thier TLD which is intended to be read as part of the "name". Pronunciation standard could reduce confusion when the page uses a "correctly" pronounced word or phrase that doesn't seem to match the domain.
Security (Homograph attack)
Is it worth mentioning in the use cases document that homograph attacks in domain names could be an attack vector for AT users?
Similar to how homoglyph attacks target sighted users. I see correct pronunciation as an additional layer of protection (albeit easily reproduced) where a user depends on AT to announce link resolution/page loading.
The text was updated successfully, but these errors were encountered: