Fact-checked by Grok 2 weeks ago

VisualEditor

VisualEditor is a extension that provides a WYSIWYG (what you see is what you get) rich-text editor for creating and modifying wiki pages, allowing users to work directly with formatted content rather than underlying wikitext markup. Developed by the Wikimedia Foundation's Editing team, it leverages a to enable browser-based editing and integrates with the Parsoid parser to convert between visual content and wikitext. First released as an opt-in alpha in mid-2012 on MediaWiki.org, VisualEditor became available on the in December 2012 and expanded to nearly all languages by June 2013. Key features include support for visual diffs to highlight changes, integration with Citoid for automatic generation, and TemplateData for editing complex templates without code. The extension, licensed under the , has been stable since its inclusion in MediaWiki 1.35 in 2020 and requires no database schema changes, making it compatible with various skins such as and Minerva Neue. By July 2015, it was set as the default editor for over 75% of Wikipedias, and as of 2025, it remains the primary editing interface on most Wikimedia projects, with continued enhancements to features like tools. Ongoing development addresses issues like loading speed and incomplete feature parity with wikitext editing, with community contributions encouraged via platforms like Gerrit.

Development

Origins and Goals

The development of VisualEditor was primarily motivated by a significant decline in the number of active editors on , which peaked at approximately 50,000 in 2007 before dropping to around 37,000 by 2011, with active editors defined as those making five or more edits per month. Wikimedia research identified the complexity of wiki markup as a substantial barrier preventing new and casual users from contributing effectively. The Wikimedia Foundation's 2011 Editor Trends Study highlighted these issues, emphasizing the need for tools that could lower entry barriers and boost retention among non-technical participants. In response, the initiated VisualEditor's development in May 2011 as part of a $1 million project focused on enhancing tools and features to revitalize editor participation. The project's core goals included simplifying the process for non-technical users, minimizing dependence on esoteric wiki markup syntax, and ultimately increasing editor retention and overall contributions to Wikimedia projects. By providing a what-you-see-is-what-you-get () interface, VisualEditor aimed to make article creation and modification as intuitive as using modern word processors, thereby attracting a broader demographic of contributors. Key stakeholders in the early phases were the Wikimedia Foundation, which led the effort, and initial collaborators including Fandom, Inc. (formerly Wikia), whose engineering team contributed to prototyping and design. Early milestones encompassed planning for an alpha version between 2011 and 2012, with the 2011-2012 annual plan setting targets for initial opt-in production usage by December 2011 and broader testing on small wikis thereafter. These steps laid the groundwork for integrating tools like the Parsoid parser to handle MediaWiki's complex structure.

Technical Foundations

VisualEditor is built primarily as a that operates in web browsers, with supporting server-side components implemented in for real-time processing and for integration with MediaWiki's ecosystem. This architecture enables client-side rendering and manipulation of content while leveraging server resources for parsing and serialization tasks. The entire extension is released under the , promoting open-source reuse and modification. At its core, VisualEditor relies on the Parsoid parser to facilitate bidirectional conversion between MediaWiki's wikitext markup and an enriched with annotations. Parsoid, originally developed in in 2012 specifically to support VisualEditor, generates a structured representation from wikitext that preserves semantic information, such as boundaries and relationships, allowing for intuitive visual manipulation without losing underlying data. This conversion process is essential for enabling editing, as it transforms the abstract wikitext into a concrete DOM that browsers can handle natively. A key engineering challenge in VisualEditor's development was achieving reliable round-trip editing—ensuring that modifications made in the visual interface could be serialized back to equivalent wikitext without information loss or introducing "dirty diffs" that complicate . MediaWiki's original PHP-based parser was not designed for reversibility, often flattening complex structures like templates into irreversible , which hindered seamless editing workflows. To address this, Parsoid introduced innovations such as a WHATWG-compliant DOM processing pipeline that retains during , enabling accurate reconstruction of wikitext. This required extensive automated testing on large corpora, including over 100,000 articles, to identify and resolve fidelity issues. In 2019, Parsoid was ported to to align with MediaWiki's runtime environment, improving performance by approximately double while maintaining compatibility. VisualEditor has been bundled as a standard component of since version 1.35, released in September 2020, streamlining its deployment across Wikimedia projects and third-party installations by integrating Parsoid directly into the core distribution. Beyond its role as a extension, the can operate standalone, independent of , Parsoid, or , allowing it to be embedded in other HTML5-based applications for general rich-text editing. This modularity supports broader adoption in non-wiki contexts while preserving the core visual editing capabilities. As of 2025, VisualEditor remains actively maintained, with recent enhancements to integrations like Edit Check for improved editing validation introduced in 2023 and 2024.

