Get the latest from Weapons and Warfare right to your inbox.
Major-General Wilhelm Sebastian von Belling’s campaign Pomerania in 1761 against the Swedes. At the Northern Front, the Campaign 1761 had been a more involved one than usual, for the most part. The Prussian posts at the start of the campaign were: at Anklam, stood Major Alexander Friedrich Knobelsdorf, with three companies; at Demmin, Lieutenant Colonel Golz was present with I.…
Lithuanian Grand-Duke JagieĹ‚Ĺ‚o’s brothers wanted heavier cannons to oppose the Teutonic Knights’ new weapons, but since gun carriages did not exist yet the heavy weapons could only be transported by water. Because the Teutonic Knights controlled the lower reaches of the Nemunas River, the only route from Poland to Lithuania…
Soviet cruiser Kirov protected by smoke during evacuation of Tallinn in August 1941. Bombs start to fall near ships moored in Tallinn for the evacuation. Reval Hafen 1.9.1941 (Tag der Eroberung) The Port of Tallinn on 1 September 1941 after having been seized by the Germans. Admiral Vladimir F. Tributs.…
Austro-Hungarian Emperor Karl’s promise of a two-pronged offensive flew in the face of warnings that Field Marshal Boroević (his new rank) had sent to the high command since the end of March. Karl and his chief of staff hoped to make Rome negotiate, and enlarge their spoils when Germany won…
The final and decisive Egyptian battle in Asia, a turning point equal to that of Megiddo under Thutmose III, took place in year five of Ramesses II at the city of Kadesh in central Syria. Yet this was the second northern campaign of Ramesses II because a preparatory advance had…
Cromwell after the Battle of Marston Moor By the time of John Pym’s death from disease in early December 1643 much of the architecture of Parliament’s eventual victory was in place, and he must take a large share of the credit for that. A military alliance with the Covenanters, in…
The well-equipped and highly motivated fanatics of the SS descended on Vevi with great speed. In countering them, Vasey’s problems at Vevi were prodigious: the Allied position lacked both depth and fixed defences, the weather was poor, and many of his units were tired from the route marches needed to…
Battle of Bagradas: Regulus’s defeat: Libya 255 BC. 255–245 BC Carthaginian Empire             Spartan mercenary…
Major-General Pajari, unaware that he is standing in a minefield on a makeshift speaker’s podium,…
The Battle of Hellsberg, 10 June 1807. This is Wilson’s battle map of 1810, clearly…
It is truly ironic that the most numerous units of foreign nationals raised by the…
Weapons and Warfare
We firmly believe that the internet should be available and accessible to anyone, and are committed to providing a website that is accessible to the widest possible audience, regardless of circumstance and ability.
To fulfill this, we aim to adhere as strictly as possible to the World Wide Web Consortium’s (W3C) Web Content Accessibility Guidelines 2.1 (WCAG 2.1) at the AA level. These guidelines explain how to make web content accessible to people with a wide array of disabilities. Complying with those guidelines helps us ensure that the website is accessible to all people: blind people, people with motor impairments, visual impairment, cognitive disabilities, and more.
This website utilizes various technologies that are meant to make it as accessible as possible at all times. We utilize an accessibility interface that allows persons with specific disabilities to adjust the website’s UI (user interface) and design it to their personal needs.
Additionally, the website utilizes an AI-based application that runs in the background and optimizes its accessibility level constantly. This application remediates the website’s HTML, adapts Its functionality and behavior for screen-readers used by the blind users, and for keyboard functions used by individuals with motor impairments.
If you’ve found a malfunction or have ideas for improvement, we’ll be happy to hear from you. You can reach out to the website’s operators by using the following email
Our website implements the ARIA attributes (Accessible Rich Internet Applications) technique, alongside various different behavioral changes, to ensure blind users visiting with screen-readers are able to read, comprehend, and enjoy the website’s functions. As soon as a user with a screen-reader enters your site, they immediately receive a prompt to enter the Screen-Reader Profile so they can browse and operate your site effectively. Here’s how our website covers some of the most important screen-reader requirements, alongside console screenshots of code examples:
Screen-reader optimization: we run a background process that learns the website’s components from top to bottom, to ensure ongoing compliance even when updating the website. In this process, we provide screen-readers with meaningful data using the ARIA set of attributes. For example, we provide accurate form labels; descriptions for actionable icons (social media icons, search icons, cart icons, etc.); validation guidance for form inputs; element roles such as buttons, menus, modal dialogues (popups), and others. Additionally, the background process scans all the website’s images and provides an accurate and meaningful image-object-recognition-based description as an ALT (alternate text) tag for images that are not described. It will also extract texts that are embedded within the image, using an OCR (optical character recognition) technology. To turn on screen-reader adjustments at any time, users need only to press the Alt+1 keyboard combination. Screen-reader users also get automatic announcements to turn the Screen-reader mode on as soon as they enter the website.
These adjustments are compatible with all popular screen readers, including JAWS and NVDA.
Keyboard navigation optimization: The background process also adjusts the website’s HTML, and adds various behaviors using JavaScript code to make the website operable by the keyboard. This includes the ability to navigate the website using the Tab and Shift+Tab keys, operate dropdowns with the arrow keys, close them with Esc, trigger buttons and links using the Enter key, navigate between radio and checkbox elements using the arrow keys, and fill them in with the Spacebar or Enter key.Additionally, keyboard users will find quick-navigation and content-skip menus, available at any time by clicking Alt+1, or as the first elements of the site while navigating with the keyboard. The background process also handles triggered popups by moving the keyboard focus towards them as soon as they appear, and not allow the focus drift outside it.
Users can also use shortcuts such as “M” (menus), “H” (headings), “F” (forms), “B” (buttons), and “G” (graphics) to jump to specific elements.
We aim to support the widest array of browsers and assistive technologies as possible, so our users can choose the best fitting tools for them, with as few limitations as possible. Therefore, we have worked very hard to be able to support all major systems that comprise over 95% of the user market share including Google Chrome, Mozilla Firefox, Apple Safari, Opera and Microsoft Edge, JAWS and NVDA (screen readers).
Despite our very best efforts to allow anybody to adjust the website to their needs. There may still be pages or sections that are not fully accessible, are in the process of becoming accessible, or are lacking an adequate technological solution to make them accessible. Still, we are continually improving our accessibility, adding, updating and improving its options and features, and developing and adopting new technologies. All this is meant to reach the optimal level of accessibility, following technological advancements. For any assistance, please reach out to
Sign in to your account