وَأَقُولُوا فِي القُرْآنِ مَا جَاءَتْ بِهِ أَيَاتُوهُ فَهُوَ الْكَارِيمُ الْمُنْزَالُوْ وَأَقُولُوا قَالَ اللَّهُ جَلَّ جَلَالُوْهُ وَالْمُصْطَافَ الْهَاديِ وَلَا أَتْ أَوْوَالُوْ الحمد لله رب العالمين والصلاة والسلام على المبعوث رحمة للعالمين نبينا محمد وعلى آله وصحبه أجمعين السلام عليكم ورحمة الله وبركاته مرحباً لكم في another episode from this brand new series brought to you by المدرسة العمرية the title of which is based upon the statement of Allah عز و جل وقال ربكم ودعوني أستجب لكم call on me and I will answer you and we have reached in this discussion on the topic of دعاء it's etiquettes, it's virtue, it's importance the things that make it answered and the things that prevent it from being answered and an explanation of some of the comprehensive ادعية the دعاء the prophets I used to make that was very comprehensive all of that is coming up in the series بِإِذْنِ اللَّهِ الْكَرِينَ but right now we reached the general discussion introducing the topic of دعاء this time from the sunnah of the messenger of Allah صلى الله عليه وسلم so we are going to start with the hadith of النعمان ونبشير رضي الله تعالى عنه وارضا or we should say رضي الله عنهما may Allah be pleased with him and may Allah be pleased with his father among the Sahaba رضي الله عنهما and he said that the messenger of Allah رسول الله صلى الله عليه وسلم قال ادعاء هو العبادة he said that the prophet صلى الله عليه وسلم said the messenger of Allah صلى الله عليه وسلم said دعاء is عبادة ثم قرأ وقال ربكم ودعوني أستجب لكم إن الذين يستكبرون عن عبادة سيدخلون جهنما داخلي this is surah ghafir ayah number 60 and the prophet صلى الله عليه وسلم recited this ayah we mentioned this in the last episode and your lord said call upon me and I will answer indeed those people who are too proud to worship me will enter jahannam disgraced will enter jahannam disgraced so in this hadith the prophet صلى الله عليه وسلم he said ادعاء هو العبادة دعاء this is عبادة all of the essence of what عبادة is lowering yourself before Allah having humility and servitude before Allah سبحانه وتعالى الزل الخودور العبودية servitude humility submission presenting yourself before Allah as a slave as a poor slave that has nothing that whole concept that you find within عبادة that is exemplified by دعاء as exemplified by دعاء and الحاكم رحمة الله تعالى وانتقلت مع عبادة حسن حسن عباس رضي الله عنهما مرفوعا من عبادة صلى الله عليه وسلم that he said افضل العبادة الدعاء وقرأ وقال ربك مدعوني استجبك the best kind of عبادة is دعاء now when we see the best kind of عبادة here we have to be a little bit careful what this means that is an statement which is to be understood in an unrestricted way in the sense that the time for صلى الله عليه وسلم but instead of doing my ضهر prayer I'm making دعاء instead that's not the meaning because this تفاضل بين الأعمال this issue of making certain actions more important than others and better than others it has a fiqh to it it could be different depending on the place you're in the time you're in the ability that you have the what is required from you in that particular situation in that particular situation because if the time if the إقامة for ضهر comes then what is required from you is to pray ضهر and there is nothing better you can do than except to pray ضهر because the إقامة for ضهر has gone and you are you know مقيم you're in your place of إقامة your home place your home city and the time for the إقامة goes there's nothing better you can do than to go to the مسجد that's what you have to do at that time so you shouldn't understand this in the wrong way and take this to mean that that even when there are other things that I have to do like your mother calls you for example but it's better for me to make دعاء that's not what the meaning is but this at least indicates the importance of دعاء and it's high status among the عبادات that the Prophet ﷺ said أفضل العبادة the best act of worship is a دعاء and أبي حرير ربي الله عن narrated a حديث this حديث is found in جامعة ترمدي from the Prophet ﷺ that he said ليس شيء أكرم على الله من a دعاء there is nothing which is more noble in the sight of Allah than making دعاء so these حديث indicate the virtue of دعاء they indicate the virtue of دعاء and as we said there are certain reasons and the scholars spoke about some of the reasons for this and by the way this is a fantastic book on this topic which is the book فق الأدعية و الأذكار the thق of دعاء and ذكر by شيخ عبد الرزاق عبد المحسن البدر حبيضهم الله this is an amazing book and the sheikh went into a lot of detail in this and much of the class that I'm delivering to is going to be taken from this book in a summarized form we're not teaching the book here but just many of the benefits here and the sheikh mentioned in this he mentioned that there are the scholars when they talk about the reason why دعاء has such that virtue they put forward a number of things and I'll mention a few of them one of them is that دعاء contains اتضر إلى الله وضعف وإضحار وضعف و الحاجة إلي it contains submissiveness and showing your need of Allah showing your weakness before Allah showing your desperation and your need of Allah عز وجل glorified as he exalted in his perfection دعاء really shows that essence of عبادة as we said and another thing the scholars mentioned is that عبادة the more خشور is in the heart the more the heart is submissive and attentive and dedicated towards Allah and the more concentration a person has the more their mind is present this is better and more complete and دعاء is one of the closest of the عبادة the most likely of the عبادة for this to be present in it's easier I mean subhan Allah how difficult it is for example when you're praying in your salah and you know to keep that خشور and that concentration and that presence of mind and presence of heart it's not easy to do it when you're praying in the salah but in دعاء it's relatively easier to achieve and it's something which is natural that you're when you're asking for something and you're pleading Allah for something that generally it's easier for your heart to be present for your mind to be present to have that state of attentiveness and submission and desperation it comes naturally within دعاء and so دعاء really exemplifies what you should have in all of your in all of your عبادة to make them from the best of the عبادة also some of the things that scholars mentioned they said that دعاء comes along with and it necessitates تواكل and إستعانة بالله you can't when you're making دعاء the essence of that دعاء that you are making is تواكل that's the essence of the دعاء you're making it's saying that oh Allah I don't have the ability to do this if I don't put my reliance in you I don't have any way for this to happen so it brings about تواكل and it is the essence of إستعانة and that's why the prophets I'm saying in the famous حديث عبدالله عباس رضي الله عنهما إذا سألت فسأل الله وإذا استعانت فاستعين بالله if you ask then ask Allah and if you seek help seek help from Allah دعاء and asking Allah brings about إستعانة it entails it it has to be that it's ملازم it has to be that the two of them go together that the essence of what you're doing when you're making دعاء is that your دعاء comes along with تواكل and comes along with seeking help from Allah إياك نعبد وإياك نستعين because of the position of إستعانة in Islam so important look seeking help from Allah look at how Allah عز وجل said صورة الفاتحة إياك نعبد وإياك نستعين إستعانة was singled out among all of the عبادات to be mentioned in صورة الفاتحة it was singled out you alone you alone we worship and the عبادة that's singled out you alone we seek help from so دعاء comes along with that and embodies that soul and it necessitates that so that is another reason why دعاء is from the best of the عبادة from that حديث that we can quote which really tell us part of the virtue of دعاء and the importance of دعاء is that which was narrated by أليمام أحمد is Musnad by أليمام الترمذين رحمهم الله تعالى in his جامع and ابن ماجى in his سنن رحمه الله تعالى and others with a third chain from أبي هوريرة رضي الله عنه لما سنجأ الله صلى الله عليه وسلم he said من لم يدعوا الله سبحانه غاضبا عليه whoever doesn't make دعاء to Allah Allah becomes angry with them قلما يعبأ بكم ربي لو لا دعاءكم say my lord would not care for you would not give any concern to you if it were not for your دعاء whoever doesn't make دعاء to Allah الله becomes angry with him and أليمام البخاري narrated in الأدب المفرد outside of الصحيح أدب المفرد and likewise من حبان narrated in his صحيح from أبي هوريرة from the statement of أبي هوريرة and the طبراني narrated from him from the prophet صلى الله عليه وسلم from the statement of the prophet صلى الله عليه وسلم أعجز الناس من عجز عن الدعاء وأبقال الناس من بخلا بالسلام so this was narrated as a statement of أبي هوريرة by البخاري and by ترمذي and it was narrated by others as a statement of the prophet صلى الله عليه وسلم and this is that the person who is the most unable to do something عجز that has is totally has the most inability is the one who is unable to make دعاء and wallahi is so true even if it is a statement of أبي هوريرة رضي الله عنبا this is صلى الله عليه وسلم صلى الله عليه وسلم صلى الله عليه وسلم that is سبحان الله if you can't even make دعاء we're not talking about praying five times a day or a person who you know giving lot of صدق for the sake of Allah or a person who's going to هجن أمرا or a person who's fasting the days of the year the month of رمضان and the Mondays and the Thursdays but the least of the things دعاء is so easy to do it's the least of things that Allah سبحانه وتعالى requires from you the smallest thing that's so easy for you to do the trauma among the things that are extremely easy and that's why the person who is really truly عجز like truly just completely unable like really is is not doing anything at all that's the person who can't make even make دعاء to Allah سبحانه وتعالى but that has also a reverse benefit that when a person is struggling and you know if we talk about some of the people who might be watching you might have relatives or friends or family who are struggling to pray maybe they're struggling with it you know the important critical acts of worship in Islam one of the things you can start them off with you know when they feel like I'm عجز I can't do anything I can't pray I can't just I'm irregular with it I can't make keep you consistent with it one of the beautiful things you can tell them to do is دعاء just to start them off just to get them you know to get them in the status and so دعاء to ask Allah to give you the ability to pray to give you the ability to fast to give you the ability to do the actions that are required of you in Islam just to just to say a few words or Allah make it easy for me سبحانه وتعالى how difficult is that it's one of the easiest things in the world to do and that's one of the beautiful things about دعاء is how easy it is for a person to make دعاء اليمام أحمد and likewise اليمام الماجه رحمهم الله تعالى they narrated from ثوبان رضي الله عن أن النبي صلى الله عليه وسلم قال that the prophet صلى الله عليه وسلم said لا يرد القادر إلا الدعاء nothing repels the decree except دعاء this is a hadith that sometimes people struggle with because we have our belief in قادر it's a hookah it's a pillar from the pillars of ايمان people struggle to understand this what does it mean but in essence without going into too much detail it means that Allah سبحانه وتعالى has made دعاء a cause to protect a person and to keep a person away from negative things that might otherwise have happened to them and that دعاء doesn't go outside of the قادر of الله عزوجل that دعاء doesn't go outside of the قادر of الله عزوجل it doesn't go outside of the لوه المحفوث it's still from that which Allah سبحانه وتعالى knows about and knew about before he created you and the things which Allah سبحانه وتعالى commanded the pen to write but if you had not made that دعاء there was a something bad to happen but you made that دعاء which didn't go outside of the قادر of الله عزوجل and the decree of Allah سبحانه وتعالى and that دعاء was what prevented that thing that would otherwise have happened that would otherwise have happened to you and therefore دعاء is one of the major means of achieving happiness in this world and the next it's one of the keys to happiness in this world and the next it's a call upon Allah and to make دعاء and I'm going to give you a quote from الإمام ابن القيم رحمه الله تعالى he said أساس كل خير أن تعلم أنما شاء الله كان وما لم يشاء لم يكن he said the essence of everything good is for you to know that whatever Allah willed will happen and whatever Allah didn't will will not happen إذن أن الحسانات من نعمه فتشكوره عليها وتتضرع إليه أن لا يخطاعها عنك he said سوذين at that time you become certain that all the good things that happen to you are from the blessings of Allah so you show gratitude to Allah for them and you humble yourself and submit this yourself before Allah in fear so that Allah does not cut those blessings off out of the fear that Allah will not cut those blessings off from وأن السيئات من خضلانه وعقوبته and that the sins that happen are from the punishments of Allah and from what Allah عز وجل brings about which lower to lower a person and to take down this tears فتبتاه إليها أن يحول بينك وبينها so you turn to Allah and you you beg from Allah to make something to a barrier to come between you and between those sins ولا يكلك في فعل الحسانات وترك السيئات إلى نفسك and that Allah عز وجل doesn't leave you and abandon you to do good deeds and to leave sins by yourself because you can't do it without the help of Allah عز وجل that's why that's just part of the quote that our Imam إبن القيب he said رحمه الله in the essence of of you believing that all the good deeds are from the blessings of Allah if Allah left you alone to yourself you wouldn't be able to do those good deeds and keeping away from these sins that's from what Allah عز وجل gives you و هو بيد الله like إبن القيب said this in the hands of Allah لا بيد العبت it's not in the hands of the servant فمفتاحوا الدعاء و الافتقار و الصدق اللجاء و الرغبة و الرغبة إليه the key what is the key to opening up the state of knowing this and submitting to this what's the key to it the key to it is what's the key to the توفق of Allah عز وجل in this the success from Allah the key to it is دعاء and presenting yourself in a state of poverty and desperate need and truly turning to Allah and seeking refuge from Him and hope and fear of Him when you take this key like إبن القيب said when you when Allah gives the servant this key he said فمتع عطى العبت هذا المفتاح فقد أراد أن يفتح لها whoever Allah عز وجل whichever person Allah gives this key to the key of دعاء this is a person Allah really wants to open things up for them open up opportunities and a means to success from them ومتع عضله عن المفتاح بقيا باب الخير مرتجن دولة he said whenever the person loses or Allah عز وجل causes them to lose this key which is دعاء the things that he mentioned with it then the person will not be able to reach the door the means to be able to do good and then إبن القيب رحم الله he said وما أوتي أمن أوتي إلا من قبلي إضاعة الشكري وإهمال الافتقاري و الدعاء he said in the people who were put to trial they were only they only suffered these trials because they lost gratitude and they lost their need of Allah and they lost their دعاء making دعاء to Allah و لا ضفر من ضفر and no one was successful who was successful بمشيئة الله وعوني by the by the will of Allah and with Allah's help إلا بقيامه بشكر وصدق الافتقار ودعاء except because of the person was grateful they showed gratitude and they were truly they truly showed their need of Allah and they made دعاء to him there is a hadith that I would like to conclude this episode with and it's a rather long hadith it's narrated by الإيمان مسلم from a long hadith and it's the hadith of Abidar رضي الله عنه but this hadith has many many benefits in as it relates to دعاء and our desperate need of Allah and that دعاء is the key to opening up the doors to success and from this is and it's a hadith it's a hadith which the prophet is narrated from Allah سبحانه وتعالى in which Allah said يا عباد كلكم قالوا إلا من هديتوا فاستهدوني أهتكم all my servants all of you are misguided except the one that I guided so seek my guidance and I will guide you يا عباد كلكم جاعين إلا من أطعمتوا فاستهدوني أطعينكم all my servants all of you are hungry except for the one that I feed so seek food from me and I will feed you يا عباد كلكم معالن إلا من كسوتو فاستهدوني أكسكم all my servants all of you are naked except the one that I clothed so seek clothing from me and I will cloth you يا عباد إنكم تخطيون بالليل والنهار وأنا أغفر الظنوذة جميعا فاستغفروني أغفر لكم all my servants you commit sin all my servants you commit sins in the day and the night and I forgive all sins so seek forgiveness from me and I will forgive you until Allah عز وجل said يا عباد لو أن أولكم وأخركم وإنسكم وجنكم قاموا على صعيد واحد فسألوني فعطيتوا كل واحد مسألتها ما نقص ذلك مما عندي إلا كما ينقص المخيط وإذا أدخل البحر or my servants if the first of you and the last of you or and the men of you and the jinn of you stood on a single plane and all of you asked and I gave every one of you what you asked for that would not detract anything from what is with me except like the needle detracts from the water when it takes when it's dipped into the sea when you dip a needle into the sea does the volume of water in the sea decrease? that's God all the water that's coming into the sea by the time you dip the needle and take it out the water didn't decrease anything if Allah gave all of us everyone watching this video everyone on the earth every jinnie every human being of all time from Adam until the last human being on this earth and they all asked Allah at a single time one time and they all asked Allah for everything that they wanted and Allah gave everyone what they asked for it wouldn't decrease from what is with Allah except like the needle that is dipped into the sea and the reality is that when you dip a needle into the sea nothing from the sea is lost and as we said the Hadith narrated by Aliman Muslim and this really shows us our desperate need of Allah and it shows us that dua is the key if we use this dua dua is the key dua is the key for us to be able to open this door to good and to open this door to the forgiveness of Allah to the things that we want in the dunya and the akhirah to all of the khayr that Allah سبحانه وتعالى gives to His servants the key to this is a dua so we really have to show us the importance of dua and our need of Allah and our need of making dua to Allah سبحانه وتعالى so that's what we have time for in this episode and Allah knows best صلاة و السلام على نبينا محمد و على آله و صحبه أجمع السلام عليكم و رحمة الله و بركاته كيف يمكنك أن تفعل اعطاء الثقافة right now that will give you a share of the reward of everything we're doing on this YouTube channel simple like this video and click subscribe why it will allow YouTube to recommend our videos to other users and imagine the huge amount of reward that could be waiting for you on the day of judgment if you did that with a sincere intention of spreading the deen of Allah you'll be rewarded for every single person who benefits from one of our videos as a result of your like or subscribe that's an easy two second action that you definitely don't want to miss out on do it now click like and subscribe and don't forget to make that intention