Features and Capabilities

Core Editing Tools

VisualEditor offers a (What You See Is What You Get) interface that enables users to edit wiki pages directly in a rich-text environment, manipulating text and applying formats without needing to interact with underlying wikitext markup. This approach provides an intuitive experience similar to word processors, where changes are visible immediately as the editor renders in + , generated through Parsoid for seamless with . The primary serves as the central for actions, featuring accessible icons and menus for operations. Users can bold (Ctrl+ on PC or ⌘ Cmd+ on ) and italics (Ctrl+I or ⌘ Cmd+I) formatting with simple shortcuts, while links are inserted via a dedicated chain icon or Ctrl+K (⌘ Cmd+K), allowing selection of internal or external targets. For structure, the includes a pull-down to set paragraph styles such as headings or sub-headings, and buttons to create bulleted or numbered lists, with indentation adjusted using or Shift+ keys. can be inserted as a default 4x4 grid via the , followed by options in a contextual for adding or removing rows and columns. Basic templates are supported through an Insert icon, enabling users to add and configure simple parameterized elements without markup knowledge. Media insertion is streamlined via the "Images and media" tool in the Insert menu, where users can upload files directly or select from existing ones, adding captions and alignment as needed. Throughout the editing process, VisualEditor delivers real-time previews of modifications, ensuring that the visual layout matches the final published output in +. Undo and redo functionalities are readily available via toolbar icons, supporting iterative refinements. Since 2023, VisualEditor includes the Edit Check tool, which scans edits in real-time and suggests improvements such as checking pasted content for formatting issues, verifying link validity, and ensuring image licensing before publishing. This feature helps maintain article quality and is accessible via notifications in the editor interface. The editor is designed for cross-platform compatibility, functioning reliably in modern web browsers on desktops across operating systems, making it accessible to a broad range of users without specialized software.

Integrations and Extensions

VisualEditor integrates with Citoid, a that automates generation by translating URLs, DOIs, ISBNs, and other identifiers into formatted references using translators. This feature, accessible via the tool in the editor's , populates templates with such as author names, publication dates, and titles, reducing manual entry errors and streamlining the process for editors. Citoid's integration has been available in VisualEditor since 2015, enhancing its utility for academic and reference-heavy wikis. Support for templates in VisualEditor relies on TemplateData, a structured documentation system that enables a user-friendly interface for inserting and editing wiki-specific templates without raw wikitext knowledge. Editors can access parameters through dialog boxes that display descriptions and previews, allowing modifications to complex elements like infoboxes or navigation boxes directly in the visual mode. Additionally, support extends VisualEditor's customization via MediaWiki's Gadgets extension, permitting wiki administrators to add JavaScript-based tools, such as custom buttons for wrapping text in templates or automating repetitive edits. These gadgets integrate seamlessly with the core toolbar, providing wiki-tailored enhancements without altering the base editor. VisualEditor maintains compatibility with other extensions, exemplified by its integration with SyntaxHighlight, which enables visual editing of code blocks through a dedicated . When SyntaxHighlight is installed, users can edit <syntaxhighlight> tags via a in VisualEditor, supporting selection, line numbering, and highlighting previews to facilitate accurate code insertion and modification. This compatibility ensures that technical content, such as programming snippets, remains editable in a environment without switching to source mode. In collaboration with (formerly Wikia), VisualEditor has been adapted for enhanced media handling on community-driven wikis, incorporating features like streamlined image uploads, creation, and integration with Fandom's Portable Infoboxes. This partnership, initiated around 2013, allows editors to search and insert media directly via toolbar icons, add captions and positioning options in real-time, and perform mass uploads for efficient content enrichment. Fandom's implementation extends VisualEditor's core media tools to better support fan wikis' visual demands, such as embedding videos and organizing image .

