The old 14th century Sanctuary was built in the municipality of Azuaga and D. Enrique Infante de Aragón, Grand Master of the Order of Santiago, ceded part of the municipality of Azuaga to Guadalcanal on 10th April 1428. There were debates and disputes between the two towns, for which the Grand Master appointed judges, who gave a clarifying sentence on 20 November 1469, in favour of Guadalcanal, which was subsequently confirmed by the Catholic Monarchs in 1494.
Don Alonso Carrasco de Ortega, a descendant of the conquerors of Extremadura, and his wife Doña Beatriz de la Rica, ordered the construction of a new Sanctuary. Work began in 1638 and was completed in 1647. The paintings of the Sanctuary were made by the painter Brieva de Llerena, in 1800. He was assisted by his son. The metallic lustre tiles on the main altar date from 1913. It was not until 24 May 1792 that the annual pilgrimage was instituted. Before that, the Virgin only came to the village in exceptional cases of calamity.
The chapel was built in 1718 and completed in May 1719. On the front wall there is a mural of the Virgin as she was dressed in the 18th century, next to her is the Virgin and Child, Saint Joseph, Saint Joachim and Saint Ignatius. On the right wall there is a painting, possibly the Marquis of San Antonio. The Infant Bellotero dates from 1300. On 4 September 1722, Philip V granted by Royal Decree, signed in Balsaín, the Patronage and Administration of the Sanctuary of Guaditoca, in favour of the Marquis of San Antonio and Mira del Río, Don Alonso de Ortega y Toledo.
XIX, Our Lord Jesus Christ”, of which the current image of the Cristo de la Humildad (Lord seated on the Rock) was part of. This image is the oldest one that is carried in procession during Holy Week in Guadalcanal, due to the fact that in 1936 it was hidden in the well of the aforementioned hermitage. Until the 1920s, pilgrimages were made to this hermitage. On 21 March, the Señor Sentado en la Peña and the Virgen de los Dolores were taken to the church of Santa María and returned on Easter Sunday. On 11th April 1977 it was sold to Antonio Fontán Pérez.
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 of 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 of 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), both for Windows and for MAC users.
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