NEHEL There's a case of Huntergatherer complexity, this is another complexity that's probably are old fashioned, nowadays, concept in Huntergatherer studies Ond roedd dysgu tyn nhw'n ddim y tro o'r gael o'r Rhifn gen i wnaeth i ddweud cael eu mynedion. Yn y gallu llawer o dynnu Cymru sy'n cyfal o gael ar gyfer Euramun i'r Serviw, ond yn y gallu unig mawr yma yn yr Ym wrthyn ni wedyn, bywyd y rhifn argynnu Cymru ar gyfan y Gymraeg, And this section of the river was dammed, at this point here with the Iron Gate's one dam and the Iron Gate's two 80 kilometres downstream. And archaeological surveys in advance of completion of those dams resulted in recognition of some 50-55 sites with mesolithic and or early neolithic occupation on them. If you study that in detail and wish you had time too, you will see that there are far more neolithic sites than there are Mesolithic sites, there are only about 20 sites of those 50 on Mesolithic occupation. Interestingly, most of those sites with Mesolithic occupation also have early Neolithic occupation. ac yn ystafell yn ymgyrch. Byddwn yw'r gweithio i'r ffyrdd, a'r gweithio i'r bwysig i'w Llywodraeth i bwysig i bobl. Mae'r ffyrdd yn gweithio'r bwysig, yn ymgyrch gweithio'r gweithiau, mae'n gwithio'r gweithiau, a'i wneud i gyd yn gweithio'r gweithio'r gweithio'r gweithio, a fyddo i ddechrau i ddangos a gweithio yn ystod y llefwyr yn ysgolio'r ffeithio. Yn ystod yn ysgolio, yn ysgolio, yn ysgolio ar gyfer ymlaen ymlaen. Mae'r idea o'r cyfeisio i ddechrau'r ffeithio i ddweudio'r ffeithio yn ysgolio. Mae'r idea i gyda'u cyfnod mezzolithu, bywyd yn i gyd yn ddiddordeb yn y ddiddordeb am yma. Mae'r idea gan hyn oedd ystafell, yw ystafell mewn datblygaeth i'r rhwythryngau, i'r idea o'r ffordd cymaint i'r cyflwyngau cyflwyngau a'r bywyd. Wel, mae'r cyfnod ar gyfer archiologiol yw'r cyflexyd? Mae'r cyfnod ar gyfer y prysau a'r idea yw'r cyfnod, ac mae'n gweithio'r cyfnod, a'r ddechrau'r ddodol, ac mae'r ddodol o'r rydw i'r cyfnod. A'r cwestiynau, mae'r ddodol o'r ddodol o'r cyfnod yn y cyfnod ar gyfer archiologiol yw'r cyfnod?  Gidegwch i'r blaenau a'r trofnegf kas i'r hyffyddiad i fynd i gael ycing, i'w gweithio, i ffinsiau, a'u llachau i'r bobl i'r hyffyddiad. Diolch yn fawr, Adela Byr yn cofnod i ddim yn ddifrif i gyfweld a dyfodol i'r gael, ond ydych chi'n edrych ar gyfer y banyddol, ond y ddweud o'r llei fathion ei wneud yn gadael, ond mewn ffwrdd y ddiolch yn ei wneud yn ddifrif. Rwy'n meddwl â'r ddechrau dechrau mewn i Gwaith, ond mae'n cymdwylliant i'r ddechrau at y bobl sydd yw'r cynnig yn ddifrif. Wel, mae'n meddwl ei ddweud i'r ddweud i'r ddigwyd, 12000 oedd, 12500 o arian. There's no clear way of dividing up the meselithic into stages in terms of cultural changes. So, we use the climatic record. So, for the sake of argument, we say early meselithic is the late place. You're middle meselithic is the period between the young to die rise and the 9.3K event, and then late meselithic between the 9.3 and the 8.2. ac mae'n gweld y 8,2 yn y pepper gan drwyg. Felly mae'n gwisio i gydechrau yaynici, a pwysigio bod chi'n cyffredig ei ddyliad ar y bwyd mlynedd. Ynogi, mae bwysig ei bwysig oedd iawn yn ein bwysig yn f Otherfyn, mewn eu cyffredig ar y... Yn y gallw'r cyrchaf, ac mae'n ystafell o unrhyw cynnoddiadol yng Nghyrprifesedd Ames Radio Carbon o'r cyflawn, a os ydych chi'n bwysig, y gweithio'r stafellau cyrchaf o'r gyflawn cyflawn. Yr hyn o beth ar gyfer ymlaen, y cyfrifio ar gyfer ymlaen, y cyfrifio ar gyfer ymlaen i cramio'r gyfrifio. Mae'n ddweud o'r wych yn y Gagog Lleith. Mae'n gweithfyrdd sydd y gyd-egaf iawn i gael gwasanaeth yma. Mae'n ddweud o'r rhaglen gan y cyfnod. Mae'n ddweud i gael gwasanaeth yma. Mae'n gofynu'n gwaith i gael'r dynnu'u gwahanol. Yn y gwasanaeth yn ddweud i ddweud i gael gweith ag hyd yn y Gagog Lleith i gael gwasanaeth yma, mae'n gweithfyrdd a'n gweithfyrdd i gael gwaith i gael gwasanaeth yma. elli, mwy o'r arnoch, yn gweithio amhaith, ymlaenwch yn ffysg ychydig i'r hath. Y hwyl yn ymddangos i'w ahirweith yw o'r amlant i bidio a'r ffordd yma? Mae'r iawn y cymaint yn beth amlaenwch, menner ac dros hynny, y wneud a'r amlant a', oes deis. Mae'n adroddau hynny yn digwyddio ar y hwnnw. I think there's been a bit argument about what the sulphur isotopes actually mean, but I think one thing we can get from the sulphur isotopes is it shows that things are more complex than we thought based on carbon and nitrogen. And what we can say from the sulphur is that there seems to be a being in the course of the mesolithic in the Iron Gates an increase in dependence on fishing. They were always fishing right from the Lake Glacier, but there was an increase in dependence on fishing. I can't go into great detail. In parallel with that, we've got this, it's not my term, like Duchamp Borrach uses this term, fish-related symbolism. This, along with the increase in dependence on fishing, we see this fish-related symbolism coming into the Iron Gates. It's reflected, in fact, in the presence of siphonid teeth in burials. Duchamp Borrach and Manuel Christiani wrote about this in the context of Lasat. This is a little reconstruction where these pharyngeal teeth, or the tops of them, broken out of the pharyngeal bone of carp, or a particular species of carp, are probably sewn. We know they were sewn on to skin, or textile, clothing, or garments. And it wasn't just for burial. They found in burials, but it wasn't just for burial, because these things that we've shown are very, very heavily worn, and they must have been worn over a long, long period in life. And that, of course, they don't understand. We've got the carved boulders from Lepanskivir. And all this is a late phenomenon. This comes in about 7,200 BC, about 1,000 years before the beginning of the following. So this goes along with the ice-tope evidence for increased dependence on fishing. Now, your round occupation in the Iron Gates seems to me would have been as unlikely without food storage. Living in one place in a big group all year round would have been difficult without some form of food storage. Although the fish are there year round, catching them is not easy at certain times of year, and there are particular times of year when you think of sturgeon migration, sturgeon coming out from the Black Sea, when you can exploit the sturgeon and other times of year when they're not there. So winter would have been a lean time for anybody fishing in the Danube. It was difficult to catch carp and catfish in the winter. So without food storage, you're going to have difficulty. That's a sturgeon, a beluga, I believe. If you go to Verdina, you wouldn't have to translate that. It's quite an amusing comment. But do we get storage facilities in the Iron Gates? Well, not that we can recognise archaeologically. But, as I pointed out in front before, people kept dogs in the Iron Gates, in the Iron Gates Meslithic. They kept dogs in large numbers, and they ate dogs in large numbers because dog bones were found, butchery marks on them and so forth. I've pointed out before that this is an indirect form of storage. The dogs will scammage around the site, will basically feed themselves on the human food refuse, and then at times when you haven't got the fish, you eat the dogs. Now, the ethnographic record for hunter-gradders will probably show us that when people are living in one place for a longer period of time in bigger groups, they tend to get a greater investment in structuring of the use of space, the way in which huts or houses are arranged. And we can see this in a sense, if we accept the Trapezole plan buildings, Lepensky Beer and Paddenham, as houses or huts, you can see how it's all neatly arranged, particularly in Lepensky Beer and Rhodes. But that, again, is a very late phenomenon in the Iron Gates, in fact, having that there's some question as to whether this is meslithic or neolithic. There was a big argument that's even a question as to whether this is meslithic or neolithic. It's a big argument, but I think it's now fairly certain. The Trapezole plan buildings at Lepensky Beer are final meslithic, and it may also be the same at Paddenham. The radio problem dates, and I'm not clear enough to tell us. If we go back a bit earlier into the late meslithic here, places like Blasats, and the Carter and Scalae Cloud would be on the Romanian bank, yes, we have evidence of Trapezole plan buildings, but not like this. It's very few. And because the sites haven't been excavated as extensively as Lepensky Beer and Blasats, we can't really say how regular the arrangement of these buildings was. But my impression is that there are far fewer buildings and they're not regularly arranged in these sites. Certainly not at Scalae Cloud would be a requirement. When you go back even earlier into the early meslithic, we haven't got any obvious butt structures. But, having said that, there's all the activity that goes on on these sites, which are being intermittently occupied throughout the meslithic. So, neolithic and late meslithic occupation tends to destroy early meslithic occupation. Seasonality? Nobody really looks at this until recently. Besnith Dimitriovic and colleagues have looked at this. There have been very few studies. What they concluded was that the sites they looked at and there was very little evidence were occupied year round. The seasonal indicators did indicate occupation at different times of year. And again, they thought that they only found this in the late meslithic. So, in conclusion, the evidence points to, I think, greater emphasis on fishing in the late final meslithic. Possibly an increased investment in the structuring of settlement space. I think in what we see at the peninsula here in Padana. By implication, perhaps larger group size and sedentism. But, I don't think we can rule out sedentism in the early meslithic here. Thank you.