Rollout and Adoption

Initial Deployment

The initial deployment of VisualEditor followed a cautious, phased rollout strategy to test and refine the tool while minimizing disruptions to established editing workflows on Wikimedia projects. Development began with an alpha release in mid-2012 on MediaWiki.org, a small technical wiki, allowing early opt-in testing in a controlled environment. This was expanded in December 2012 to the , where an opt-in alpha version was made available to registered users for feedback on functionality and issues. The approach prioritized gathering input from experienced editors to address core goals of simplifying page editing without requiring markup knowledge. By April 2013, the alpha phase extended to 14 additional Wikipedias, including the , where it remained strictly opt-in for logged-in users to enable localized testing and translations. In July 2013, the rollout advanced to beta status on the , becoming the default (opt-out) editor for all registered users and soon extended to anonymous editors by September 2013. This broader availability aimed to increase but encountered early implementation challenges, such as performance issues and incomplete feature support, prompting community feedback on stability. Persistent bugs and user complaints led to a temporary shift back to opt-in status across the in September 2013, reflecting the challenges of scaling a complex rich-text editor to a high-traffic site. To balance innovation with reliability, further adjustments occurred in October 2015, when VisualEditor was partially reverted to default only for new registered users, while experienced editors retained options. This iterative strategy highlighted the tension between rapid deployment and ensuring robust performance during early adoption.

Current Usage and Statistics

As of 2020, VisualEditor has been enabled by default on mediawiki.org, most language versions of , and . It remains available as an opt-in Beta Feature for logged-in users on other Wikimedia projects, and is primarily enabled for pages in content namespaces, such as articles, though it can be configured for other namespaces including user pages. As of mid-2023, editors on the alone had made more than 25 million edits using VisualEditor. From 2023 to 2025, VisualEditor has seen continued maintenance and development, as documented in biannual multilingual that cover updates, bug fixes, and community integration. archives reflect active user reports and discussions on usability issues and enhancements through 2024, with ongoing monitoring via dedicated channels. On the , VisualEditor is enabled by default for logged-in users, including new registered editors, on desktop interfaces.

Reception and Impact

Community Responses

The rollout of VisualEditor in 2013 encountered significant opposition from the due to persistent bugs that hindered editing reliability, prompting opt-out petitions and widespread user frustration. In particular, the community conducted a vote in July 2013, with hundreds of editors overwhelmingly rejecting VisualEditor as the default editor and advocating for an opt-in model to preserve user choice. Early support for VisualEditor emerged prior to its full deployment, with The Economist praising the 2011 prototype as Wikipedia's most significant change, emphasizing its potential to lower barriers for new contributors through intuitive visual editing. Similarly, Softpedia described the tool's initial release as the best update in years, highlighting its transformative impact on collaborative editing while encouraging community input for refinements. Community discussions on VisualEditor's usability persist into 2024, as evidenced by feedback archives where beginners value its straightforward for basic tasks like adding categories and previews, though some report navigation challenges such as difficulty returning from preview mode without losing work. Experienced power users, however, often criticize limitations in handling complex elements like infoboxes and references, which can lead to formatting errors or duplications, leading many to prefer the source editor for precise control.

Research and Evaluations

