For many years, I have heard that there had been written communication between the Prophet Muhammad and the Armenian Patriarchate of Jerusalem, but I had not seen any of the documents to that effect.
Two months ago, I read a fascinating article published in the Armenian newspaper Aztag in Beirut, Lebanon, by Dr. Garbis Harboyan of Montreal, Canada, who had uncovered the details of the communication between Prophet Muhammad and the then Armenian Patriarch of Jerusalem and their successors.
Dr. Harboyan mentioned his sources as: Gregory Krikorian’s, “Through the eye of an Armenian needle,” published by the Armenian Catholicosate of Cilicia in 2002. Krikorian had stated that his book was the summary and English translation of “History of Jerusalem,” a two-volume, 1385-page book by Dikran Sayalanians, published by the Armenian Patriarchate of Jerusalem in 1931. Dr. Harboyan also mentioned that he had recently seen the book, “Armenian Art Treasures of Jerusalem,” by Bezalel Narkiss, Michael E. Stone, and Avedis Sanjian, published in New York, in 1979, which included a copy of Prophet Muhammad’s decree to the Armenian Patriarchate.
The Armenian Patriarchate was established in Jerusalem almost 2,000 years ago. Many Armenians had gone on pilgrimage to Jerusalem after converting to Christianity in 301 AD. They had built a part of Sourp Hagop Convent in 420 AD. By the sixth Century, Armenians had constructed 66 religious institutions in Jerusalem.
In 626 AD, the Armenian Patriarch Apraham of Jerusalem, seeing the looming dangers of Islamic expansion and conquest, went to the Holy Islamic city of Mecca with a delegation of 40 prominent Armenians to meet with Prophet Muhammad to secure his protection.
Dr. Harboyan reported that the Prophet had welcomed the Armenian guests with affection, respect, and kindness, and listened to Patriarch Apraham’s suggestions. The Armenian delegation expressed its submission to the Prophet, readiness to cooperate with him, and sought his protection.
At the end of the meeting, Prophet Muhammad issued an decree which stated: “I, Muhammad, the son of Abdallah, prophet and servant of God, I pay my respect to Patriarch Apraham, I honor him and all archbishops, bishops, and priests in Jerusalem, Damascus, and Arab regions, in other words, those people who are subject to Jerusalem, such as Ethiopians, Copts, and Assyrians. I recognize and guarantee their monasteries, churches, educational centers, properties and lands. I, Prophet Muhammad, with the witness of God, and the 30 people around me, I grant my patronage and protection, and I dispense my mercy to the Armenian churches, wherever they may be, throughout Jerusalem, the Holy Tomb of Christ, Sourp Hagop Church, Bethlehem Church, all prayer houses, monasteries, Golgotha road, and the holy sites. I also secure and ensure that my protection also extends to Christian hills, valleys and Christian income-generating institutions. I declare all of this in my name as Prophet and in the name of my Muslim faithful.”
The Prophet Muhammad instructed his successors to respect his decree and execute it in all of its details. Present at that meeting was Omar the son of Khattab who became one of the Prophet’s successors and issued a similar decree confirming the Prophet’s decree.
Thus, the Prophet’s decree became the first official document confirming the status of the Armenian Patriarchate in Jerusalem. Unfortunately, the original decree cannot be located in the Patriarchate’s archives. However, a yellowish copy exists in the Patriarchate’s Mardigian Museum.
When Omar took over as Khalif in 634 AD, he appointed Abu Obeid as the head of the army. Abu Obeid’s forces attacked Damascus and Jerusalem. The Greek Patriarch Sophronius and Armenian Patriarch Krikor met with Abu Obeid and informed him that occupying Jerusalem would enrage God, because Jerusalem is a holy city. Abu Obeid reported to Khalif Omar about his meeting with the two Patriarchs. Omar personally came to Jerusalem. The brother of the Greek Patriarch met with Omar and reminded him about the decree of Prophet Muhammad. Omar then issued his own decree and confirmed the Prophet’s decree. Omar entered Jerusalem with his followers, visited the religious sites, and suggested building a Mosque in a plot of land next to the church of Christ’s tomb. The Mosque was built in 935 AD and named “Al Omariye.” Omar allowed freedom for Christian worship, but forbade the ringing of church bells.
Omar was succeeded by Khalif Ali who also issued a decree for Armenians in Jerusalem, confirming the previous decrees by the Prophet and Omar.
In 1097 AD, the Crusaders invaded and liberated Jerusalem. In 1187 AD, Salahuddin al Ayoubi who is Kurdish and his family originated from Dvin in Armenia, occupied Jerusalem and expelled the majority of 100,000 Christians from the city. He took over all the Latin churches in Jerusalem and forbade church services. However, he granted Armenians partial freedom.
Armenian Patriarch Apraham with a group of his clergy met with Salahuddin and showed him Prophet Muhammad’s decree. Salahuddin then issued his own decree and confirmed the decrees issued by the Prophet and Khalifs Omar and Ali. Salahuddin particularly noted in his decree Armenians’ jurisdiction over churches, holy places, Sourp Hagop Convent, churches of Bethlehem and Nablus, the Holy Tomb, other holy sites, and especially Armenians’ freedom to worship. He also lowered the taxes on Armenian merchants and pilgrims.
In 1517 AD, Ottoman Sultan Selim occupied Jerusalem and issued his decree which confirmed the privileges bestowed upon the Armenian Patriarchate of Jerusalem by Prophet Muhammad, Khalif Omar, and Salahuddin. Sultan Selim’s successor, Sultan Suleiman, issued his own decree reconfirming the Armenian rights in Jerusalem. Subsequent Sultans also issued decrees, such as Mehmed IV in 1659 AD, Sultan Mahmud I in 1735 AD, and Sultan Abdulmejid I in 1853 AD.
The Prophet Muhammad’s decree, besides being a valuable historical document, indicates that Armenian Christians and Muslims have enjoyed the most cordial relations from the ancient times to the present. Armenians need to publicize the Prophet’s crucial decree as well as those of his successors to counter the anti-Armenian propaganda spread by Turkey and Azerbaijan in the Islamic world.
This mode enables people with epilepsy to use the website safely by eliminating the risk of seizures that result from flashing or blinking animations and risky color combinations.
Visually Impaired Mode
Improves website's visuals
This mode adjusts the website for the convenience of users with visual impairments such as Degrading Eyesight, Tunnel Vision, Cataract, Glaucoma, and others.
Cognitive Disability Mode
Helps to focus on specific content
This mode provides different assistive options to help users with cognitive impairments such as Dyslexia, Autism, CVA, and others, to focus on the essential elements of the website more easily.
ADHD Friendly Mode
Reduces distractions and improve focus
This mode helps users with ADHD and Neurodevelopmental disorders to read, browse, and focus on the main website elements more easily while significantly reducing distractions.
Allows using the site with your screen-reader
This mode configures the website to be compatible with screen-readers such as JAWS, NVDA, VoiceOver, and TalkBack. A screen-reader is software for blind users that is installed on a computer and smartphone, and websites must be compatible with it.
Visually Pleasing Experience
Adjust Text Colors
Adjust Title Colors
Adjust Background Colors
Big Dark Cursor
Big Light Cursor
August 10, 2022
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
Screen-reader and keyboard navigation
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.
Users can also use shortcuts such as “M” (menus), “H” (headings), “F” (forms), “B” (buttons), and “G” (graphics) to jump to specific elements.
Disability profiles supported in our website
Epilepsy Safe Mode: this profile enables people with epilepsy to use the website safely by eliminating the risk of seizures that result from flashing or blinking animations and risky color combinations.
Visually Impaired Mode: this mode adjusts the website for the convenience of users with visual impairments such as Degrading Eyesight, Tunnel Vision, Cataract, Glaucoma, and others.
Cognitive Disability Mode: this mode provides different assistive options to help users with cognitive impairments such as Dyslexia, Autism, CVA, and others, to focus on the essential elements of the website more easily.
ADHD Friendly Mode: this mode helps users with ADHD and Neurodevelopmental disorders to read, browse, and focus on the main website elements more easily while significantly reducing distractions.
Blindness Mode: this mode configures the website to be compatible with screen-readers such as JAWS, NVDA, VoiceOver, and TalkBack. A screen-reader is software for blind users that is installed on a computer and smartphone, and websites must be compatible with it.
Keyboard Navigation Profile (Motor-Impaired): this profile enables motor-impaired persons to operate the website using the keyboard Tab, Shift+Tab, and the Enter keys. Users can also use shortcuts such as “M” (menus), “H” (headings), “F” (forms), “B” (buttons), and “G” (graphics) to jump to specific elements.
Additional UI, design, and readability adjustments
Font adjustments – users, can increase and decrease its size, change its family (type), adjust the spacing, alignment, line height, and more.
Color adjustments – users can select various color contrast profiles such as light, dark, inverted, and monochrome. Additionally, users can swap color schemes of titles, texts, and backgrounds, with over 7 different coloring options.
Animations – epileptic users can stop all running animations with the click of a button. Animations controlled by the interface include videos, GIFs, and CSS flashing transitions.
Content highlighting – users can choose to emphasize important elements such as links and titles. They can also choose to highlight focused or hovered elements only.
Audio muting – users with hearing devices may experience headaches or other issues due to automatic audio playing. This option lets users mute the entire website instantly.
Cognitive disorders – we utilize a search engine that is linked to Wikipedia and Wiktionary, allowing people with cognitive disorders to decipher meanings of phrases, initials, slang, and others.
Additional functions – we provide users the option to change cursor color and size, use a printing mode, enable a virtual keyboard, and many other functions.
Browser and assistive technology compatibility
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.
Notes, comments, and feedback
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