I'm Bill Hammack. And I'm Don DeCost. And we created this lecture series, Michael Faraday's The Chemical History of a Candle. And this is a commentary track to just kind of deepen or enrich the lectures. And I would suggest that if possible, you have the subtitles for the lectures turned on. In the first lecture, Faraday gave us an overview of how a candle works. Now let's listen to Faraday's words about the subject of lecture two. Faraday happens in any particular part of the flame, why it happens, what it does in happening, and where, after all, the whole candle goes to. Throughout this lecture, Michael Faraday focuses on the properties of the flame of a burning candle using those properties to understand how a candle works. Now what's interesting is the number of tools he creates to probe the flame. We normally think of sophisticated scientific instruments like microscopes or spectroscopes or balances. But Faraday's simple tools are just as specialized. And of course that's part of science to invent or create tools that let us see the invisible or to quantify nature. You know, and this is one of the things that makes chemistry a difficult subject, especially when you're first studying it. And that is many of the properties are invisible. Now you see here that he's using a specially shaped glass tube to capture what he calls the wax of the candle made into a vaporous fluid. At this point Faraday makes a distinction between a gas and a vapor, noting that a gas is permanent and a vapor can be condensed at least at the pressure and temperature of interest. But the larger issue is that he points out that science makes use of precise terminology. Now that said, we're going to take Faraday to task in a few minutes for some imprecise usage of the word air, but more on that in a moment. You know, there's a couple of different ways to see things. As Bill mentioned, you make tools to do this. You can also take things out of context. And what Faraday is going to do next is he's going to take a large sample of wax and heat it, not burning it like a candle, but heating it in a flask. And this is something deep here. He's going to make an assumption that the sum of the parts equals the whole. And this is a type of reductionism. Let's listen here to the extent that Michael Faraday uses reductionism. This then is exactly the same kind of vapor as we have in the middle of the candle. Of course, there's a limit to this analogy as to all analogies. For example, why does the vapor flame out in the flask, but not in the candle? The idea here is that it's not exactly like a candle. Now, this is one of our favorite demonstrations. It's truly stunning. He shows clearly that it's the vapor that ignites. And he mentions that production and combustion of the vapor occur in two different parts of the flame. And he says this in a single sentence, but it's really a big deal. The key here is to note where the tube is positioned in the flame. It's placed in a point where the production of the vapor is occurring so that he's able to light the vapor as it comes out the top of the tube. So this great demonstration really shows that there are different parts of the flame that it's not homogeneous. In fact, watch what happens when he moves the tube. So what he's done is move his tube from the place of the production of vapor to the place where the combustion has occurred and so the vapor is spent and so it won't relight. And it was at this point that Michael Faraday mentioned the intense chemical action which the air meets the vapor in the candle flame. And this is the first time he's really getting into the chemistry. So now he's going to move from the production and combustion of the vapor to show us about the temperature distribution in the flame. So notice here that he's going to use another tool. It's just a simple tool, but it's extremely effective. And this is another tool that makes the invisible visible. We would think that the whole flame was hot, yet it isn't homogeneous in temperature. The heat generated by the chemical reaction takes place in only parts of the flame where the dark ring appears. Faraday mentions again the chemistry happening between the air and the vapor. But we want to listen carefully to his words because there's a little bit of imprecision in them that we want to talk about later. Air is absolutely necessary for combustion. And what is more, I must have you understand that fresh air is necessary or else we should be imperfect in our reasoning and our experiments. So the problem here is the use of the term fresh air. What exactly does this mean? I mean we know today that what he's trying to get to is the amount of oxygen that's in the air, but it kind of implies that regular air or normal air doesn't have oxygen in it. So let's listen to what he says next, which is just a little bit better. The jar is full of air, partly changed, partly not changed, but it does not contain sufficient of the fresh air which is necessary for the combustion of a candle. And this is better of course because Faraday uses some change, some not changed for the air showing that there's a chemical reaction that's occurring. But he still uses the phrase fresh air and he does this because he doesn't want to prejudge the idea that there's oxygen in the air. What Faraday does as a teacher here is very interesting, he uses this imprecise metaphor of fresh air so he doesn't have to introduce a new topic yet. Now let's watch in this next section how he returns to that notion of reductionism. Here is a larger wick made from these cotton balls. All these things are the same as candles after all. So notice he's saying all of these things are the same as candles, which means that the cotton balls are the same as candles, but of course they're not. And this is one of the really, I think, subtle parts of science. So we use models to capture the essential physical phenomenon. But what we have to do as scientists is we have to know how far to take a model and we have to know when it falls apart. Now his goal here is to reduce the amount of oxygen that can get to the burning cotton.  So this means that the oxygen is limiting. Now earlier on he showed us that we need something in the air, which we know is oxygen, by putting the jar over the top of the candle. And now he shows us that without enough oxygen there's incomplete combustion. Now what Faraday did here was very interesting or more to the point what he didn't do. He did show us there was black smoke. He didn't tell us what that black smoke is. We probably have guessed that it's carbon particles. And today we would just say, look I'm going to make carbon in the flame and then we would tell you that the carbon makes the candle glow. And Faraday inverts this process. He puts the observation first. He says a candle glows, why does it glow, and then he goes back and looks at what the black inner flame means and shows that it's carbon particles that glow. So up to this point Faraday has done a few things. One, he started by showing us that a flame is not homogeneous with respect to the chemical action. There are different places of production of vapor and combustion of vapor and he showed us that it's not homogeneous with respect to temperature. There's a hottest part of the flame. Now in both of those cases we couldn't really see them and he used tools to do this. Now what he's going to do is he's going to show us that the flame is not homogeneous with respect to brightness which we could see although we have to really be observant to do that. And he's going to discuss this by talking about things that burn with the flame and not with the flame. And he's playing a little bit fast and loose here with the word burn but again a little imprecision to get to a larger point I think is justified. In this case the chemical reaction of the gunpowder with the oxygen produces the heat to form a flame and the iron particles are heated until they glow which we call incandescence. Now of course he's going to show us in a little bit that the carbon particles that are in the flame are what's glowing and of course there's carbon particles in gunpowder. So he's really adding the iron filings here for effect. Now the last thing that he mentions here as well is that the oil, the gas, the candle all of these that we use for illumination. He uses the phrase their fitness depends on these different kinds of combustion which is a really nice way then of expanding this to more than just a candle. So when we were recording the lectures we noticed that this demonstration was redundant it contains really the information of the previous demonstration and we did take a number of these redundant demonstrations out but we really liked this one and it highlights just how great a showman Michael Faraday was because this produces just an absolutely brilliant flame that would have delighted his audience. So what's coming up next is kind of a continuation of what he had done before. Bill had mentioned earlier how it's interesting how Faraday starts with an observation and then goes in search of how to explain that observation. The one observation was when he used the cotton balls to make a large flame we had restricted oxygen and we noticed that we see some black smoke. Now where is that black smoke coming from? Now Faraday uses this simple tool of this glass tube to place it inside a part of the flame in this case the brightest part of the flame and we can see that the black smoke is coming from there. We now know of course that the black smoke is carbon and the carbon actually reacts with the oxygen in the air when it meets the interface of the flame and the air.  He points out that the carbon that's coming out of the candle and the smoke was the carbon that was originally in the candle and he makes an observation that shows how science links together all sorts of observations. He mentions the soot that's in London that that's also carbon so carbon is carbon that's a theme that we'll see come up a couple of times particularly when he talks about water. And so here Faraday is reminding us that it's the glowing carbon particles that give us the bright part of the flame just as he showed the iron filings were glowing in the gunpowder. At this point Michael Faraday sums up what he concludes from his experiment so let's just listen to him. What I have to say is applicable to all substances whether they burned or whether they do not burn that they are exceedingly bright if they retain their solid form and that it is to this presence of solid particles in the candle flame that it owes its brilliancy. So Faraday here is using reductionism. He said that carbon particles glow so he's going to isolate the carbon and interestingly what he does here is he makes it human sized so he's got a large chunk of carbon and when he puts it in a flame you can see that it glows and this as he says is what gives the candle its brightness. Let's listen to Faraday comment on a kind of counterintuitive aspect of beauty and nature and we'll talk about it a bit after. Is it not beautiful to think that such a process is going on and that such a dirty thing as charcoal can become so incandescent? You see it comes to this that all bright flames contain these solid particles all things that burn and produce solid particles either during the time they are burning as in the candle or immediately after being burnt as in the case of the gunpowder and iron filings all these things give us this glorious and beautiful light. So when Faraday says that a dirty thing like charcoal has beauty he's really echoing some thoughts that he had in the first lecture where he looked at decorative candles which most people thought were beautiful but they were bad burning and argued that a normal candle is a beautiful thing and also there's a subtle reminder here that science gives us a unified way to look at the natural world. So this demonstration kind of like a podium demonstration is a little bit redundant at this point he's talked about the brightness of flames coming from the solid particles but again it's a spectacular demonstration so Faraday being the showman wants to see this but he also does something interesting from an educational aspect and he asks the audience, I've given you all the tools now you can reason your way through this does this flame contain particles or not? Here Faraday burns propane which of course provides the carbon in a bunch in burner and he's allowed very little oxygen into it and so what happens is you get this very yellow flame because of the carbon particles now watch what happens as he allows a lot of oxygen into the flame all of the carbon burns so he no longer has carbon particles so he no longer has the yellow flame but instead has just a blue flame So it's interesting here that Faraday now is using this bunsen burner as a tool although not as we normally use it in the lab he's doing this to kind of sum up two of the key observations that he's made one, the oxygen controls the amount of particles that we have in the flame and two, it's the particles here that glow brightly and give the flame its brightness so he's using this then to control these variables So here Faraday is again making the invisible visible he's already shown us this once before covering the candle with the jar but before he focused on the flame and now he's focusing on the cloudiness inside the glass jar and he's doing that because it's the products of the candle that actually make this cloudiness and he's hinted a little bit he's talked about this invisible substance when he talked about the carbon burning he'll talk about carbon dioxide in lecture four but what he's really hinting at now is the fact that water is one of the products of combustion and he does this with a spoon, something you can do at home And water is the subject of the next lecture Faraday looks at it thoroughly in lecture three and I hope you join us for commentary on that lecture I'm Bill Hammack and I'm Don DeCost and thanks for listening


