Get the latest from Weapons and Warfare right to your inbox.
Mauri The western region of North Africa was home to Berber-speaking groups whom the Greeks and later Romans identified as Mauri, or Moors. The term probably comes from a generic designation of Numidian tribes operating in the Atlas Mountains and West Africa in modern-day Morocco. The Romans took over the region and made it into the provinces of Mauretania Caesariensis,…
By Richard GabrielIn 31 bc the last two great generals of the Roman civil wars faced each other at Actium off the coast of Greece in a naval battle that would settle the future of Rome. For months Mark Antony and Egyptian Queen Cleopatra had tried in vain to break…
After Actium, as we have seen, Augustus concentrated his ships at two bases, Misenum and Ravenna, to watch the western and eastern Mediterranean. These two ports continued to be the chief bases of the Roman fleets for three centuries or more. Under the Empire, the fleets had, we may think,…
PRINCIPAL COMBATANTS: Syria (Seleucids) vs. Rome (with Rhodes and Pergamum) PRINCIPAL THEATER(S): Asia Minor DECLARATION: Rome on Syria, 192 B.C.E. MAJOR ISSUES AND OBJECTIVES: Syria wanted Rome’s compliance in the conquests of its ally Aetolia. OUTCOME: Rome attacked a Syrian fleet, triggering a war that proved disastrous for the Syrians,…
1: Alaman warrior This reconstruction follows the rich graves of the Rhine border and the descriptions of the ancient authors. Ammianus describes long, thick hair dyed red with natural substances. The narrow, long-sleeved woollen tunic is decorated with trim in red-purple silk. Note his woollen close-fitting trousers, and typical Germanic…
A small promontory jutting into the Tyrrhenian Sea from the coast of Campania in Italy on the Bay of Naples. Misenum was situated in the region of Cumae, Bauli, Baiae and Puteoli. Its name was derived supposedly from Misenus, the trumpeter of Aeneas, who drowned in the waters of its…
Excavations on the site of the Mainz Hilton discovered eleven fast patrol boats of the Roman navy, which must have been used for defending the Rhine frontier. Tree-ring dating of one boat shows that it was constructed in the 370s, and repaired with wood cut in 385 and again in…
1. EARLY VILLANOVAN CULTURE, 9th–8th CENTURIES BC.(1) Leader with war-chariot, Tarchuna area. The early example…
King Philip V, and Amyntas, Son of Alexandros, 197 BC Battle of Cynoscephalae When the…
The sixth-century army of Justinian’s era, like its earlier counterparts, was an entirely professional force,…
Sertorius was a disaffected Roman who fought successfully against Sulla and Pompey. He was a…
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