Universal Acceptance Day 2026 is being celebrated across more than 30 countries — from Nairobi to Hanoi, from Hyderabad to Port of Spain. Universal Acceptance or UA, is a technical standard that ensures all valid domain names and email addresses — regardless of script, language or character length — work seamlessly across all internet-enabled systems, websites, applications and platforms.

This year’s celebration carries particular significance. UNESCO and ICANN have signed a formal Memorandum of Understanding on multilingualism and presented a Joint Policy Brief at ICANN85 in Mumbai. The brief outlines recommendations for governments, the technical community, and the private sector to integrate UA into digital inclusion strategies worldwide.

This is a moment to recognise how far we have come and to be honest about the work that still remains.

Where It Began: Technology Without Policy

The technology for Internationalized Domain Names (IDNs) was pioneered by engineers like Dr. Tin Wee Tan of the National University of Singapore, who first implemented IDNs in March 1998, and Prof. S. Subbiah Subramanian, Co-Inventor of IDN and Chairman of iDNS.net International. Together, they built the technical foundation for a multilingual internet.

But the technology alone was not enough. The prevailing global authority had rejected it, they said. That is where policy leadership became essential.

When I served on the ICANN GNSO Council (2005-2007), the IDRU group, the International Domain Resolution Union, which represented the major global IDN community domain names community in non-Latin scripts like Arabic, Chinese, Russian, Hindi, Hebrew, Korean, Cyrillic, and many others, came to me. They had the technology. They had the evidence. They had the global need. What they lacked was a policy strategist inside the ICANN machinery.

As IDRU’s Executive Director, David Allen, documented on behalf of the global IDN community they represented: “You have worked hard and long to champion Internationalized Domain Names. You have made the case within ICANN for a policy development process that will see IDNs in service of the world community.”

Moving IDNs from rejected technology to formal ICANN policy required as much advocacy as innovation. I proposed that we address IDNs as a formal policy gap. I pushed for a policy dialogue. I chaired the effort. The GNSO Council accepted IDNs as a legitimate policy gap, and the work began. Despite past controversies, in fact, Vint Cerf, Chair of ICANN at the time, accepted it as a welcome initiative.

The IDRU later gave me a testimonial for my contributions. But the real achievement was not personal. It was the recognition that multilingualism on the Internet was not a technical luxury—it was a policy necessity.

Remaining Challenges - and the Need for Honest Framing

Progress on UA is real. But some of the framing around remaining challenges deserves closer examination.

For example, a recent article in The Star Kenya, reporting on UA Day events held in Nairobi on March 14th, 2026, cited .africa as an example of a domain still facing Universal Acceptance challenges: “Currently, some businesses using newer domain names such as ‘.africa’ or local-language email addresses still face difficulties because certain online systems fail to recognise them.”

That framing is misleading. Universal Acceptance is specifically about Internationalized Domain Names, domain names in non-Latin scripts like Arabic, Chinese, Hindi, and Cyrillic. .africa is an ASCII string. Its challenges are not technical. They are operational.

According to domain registration data from netapi.com and DomainMetaData, approximately 55,000 active domains are registered under .africa as of early 2026 serving a continent of 1.5 billion people under the AUC-aligned registry operator. For context, the same operator manages .co.za for South Africa’s 63 million people. After more than 20 years, .co.za has approximately 1 million active domains (source: SME South Africa / ZARC). That is not a success story. It is a decade of stagnation followed by another decade of stagnation. .africa has simply repeated the pattern.

That is not a multilingual internet problem. That is a registry management and accountability problem. The UA community should be careful not to allow genuine technical challenges to become a convenient cover for operational failures.

What Still Needs to Be Done

Universal Acceptance is not a new problem. It is an unfinished one.

• Software vendors must make UA a compliance requirement, not a best practice.
• Payment platforms must test every domain—not just .com and .org—before they block transactions.
• Government portals must accept IDN email addresses for citizen services.
• Registry operators must advocate for their own domains rather than waiting for the internet to accept them.

The next billion users do not need a one-day event. They need an Internet that works for them in their languages, in their scripts, in their own domains every day.

Universal Acceptance Day 2026 is a celebration. But celebration is not completion.

The engineers did their part. The policy wonks did theirs. Now it is time for the implementers to finish the work.

The long arc of multilingualism bends toward inclusion. But it does not bend by itself. It bends because people push.

Let us keep pushing.