WikiFusion

What's new in 1.5

WikiFusion is a fast lookup add-on for NVDA that combines the best parts of wikiSeek (Wikipedia) and dictionarySeek (Wiktionary) into one workflow. If you used either of those add-ons before, WikiFusion should feel instantly familiar.

Quick start

  1. Press NVDA+Alt+I to open WikiFusion.
  2. Type a word or phrase, then press Enter to search.
  3. Use the results tree to choose an item, then press Enter to load it.

Smart routing

The results tree

Results are shown in a tree with Wikipedia first, Wiktionary second, and any optional sources after them:

Each search automatically expands the sections so you don’t miss results. You can collapse a section to reduce scrolling.

Tree navigation

Keyboard shortcuts

Media list (pronunciation guides, audio examples)

When a page includes audio files (for example, Wiktionary pronunciations), they appear in a Media list to the right of the article view.

The media controls stay hidden until the currently loaded result actually has media. After you load a result with media, its tree item is also marked with [media].

WikiFusion plays media directly inside the add-on and will not open your external media player. Many Wikimedia pronunciation files are in formats such as OGG or OPUS. If the ffmpeg tool is available on your system PATH, WikiFusion will automatically use it to decode these formats so they can be played internally.

If ffmpeg is not available, WikiFusion will notify you and you can still download the file using Ctrl+Enter.

Copy behaviour (Ctrl+C)

WikiFusion copies different text depending on the source:

Why the difference? Wiktionary is often used to check spelling and meanings quickly, where pasting the URL is usually noise. Wikipedia links, on the other hand, are frequently shared.

Settings

Hotkey note (dictionarySeek)

WikiFusion uses the same default hotkey as dictionarySeek: NVDA+Alt+I.

If you still have dictionarySeek installed, the two add-ons will clash. You can either:

Why the letter “I”?

A bit of trivia: we kept I because it’s a natural fit for both “wiki” and “dictionary” workflows, and many users already had the muscle memory from dictionarySeek / wikiSeek.