Get the latest from Weapons and Warfare right to your inbox.
Close Quarters, by Russell Smith (SPAD XIII & Fokker DVII) Air superiority enabled the French to resist the attacks of late May and early June, but the sheer effort of maintaining their position was taking an enormous toll of men and machines. ‘Most of our victories came during 1918 but we also suffered heavy losses,’ admitted Paul Waddington (SPA154). ‘We…
HMS Argus in November 1918, while preparing for the planned attack on the German High Sea Fleet in its harbours, with Sopwith T.1 torpedo-bombers on the flight deck. The ‘splinter’ paint scheme was designed to confuse enemy range-finders, but had the negative effect of making the ship more obvious. HMS…
The first A-37B at Edwards AFB in 1968. Of the 577 A-37Bs built, 134 were delivered to the USAF and served in frontline units until 1975. The final examples were retired from USAFRES and ANG service in 1992. The Dragonfly served the USAF until the early 1990s, including use in…
‘Caught on the Surface’. The sinking of U-461 by RAAF Sunderland “U” of 461 Squadron RAAF, in the Bay of Biscay in July 1943. [As depicted by aviation artist Robert Taylor.] Wooding, Neil; Halifax GR MkII Ser 1A JP296 of 58 Sqdn Coastal Command; Yorkshire Air Museum; http://www.artuk.org/artworks/halifax-gr-mkii-ser-1a-jp296-of-58-sqdn-coastal-command-116235 Halifax GR…
As for new attacks on the Biscay bases, which the Admiralty’s earlier Memorandum advocated, the U-boats and their essential services were sheltered under impenetrable concrete, Harris reminded the Committee, and the 10,000 tons dropped recently on the bases at Lorient and St.-Nazaire had, as the Admiralty themselves conceded, no appreciable…
Aircraft carrying six or fewer D/Cs on hunting patrols or sweeps, such as Derange, should drop the whole load in one stick; aircraft carrying more than six should drop sticks of six. Aircraft on convoy or other escort duty should drop sticks of four, leaving D/Cs for a possible second…
On the 17th, Halifax “D” of 58 Sqdn. released six D/Cs on U-628 (Kptlt. Heinz Hasenschar), the shadower boat of the Battle for ONS.5, which was returning to base. The U-boat was not damaged. One attack was made at 1721 on the 20th, by Wellington “G” of 172 Sqdn., following…
Arguably, the Focke-Wulf Fw 190 evolved into wartime Germany’s most effective fighter, offering the Luftwaffe…
Douglas A-20 Havoc Douglas Aircraft developed the Model 7B twin-engine light attack bomber in the…
Final Encounter (Spitfire v Messerchmitt) by Michael Turner. Wing Commander J E Johnnie Johnson, Spitfire…
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