Get the latest from Weapons and Warfare right to your inbox.
GSA 32nd Annual Conference, St. Paul, October 2-5, 2008 Panel 140: Perpetrators or Victims? Letters from German Soldiers at the Eastern Front, 1939-1945 Moderator: Gerhard Weinberg, University of North Carolina at Chapel Hill “Lieutenant Peter Stoelten’s Letters: Loyal and not a Nazi” Astrid Irrgang, Studienstiftung des Deutschen Volkes “Through My Father’s Eyes: From Accomplice to Victim” Konrad H. Jarausch, University…
PHL Posters in light-boxes in Lviv praised the SS Galicia, a Ukrainian unit that fought under Nazi Germany, as defenders of the nation against Soviet aggression. Nationalist politician Oleh Tyahnybok placed the ads. The debate still rages over the SS Galicia, hailed by some as anti-Soviet nationalists. They are either…
Ray Brandon, Wendy Lower, eds. The Shoah in Ukraine: History, Testimony, Memorialization. Bloomington: Indiana University Press, 2008. ix + 378 pp. $35.00 (cloth), ISBN 978-0-253-35084-8. Reviewed by Jeff Rutherford (Department of History, Wheeling Jesuit University)Published on H-German (April, 2009)Commissioned by Susan R. Boettcher Perpetrators, Victims, and Memory: The Holocaust in…
The Russian émigrés would certainly not be welcomed back. Not only had they done nothing for their homeland, but the simple fact was that ‘Russia had been conquered with German blood for the protection of Europe against Russia’. When shortly after the German invasion of the USSR the Russian Grand…
Desperate Soviet PoWs struggle to lap up water from a semi-frozen stream. The brutal neglect of their captives by the Germans forced many Soviet soldiers into similar humiliating scenes. Huddled in tattered greatcoats Soviet prisoners glance up at the Signal photographer as they are marched westwards in the winter of…
…Forced and Slave Labor Across Europe, began with Andrej Angrick’s (institution, place) discussion of the use of SS-assigned slave labor in the construction of DG-IV, a main transit road built by the Germans and essential to their assault on Stalingrad and the Caucasus. Sarah Farmer of the University of California–Irvine…
Captured Red Army men march to the rear. Most of the Soviet POWS captured in 1941 did not even make it to the camps in Poland. The German Army simply had not prepared/or cared for such massive numbers of prisoners. Here is an example of the attrition they suffered. It…
It is truly ironic that the most numerous units of foreign nationals raised by the…
Bronislav Kaminski, leader of the RONA. by Major Bob E. Willis Jr. U.S. Army …
“Ostarbeiter” (eastern workers) were mostly eastern European women brought to Germany for forced labor. They…
The German prisoner of war camps, containing millions of Soviet prisoners, were a potential source…
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