Get the latest from Weapons and Warfare right to your inbox.
Top left: Polish FT tanks of the Polish 1st Tank Regiment during the Battle of Dyneburg, January 1920. Below left: Polish and Ukrainian troops in Kiev, Kiev Offensive (1920) Khreshchatyk, 7 may 1920. Top right: Polish Schwarzlose M.07/12 MG nest during the Battle of Radzymin,August 1920. Middle: Polish defences with a machine gun position near MiĹ‚osna, in the village of…
Painting of Polish soldiers by J. Ch. Mock, “Kampament wojsk polskich i saskich pod Wilanowem w 1732 r.”, Muzeum Wojska Polskiego w Warszawie. Europe after the 1738 Treaty of Vienna, which concluded the war. PRINCIPAL COMBATANTS: Stanislaus I Leszczynski (backed by France, Spain, and Sardinia) vs. Augustus III (backed by…
In the war that began on 1 September 1939 air power played a crucial role from the start. The Germans considered a massive opening attack on Warsaw, but bad weather forced them to attack alternative targets. The Luftwaffe’s most important contribution in the Polish campaign lay in quickly gaining air…
In spring 1787 Catherine the Great of Russia set off on an imperial progress through her southern dominions. As she drifted down the Dnieper greeted by crowds of subjects lined up along the banks by her minister Prince Potemkin, King StanisĹ‚aw Augustus left Warsaw to greet her on the Polish…
P11 VERSUS THE LUFTWAFFE During the summer of 1939 the Polish air force found itself dealing with repeated violations of its airspace by photoreconnaissance Do17s of the Luftwaffe, and the experience of the P11c, the principal Polish fighter, was not encouraging. Unable to reach either the speeds or the altitudes…
Friedrich Augustus. Elector of Saxony (1694-1733); king of Poland (1697-1704; 1709-1733). The shattered sanctuary 1706 On 8 January 1706 a Swedish army of between 18,000 and 20,000 men left Blonie. `My soldiers have enjoyed their winter quarters in summer’, declared their enigmatic King, so it was `only right that they…
Prince Jozef Poniatowski was a nephew of the last king of Poland-Lithuania. Born into an affluent family, he was raised to be a soldier. He spent a large part of his life fighting for Poland: first against the Russians in the war of 1792-1794, then as one of Napoleon’s generals,…
Polish army throughout the 18th century, by Karol Linder. Sweden had been wiped out as…
Augustus II of Poland. 17th Centruy Polish Dragoons By the last quarter of the seventeenth…
Soldiers of the SS-Heimwehr Danzig round up “undesirables” in the free city of Danzig. The…
After the First World War, Poland was revived as an independent state by grouping together…
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