A 2015 study conducted by the analyzed the impact of enabling VisualEditor by default for newly registered editors across , Czech Wikipedia, and . The experiment found no significant increase in productivity, with productive edits per user remaining comparable between the VisualEditor group (1778 edits) and the control group using the traditional wikitext editor (1772 edits). Additionally, short-term survival rates for new editors showed no meaningful difference, at 0.030 for the VisualEditor group versus 0.029 for the control. The same study revealed drawbacks in editing efficiency and completion. Newcomers using VisualEditor spent approximately 18 seconds longer on edits before attempting to , as measured by the time from initiating an edit to the save (t = -4.9083, p < 0.001). They were also significantly less likely to complete and edits, with attempt rates per session at 0.629 for VisualEditor users compared to 0.685 for controls (χ² = 31.1, p < 0.001), and success rates at 0.577 versus 0.637 (χ² = 32.9, p < 0.001). These findings highlighted early challenges in , partly influenced by prior community opposition that shaped the study's focus on newcomer retention. Subsequent evaluations addressed mobile-specific enhancements. A 2019 Wikimania presentation outlined improvements to the VisualEditor, including simplified workflows that increased edit completion rates by 78%, reduced revert rates by 17%, and made editing 40% faster on devices like the . These updates introduced a unified for all tools, an Advanced Mode mimicking functionality, and section editing optimizations that boosted completion by 3% in A/B tests, aiming to better support novice contributors. A 2018 report on mobile VisualEditor usage provided further insights into edit completion dynamics, using data from May 2018 across wikis. It reported completion rates of 15.8% for mobile VisualEditor sessions versus 2.6% for mobile wikitext, with anonymous IP editors achieving 11.4% completion using VisualEditor compared to 1.5% with wikitext. The report discussed experimental opt-in features, such as for logged-out users since , and proposed UX refinements to elevate completion rates toward desktop levels (24.6% for wikitext). These opt-ins were tested to gauge adoption without default enforcement. In 2025, insights into editing revealed persistent challenges, including an 8.44% reversion rate for IP editors using VisualEditor on (compared to 0.57% on ) and a ~95% drop-off rate among IP users who open but do not complete edits. The Product and Technology Advisory Council recommended further enhancements to support contributors. Overall, on VisualEditor has yielded mixed results regarding editor retention, with early studies showing no gains in or and higher abandonment rates among novices, yet later mobile-focused evaluations demonstrating positive effects on and completion for inexperienced users through targeted improvements.

Technical Details

Architecture and Components

VisualEditor operates as a client-server system, with the core editing functionality divided between browser-based components and server-side processing integrated into . The client-side architecture relies on a modular that runs directly in web browsers, enabling real-time manipulation of document content through the browser's (DOM). This library includes key modules such as the linear (ve.dm) for representing page structure as a sequence of nodes optimized for transactional edits, the content editable surface (ve.ce) that leverages HTML5's ContentEditable API to render and track changes in the DOM, and user interface elements (ve.ui) for handling interactions like toolbars. These components ensure reversible operations and support for collaborative editing by processing user inputs as transactions that can be serialized and transmitted efficiently. On the server side, VisualEditor functions as a PHP-based extension, installed via standard configuration in LocalSettings.php, which handles integration with the wiki's backend services including user permissions and page storage. It depends on Parsoid, a dedicated parsing service that can be implemented either as a application for high-performance processing or as a PHP port integrated directly into (available since version 1.35). Parsoid serves as the bridge for content transformation, exposing HTTP APIs for loading and saving documents while maintaining compatibility with 's database and caching layers. This setup allows VisualEditor to interface seamlessly with the existing ecosystem without requiring modifications to core parsing logic. The system's round-trip editing pipeline ensures fidelity between the stored Wikitext format and the visual editing experience, following a structured : Wikitext is first parsed by Parsoid into annotated enriched with data attributes to preserve semantic information, which is then loaded into the client-side editor for manipulation. Edits performed in the generate transactions that update the linear data model, and upon saving, the modified is serialized and routed back through Parsoid to regenerate clean Wikitext, minimizing diffs and avoiding loss of structure. This pipeline supports configurable lossy switching between visual and source modes, prioritizing round-trip accuracy for supported elements while isolating complex syntax for fallback editing. VisualEditor's architecture emphasizes scalability for high-traffic environments like large wikis, incorporating to gracefully degrade on unsupported browsers or devices, and leveraging 's caching mechanisms to optimize Parsoid requests. It achieves cross-platform compatibility across modern browsers (IE9 and later) and various MediaWiki skins, such as and Minerva Neue, by adhering to standard structures and avoiding reliance on proprietary features. Experimental extensions, like volunteer-developed collaboration servers, further enhance its capacity for real-time multi-user editing in production settings.

