#language selection

Introduction

As millions of medical aspirants across India prepare to register for NEET UG 2026, the National Testing Agency (NTA) has released a special video to guide students through the often-confusing parts of the application process the selection of exam cities and the medium (language) of the test. With registrations underway and the deadline approaching, understanding these details has become essential to avoid avoidable errors that could affect exam centre allocation later.

Why This Guidance Matters

Every year, NEET UG attracts over 20 lakh applicants who must complete a detailed application form accurately to secure a centre and avoid complications. Even minor mistakes during form submission can lead to incorrect exam centre allotment, language preference issues, or even rejection of the application.

The newly released NTA video explains step-by-step how exam city and language choices are processed, stressing attention to detail when filling out the application form. This guidance is especially helpful for first-time applicants and students in remote areas who might be unfamiliar with the technical aspects of the process.

Choosing Your Exam City: What You Must Know

A key focus of the NTA guidance is how your exam city choice is determined during registration:

The exam city allocated to each student is based on the details entered in the application form, particularly the permanent and present address fields.

It is crucial that both current and permanent addresses are accurate and complete, because these directly influence which centres you may be offered.

The new process ensures that exam centre allocation is fair, logical, and aligned with where candidates actually live, reducing travel burdens and logistical issues.

This means aspirants should double-check their address information before final submission. Incorrect or inconsistent details can lead to the system placing them in a distant or unintended exam city.

According to newer guidance, choices of multiple preferred cities have been refined, and in some cases the traditional multiple city preference option has been significantly changed or removed, making the accurate address even more critical.

Language Choice Explained

NEET UG is offered in multiple languages to ensure accessibility for students from different regions. The language of the question paper is selected while filling the application form. However, as emphasized in the NTA video, the language choice is also tied to the details submitted in the form:

Students must select their preferred medium of examination carefully during registration.

Incorrect or rushed selections can lead to complications or issues on exam day if the medium is not supported at the exam location.

NTA’s guidance specifically tells candidates to make informed language choices and verify that their selection aligns with their comfort and preparation.

Selecting the correct medium is vital because NEET UG offers a range of languages, and not all centres may administer exams in every language. Making the right choice helps ensure that candidates receive the NEET question paper in a language they understand well.

Common Questions Covered in the NTA Guidance Video

The NTA video addresses several typical confusions and questions that candidates often face, including:

Can the exam city be changed after submission? Practical possibilities and limitations

When should the language be selected? Clarification of timing during the form process

How do address fields affect centre allocation? A detailed explanation of the system logic

What happens if addresses and preferences conflict? Guidance on avoiding mismatches and errors

This proactive information from NTA aims to reduce the number of avoidable mistakes during the application process, making the entire system more efficient for applicants.

Important Dates to Remember

Although the official NTA guidance video focuses on exam city and language selection, candidates must also be aware of the broader NEET UG 2026 timeline:

Application window: The registration process is currently underway until early March 2026.

Exam date: The NEET UG 2026 examination is scheduled for early May 2026.

Correction window: A brief period after submission during which applicants can edit certain details.

Result announcements, admit cards, and answer keys: Will follow later on the official NTA portals.

Being mindful of these dates helps applicants plan their registration timeline, including when to finalize critical choices like exam city and language.

Final Tips for Applicants

If you are applying for NEET UG 2026:

Review your address details carefully before final submission.

Watch the official NTA video guidance to avoid common errors.

Make your language choice thoughtfully based on your preparation and comfort.

Check deadlines and retain copies of submitted information for future reference.

Accurate form filling during the NEET UG 2026 registration stage translates to a smoother experience later in the exam journey.

Conclusion

The NTA’s new video explaining exam city and language choice for NEET UG 2026 applications is an important resource for aspirants. With registrations ongoing and deadlines approaching, paying attention to address details and language preferences is essential to secure the best possible exam centre and ensure a hassle-free application process.

The Autonym font was announced in the Wikimedia blog. The Autonym font is a font that contains only the glyphs that are absolutely necessary for display a list of languages. This small font solves an interesting conflict between UX and performance when dealing with lists of languages.

The problem of discoverability

When content is provided in several languages, you can find a list of languages somewhere. If you support languages for which users may lack their fonts, you have to decide when to deliver those fonts to them or not.

For a page mostly written in Thai, it makes sense to deliver a Thai font to users. However, if the page contains a language list, should you deliver all the fonts necessary to display all languages in that list?

Deliver fonts impacts bandwidth. On the one hand, if we want all users to be aware that content is available in their language, we had to load a lot of fonts to make sure they display properly. This has a severe impact on bandwidth in a very inefficient way since users are downloading a whole font just to display each language name (e.g., a thai font is downloaded just to display "ไทย").

Not delivering fonts harms discoverability. On the other hand, if you don't deliver fonts to the users for the list of languages, you generate a problem of discoverability. Users lacking local fonts will not be able to discover that behind a link like "□□□□□" there is a version of the content in their language (a version they can display and read once they reach the content thanks to webfonts, but is undiscoverable for them). This problem is illustrated below:

Autonym solves the above problem by including only the glyphs needed to display language names, so language lists can be displayed properly with minimal bandwidth impact. This font will be used in language lists such as the one shown at the Universal Language Selector, or those you find at the sidebar of your favourite Wikipedia articles.

It's free to use

The font has been created by the Language Engineering team from the Wikimedia Foundation, and you are totally welcome to use it in your own website.

