Get the latest from Weapons and Warfare right to your inbox.
Battle of Hohenfriedberg – Attack of Prussian Infantry, 4 June 1745, by Carl Röchling. In contrast to the absolutism of the kingly state, the territorial state was a state of definite limits. We have seen this to be the case in the composition and maintenance of its armies. The governments of territorial states were limited in the revenue base they…
Cossacks burn Zorndorf On August 20, the king’s Prussians arrived at the gates of Frankfurt-on-Oder; Fermor was out by CĂĽstrin with his army. The bluecoats initially moved to Tschicherzig. Frederick reached it on August 16, but Dohna was still out of the vicinity busy in his dealings with the Russians.…
Hemmed in by the Meitzel River at its back, the Russian Army had no way to retreat if the battle went badly. Meanwhile, the Prussians mounted an attack on the Russian right. At about 0300 hours, the Prussians rose and pressed off moving westward—the cavalry closest to the enemy array,…
Clutching the colors of the 46th Infantry Regiment, Frederick rallies his men in a last-ditch stand on the Prussian left. Seydlitz’s cavalry would save the day. The Russian right was no longer capable of organized resistance, but an incredibly bloody and desperate struggle was kept up there until about 1300…
In the middle of January 1762, Prince Henry experienced a bout of illness, which caused him to enquire whether he could be replaced, at least temporarily, by another officer, preferably Seydlitz or General Forcade, but the king advised that his brother should be able to recover in time to assume…
The Prussians were after more than just a nuisance raid or two. Tearing up property, looting, raping citizens, might all help demoralize the civilian population in the affected areas all right, at least to an extent, but the destruction of the Austrian magazines in Northern Bohemia would compel the whitecoats…
The Prussians struck first instead. During the night of October 28–29, the bluecoats succinctly pushed off.24 Prince Henry himself was with Seydlitz. The enemy had been tipped off by a deserter, and, about 0100 hours, the Allies braced themselves for the coming blow. The plan was indeed bold, for Otto…
“Napoleon on the field of Eylau” by Antoine-Jean Gros The Battle of Eylau, 1807 –…
Cossacks burn Zorndorf On August 20, the king’s Prussians arrived at the gates of Frankfurt-on-Oder;…
Background Two conflicts formed the bookends, so to say, of the fourteenth century in Prussia.…
GERHARD von SCHARNHORST (1755-1813) Chief of the Prussian General Staff. Napoleon’s defeats were important, especially…
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
We noticed you're visiting from France. We've updated our prices to Euro for your shopping convenience. Use United States (US) dollar instead. Dismiss
Sign in to your account