Get the latest from Weapons and Warfare right to your inbox.
In March the Agamemnon went down the Medway to Sheerness: Hood hinted that Nelson should prepare for a cruise and then join the fleet at Gibraltar. The combination of getting to sea and a letter from Hood put Nelson in fine spirits; he told Fanny that āI was never in better healthā. While the ship completed for sea Nelsonās personal…
Background The Irish Rising took place on the 24th of May 1798. It was only partial; confined chiefly to the counties of Kildare, Wicklow and Wexford; and there were some slight attempts in Carlow, Queenās Co., Meath and county Dublin. But Dublin city did not rise, for it had been…
Storming of Badajoz by Chris Collingwood. The last siege of Badajoz conducted by Wellingtonās army was typified by a failed main assault on the breech and a successful secondary assault on the castle. The Allies had failed to take Badajoz before, and the lack of an adequate British siege train,…
HMS Mersey, one of the monitors used for bombarding German positions on the Belgian coast in 1914. English Channel Though little noticed, the naval campaign in the English Channel was of vital importance in permitting the maintenance of the British Army in France. Like the North Sea campaign, it consisted…
A Humber Armoured Car Mk II, one of the few armoured vehicles to use the 15-mm (0.59-in) Besa heavy machine-gun as its main armament. Originally known as a wheeled tank, these vehicles gave sterling service in many theatres through the war. The Humber armoured cars were numerically the most important…
Supermarine Spitfire PR.XI ERWIN ROMMEL (1891-1944). German Field Marshal. Rommel, commander of the German Afrika Korps, inspecting the German position at the Atlantic Wall near Fecamp, Normandy, France. Photographed 17 January 1944. The Mark XI PR Spitfire relied on speed and agility for protection. Travelling at 400 miles per hour,…
Map of the assault on the Merville Gun Battery 6 June 1944 The lengths the Germans were going to in order to protect the battery, combined with the information provided by the Resistance, was enough to convince Morgan that the guns at the battery must be of 150mm calibre. When…
British coastal assault on St Cast in Brittany in September 1758. A German map, published…
The Hanoverian contingent in Wellingtonās army was integrated fully into the British divisional structure; it…
European matchlock musketeers of the Elizabethan period. By the early 1570s the Puritans had grown…
The Gordon Highlanders storming Dargai Heights during the Tirah campaign in 1897. It was here…
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