When I am using a computer which is not mine, sometimes I have a hard time to find some "special" characters used in Catalan or Spanish such as "ç" and "ñ". Then, I imagine what would happen if all my characters were "special", and even my own computer's keyboard was not prepared for them. This is the situation for many languages around the world.

But typing is not a problem at all if your computer is not even able to display text in your script. If you visit this page about the Javanese language you may get the impression that Javanese is an original language based on a single character: the square. Unfortunately, squares are what your computer uses to indicate that it lacks fonts for a specific script.

Language is our vehicle to communicate knowledge. Allowing users to read and write in their own languages is essential for projects such as Wikipedia. To help users to achieve this goal, new language tools have been added recently.

  The Universal Language Selector

The Universal Language Selector is being deployed to Wikimedia projects, and provides the following tools and settings:

Input methods allow users to type in a language their keyboard is not prepared for. For example, when the Greek input method is enabled, users can type "π" by pressing "p" in a non-Greek keyboard.

Web fonts. For languages with poor font support, fonts are delivered to the user automatically, so that the content is properly displayed.

Change menu language. You can change the language in which menus are displayed.

These tools are essential for many language communities but will also help in other scenarios as well.  For example, as Amir Aharoni explains, now Akkadian cuneiform is properly displayed when reading about the Tower of Babel in English Wikipedia (where mixed-language content is quite common). In addition, readers with dyslexia will also benefit from the inclusion of Open Dyslexic font as a choice for users.

  Design considerations

Many design considerations were made while designing these language tools, some are summarised below:

Different languages are supported to different degrees. Some users do not need language tools, while other users need them for the most basic activities. Thus, you need the right balance in order to make tools easy to find for those users that need them, but avoid disturbing the users that do not. 

Users speak a small number of languages. Despite the high number of languages supported by Wikipedia, each user is interested on a very small subset of those languages. Thus, providing the full list of all languages each time the user needs language support is sub-optimal. Different design patterns were applied in our designs to make language selection easier such as anticipation (show a small list of the likely languages according to previous selections and user context), forgiving input (allowing the user to search a language in different languages, even with typos), and undo (allowing to quickly revert if the user choice may led the user to a foreign language UI).

Repetitive use needs to be properly supported. Most language related actions do not happen in isolation. For context where switching between languages can be repetitive such as typing, it make sense to avoid extra steps and provide the tools at hand. For example, when selecting input methods, we allow the user to select previous languages right from the typing context, and by selecting a language the last input method used for this language is used avoiding an additional selection most of the time. 

If you are interested on more aspects of the design and you are attending Wikimania 2013 at Hong Kong, you can attend my talk: Improving the user experience of language tools.

An open project

While reading this post you may have tried to use the new language tools for your language. If you found they are useful we have good news: you can take these tools to your own website. Input methods, web fonts and language selection tools are available as jQuery components that can be used for any web projects.

Before I started working for the Wikimedia Foundation, I have never heard about Wolof, Tok Pisin, Wáray-Wáray or most of the 285 languages in which Wikipedia is available (or the 400 languages in which its software has been translated to).

This suddenly changed when I started working in the Universal Language Selector project. The goal of the Universal Language Selector is to make it easy to select a language and configure its support. This is a complex task for different reasons:

Amount of data.  When the number of possible languages approaches 400, a simple list just does not scale and we want people to find their languages of interest really quickly.

Diversity of data. There are very different kinds of languages and not all solutions work for all of them. For example, when organizing languages by region, you need to decide what to do with languages spoken in several regions or languages which are not associated to any specific geographic area (such as most constructed languages). Even ordering languages alphabetically is problematic when you target languages that are written in different (and even multiple) scripts.

Diversity of user needs. Some users are interested in their local language, other users may be interested in a language they are studying which is not spoken in their local area, or they may be abroad using a keyboard not prepared to write in the correct script.  

In order to solve those problems, we analyzed user scenarios and explored several design ideas at different fidelity levels (wireframes, linked images-based prototypes, html-based prototypes). Thanks to the valuable information provided by the Localisation team, the interactive prototypes by Arun Ganesh, and the involvement of the community participating in the usability tests, we were able to find a design that was easy to learn and operate.

    The selector.

  The design for the selector combines several mechanisms to reduce the complexity of the language list:

Anticipate the user needs. A short list of languages is provided based on the browser settings, the geographic area of the user, and previous selections. If the language is not in the list, the user can access a larger list of languages (shown above) with different aids.

Flexible search. The user can type the language he is looking for to reduce the list of possible languages. Search will be flexible so the user can type the language name in a different language.

A map for filtering. A world map divided in four regions is used to filter the language list (with the user region selected by default). The world has been divided in few regions since defining more regions requires more precision in the selection and geography knowledge. A "worldwide" region has been added to include constructed languages and world languages.

A list of languages arranged by script type and region. The list of languages has been divided in different geographic zones and languages are arranged by script type (to make it easy for the user to identify zones of interest in the big list). Languages are arranged in 10-item blocks, to properly indicate the intended way of scanning the list. The list also highlights the languages which are likely the user is interested in.

Usability tests with prototypes confirmed that the different aids proposed were useful to locate a given language. Most users used search as their first option and made several attempts with search before trying the map or scrolling the list. More information about the designs and the test results is provided at the project page.

    Further work.

Although selecting a language from a list of 400 possibilities is itself a challenge, one of the most debated aspects has been regarding the integration with the current (and future) Wikimedia projects and more discussion is expected in the very near future.

I never thought of it before, but Karl Gilis made an excellent point about flags in language selection screens on his website (dutch). Flags are linked to countries, not to languages. One country can have more than one language. So, linking flags to a language doesn't make sense!