Get the latest from Weapons and Warfare right to your inbox.
Last Defence before Berlin By early April the situation for Army Group North, now renamed Army of East Prussia, deteriorated further. Its forces were now hemmed in around the Bay of Danzig from Samland and Konigsberg to the mouth of the Vistula. The remnants of two corps were given the task of holding positions north of Gotenhafen on the Hel…
42nd Highlanders the Black Watch at the Battle of Corunna on 16th January 1809 in the Peninsular War: picture by Harry Payne The positions of the armies at Corunna. The British are in red and the French in blue. Despite their predicament, the British had two factors in their favour.…
Trant’s Raid was the Portuguese recapture of the city of Coimbra from the French on 7 October 1810 during the Peninsular War. The assault was undertaken by a Portuguese militia led by Colonel Nicholas Trant, an Irish officer in the British Army. This view looks north-west towards the plain beyond…
27–28 July 1809 Wellesley’s chief problem was a shortage of supplies, for he insisted that his men should not plunder the countryside so as not to antagonize the local population. He continued his march and on 16 July moved forward from Plasencia, reaching Talavera six days later. It was the…
A European coalition united by the cause of Greek liberty defeats the Turkish navy to create an independent Greek state and further weaken the grip of the Ottoman Empire in Europe Early on a bright Saturday morning in October 1827, a combined fleet of British, French and Russian warships was…
In mid-summer, the expedition reached Metemma, where they found the remains of positions dug by Wolseley’s troops fourteen years earlier, along with the graves of those who had died at Abu Klea and Abu Kru. Supplies were again built up, and the troops, Egyptian and British alike, were spoiling for…
30 June 1643 The Earl of Newcastle’s reaction to the storming of Wakefield must have been of considerable concern to the Fairfaxes. It must have come as a great surprise when Newcastle tamely withdrew his army to York. The Earl’s main task was still the protection of the Queen and…
The Gordon Highlanders storming Dargai Heights during the Tirah campaign in 1897. It was here…
In early March 1945 the American troops entered an almost deserted area that had been…
As Gruppe Edelsheim reaches the southern railway station around 1600 hours they pass close to…
One of the lessons learned from the Zulu War by Britain’s enemies was that 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