Johann Franck (1618-1677)
Johann Franck (1618-1677) HPD nº 143 e 208 Nasceu: 1º de junho de 1618, em Guben, Brandemburgo, (Niederlausitz), Alemanha. Faleceu: 18 de junho de 1677, em Guben, Brandemburgo, Alemanha. Em
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 maisJohann Franck (1618-1677) HPD nº 143 e 208 Nasceu: 1º de junho de 1618, em Guben, Brandemburgo, (Niederlausitz), Alemanha. Faleceu: 18 de junho de 1677, em Guben, Brandemburgo, Alemanha. Em
Johann Georg Gessner (1765-1843) HPD nº 245 Nasceu: 16 de março de 1765 em Dübendorf, próximo de Zurique, Suíça. Faleceu: 28 de julho de 1843 em Zurique, Suíça. Johann Georg
Henriette Marie Luise von Hayn (1724-1782) HPD nº 202 Nasceu: 22 de maio de 1724, Idstein, Hessen-Nassau, Alemanha. Faleceu: 27 de agosto de 1782, Herrnhut, Alemanha. Henriette Marie Luise era
Philipp Friedrich Hiller 1699-1769) HPD nº 157, 187, 224 Nasceu: 6 de janeiro de 1699, Mühlhausen an der Enz, Württemberg, Alemanha. Faleceu: 24 de abril de 1769, Steinheim/Albuch, próximo de
Keimann, Christian (1607-1662) HPD nº 30 Pedagogo e poeta na época da ortodoxia luterana. Nasceu: 27 de fevereiro de 1607, em Deutsch-Pankratz, próximo de Grottau, na Boêmia. Faleceu: 13 de
Johannes Theodor Rudolf Kögel (1829-1896) HPD nº 111 Nasceu * 18 de fevereiro de 1829 em Birnbaum, Província de Posen Faleceu + 2 de julho de 1896 em Berlin. Rudolf
Charlotte Elliot (1789-1871) HPD nº 192 Nascida: 18 de março de 1789, Clapham, Surrey, Inglaterra. Morta: 22 de setembro de 1871, Brighton, Sussex Oriental, Inglaterra. Enterrada: St. a Igreja de
Michael Franck (1609-1667) HPD nº 136 e 293 Nasceu: 16 de março de 1609 em Schleusingen (Turíngia). Faleceu: 24 de setembro de 1667 em Coburgo. Michael Franck era muito inteligente
Salomão Luiz Ginsburg (1867-1927) HPD nº 119 (Tr.) Nasceu: 6 de agosto de 1867, próximo a Suwalki, Polônia. Faleceu: 1927 Salomão Luiz Ginsburg, nascido na Polônia, era filho de um
Reginald Heber (1783-1826) HPD nº 125 Em nosso hinário se encontra da autoria de Reginald Heber (em1826) um hino baseado em Isaías 6,1-8: Santo, santo, santo! Deus onipotente! Cantam de
Heinrich August Hoffmann von Fallersleben (1798-1874) HPD nº 211,2 Fonte: de.wikipedia.org Nasceu: 02 de abril de 1798 em Fallersleben, Baixa Saxônia (Alemanha) Faleceu: 19 de janeiro de 1874 em Corvey,
Thomas Ken (1637-1711) HPD nº 259 Nasceu em julho de 1637, Little Berkhampstead, Hertfordshire, Inglaterra. Faleceu: 19 de março de 1711, Longleat, Wiltshire, Inglaterra. Enterrado: Frome, Somerset, Inglaterra. Thomas Ken
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