Mobile and Accessibility Support

The mobile version of VisualEditor has been available as an opt-in feature since 2014, following an initial release for tablet users in 2013 and expansion to logged-out users in April 2015. In November 2019, the Wikimedia Editing team initiated an test to evaluate VisualEditor as the default mobile editor on select s, which ran until September 2022 and showed no significant differences in user retention compared to the source editor. By April 2024, VisualEditor was deployed as the default editor for new accounts and logged-out users on , with users able to switch to wikitext mode via a dropdown menu. A July 2023 report on mobile VisualEditor usage, based on data from May 2018, indicated improved edit completion rates of 15.8% for VisualEditor sessions compared to 2.6% for wikitext editing on mobile, though overall session volumes remained low due to the opt-in nature. The report noted that VisualEditor remained in an experimental phase on certain projects during this period, with ongoing to assess broader adoption. Accessibility features in VisualEditor align with Wikimedia's broader efforts to meet WCAG 2.1 Level AA guidelines, including specific enhancements for compatibility. support has been partially implemented and is under further development for key interface elements, such as the editor sidebar and , to ensure announcements of changes and focus states for users relying on assistive technologies like NVDA or . Additionally, VisualEditor includes a high-contrast mode, enabled via or , which adjusts interface colors for better visibility, as demonstrated in early implementations dating back to 2013. Performance challenges on mobile, including scrolling issues in Mobile and limited screen space, prompted fixes in 2019, such as loading overlays (deployed March 2019) and section-specific (April 2019) to reduce during transitions from reading to . Integration with the mobile has been supported through of use cases since Q1 2018, allowing the to leverage web-based VisualEditor functionality via embedded views, though primary remains tied to source mode in some contexts. As of November 2025, VisualEditor on mobile undergoes ongoing maintenance as part of MediaWiki's quarterly security and stability releases, with no major overhauls reported in recent tech news; focus remains on iterative improvements like adaptations for cursor position to enhance on small screens and bug fixes, such as resolving persistent highlighting in the find-and-replace feature.

