Ponosen grič, ki se dviguje nad Maribor, je kraj, kjer je Maribor začel pisati svojo zgodovino. Na njem je v 12. stoletju ponosno stal grad obmejne Dravske marke, ki je Mariboru podarila svoje ime Marchpurg oz Marburg.
Grad, ki je bil zgrajen za obrambo pred Madžari in je predstavljal eno od obrambnih točk v obmejni pokrajini, je leta 1528 pogorel. Grad 30 let kasneje obnovijo v renesančnem stilu, ki pa ga leta 1790 porušijo in iz njegovih ostankov zgradijo kamnito piramido, ki da griču, na katerem je, ime. Od gradu pa je ostal samo okop s strmim nasipom ter vodnjak brez venca. Na vrhu okopa pa najdemo klasicistično kapelo, v kateri je napis, ki priča o tem, da je prvotno piramido, leta 1821, uničila strela.
Grad v marki je bil prvič omenjen leta 1164, najverjetneje pa je grad bil zgrajen že prej, kajti nedokumentirano se grof Bernhard Spannheim že leta 1124 omenja kot Mariborski – sklepa se, da po gradu, ki je stal na Piramidi.
Grof Berhand naj bi potem, ko je pregnal Avžine iz Dravske doline, podedoval eppesteinske posesti v Podravju in s tem prenesel svoj sedež v na novo zgrajen grad na Piramidi in s tem ustanovil Maribor. Pod gradom je nov gospodar Maribora uredil naselbino rokodelcev, ki pa ni imela posebnega pravnega statusa, ustanovljena pa je bila tudi naselbina ob Koroški cesti z okoli 34 hišnimi parcelami. Skupaj s škofom Konradom I Abensbergom je ustanovil tudi Mariborsko pražupnijo. Obnovil je tudi nekdanji rimski most, na katerem je postavil mitnico, s čimer je postavil naselbinske temelje nadaljnjega urbanega razvoja.
Mariborska trdnjava pa je bila prvič omenjena v kroniki iz leta 1147, v kateri je bilo zapisano, da je grof Bernhard padel v drugi križarski vojni v Mali Aziji ter da je svojemu dediču in bratrancu, mejnemu grofu Otakarju, zapustil med drugim tudi hišo – daz huss ze Marpurch in mariborske ter limbuške ministerialne.
Prvo zanesljivo poročilo o obstoju trdnjave na vrhu griča pa je iz leta 1164, kjer mejni grof na svojem gradu nad prihodnjim krajem izroči zemljišče v Melju šentpavelskemu samostanu, v zameno pa prejme v last dve kmetiji pod mariborsko trdnjavo.
Prva naselbina v Mariboru pa ni nastala pod gradom, zaradi pristave pod gradom ter močno močvirnatega jugovzhodnega območja. Naselbina je tako nastala vzdolž Koroške ceste z iztekom na današnji Glavni trg. Naselbina kmalu postane upravno središče obsežnega deželsko-sodnega urada z deželskim sodiščem, središče trgovine z lesom, vinom, žitom ter obrtno središče mlinarske in strojarske obrti.
Tekst zbrala in uredila: Eva Mataln
Prevod: Maja Miklavc & Miha Odar
Fotografije: Igor Unuk
Viri:
Hostel Pekarna
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