Joachim Neander (1650-1680)
Joachim Neander (1650-1680) HPD nº 36,39,116,124,171, 246 Nasceu no ano de 1650, em Bremen, Alemanha. Faleceu aos 31 de Maio de 1680, em Bremen, Alemanha, de tuberculosa. Joachim era o
Clique em “Ver mais” para ter a visão geral ou acesse diretamente os conteúdos através dos links abaixo.
Ver maisConheça as ênfases e atividades realizadas na Igreja Evangélica de Confissão Luterana no Brasil (IECLB).
Ver maisTenha acesso a conteúdos por temas e âmbitos de trabalho da Igreja Evangélica de Confissão Luterana no Brasil (IECLB).
Ver maisAcesse serviços e documentos da Igreja Evangélica de Confissão Luterana no Brasil (IECLB).
Ver maisConfira os eventos e os cursos oferecidos pela Igreja Evangélica de Confissão Luterana no Brasil (IECLB).
Ver maisFortaleça a fé com as Senhas Diárias, as Meditações Diárias e o Culto Nacional Online.
Ver maisFique por dentro do que acontece na Igreja Evangélica de Confissão Luterana no Brasil (IECLB).
Ver maisJoachim Neander (1650-1680) HPD nº 36,39,116,124,171, 246 Nasceu no ano de 1650, em Bremen, Alemanha. Faleceu aos 31 de Maio de 1680, em Bremen, Alemanha, de tuberculosa. Joachim era o
Johann Scheffler (1624-1677) HPD nº 177, 203, 205 Nasceu: 1624, Breslau, Schlesien (Silesia). Faleceu: 9 de julho de 1677, St. o Matthias monastério, Breslau, Silésia. Sepultado: St. Matthias monastério, Breslau,
Hans Leo Hassler (1564-1612) HPD n° 53, 297 Nasceu: 25 de outubro de 1564 em Nuremberg, (Baviera) Alemanha Faleceu: 08 de junho de 1612 em Frankfurt/Meno, Alemanha. Vem de longe
Johannes Tauler (1300-1361) HPD 04 Nasceu: Aproximadamente 1300, Strassburg. Faleceu: 16 de junho de 1361, Strassburg. Johannes parece ter sido o filho de Nikolus Tauler (ou Tawler) de Finkweiler que
Lindolfo Weingärtner (*1923) HPD nº 68, 69, 135, 138, 139, 144, 145, 158, 165, 190, 195, 196, 266, 302 Lindolfo Weingärtner nasceu em Santa Isabel – município de Águas Mornas/SC
Eu venho a vós dos altos céus – HPD nº 15 Este é um dos 37 hinos de Martim Lutero. Lutero era pessoa um tanto rude, porém, não era nenhum
Johann Schop (1590-1664) melodias HPD 122=126, 188, 244 Nasceu: Aproximadamente 1590, Niedersachsen (Baixa Saxônia), Alemanha. Faleceu: 1664 ou 1665 ou 1667, Hamburgo, Alemanha. Johann Schop, Sênior, era compositor alemão e
Sudermann, Daniel (1550-1631) HPD nº 4 Nasceu: 1550 em Lüttich (Liége), Bélgica. Faleceu: cerca 1631 em Estrassburgo, Alsácia. Daniel Sudermann, filho do pintor, gráfico e ourives Lambert Sudermann, foi batizado
Johann Jakob Schütz (1640-1690) HPD nº240 Nasceu: 07 de setembro de 1640, Frankfurt sobre o Meno, Alemanha . Faleceu: 22 de maio de 1690, Frankfurt sobre o Meno, Alemanha. Depois
HPD nº 53 Ó fronte ensangüentada Letra – Poema Latino Medieval, adaptado por Paul Gerhardt (1607-1676) Música – Hans Leo Hassler (1564 – 1612) O autor do hino do séc.
Wolfgang Egenolf Dachstein (ca 1487-1553), HPD 43 e 152 Nasceu cerca de 1487 em Offenburg, (Baden) Alemanha, Faleceu: 7 de março de 15531 em Strasburgo, Alsácia. A partir de 1503
Johann Rist (1607-1667) HPD nº 8, 36, 39 Nasceu: 8 de março de 1607, Ottensen, Holstein, na Alemanha (perto de Hamburgo). Faleceu: 31 de agosto de 1667, Wedel an der
Todas as notícias
Portal Luterano
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