References

  1. [1]
    Extension:VisualEditor - MediaWiki
    Aug 29, 2025 · The VisualEditor extension allows for editing pages as rich content. It is based around a JavaScript library, also called VisualEditor.Installation · Download · Setting up VisualEditor · Complete list of configuration...
  2. [2]
    VisualEditor/Portal - MediaWiki
    Sep 22, 2024 · Welcome to the portal for VisualEditor. VisualEditor (VE) is a new way of editing Wikipedia that is being developed by the Wikimedia ...
  3. [3]
    Editor-to-Reader Ratios on Wikipedia – copyrighteous
    Feb 6, 2011 · The number of active editors on Wikipedia (usually defined as people who have edited at least 5 times in a given month) peaked in 2007 and has been mostly ...<|separator|>
  4. [4]
    [PDF] Wikipedia Editors Study: Results From The Editor Survey, April 2011
    Looking closely at English Wikipedia, the study found significant decline in editors with more than 10 edits. It has been hypothesized that edit wars, reverts ...
  5. [5]
    Editor Survey 2011/Executive Summary - Meta-Wiki - Wikimedia
    Oct 4, 2016 · 1. Editor Decline & Community: The Wikimedia movement has made increasing its editor base to 200,000 by 2015 a major priority. · 2. Positive ...
  6. [6]
    Editor Trends Study - Strategic Planning - Wikimedia
    This Study aims at understanding Wikimedia Editors' Trends. The main challenge is: many users are joining us, but “Active Editors” aren't growing.Missing: 2006 | Show results with:2006
  7. [7]
    VisualEditor - Wikipedia
    One of VisualEditor's goals is to empower knowledgeable and good-faith ... calling it "the most significant change in Wikipedia's short history" in 2011.Missing: origins | Show results with:origins
  8. [8]
    Help test the first visual editor developer prototype - Wikimedia Diff
    Dec 13, 2011 · The development of a Visual Editor is one of the Foundation's top priorities for the upcoming year, as laid out by the 2011-2012 Annual Plan ...Missing: origins | Show results with:origins
  9. [9]
    Inventing as we go: building a visual editor for MediaWiki
    Dec 7, 2012 · The 2011/2012 targets were, “Develop Visual Editor. First opt-in user-facing production usage by December 2011, and first small wiki default ...Missing: origins goals
  10. [10]
    VisualEditor - MediaWiki
    VisualEditor is a reliable rich-text editor for HTML documents. It was created by the Editing team for MediaWiki's HTML+RDFa document format.Extension:VisualEditor · VisualEditor:Test · VisualEditor/Design
  11. [11]
    wikimedia/mediawiki-extensions-VisualEditor: This is a ... - GitHub
    VisualEditor provides a visual editor for wiki pages. It is written in JavaScript and runs in a web browser. It uses the Parsoid parser to convert wikitext ...<|control11|><|separator|>
  12. [12]
    Parsoid - MediaWiki
    ### Summary of Parsoid from https://www.mediawiki.org/wiki/Parsoid
  13. [13]
    Parsoid in PHP, or there and back again - WM:TECHBLOG
    Feb 12, 2020 · The VisualEditor project required new types of information to be extracted from wikitext, and it required (for the first time) *reversible* ...<|control11|><|separator|>
  14. [14]
    Parsoid/About - MediaWiki
    Aug 26, 2025 · We use automated round-trip testing on 100,000 Wikipedia articles, unit test cases and statistics on Wikipedia dumps to help us identify the ...
  15. [15]
    wikimedia/VisualEditor: Standalone rich HTML5 editor ... - GitHub
    VisualEditor provides a rich-text editor for HTML documents. It is written in JavaScript and runs in a web browser. API documentation · Code coverage.<|control11|><|separator|>
  16. [16]
    Help:VisualEditor/User guide - MediaWiki
    Oct 11, 2025 · Help:VisualEditor/User guide · Opening the visual editor. To edit a page using the visual editor, press on the Edit tab at the top of the page.
  17. [17]
    Citoid/Enabling Citoid on your wiki - MediaWiki
    Jun 12, 2025 · It is currently available as a VisualEditor feature, and in the 2017 wikitext editor . Citoid uses Zotero translators to convert a page link ...Missing: integration | Show results with:integration
  18. [18]
    VisualEditor/Portal/Gadget - MediaWiki
    Jul 20, 2015 · You need to be an administrator on your wiki to set up the gadget: On your wiki, create the page MediaWiki:Gadget-HideVisualEditor and add a ...
  19. [19]
    Extension:Gadgets - MediaWiki
    Oct 31, 2025 · The Gadgets extension allows users to select JavaScript or CSS-based "gadgets" provided by other wiki users.
  20. [20]
    Extension:SyntaxHighlight - MediaWiki
    Oct 9, 2025 · The SyntaxHighlight extension, formerly known as SyntaxHighlight_GeSHi, provides rich formatting of source code using the <syntaxhighlight> tag.
  21. [21]
    VisualEditor/Tag extensions - MediaWiki
    Sep 20, 2021 · This tutorial explains how to integrate tag extensions with the visual editor. While geared toward a specific kind of extension, ...
  22. [22]
    User blog:BertH/The Road to VisualEditor - Community Central
    Wikia engineers presenting about VisualEditor at Wikimania 2013 in Hong Kong. Wikia engineers Christian and Inez have been part of a long-term collaboration ...
  23. [23]
    Help:VisualEditor | Community Central | Fandom
    The VisualEditor feature allows users to edit an article quickly and easily. The editing interface will always reflect how the article will look when published.
  24. [24]
    Help:Editing - Community Central | Fandom
    The VisualEditor. Editing on Fandom is as simple as clicking the "Edit" button on a page. Doing so will take you to an edit page. This is where you can make ...Missing: collaboration | Show results with:collaboration
  25. [25]
    Try out the alpha version of the VisualEditor - Wikimedia Diff
    Dec 12, 2012 · Yesterday we launched an alpha, opt-in version of the VisualEditor to the English Wikipedia. This will let editors create and modify real ...Missing: 2011-2012 | Show results with:2011-2012
  26. [26]
    The alpha version of the VisualEditor is now in 15 languages
    Apr 25, 2013 · Today the Wikimedia Foundation launched an alpha, opt-in version of the VisualEditor to fourteen Wikipedias, which follows our release to ...
  27. [27]
    Wikipedians: Meet VisualEditor and help with the rollout
    Jul 1, 2013 · […] Wikimedia Foundation has finally enabled its long-awaited VisualEditor for all logged-in users on the English-language version of Wikipedia.
  28. [28]
    VisualEditor/Newsletter - Meta-Wiki
    Aug 21, 2025 · The VisualEditor newsletter is a multilingual newsletter sent twice a year, written by Whatamidoing, and can be delivered to your talk page. ...Missing: 2023 2024 maintenance
  29. [29]
    VisualEditor/Feedback/Archive/2024 - MediaWiki
    Oct 22, 2024 · This page is an archive. Do not add new topics here. Please ask new questions at VisualEditor/Feedback instead.
  30. [30]
    VisualEditor/Rollouts - MediaWiki
    Jul 17, 2025 · Every public Wikimedia wiki has the visual editor available for opt-in testing and use by logged-in users ("Beta Feature"). Though the ...
  31. [31]
    Wikipedians say no to Jimmy's 'buggy' WYSIWYG editor - The Register
    Aug 1, 2013 · Last weekend hundreds of German Wikipedia editors rebelled. VE has been made the default editor, which requires users to opt ... voting ...
  32. [32]
    Seeing things - The Economist
    Dec 13, 2011 · Wikipedia unveiled its new visual editing tools which make contributing to the online encyclopedia easier than ever. Share. Dec 13th 2011 |3 ...
  33. [33]
    Research:VisualEditor's effect on newly registered editors/May 2015 study - Meta-Wiki
    ### Summary of 2015 Study Findings on VisualEditor’s Effect on New Editors
  34. [34]
    [PDF] The future of mobile editing - Wikimedia Commons
    1) Make common editing workflows simpler on mobile. 2) Expand the functionality to more closely resemble the desktop version of the site. Page 11. Why visual ...
  35. [35]
    VisualEditor on mobile report - MediaWiki
    Jul 14, 2023 · This page is a report on mobile editing using the visual editor that is being produced as part of the Editing team's work from the 2018-2019 ...
  36. [36]
    VisualEditor/Design/Software overview - MediaWiki
    Jun 18, 2024 · MediaWiki allows users to quickly edit web pages. Editing is done by modifying an article's source code directly within the browser.
  37. [37]
    VisualEditor on mobile/VE mobile default - MediaWiki
    This page talks about the Editing Team's work experimenting with VisualEditor being the default mobile editor on a select number of wikis. VE as mobile default.Missing: millionth | Show results with:millionth
  38. [38]
    Accessibility statement - Wikimedia Foundation
    The Wikimedia Foundation website is partially conformant with WCAG 2.1 level AA, meaning some content does not fully conform to accessibility standards.Missing: VisualEditor features screen reader
  39. [39]
    T289653 Screenreader support for the new VisualEditor template ...
    Screenreader support for the new VisualEditor template editor sidebar ... We would like to meet Level A as defined in WCAG ... accessible to screen readers as ...
  40. [40]
    File:VE High Contrast.jpg - Wikimedia Commons
    Aug 9, 2013 · English: A partial screenshot of VisualEditor with High Contrast mode enabled. Created with Firefox on Windows Vista. Date, 9 August 2013, 12:09 ...
  41. [41]
    VisualEditor on mobile - MediaWiki
    From mid-2018 to the end of 2019, the Editing team improved the editing experience for contributors using the VisualEditor on the mobile browser.
  42. [42]
    Tech News 2025, week 45 - Wikimedia Diff
    Nov 3, 2025 · Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Missing: ongoing maintenance
  43. [43]
    Security and maintenance release: 1.39.15 / 1.43.5 / 1.44.2 - Lists
    Oct 3, 2025 · MediaWiki 1.39 (the old LTS before 1.43) becomes EOL in December 2025. It is strongly recommended to upgrade to 1.43 (the next LTS after 1.39), ...