Get the latest from Weapons and Warfare right to your inbox.
The Battle of Kawanakajima was an annual event fought between Uesugi Kenshin and Takeda Shingen. Both daimyo would ensure the battle ended in a draw. Depiction of the legendary personal conflict between Kenshin and Shingen at the fourth battle of Kawanakajima. Two of the early Sengoku Jidai’s most colourful daimyo were Takeda Shingen and Uesugi Kenshin. They represented the last…
The wedge formation consisted of battle lines ‘made up of a number of deep wedges of cavalry, followed by infantry. The more heavily armed knights would lead the wedge, while the more lightly armed men-at-arms would form the centres. The idea was to slice into the ranks of the enemy…
During the minority of King Charles VIII (1470-98) of France, a dispute broke out among rival claimants to the regency. The young king’s sister Anne of France (1460- 1522) was opposed to the insurgent claims of Duke Louis (1462-1515) of Orléans, who had gained the support of Brittany’s duke Francis…
French raid on Brighton, 1514 Anglo-French naval conflict in the early sixteenth century was a period of transition from medieval naval warfare, which had been dominated by coming alongside and boarding, to stand-off tactics in which warships put more of an emphasis on firepower and did not come into direct…
The origin of the term Schiltron, also variously spelled schiltrum or schiltrone, is obscure. A strong body of opinion holds that it translates as a shield-round or shield-ring, but whilst at first sight attractive this interpretation is not supported by the evidence. Shield-rings as used by Saxon and Norse warriors…
Andrew II died on 21 September 1235. Two years earlier he had lost his second wife, Yolande de Courtenay, sister of Robert and Baldwin II, Latin emperors of Constantinople. Although nearing sixty, he contracted a third marriage with Beatrice, the young daughter of the marquis of Este. Upon Andrew’s death,…
TAGLIACOZZO, BATTLE OF, 23 AUGUST 1268 Defeat for Conradin, son of Conrad IV (HRE), the last Hohenstaufen in Sicily. He invaded the kingdom of Sicily with German and Spanish allies in 1267, seeking to make good his claim against Charles of Anjou. Suppporters revolted against Charles in Sicily. The battle…
TAMERLANE (1336–1405). Turkic chieftain and conqueror. He was not Mongol, but sought to trace Mongol…
Background Two conflicts formed the bookends, so to say, of the fourteenth century in Prussia.…
Imposing: This form the helmet of this knight comes from illustrations of the the so-called…
This late 15th-century picture of the battle of Neville’s Cross in 1346 shows fallen warhorses.…
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