Today we have Manoj with us, who is going to talk about tips from the trenches accessibility testing. And Manoj is a principal technologist at ThoughtWorks. I'm super honoured to be hosting him today. So I'm sure we all will enjoy his session.  Sure, thank you. Hey everyone, so happy to be here and thanks for being equally honoured too. Thanks for all of this. We have been meeting each other in different conferences. So I'm so glad to see Parvin again. So as Parvin already shared, today's session is going to be tips from the trenches accessibility testing. And before that, I'm Manoj and as Pravin mentioned, we work for ThoughtWorks and I'm a principal technologist. I like to be called myself as a T-shaped technologist where I go across breadth as well as go deep dive in tech where think QA and a few other like DevOps and mobile and think react front-end accessibility performance. There's a number of things that I do. They never one thing I easily get bored. So I try to go hands-on with different texts. So that's how I get experience in multiple areas. So today specifically, I'm going to share about accessibility testing and how I got involved. So this was during one of my engagements when I worked with an insurance provider in Australia where I got the opportunity to work more on, you know, transmitting front-end from Angular to React when mostly as a single-page application, right? I think it was at least six years back. So you could imagine at those stages, React was still picking up and as everyone, you know, the tech as a dev, they're trying to move from one piece of technology to the other. I think framework. I think it's basically due to try new stuff. And single-page application was trending. I don't know if it's still trending. So I still see a few providers, insurance providers specifically as well as a few forms still follow the pattern. And what's more challenging when you do that is try to bake in accessibility with that, right? I think it's becoming even more challenge. So I'm going to share some tips from there. And I think that's from since then, since I developed my passion around accessibility and I start researching about it whenever I get a chance. As a consultant at ThoughtWorks, whenever I speak to my clients, I always, you know, keep this as one of the agenda items and try to understand what is there mindset about empathy and inclusive culture, you know, all around these things. And I'm going to share a couple of things in terms of accessibility itself, what it means. And as a key takeaway, if you're someone who's new to accessibility, what is something that you should take away from the session. And after you understood what is accessibility, I think the most important or the immediate key takeaway would be to see this is all good, I understand accessibility. Now, how will I fit this within my SDLC, which is my life cycle, software development life cycle, and then more specifically deep dive into accessibility testing perspectives to see how quickly I can check. Because if you're in a green field project, that's great. You can start baking in. I'm sure there'll be a couple of takeaways from the good for all SDLC phases that I have. But if it's a brownfield and if you already have something, so you could go ahead and, you know, implement some of the testing features from there. Before that, I will actually start my captioning. This is something that I usually do for all my accessibility sessions. I just forgot. But nevertheless, we are never, you know, too late. It's just second slide and just the agenda. Let's get started. I'm more on accessibility. So what is first thing that comes to your mind when you hear accessibility? Wish this was an in-person conference so I can, you know, hear all your voices, but unfortunately, we can't do that. So accessibility to me is all about how easy I can do things, right? So what is my situation right now? What is I'm capable of? What I'm able to do? And a number of things that comes into picture, right? If the things around us are something quite naturally aligned to what humans can do or, you know, we humans have done a lot of damage to our environments already, easy for our lives. But that said, there are different set of people, different persona group who have different set of needs. And often we forget that as well, right? So before I deep dive on the core principles of accessibility and all that, right? So this is more of something that stuck me when I was looking at what is accessibility and how easily that I can say to someone, right? With the next slide, I want you to, I'll make a quick pause, probably say 20 seconds or 10 seconds. You have a read for yourself and I hope that will give you some sort of sense on what is that you're going to learn if you're someone who's very new to accessibility. Or if you're already someone who know accessibility, that's great. This is something that you could also go forward and, you know, look at implementing it. I'll take a pause here. Cool. The pause is over. So I'm sure this is something would have already reflected in your mind, right? So I don't know how many of you had a smile after you read this. I had the first time when I looked at this picture, which is simple and easy enough that we think, oh yeah, it really makes sense.  So we talk a lot about, you know, our country, things especially coming from India, the transport is being bad, the roads are bad, and it's not accessible. But how, you know, what's the impact that we're making, right? I think forget about the technology, forget about digital accessibility. But this is all about what you can do to the human that is standing right next to you, who may be healthy, who may not be, who may be temporarily disabled. And it could be a number of situations that I spoke about, right? But when you think about that, I think that's where you may start making a small change for the better of the world. So with that, he'll take away as a learning. To me, accessibility is not just about physical conditions, right? It is not about physical condition at all. I perceive it more of a limited human interaction. So if we understand what that limited human interaction can do for our day-to-day lives, and if we find a ways to include them in the things that we do, I think that is great, right? Like say for example, if I'm using my computer to book, you know, flight tickets or air tickets. Yeah, it is developed with some ideology in mind that, okay, with someone who knows the civilized enough to know how to use a computer who can read English, who knows to use operate mouse, I think they can go ahead and click. But if you think of the other persona where someone who's blind or someone who is having vision but can't see different colors, you know, what is something that they would do, right? It'll become very hard for them to, you know, understand and go further with that. So to me, that is all about it. So this is something that I advocate wherever I go. And it's beat, I'm building a small house next to me and I'm making it more accessible as well. So that any guest that comes to my house will be accessible. And this is going to take forward in multiple ways in the society as well, right? And I think this is something that everyone should keep in mind and accessibility is not something, you know, you need a special learnings. And of course it has few nuances that you should learn and this session is going to be all about. And of this 45 minutes, I'm sure you'll be able to understand what are those at least and research by your own and try and contribute that. So as I've been keep on telling about the number of situations, right? So this is a beautiful piece of kit that Microsoft has provided, which is the Microsoft inclusive design kit, where it says about common things that humans do, right? So humans can touch, humans can see, humans can hear what is going around and humans can of course speak. But if we look at people who has some sort of disabilities, yeah, it's not their fault, right? I think some people born with some sort of disabilities and some people happen to be accidentally become one of that, you know, vulnerable to become one of those disabilities and also situational. Like if you look at, say for example, the first one like touch, there could be chances where you could have seen a human born without an arm and there's nothing wrong about it, right? I think it's all about if you find a ways to include them in our day to day lives and I think that's great. And an arm injury, I've broken my arms a couple of times during my childhood days and I know how hard it is.  And of course you have to operate it everything on your single hand, right? If the applications that you access is not able to do things, I think that is where we are talking about inaccessible. So how did we make it accessible? And I think moving on from here, digital accessibility, that's where it comes to. So now so far we have heard about what is accessibility and in real world how people think accessibility means. And I think that picture that I showed you would have given you some insights about how you should start perceiving accessibility itself, right? Yeah, I think, I hope my audio is clear. Yeah, yeah. So what I want to say is, so similarly, if the applications that you develop isn't accessible, then you're creating a barriers and making their impairment a disability. So the key words to notice here is the word impairment. Definitely they have an impairment, but it doesn't mean that, you know, they can't do things. They can do things provided if you find a ways to include them. And that is, this is all going to be. Now, this is great Manoj, I understand. You have opened my eyes. Now tell me, how should I make them, you know, make them use the applications with that limited interactions. When it comes to especially around digital accessibility, there is a group W3C group, I'm sure most of you have heard about it. For those of you don't know what W3C, it's the World Wide Web Consortium. So World Wide W3C standards define an open web platform for application development that has unprecedented potential to enable developers to create rich interactive experiences. So any spec, any technology that you see like PDFs, for example, how PDFs should behave in a web browser is like say automation tools like Selenium, how it should drive the browsers. So everything has a specification. And if you're developing one such it should abide by that. And that is what W3C all about. And when it comes to accessibility, there is a small group within W3C called the Web Accessibility Initiative, which is the Y group, WAI, where they have given a beautiful set of recommendations and guiding principles, which is the WCAG. We call it as WCAG, which is WCAG. And then that's nothing but the Web Content Accessibility Guidelines. And this itself will take a lot of time if I get into what the guidelines are, but I have a good picture that I will show you next couple of slides. And when you look at these principles, the next question that will come to you, come to your mind is, this is really great. I understand there are some principles that I can look at, but is there a way that I can measure against, you know, what is the target that I should have. If I'm taking accessibility as one of my bets that I'm going to solve in next year, how should I measure against? So typically, all these guiding principles has some sort of, you know, levels onto it. So I'm going to cover this as well in next couple of slides. But basically, all you should think is there is, you know, level one, there is level two and there is level three, right? Apparently that's nothing but level A, level AA and level AAA. As you see, level A means you're trying to adhere to the basic level of accessibility, which means you're trying to address and make sure your applications are accessible with some basic level of accessibility, like making sure at least the basics are covered. Like, something is better than nothing, right?  And it's been overall estimated around 1 billion people around the world have some sort of disability, right? And if you're building a product, which means, and if that product is not accessible, then you could imagine that, you know, you're losing out of business on that specific sort of people. So and the next level is AAA if that's the gold standard, which has around like 61 rules that you should abide by, right? And I think this is the levels that you could choose. And putting this all together, this is what the WCAG, you know, it tells about principles. It suggests that your application should be perceivable, operable, understandable and robust, and it has some guidelines on what you should do about it.  And if you feel, yeah, I'm already done with AA and I'm going a little bit aggressive and making sure I get it to, you know, a special set of people. So that's where, you know, level AA comes into picture. So like that it goes on and on. And I think level AAA is, you know, it's practically impossible. I wouldn't say impossible, practically challenging, because it has to adhere to a lot of things. And I think that's where the interesting conversation starts to begin between a product owner of BA and a QA, because a lot of attracting challenging sessions will happen. So I think in my experience, most companies try to aim at AA. I think a few government agencies like the Gov.UK, Gov.US in the Australia, in the Europe, I think those agencies will try to abide by AAA. Otherwise, I think AA in my opinion seems to be, you know, a decent contribution that you can make to make, you know, the digital applications more accessible for people. Now with that, how can I take this back into my, you know, software development lifecycle? So when this is an interesting question to ask for yourself, right? So this is something that I tell everywhere I go. I think in any situations you would have seen that people tend to throw things on over the wall, especially if you're a QA, you'll understand how things that happens. But when it comes to accessibility, I would say, I think, please stop there, understand. It's not someone else's job. It is everyone's responsibility. No matter what role that you play in your current job, it's your responsibility. Right?  I think that's, you should collaboratively, as a company, make sure that you arrive at that sort of, you know, collaborative and inclusive environment so that you think about those people and make sure, you know, you make ideologies and then take it from there. And I'll just speak to the next one. Yeah, so to begin with, in any, as if you're, you know, if your product is just shipping up and if you're trying to do, I think analysis and planning is one of the first things that you would do, right? So in my opinion, accessibility deserves a dedicated thinking and planning. But definitely, I'm not saying it should be done in isolation, right? Rather it should be integrated in your organization process. And there should be, and there will be some sort of legal requirements that will be needed depending upon which country you develop your product and which, where is your customer base. And if it's a global, that's great. You can just follow blindly the WCAG guidelines and pick up AA or AA as a success criteria. And that is good enough, right? But starting, I think early planning on accessibility, it'll lead to a lot of benefit, as I mentioned earlier. I think on an overall, if you look at in your experience, Manoj, tell me, I have a brown feed project. If I have to make my application accessibility, how much cost will take? I mean, I can't give you an exact number, but you could imagine somewhere between, you know, 40K or 50K dollars. So you can imagine, you know, if you spend that instead, you can avoid a legal risk, which will cost you billions and billions of lawsuits.  You can see how much they're paying back just because your applications are not accessible, where in that country, they have to be, you know, accessible enough. So yeah, you could avoid legal risk. You can strengthen your brand experience, customer experience automatically. So by being more accessible, your search engine optimization definitely gets increased. And you also, you know, try to tend to have the inclusive and productive teams. And so these inclusive design practices should be advocated very early enough. Like say, for example, one of the first things that you should you will be probably doing when you create a product roadmap is that, okay, a user goes to the website and do blah, blah, blah things. So when you define such sort of roadmaps, I think it's very important you should think of user personas with disabilities, right, with some user interaction. So when you do that automatically, a new set of feature or a new EPIC will automatically create it in an agile role in my opinion, and that's, I've seen that happening. So think about user personas with disabilities, design for user interactions, considers other experiences than a normal human would do, and automatically things will pick it up, right. And then finally, as I mentioned earlier, there are different levels. So, you know, understand the guidelines and see which user base that you cater to, which country you're coming from and try and add her to one of the standards. And I think that is a first step to start with. And really what's the next step at the design phase. It is all about, you know, starting as early as possible. I would say I already talked about analysis and planning phase thinking about product thinking about user personas. I think the immediate next step would be to start creating the UX prototypes. And it is also very important that you bake in accessibility at that stage early. So there are companies who follow some sort of design kits which will help them, you know, make a product seamless across different streams like you can take a look at Atlassian design kit. You can take a look at BBC British broadcasting. Global experience gel, so GEL gel is nothing but the global experience language where it is a document which shows you what an every accordion would should look like. How does the button should look like, how the link should be given. So, you know, by doing that way, you're making your product seamless. If you're a global product company, so that the UI itself is more seamless and looks pleasing and same across different, you know, different, different products as well as more importantly accessible, right. And when you look at the design phase, also, you can actually determine what are the colors that I'm going to do. Like I think the first thing that you will do is, you know, choosing a logo or, you know, picking up what should be the color theme of my website or the product. Right. I think in that way, if you think earlier about color contrast requirements or the color contrast guidelines from the WCG that I showed you earlier, I think you can easily, you know, cater to make sure that the color contrast is the same. Make sure that the color contrast is covered. And of course, think about technology that are inaccessible like flash, you know, flash is gone, but I think it's still there at some places and now even can was coming into picture. So you can think about carefully using the tech, making sure that it's accessible. And more importantly, contact a usability testing outside your organization, which will help you really understand, you know, where your product is, whether it's inclusive or not. And of course, the next is development phase where things get interesting, where it's very hard to convince your developers. But I think, as I mentioned earlier, if it's collaborative effort from the beginning, and I think this is something that can easily be tackle. In my experience, I've seen the checklist has worked often very well. So, you know, especially coming from a developer mindset, it is an essential at a planning stage when product requirements are defined and the design stage is created. And during development, the implementation of the product begins where if you have a checklist of, you know, things, and I have a link I'll actually share in the references or a little later. I think most of the things are can be, you know, looked at that checklist and make sure that you're making changes like it given at a story level if you want to make a change, you know, make sure that you abide by the checklist. I think that's that's good enough. And I think when it comes to accessibility, if you ask most developers, they would say yeah, I will fix it up with area. So that is something that we should don't think about so usage of area is should be done very judiciously. It's not like a patchwork to, you know, patch fix for your accessibility, right? So if you properly use your native HTML contracts, constructs, it will automatically fix accessibility issues for you. So you don't have to explicitly use or learn about area attributes so that you will fix accessibility accessibility is not just area, it's more than that. So even your proper HTML constructs will do the, you know, job for you. And more importantly, as I have as a second point, design what everyone can use and not what is easy to develop, right? And next is the most important in the testing phase where you should start considering people with disabilities for user testing. That is one of the foremost things. And we have a lot of tools and plugins in the accessibility space. And it's not a silver blood solution in any way. But it is estimated that it will try and fix you some 40 to 50% of accessibility issues for you. As I've kept on saying, something is better than nothing. So I think some start is better. It will help you fast track your process. You can include it within your CI CD pipeline. I think that's all great. And next, if as a testing strategy, if you're a QA or a test manager, or even if you're, you know, someone coming from a C-suite who's listening to the stock, even now or a little later in a YouTube, I think make sure, you know, accessibility is also big as part of your test pyramid. Like you have various levels of testing like unit integration and end-to-end. So make sure I know there are ways that we could include accessibility to each level, which I will cover that shortly. And specifically use screen readers. I think that is one of the main things. I'll actually have a demo and I'll be happy to show you in a couple of things, right? So and what is after testing, I think I don't have a slide next talks about what is next. I think it's more around, you know, maintenance and production monitoring and stuff. I think a couple of you would have seen or most of you have sort of a way to look at synthetic monitoring as a way. I think you can make an accessibility there as well. I think there's no harm in doing it. Since you're already doing at various levels, there could be something broken where you don't know. But I think it's great if something tells you that, you know, something is not accessible. And you can go and ask companies which does accessibility certifications to give you a VPAT or sort of a conformance document. So QA's can learn accessibility. Developers can learn accessibility. But when it comes to certification, it is a little risky. So ThoughtWorks doesn't do that or I highly doubt if services companies would do that. But there are specific, you know, companies who are dedicated for that who knows the in and outs of accessibility and who will certify you where you're up to, right? So with that, I'll deep dive on to the accessibility testing, right? So when we start early, you know, starting early brings in a lot of benefits. As I mentioned earlier, it's less costly than, you know, looking at, you know, solving lawsuits and stuff like that. And you should also make sure the designers, the product owners and everyone is onboarded. I think the most robust way to ensure the long term accessibility is to make sure that the accessibility as a knowledge is being, you know, inculcated within the culture. And if inclusive practices is not one of the culture, I think go ahead and make and advocate that for your organization and then keep that as, you know, upcoming bets to something that you could solve. There is no substitute for real user feedback include people with disabilities to test. I think this is something that I always say there are tools and we are super smart and good enough and there are some tools which claim a can solve things for you from accessibility. Honestly, I don't believe so please go ahead and include the real people with disabilities to test. So what is something that we can test for so you talk about, I think if you just, you know, quickly step back and see what we have learned so far.  And I spoke and I mentioned you about some guidelines and I told you about there are different levels about it. And then we slowly transition into how accessibility can be fit into different levels, right. And now we are specifically deep diving on to accessibility testing as a phase and what is something that you could, you know, do keep on doing. And these are some of the things that you can actually test for like and test for keyboard navigation landmarks color contrast assistive devices. And in the previous slide if you remember I had a point which said that it's not a silver bullet which is still true. But if you remember it had a mention that around 40 to 50% it can solve so that is this slide talks about right. So if you make sure these things are covered, I think that easy 40 to 50 is automatically covered. And again this is not a silver bullet sort of like make sure you go test this and it'll automatically be 50% done. No, it's not that it's coming in from experience that I have made sure these things are covered in the applications that I test and I contribute to. And I've seen good progress with that. With that, I have four demos to show you will see if I have enough time to show that quickly one by one. Firstly I will show you a wise over demo. I think as I've been mentioning about screen really testing is something very important that you should go and advocate for.  When you do an exploratory testing. So just turn on your voice over if you're on a Mac or if you can install tools like Jaws for Windows and and even if you test or develop for Android and I was it has similar screen data options, which is nothing but the assistive devices we call it as assistive devices right where it'll help people with disabilities or people who can't see who can't hear will use these devices to navigate things around. And with that I'll quickly show you I'm hoping you can hear the voice over. Hey, I've turned on voice over. Chrome bit busy busy. Well, I'm feeling lucky button Google search by voice search list box pop up menu pop up combo box. A G I L E agile I N D I A in the agile India Google search leaving agile India Google search Google Chrome in Kotlin. So I had a quickly pause so that I can tell you and I walked through. So if you look at the this is nothing but the voice over right so as and when you move changes around like whether if you use a mouse or a keyboard, it will actually start dictating whatever you see right. So if you see when I press tab on my keyboard it automatically should skip to main content. So which is also one of the things that we should be making sure that is covered. If you're already testing a web application, load up the, you know, refresh the URL and just plainly click a tab button on your keyboard and it should show something like that because automatically it'll skip to the main content on the page. So in this case, the results on agile India is very important for me so that I can skip into it. Rather, I don't want, you know, the voice over to keep talking about all news maps images and all of those stuff. But in this case it automatically moved into it. So now what I'm going to do is click on agile India go inside the website and then do a few stuff. I don't know if you closely watched it it shows it said link twice but it didn't highlight anything which is an issue that you know, I think I'm one of the organizers to we as a team should fix our webpads. But I think after that it shows you where the focus is on like link sponsors and schedules and most importantly it didn't show the skip to main content as well. I'll quickly. So in this case if you see I moved on to the speakers page but then it's still dictating my, you know, the menu which as a user I don't want it right so you'll be annoyed by looking at it again so in this case I ideally I would like to have a skip to main content button so that I'll directly jump into the most very interested speaker I'm in so that I can listen to the talk. So I think I hope this would have give you some, you know, view about how, you know, what you're going to do. I think I'm going to have a skip to main content button so that I can listen to the talk. So I think I'm going to have a skip to main content button so that I can listen to the talk. So I think I hope this would have give you some, you know, view about how, you know, why so what testing is all about. So now if you're testing on a web application or whatever desktop application, turn on this voice over and see what it talks about right if you see. And this is not bad, you know, if you can, it mentions link speakers link schedule so that I if I'm blind, I am able to understand I'll just click on enter. But then I'll go into into that page. But if I'm something, you know, I can't see where it goes. I don't have an idea which which which page I'm thinking about it and that's something that you should look at. And now, in order to, you know, look at how things you can what are the different things that you can do. So the next thing that I usually do is to use plugins. One of the things that I use is axe DevTools web access everybody testing so you can just include a plugin and then just go from there. Where I okay I just saw an application that I built I mean reusing from Harris Harris from DQ has this wonderful workshop that I attended and I had an opportunity to reuse the same stuff. So I go and inspect, and I've already added the axe DevTools in my browser so all I'm going to just click is scan, click on DevTools and I scan all of my page. And it showed me it has two issues, right so automatically it shows element must have sufficient contrast and of course this one right is very important and it is one of the, you know, perceivable guidelines that even people with color blindness or with less vision or low vision should be able to look at the applications. And it will highlight you and also you can go and inspect and find out why it is there so this is the color button. And one of the quick fixes that even you know rather than finding a bug about color contrast you can even guide your developers and say that hey this is a bug that the DevTools shows. So when you click on this, it actually shows you by contrast ratio is just 1.19. But if you're abiding by the rule AA or AAA the conformance levels that I mentioned you earlier. It should, it says that if you're looking at abiding by AA it should already be at level three, but right now it is just at 1.919. So simply you can just, you know, drag this bubble and come inside this line, which means that okay you are good from a AA level which means that right now I'm at 3.7. And also you can actually naturally notice that this is becoming more visible even as a naked, you know, eye user. And if you're so as I mentioned if you're super aggressive about accessibility and wanted to be the gold standard, you know, further drag even more down. And you can see this is also picked where your contrast ratio is 5.73. And this is a generic rule, right? And this is just doesn't change per the color that you're looking at. So in any page that you take, if you're abiding by having 4.5 as a contrast ratio, that's good enough. That will work simply work for any page, a foreground background. So now you can see the text is also more visible. So this is one of the things that you could see and it has been estimated that at least out of, remember the WAI group that I mentioned. So they estimated at least 97% of accessibility issues that they have seen will fall under six categories, only six categories. So if you remember what is that six categories and make sure you fix them, you're already in a much better shape than, you know, having an application that is not accessible in that six color contrast is one of them. I know by now you'll be super interested to know, just give me that six and I'm done. Don't worry, I have a slide and I'll show you towards the end of the session. And Microsoft also have something called accessibility insights. This is something that you could install. It is more or less like Axe DevTools. And more importantly, you should also heard about Lighthouse, which has accessibility as well. So Lighthouse by Google under the hood uses Axe Core, which is nothing but this Axe DevTools. So in my opinion, it's either as fine should have to keep on using everything. So if you use either of these, that is great. And this is just for a plugin-based testing or a screen reader-based testing. This is, as I mentioned, accessibility is everyone's job. Everyone in the team can do it. So now if you're a QA or a Dev and if you're looking at what you want to do, as I mentioned, you could come and fix this. We have changed this color to be, say, 4.7 or 5.7. Grab the hex value, go to your CSS file and you would change it as a Dev. And that's pretty much it. So now what are the other things that you could do in here? I have two different workspaces. I think both of them will be in my GitHub page. You can take a look at it. So I have an end-to-end test folder, which has a complete test for each pages, which is nothing but this page. It's a simple website. I'll just quickly, it's in Agile India, which has actions. So if I just do tab, it should come here and just keep on going. Tab specifically, I'll do stuff. And if I go to about page, it's just a couple of things around here and also a contact on a form where if I keep on doing a tab, it should focus each and everything. So which means that if you don't have access to a trackpad or even a mouse, you should be able to navigate by a keyboard. So that is one of the things that I mentioned on the QA testing aspect as well, where keyboard navigation is one of the things that you should look at it. And I have this website where we are closely running on time. Let me quickly show this up. So yeah, right now if you see, I'll just refresh this website and I'll do the tabbing. I'm not using a trackpad at all. It shows skip to main content and then it's coming here. So now I don't, I didn't click on skip to content. Now if I'm doing skip of the main content, it automatically comes to the contact page. And now I'm checking in message and asking Naresh, what do you call sheep without no legs? It's just a small pun. It already says he says it's a cloud, right? So you could imagine it's just a diagram of the cloud. So everything is done within a keyboard. So you could imagine without using mouse, you're able to do stuff, which is really great. And if you're able to do this in your applications, and that is what more important as well. And now specifically coming back to, you know, testing as such, what is something that you could really do? Well, we had a menu button which has the actions, right? So ideally what we should be doing is focus on the menu button, the actions. And then without using mouse or a trackpad, if you click on the, you know, up arrow and down arrow, it should be able to traverse up and forth, right? I think that is exactly what, you know, the test does here where you're trying to look at it. And there are many other stuff which we have written here, like role as a button. And even like say for example, let me go to my index. The role is a very important item. Like say for example, we have a menu item and we say the role of that button is a menu. So if I go and change, like say for example, you know, agile India, it shows an error, right? So which is nothing but an error which shows elements with earlier roles must use to valid and non-obstruct earlier roles. And this error message is coming in from an excellent plugin that I'm using in this repository, which is called JSX Ali area role. So by this, what I'm trying to say is you don't have to keep on writing an end-to-end test or use a plugin or use a screen data to do testing. But as a developer when you write, when you, you know, write your HTML code, if you make any small mistakes, it'll automatically show you. It's nothing but code linting or scanning tool, which we normally use, right? And this is something that you could use. And if it'll go back to my package.js and I have something here like eslin plugin JSX Ali. So as a dev, it'll be super awesome. It'll be helpful. Like when you write a component, a piece of code, it'll tell you where it goes wrong. And the next demo that I had was a completely, you know, a web driver IO based demo where it'll, you know, this is nothing but a page object pattern where I have a base page homepage and a menu page and I have a spec file and I run the spec file. It'll, you know, the web driver test will go to that website and land on that website. As in when it lands, I'm using acts to scan my page and I'm just saving that results in a CSV file. So this is something that it shows as a result that ensure contrast between the foreground and color meets. And, and it'll tell you, it'll give you a HTML dump also so that you can fix it things online. And more than that, one of the things beautiful things about acts that I like really is all about the link that it shows. Like when you click on this link, it'll actually show you what are the things that you would want to fix as well. Right. So it'll also show you how to fix the problem and why it matters so that you also learn while you fix things. So that is one of the good things. So go ahead, you know, use tools like acts and I'll open source it with my GitHub repo at the rate of Manoj 9788. And that's my GitHub ID also can keep watching and keep doing that. Yeah, just a heads up like, yeah, we just have a couple of minutes more. Yeah. Yeah. So I'm putting this all together. Here I present to you the accessibility test pyramid we have seen about accessibility, you know, test pyramid or, you know, the diamond or a champion trophy. I wanted to try different. So here is the accessibility test pyramid I showed you about the static linting checks. So there you go. That's at the bottom. You can tools like that. So this shows you accessibility is everyone's responsibility where user persona something you could do it early when it comes to development. Right. When when you code, it'll show you using those plugins. And as a unit test, if you're using X core or adjust tools, you can integrate with those and do some sort of integration testing. And as a QA, if you're running an end to end test automatically, you can integrate with Selenium and Cypress and also use the plugins that I mentioned to you, right? I think that I showed you something that you can do now to scale it further. So by the moment you integrate into the test pyramid or have an auto into an automated framework, you can obviously scale this into a path to production. Right. And of course I wanted to present to you again, an inclusive path to production. I don't know if I've seen this word everywhere outside, but this is something I think it's quite new. So inclusive path to production, right from concept to deploy to production to disaster recovery. There are different stages as per your product. You will have different builds. And this is something that I currently practice and advocate for my toolbox clients where where where you can do what sort of accessibility testing. So as you see, the things in that are grade out or something that is not necessary for this session, but also very important. But the things that are highlighted in Ali or something that is very important and also a key takeaway for you as well. So take a look at it offline if you have any questions, you can ask me around it. And these, this is nothing but the six common errors that I talked to you about. So low contract stacks, missing alternative, missing input labels, you know, empty links, empty buttons, document language. So these are the things that are significantly will improve if you, you know, make sure that this is not something happening in your things. So I think I think this mostly end of my session with that. I just wanted to thank you so much for people joining and I consider this as a passion. Let us hear, you know, I see a couple of people already here. And if you're already coming into the session, which means that you already care for accessibility. So that inclusive mindset is already within you, or even for people watching this offline in a YouTube or little later.  Be an inclusive tech disruptor, not just a tech disruptor, but as an inclusive tech disruptor. And I do hope that you had some of that key takeaways from the session and then, you know, make the world more digitally connected with inclusive inclusivity. And this is some of the links to refer you can go ahead and refer. And lastly, thanks for the opportunity to talk about an important topic that I most care about. And not only my talk and I think there were two other talks that spoke about importance of agility and inclusivity. So please go ahead and check out the other talks as well. And I think as a conference, I think this is something we care about a lot and lots of gifts out there and happy Thanksgiving and a new year to everyone. Thank you. Thank you so very much. So there was so much information about all about accessibility and especially inclusive path to production was something really new and yeah there's so much learnings there. And I'm sure a lot of people have enjoyed the session and they got a lot of takeaways.