Article by: Cynthia Hamouche
In my family, we used to start preparing for Christmas in November, including a huge Christmas tree, decorations, gift shopping, and a delicious Christmas Eve menu.
That year we didn’t even think about Christmas.
We were focused on the twins; we didn’t actually believe they would come. Although my mum insisted, my husband and I decided not to put up a Christmas tree. We couldn’t stand the thought of something bad happening, and if the twins were ok, our home would be full of baby decorations.
There was no place for Christmas decoration that year.
On the December 13th, Karim and Yasmina came into the world after a hard and almost impossible pregnancy. We waited for them for so long, but we knew they would be born prematurely. When I heard them crying, it was the most beautiful sound in the world.
A few minutes later my husband, Charbel, who was with me during the C-section, told me Yasmina was healthy but Karim would need to stay in the incubator; his lungs were not fully developed.
Three days later, I returned home with my beautiful tiny 1.87 kg daughter, leaving
Karim in the hospital. Yasmina didn’t know how to drink milk. My mum had to feed her using a syringe since I was too scared to do it. Between a newborn at home, congratulation visits, post-operation pain and going to see my son in the hospital there was no time left for sleeping, eating and even less for thinking about Christmas.
I didn’t want festivities while my son was alone in the hospital.
On the 23rd of December, Charbel called me from work and asked me, “Do you think you can drive? The doctor told me to come and pick up Karim.” I couldn’t believe it. I drove to the hospital. My husband was already there. The nurses dressed up Karim, gave us some instructions and we left. It all happened so fast it was hard to believe.
Charbel drove back home while I was sat in the back with my son. He was the sweetest thing ever and slept the whole way.
Karim and Yasmina were reunited at home the day before Christmas Eve. The next day would be their first Christmas Eve in their home; we suddenly wanted to get into Christmas spirit. On the 24th, we improvised a small Christmas tree, we decorated the house, we purchased gifts from nearby shops and we prepared dinner knowing that most probably we wouldn’t even have time to sit and eat. We dressed up the kids but kept them in an overheated room because we were so scared they would get cold. It was a miracle. After years of struggling, we were finally able to spend Christmas with both of our children.
Since that day, Christmas has taken on a totally different meaning for us. It is now all about them, how to make them happy, how to make them feel the joy of that special day.
I realized that year that Karim and Yasmina were the most precious, most wonderful Christmas gift, and every year I remember that blessed period that changed our lives.
HOMEland Magazine
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