Difference between revisions of "Team:Vilnius-Lithuania/Inclusivity"

 
(17 intermediate revisions by 4 users not shown)
Line 1: Line 1:
<html>
+
<html>  
<head>
+
  <head>  
  <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/main&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
+
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/main&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>  
  <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/fonts&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
+
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/fonts&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>  
  <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/background&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
+
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/background&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>  
  <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/contentpage&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
+
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/contentpage-desktop&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>  
  <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/sideindex&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
+
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/contentpage-mobile&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
  <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/navbar&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
+
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/sideindex-desktop&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>  
  <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/navmenu-desktop&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
+
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/sideindex-mobile&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
  <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/navmenu-mobile&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
+
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/navbar&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>  
  <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/accesibility-menu-desktop&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
+
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/navmenu-desktop&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>  
  <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/accesibility-menu-mobile&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
+
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/navmenu-mobile&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>  
  <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/button-pill&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
+
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/accesibility-menu-desktop&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>  
  <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/footer&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
+
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/accesibility-menu-mobile&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>  
</head>
+
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/button-pill&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>  
<body>
+
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/footer&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>  
  <div class="navbar-container">
+
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/table&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
  <nav class="navbar">
+
    <link href="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/styles/bypass-block&amp;action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css"/>
    <a class="navbar-logo" href="/Team:Vilnius-Lithuania">
+
  </head>  
    <img alt="AmebyeLogo" src="https://static.igem.org/mediawiki/2021/b/b0/T--Vilnius-Lithuania--amebyeLogo.svg"/>
+
  <body>  
     AmeBye
+
    <div class="navbar-container">  
    </a>
+
      <nav class="navbar">  
    <ul class="nav-menu">
+
        <a class="bypass-block-link visually-hidden visible-when-focused" href="#main-content">Skip to main content
    </ul>
+
        </a>
  </nav>
+
        <a class="navbar-logo" href="/Team:Vilnius-Lithuania">  
  <div class="progress-container">
+
          <img alt="AmebyeLogo" src="https://static.igem.org/mediawiki/2021/b/b0/T--Vilnius-Lithuania--amebyeLogo.svg"/>      AmeBye  
    <div class="progress-bar">
+
        </a>  
    </div>
+
        <ul class="nav-menu">
  </div>
+
        </ul>  
  </div>
+
      </nav>  
  <div class="background">
+
      <div class="progress-container">  
  <canvas id="background-canvas">
+
        <div class="progress-bar">
  </canvas>
+
        </div>  
  <div class="app-header">
+
      </div>  
    <h1 id="title">
+
      <div class="animation-container">  
    INCLUSIVITY
+
        <script>     document.querySelector('body').classList.add("content-hidden");
    </h1>
+
          window.addEventListener("load", function() {
    <div class="app-header-image-wrapper" id="img">
+
            setTimeout(function() {
    <img alt="Header" src="https://static.igem.org/mediawiki/2021/d/de/T--Vilnius-Lithuania--placeholder.png"/>
+
              document.querySelector('body').classList.remove("content-hidden");
    </div>
+
              document.querySelector('.animation-container').classList.add("loaded");
  </div>
+
              document.querySelector('.animation-container').innerHTML="";
  <div class="app-content">
+
             }
    <div class="app-content-text">
+
                      , 200);
    <div class="content-page-container">
+
          }
        <h3 class="index-headline">
+
                                );
             Introduction
+
        </script>  
        </h3>
+
        <div id="loading-animation">
        <p>
+
        </div>  
            Last year the world faced an unpredicted mass pandemic which has already caused more than 4.4 million deaths, according to WHO (World Health Organization) . However, it is not the only disease that is encroaching on human lives. Over the last 30 years, the world has faced at least 30 new infectious diseases, including Swine flu, well-known Ebola, SARS, etc. There are beneficial conditions for that - favorable climate and weather, ecosystem changes, human susceptibility to infections, international trade, and travel, or even lack of public health services. All factors sum up and contribute to the excellent environment for the new emerging or reemerging infectious diseases.
+
        <div>Loading...
 
+
        </div>  
        </p>
+
        <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/lottie&amp;action=raw&amp;ctype=text/javascript" type="text/javascript">
        <p>
+
        </script>  
            One of the examples - amoebiasis, an infectious disease caused mostly by Entamoeba histolytica. E. histolytica (Amebos paveikslėlis) cysts enter the human body orally through contaminated food, water or human to human contact. For this reason, this infection mainly affects the developing world in tropical and subtropical regions where there are poor sanitation, lack of publicly available health care, favorable climate for pathogens propagation, lack of knowledge about food processing and keeping conditions, defecation into water sources such as rivers, and being near animals. (Vizualas: ikonėlės atliepiančios amebiazės plitimo priežastis). After exposure to E. histolytica cysts, excystation occurs in the small intestine with the release of motile trophozoites. Trophozoites then migrate to the large intestine where they mature and begin encystation. There are two possible pathogenesis pathways. First, trophozoites stay in the large intestine, proliferate, do not cause any symptoms, and leave the intestine as newly formed cysts.  In this case, an infected person becomes an infection carrier. Second,  trophozoites might proliferate if the infected faces stress or microbiota disruptions. In this case, trophozoites adhere to the colonic epithelium by Gal/GalNac lectin, secrete proteolytic enzymes, amebaphores, causing cell lysis, or conduct contact-dependent target cells lysis. It leads to the destruction of the protective mucous barrier, surrounding cells fagocytation.
+
        <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/loading_animation&amp;action=raw&amp;ctype=text/javascript" type="text/javascript">
        </p>
+
        </script>  
        <p>
+
        <script>     var animation = bodymovin.loadAnimation({
            Symptoms of intestinal amoebiasis include abdominal pain, ulcerative colitis with mucus and blood, bloody diarrhea which later on progresses to raspberry-jelly-like stool, appendicitis, and ulcers. However, in more progressed inflammation, trophozoites from the intestine travel through the portal vein into the liver and cause an amoebic liver abscess, or less frequently lung, brain abscess, or skin infection. (Proceso iliustracija: žmogus (žemiau pateiktas paveikslėlio pvz), jame gif formatu pavaizduota histolytica kelionė (per burną, į žarnyną, kur iš rutuliuko virsta į banguojačią dėmelę, per vartų veną į kepenis ir vėliau į plaučius, smegenis nukeliauja).
+
             container: document.getElementById('loading-animation'),       animationData: loading_animation,       renderer: 'svg',       loop: true,       autoplay: true,     }
        </p>
+
                                                            );
        <div class="figure-container">
+
        </script>  
            <img alt="" src="https://static.igem.org/mediawiki/2021/d/de/T--Vilnius-Lithuania--placeholder.png"/>
+
            <div>
+
              <b>
+
              Fig 1
+
              </b>
+
              <b>
+
              .
+
              </b>
+
              Aprasymas
+
            </div>
+
        </div>
+
        <h3 class="index-headline">
+
            Antraste 2
+
        </h3>
+
        <a
+
        href="https://static.igem.org/mediawiki/2021/5/58/T--Vilnius-Lithuania--Prokaryote_genome_quality_assessment.pdf"
+
        download
+
        >
+
            Supplementary data
+
        </a>
+
        <p>
+
            <i>Italics tekstas</i>Cras [1] ultrices eu massa vitae congue. Vestibulum arcu enim, congue              id lacus at, laoreet fringilla tortor. Praesent libero nunc,              maximus vel suscipit nec, fringilla sed augue. Praesent porttitor              vehicula efficitur. Aenean ac bibendum lectus. Praesent vestibulum              velit ut nunc accumsan, non molestie erat pretium. In a ante              vulputate, semper sapien at, tristique erat. Morbi vitae euismod              eros, at pulvinar erat. Vivamus auctor arcu sed tellus egestas,              vitae imperdiet eros viverra. Nulla molestie sapien vitae ipsum              pulvinar dictum. Sed sit amet dolor a neque dictum malesuada et              nec lectus. Aenean tristique ornare nisl, at imperdiet magna              placerat eget. Suspendisse ut blandit elit, sit amet iaculis ex.              Nam vel varius velit. Aenean pretium scelerisque enim, quis mollis              nunc finibus eu.
+
        </p>
+
        <p>
+
            <i>Italics tekstas</i>Cras [1] ultrices eu massa vitae congue. Vestibulum arcu enim, congue              id lacus at, laoreet fringilla tortor. Praesent libero nunc,              maximus vel suscipit nec, fringilla sed augue. Praesent porttitor              vehicula efficitur. Aenean ac bibendum lectus. Praesent vestibulum              velit ut nunc accumsan, non molestie erat pretium. In a ante              vulputate, semper sapien at, tristique erat. Morbi vitae euismod              eros, at pulvinar erat. Vivamus auctor arcu sed tellus egestas,              vitae imperdiet eros viverra. Nulla molestie sapien vitae ipsum              pulvinar dictum. Sed sit amet dolor a neque dictum malesuada et              nec lectus. Aenean tristique ornare nisl, at imperdiet magna              placerat eget. Suspendisse ut blandit elit, sit amet iaculis ex.              Nam vel varius velit. Aenean pretium scelerisque enim, quis mollis              nunc finibus eu.
+
        </p>
+
        <p>
+
             <i>Italics tekstas</i>Cras [1] ultrices eu massa vitae congue. Vestibulum arcu enim, congue              id lacus at, laoreet fringilla tortor. Praesent libero nunc,             maximus vel suscipit nec, fringilla sed augue. Praesent porttitor              vehicula efficitur. Aenean ac bibendum lectus. Praesent vestibulum              velit ut nunc accumsan, non molestie erat pretium. In a ante              vulputate, semper sapien at, tristique erat. Morbi vitae euismod              eros, at pulvinar erat. Vivamus auctor arcu sed tellus egestas,              vitae imperdiet eros viverra. Nulla molestie sapien vitae ipsum              pulvinar dictum. Sed sit amet dolor a neque dictum malesuada et              nec lectus. Aenean tristique ornare nisl, at imperdiet magna              placerat eget. Suspendisse ut blandit elit, sit amet iaculis ex.              Nam vel varius velit. Aenean pretium scelerisque enim, quis mollis              nunc finibus eu.
+
        </p>
+
        <ul>
+
            <li>Item 1</li>
+
            <li>Item 2</li>
+
            <li>Item 3</li>
+
        </ul>
+
        <ol>
+
            <li>Item 1</li>
+
            <li>Item 2</li>
+
            <li>Item 3</li>
+
        </ol>
+
    </div>
+
    <div class="references-wrapper">
+
      <div class="breaker">
+
 
       </div>
 
       </div>
       <h2>
+
    </div>
      References
+
    <div class="background">
       </h2>
+
       <canvas id="background-canvas">
       <div class="references-container">
+
      </canvas>
      <div class="number">
+
      <canvas id="canvas-transition">
         1.
+
       </canvas>  
      </div>
+
       <div class="app-header">  
       <div>
+
        <div class="app-header-image-wrapper" id="img">
        Trundle, K. Teaching Science During the Early Childhood Years. National Geographic Learning (2010).
+
          <h1 id="title">            INCLUSIVITY         
      </div>
+
          </h1>
      </div>
+
          <img alt="Header" class="cover" src="https://static.igem.org/mediawiki/2021/e/eb/T--Vilnius-Lithuania--Inclusivity.JPG"/>  
    </div>
+
         </div>
    </div>
+
      </div>
    <div class="index-container">
+
      <div class="app-content">
    <div class="index-header">
+
        <div class="app-content-text">
    </div>
+
          <div class="content-page-container">
    <div class="index-content">
+
            <h3 class="index-headline">          Introduction         
    </div>
+
            </h3>
    </div>
+
            <p>          At Vilnius-Lithuania iGEM, we recognize the importance of         
  </div>
+
              <b>            diversity and inclusion         
  <footer>
+
              </b>          within the science field. We are committed to making the synthetic biology community more open and creating a learning environment where everyone feels welcome.         
    <div class="logo-igem">
+
            </p>
    <object data="https://static.igem.org/mediawiki/2021/f/ff/T--Vilnius-Lithuania--iGEM-2021.svg">
+
            <p>          On 2024 September 1st changes of article 14 of the Education Law of the Republic of Lithuania comes into force and a new inclusive education chapter begins. Every general education school should be ready to accept and educate students with disabilities. However, currently not enough measures are taken to reach this goal. We learned this from numerous calls with special pedagogues, students with disabilities and others working in the inclusivity field.         
    </object>
+
            </p>
    </div>
+
            <p>          During our consultations with practitioners working with disabilities, it was often stated that         
    <div class="social-container">
+
              <b>            negative experiences in school, pessimistic outlook coming from the teachers and lack of exposure to the inclusivity of universities         
    <div>
+
              </b>          discourage pupils from fulfilling their academic potential later in life. Moreover, one of our consultants, Dr. Barbara R. Heard, an associate biology professor who focuses on inclusive education, claimed, there are still many complicated areas relating to inclusive education (read the full consultation         
      FOLLOW US
+
              <a href="https://2021.igem.org/Team:Vilnius-Lithuania/Human_Practices              " target="”_blank”">            here</a>). According to her, it is crucial to focus on changing the outlook on the problem to induce progress. This and other consultations inspired us to become the change ourselves.  <b> While planning our educational activities and thinking about the design and presentation of our project, we followed an inclusive approach. </b>         
    </div>
+
            </p>
    <div>
+
            <p>          Our main focus groups were people with         
      <div class="placeholder-social-icon">
+
              <b>            vision and intellectual disabilities.         
      </div>
+
              </b>          First, we chose audience with visual impairments due to the fact that most of the education material is visual - it takes the form of illustrations, graphs etc. This means people with impaired vision do not have a chance to learn more specific subjects like synthetic biology. Second, individuals with  <b>cognitive disabilities</b>  were chosen due to common underestimation of their abilities. Meaning that such people might not receive information on complex yet significant topics of contemporary society like vaccines, GMO’s etc.         
      <div class="placeholder-social-icon">
+
            </p>
      </div>
+
            <h3 class="index-headline">          6th SynBio sense         
      <div class="placeholder-social-icon">
+
            </h3>
      </div>
+
            <p>          As a way to make “6th SynBio sense” platform more inclusive we set several goals. First, we applied         
    </div>
+
              <b>            accessibility tools         
    </div>
+
              </b>          to the platform’s web page. As mentioned above, we made sure that the website is accessible for color blind people, by choosing the right color palette and keeping the right contrast ratio between text and background (Fig. 1).        
    <div class="mail-container">
+
            </p>
    <div>
+
            <div class="figure-container">  
      CONTACT US
+
              <img alt="Illustration of how our page looks originally, for people with deuteranopia, protanopia and tritanopia" id="Figure1" src="https://static.igem.org/mediawiki/2021/6/6d/T--Vilnius-Lithuania--website_adaptation-03.png"/>
    </div>
+
              <div>
    <a href="mailto:info@vilniusigem.lt">
+
                <b>            Fig. 1.           
      info@vilniusigem.lt
+
                </b>            Accessibility adaptations on “6th SynBio sense” website         
    </a>
+
              </div>
    </div>
+
            </div>
    <div class="grid-sponsors">
+
            <p>          What is more, as the website contains a lot of written information, it was important for us that it is readable for everyone, therefore we applied a         
    <div>
+
              <b>            font changing function         
      <object data="https://static.igem.org/mediawiki/2021/d/dc/T--Vilnius-Lithuania--VU.svg">
+
              </b>          for people with dyslexia. (Fig. 2) We also made         
      </object>
+
              <b>            sound recordings         
    </div>
+
              </b>          of the provided information for users, who have vision deficiency. In general, we tried to keep the design of the website minimalistic and with as few distractions as possible, to keep the main focus on the augmented reality models and provided information.         
    <div>
+
            </p>
      <object data="https://static.igem.org/mediawiki/2021/b/bb/T--Vilnius-Lithuania--GMC.svg">
+
            <div class="figure-container">
      </object>
+
              <img alt="Illustration comparing original text and text modified for dyslexia" id="Figure2" src="https://static.igem.org/mediawiki/2021/2/2d/T--Vilnius-Lithuania--modification_for_dyslexia.png"/>
    </div>
+
              <div>
    <div>
+
                <b>            Fig. 2.           
      <object data="https://static.igem.org/mediawiki/2021/d/df/T--Vilnius-Lithuania--SnapGene.svg">
+
                </b>            Modification for dyslexia on “6th SynBio sense” website         
      </object>
+
              </div>
    </div>
+
            </div>
    <div>
+
            <p>          We also wanted to make 3D models accessible for the blind. To reach the goal, we teamed up with a biology teacher Gintaras Nenartavičius from the Lithuanian Center for the Development of the Blind and Visually Impaired. We learned about the most used educational tools and decided to implement this knowledge into our project. After thorough consultations with an expert teacher and 3D printing specialist, we         
      <object data="https://static.igem.org/mediawiki/2021/b/bf/T--Vilnius-Lithuania--Termofisher.svg">
+
              <b>            printed 3D models         
      </object>
+
              </b>          of virus and protein translation as well as         
    </div>
+
              <b>            tactile schemes         
    <div>
+
              </b>          of protein synthesis, synthetic biology, genetic scissors, DNA, RNA, and SARS-CoV-2 virus. (Fig. 3) To test out the tools ourselves, we prepared a lesson for the students at the same institution. At first, we thought it would be rather challenging to educate people that lack one of the most commonly used senses. However, our experience was positive. Pupils were attentive and their teacher assisted us in handing out tactile models and explaining what is pictured there. Moreover, headings with some explanations of what is seen in the picture were provided         
      <object data="https://static.igem.org/mediawiki/2021/9/98/T--Vilnius-Lithuania--Nanodiagnostika.svg">
+
              <b>            in Braille.         
      </object>
+
              </b>          This simplified the process greatly and helped children to follow our lecture.         
    </div>
+
            </p>
    <div>
+
            <div class="figure-container">
      <object data="https://static.igem.org/mediawiki/2021/3/3e/T--Vilnius-Lithuania--Laborama.svg">
+
              <img alt="Photograph of person reading braille." id="Figure3" src="https://static.igem.org/mediawiki/2021/0/02/T--Vilnius-Lithuania--tactile_model.jpg"/>
      </object>
+
              <div>
    </div>
+
                <b>            Fig. 3.           
    <div>
+
                </b>            Tactile schemes explaining the basics of synthetic biology         
      <object data="https://static.igem.org/mediawiki/2021/1/16/T--Vilnius-Lithuania--Telesoftas.svg">
+
              </div>
      </object>
+
            </div>
    </div>
+
            <p>          Finally, we saw potential in making “6th SynBio sense” even more inclusive by         
    <div>
+
              <b>            simplifying descriptions         
      <object data="https://static.igem.org/mediawiki/2021/c/c1/T--Vilnius-Lithuania--Biotecha.svg">
+
              </b>          of each model to make them suitable for people with intellectual disabilities. This idea came after encountering an Istanbul convention adapted to autistic people. We contacted a representative from the National Agency for Education Inclusivity department to help us and review our adapted texts. As we found, the key things to an inclusive text are         
      </object>
+
              <b>            giving clear instructions         
    </div>
+
              </b>          on what is seen on the screen,         
    <div>
+
              <b>            explaining complex terms         
      <object data="https://static.igem.org/mediawiki/2021/7/70/T--Vilnius-Lithuania--Kopicentras.svg">
+
              </b>          separately, adding         
      </object>
+
              <b>            examples from real life         
    </div>
+
              </b>          and keeping to the main idea of the text. We also used “Internet for everyone” [1] guide for any extensive inquires.  Simplified descriptions currently are only in Lithuanian and can be accessed while previewing the text information.         
    <div>
+
            </p>
      <object data="https://static.igem.org/mediawiki/2021/4/4f/T--Vilnius-Lithuania--Grida.svg">
+
            <div class="figure-container">
      </object>
+
              <img alt="Illustration comparing regular text and its version in simple language." id="Figure4" src="https://static.igem.org/mediawiki/2021/9/96/T--Vilnius-Lithuania--simplified_description-04.png"/>
    </div>
+
              <div>
    </div>
+
                <b>            Fig. 4.           
  </footer>
+
                </b>            Example of simplified description         
  </div>
+
              </div>
  <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/navigationTabs&amp;action=raw&amp;ctype=text/javascript" type="text/javascript">
+
            </div>
  </script>
+
            <h3 class="index-headline">          Wiki accessibility         
  <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/background&amp;action=raw&amp;ctype=text/javascript" type="text/javascript">
+
            </h3>
  </script>
+
            <p>          Our goal this year was to make Wiki clear, intuitive, and accessible.         
  <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/contentpage&amp;action=raw&amp;ctype=text/javascript" type="text/javascript">
+
            </p>
  </script>
+
            <p>          Before digging deeper into the Wiki implementation, we decided to develop it according to         
  <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/navbar&amp;action=raw&amp;ctype=text/javascript" type="text/javascript">
+
              <b>            WCAG documentation         
  </script>
+
              </b>          [2] in order to make it         
  <script>
+
              <b>            accessible.         
  contentPage(        "Sections",        true,        300,      )
+
              </b>            WCAG stands for Web Content Accessibility Guidelines. It is a document that includes many recommendations to make Web content more accessible. We set ourselves a goal to make our Wiki meet as many as possible of the WCAG         
  </script>
+
              <b>            A and AA level requirements.         
</body>
+
              </b>            WCAG contains a rich list of specifications and in order to affirm our plan, which of them are the most sensible to realize, we organized a consultation with Jurij Nesvat - a testing engineer, specializing in         
 +
              <b>            testing accessibility         
 +
              </b>          of Web pages. Together we reviewed and         
 +
              <b>            confirmed         
 +
              </b>          our plan that we set ourselves to fulfill.         
 +
            </p>
 +
            <p>          <b> The plan included ‘A’, ‘AA’ level requirements and optional adjustments for groups with cognitive disability and dyslexia.</b>
 +
            </p>
 +
            <p>          The ‘A’ level requirements that demanded our attention, since they were not as intuitive as the others, were: making the website accessible by     
 +
              <b>            keyboard only,        
 +
              </b>            avoiding presentation that relies         
 +
              <b>            solely on color,         
 +
              </b>            paying attention that content would not have elements causing more than         
 +
              <b>            three flashes per second.         
 +
              </b>
 +
            </p>
 +
            <p>          The AA level requirements applied in our Wiki development were: making the website responsive to         
 +
              <b>            various screen sizes,         
 +
              </b>            introducing         
 +
              <b>            high contrast         
 +
              </b>          between pieces of text and their backgrounds, using clear headings and labels, making focus         
 +
              <b>            visible,         
 +
              </b>            making         
 +
              <b>            consistent         
 +
              </b>          navigation and identification. These requirements were the ones that we focused on, since the thoughtful implementation of them is exactly what contributes to reaching our goal related to Wiki development.         
 +
            </p>
 +
            <p>          Besides the adjustments determined by WCAG protocol, we also added a couple of functionalities in the         
 +
              <b>            accessibility toolbar:         
 +
              </b>          one that introduces markings for people with         
 +
              <b>            cognitive disabilities         
 +
              </b>          and another that changes the font of the text to         
 +
              <b>            dyslexia-friendly.         
 +
              </b>          Cognitive disability profile adjustments include highlighting of the         
 +
              <b>            buttons, headings and links,         
 +
              </b>          which makes it easier to navigate through the most important parts of the content. Dyslexia-friendly customization changes the font to make the text         
 +
              <b>            easier to read.         
 +
              </b>          We chose to implement adjustments for the mentioned target groups, since these adjustments might not be applied with         
 +
              <b>            external software.         
 +
              </b>
 +
            </p>
 +
            <div class="figure-container">  
 +
              <img alt="Wiki screencapture showing how cognitive disability profile works." id="Figure5" src="https://static.igem.org/mediawiki/2021/8/89/T--Vilnius-Lithuania--cognitive_disability_profile_demo.png"/>
 +
              <div>
 +
                <b>            Fig. 5.           
 +
                </b>            Adjustments for cognitive disability profile         
 +
              </div>
 +
            </div>
 +
            <div class="figure-container">
 +
              <img alt="Wiki screencapture showing how dyslexia friendly profile works." id="Figure6" src="https://static.igem.org/mediawiki/2021/f/f5/T--Vilnius-Lithuania--dyslexia_friendly_demo.png"/>
 +
              <div>
 +
                <b>            Fig. 6.           
 +
                </b>            Adjustments for dyslexia         
 +
              </div>
 +
            </div>
 +
            <h3 class="index-headline">          Adaptations for colorblind         
 +
            </h3>
 +
            <p>          Throughout the project, one of the priorities was to make sure that it is <b>accessible to people with colorblindness.</b> Color vision deficiency affects approximately 1 in 12 men (8 percent) and 1 in 200 (0,5 percent) women. [3] There are several main types of color blindness: deuteranopia (red-green color blindness), protanopia (red color blindness), Tritanopia (blue-yellow color blindness). One member of our team has protanopia as well, so this adaptation was especially important for us. He helped to choose the best color palette for the whole project and checked contrast ratios between colors. Therefore the colors we chose for our visual identity are easy to distinguish for people with all major color blindness types (Fig. 7). We used these colors in all visuals used for the project, on the “6th Synbio sense” website, our wiki and educational powerpoint presentations.         
 +
            </p>
 +
            <div class="figure-container center">
 +
              <img alt="Illustration of our original visual identity compared to what is seen by people with deuteranopia, protanopia and tritanopia." id="Figure7" src="https://static.igem.org/mediawiki/2021/d/d5/T--Vilnius-Lithuania--color_palette.png" width=500px/>
 +
              <div>
 +
                <b>            Fig. 7.           
 +
                </b>            Comparison of how colorblind people and common-type people see the selected color palette         
 +
              </div>
 +
            </div>
 +
            <p>          Despite the right choice of colors, it is essential to maintain the right contrast ratio of text and background. According to Web Content Accessibility Guidelines (WCAG)  2.1 AA rating success criterion 1.43, the visual presentation of text and images of text must have a contrast ratio of at least 4.5:1, and also, large-scale text (with at least 18 points or 14 points bold) and images of large-scale text must have a contrast ratio of at least 3:1 [2] (Fig. 8). We also applied this practice on the “6th Synbio sense” website, our wiki and educational powerpoint presentations.         
 +
            </p>
 +
            <div class="figure-container">
 +
              <img alt="Illustration of used contrast ratio in our web design." id="Figure8" src="https://static.igem.org/mediawiki/2021/2/2b/T--Vilnius-Lithuania--contrast_ratio.png"/>
 +
              <div>
 +
                <b>            Fig. 8.           
 +
                </b>            Contrast ratio evaluation         
 +
              </div>
 +
            </div>
 +
            <p>          We thought about applications for colorblind people not only when creating a graphic and web design, but also when designing a prototype of our diagnostic test. As the sole color shift from blue to red may be indistinguishable and slight tone differences could slip through the eyes of the end user we included <b>reference color circles for extra measures.</b> If a person is infected with amebiasis, diagnostic test outside color equalize with inner membrane color in all three windows so that person could better interpret results.         
 +
            </p>
 +
            <div class="figure-container">
 +
              <img alt="" id="Figure9" src="https://static.igem.org/mediawiki/2021/c/c3/T--Vilnius-Lithuania--3_down_v2_membrane_area.png"/>
 +
              <div>
 +
                <b>            Fig. 9.           
 +
                </b>            Colorimetric reference for diagnostic test - positive result shows as all three windows have merged colors with their corresponding outer rings         
 +
              </div>
 +
            </div>
 +
            <p>          A similar effect goes to negative results - if a person is not infected or diagnostic test is not functional at the particular moment at least one of all windows will not have merged colorimetric response with outer ring.         
 +
            </p>
 +
            <div class="figure-container">
 +
              <img alt="" id="Figure10" src="https://static.igem.org/mediawiki/2021/1/16/T--Vilnius-Lithuania--3_down_v2_membrane_albumin_correct_area.png"/>
 +
              <div>
 +
                <b>            Fig. 10.           
 +
                </b>            Colorimetric reference for diagnostic test - negative result shows only one red window for albumin         
 +
              </div>
 +
            </div>
 +
            <div class="figure-container">
 +
              <img alt="" id="Figure11" src="https://static.igem.org/mediawiki/2021/a/ae/T--Vilnius-Lithuania--3_down_v2_membrane_incorrect_area.png"/>
 +
              <div>
 +
                <b>            Fig. 11.           
 +
                </b>            Colorimetric reference for diagnostic test - non-functional test shows all three blue windows         
 +
              </div>
 +
            </div>
 +
            <p>          These two examples perfectly show that a reference guide could enhance reading assistance for users with various visual impairments. Reading instructions (Fig. 12) are proposed implementation.         
 +
            </p>
 +
            <div class="figure-container">
 +
              <img alt="" id="Figure12" src="https://static.igem.org/mediawiki/2021/0/0f/T--Vilnius-Lithuania--Diagnostic_test_colors.png"/>
 +
              <div>
 +
                <b>            Fig. 12.           
 +
                </b>            Colorimetric reference for the diagnostic test - overall reading scheme         
 +
              </div>
 +
            </div>
 +
          </div>
 +
          <div class="references-wrapper">
 +
            <div class="breaker">
 +
            </div>
 +
            <h2>          References         
 +
            </h2>
 +
            <div class="references-container">
 +
              <div class="number">            1.         
 +
              </div>
 +
              <div>            Aginskaitė, S., Gečaitė, K., &amp; Jonikaitis, G. (2018). Internetas visiems: prieinamos skaitmeninės informacijos rengimo vadovas.           
 +
                <a href="https://lnf.lt/wp-content/uploads/2018/12/Internetas_visiems.pdf" target="_blank">            To the article           
 +
                </a>
 +
              </div>
 +
              <div class="number">            2.         
 +
              </div>
 +
              <div>            Caldwell, B., Cooper, M., Reid, L. G., Vanderheiden, G., Chisholm, W., Slatin, J., &amp; White, J. (2018). Web content accessibility guidelines (WCAG) 2.1.           
 +
                <a href="https://www.w3.org/TR/WCAG21/" target="_blank">            To the guidelines           
 +
                </a>
 +
              </div>  
 +
              <div class="number">            3.         
 +
              </div>  
 +
              <div>            Colour Blind Awareness is a Community Interest Company. (n.d.). Colour Blindness. Colourblindawareness. Retrieved October 5, 2021.           
 +
                <a href="https://www.colourblindawareness.org/colour-blindness/" target="_blank">            To the article           
 +
                </a>
 +
              </div>  
 +
            </div>  
 +
          </div>
 +
        </div>
 +
        <div class="index-container">  
 +
          <div class="index-header">
 +
          </div>  
 +
          <div class="index-content">
 +
          </div>  
 +
        </div>  
 +
      </div>  
 +
      <footer>  
 +
        <div class="logo-igem">  
 +
          <object data="https://static.igem.org/mediawiki/2021/f/ff/T--Vilnius-Lithuania--iGEM-2021.svg">  
 +
          </object>  
 +
        </div>  
 +
        <div class="social-container">  
 +
          <div>FOLLOW US
 +
          </div>  
 +
          <div>  
 +
            <a class="placeholder-social-icon" href="https://www.facebook.com/VilniusiGEM">  
 +
              <img src="https://static.igem.org/mediawiki/2021/3/36/T--Vilnius-Lithuania--facebook.svg"/>  
 +
            </a>
 +
            <a class="placeholder-social-icon" href="https://www.instagram.com/igem_vilnius/">  
 +
              <img src="https://static.igem.org/mediawiki/2021/6/64/T--Vilnius-Lithuania--instagram.svg"/>  
 +
            </a>
 +
            <a class="placeholder-social-icon" href="https://www.linkedin.com/company/vilnius-igem/">  
 +
              <img src="https://static.igem.org/mediawiki/2021/e/e7/T--Vilnius-Lithuania--linkedin.svg"/>  
 +
            </a>
 +
          </div>  
 +
        </div>  
 +
        <div class="mail-container">  
 +
          <div>CONTACT US
 +
          </div>  
 +
          <a href="mailto:info@vilniusigem.lt">info@vilniusigem.lt
 +
          </a>  
 +
        </div>  
 +
        <div class="grid-sponsors">  
 +
          <div>  
 +
            <div>
 +
              <object data="https://static.igem.org/mediawiki/2021/d/dc/T--Vilnius-Lithuania--VU.svg">  
 +
              </object>  
 +
            </div>  
 +
            <div>  
 +
              <object data="https://static.igem.org/mediawiki/2021/b/bf/T--Vilnius-Lithuania--Termofisher.svg">  
 +
              </object>  
 +
            </div>  
 +
            <div>  
 +
              <object data="https://static.igem.org/mediawiki/2021/1/10/T--Vilnius-Lithuania--CityOfVilnius.svg">  
 +
              </object>  
 +
            </div>  
 +
          </div>  
 +
          <div>
 +
            <div>
 +
              <object data="https://static.igem.org/mediawiki/2021/b/bb/T--Vilnius-Lithuania--GMC.svg">  
 +
              </object>  
 +
            </div>  
 +
            <div>  
 +
              <object data="https://static.igem.org/mediawiki/2021/9/98/T--Vilnius-Lithuania--Nanodiagnostika.svg">  
 +
              </object>  
 +
            </div>  
 +
            <div>  
 +
              <object data="https://static.igem.org/mediawiki/2021/1/16/T--Vilnius-Lithuania--Telesoftas.svg">  
 +
              </object>  
 +
            </div>  
 +
            <div>  
 +
              <object data="https://static.igem.org/mediawiki/2021/7/70/T--Vilnius-Lithuania--Kopicentras.svg">  
 +
              </object>  
 +
            </div>  
 +
          </div>  
 +
          <div>
 +
            <div>
 +
              <object data="https://static.igem.org/mediawiki/2021/d/df/T--Vilnius-Lithuania--SnapGene.svg">  
 +
              </object>  
 +
            </div>  
 +
            <div>  
 +
              <object data="https://static.igem.org/mediawiki/2021/3/3e/T--Vilnius-Lithuania--Laborama.svg">  
 +
              </object>  
 +
            </div>  
 +
            <div>  
 +
              <object data="https://static.igem.org/mediawiki/2021/c/c1/T--Vilnius-Lithuania--Biotecha.svg">
 +
              </object>
 +
            </div>
 +
            <div>
 +
              <object data="https://static.igem.org/mediawiki/2021/4/4f/T--Vilnius-Lithuania--Grida.svg">  
 +
              </object>  
 +
            </div>  
 +
          </div>  
 +
        </div>
 +
      </footer>  
 +
    </div>
 +
    <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/navigationTabs&amp;action=raw&amp;ctype=text/javascript" type="text/javascript">
 +
    </script>  
 +
    <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/background&amp;action=raw&amp;ctype=text/javascript" type="text/javascript">
 +
    </script>  
 +
    <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/contentpage&amp;action=raw&amp;ctype=text/javascript" type="text/javascript">
 +
    </script>  
 +
    <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/navbar&amp;action=raw&amp;ctype=text/javascript" type="text/javascript">
 +
    </script>  
 +
    <script>     contentPage(        "Sections",        true,        300,      )   </script>
 +
    <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/GlslCanvas&amp;action=raw&amp;ctype=text/javascript" type="text/javascript">
 +
    </script>  
 +
    <script src="https://2021.igem.org/wiki/index.php?title=Template:Vilnius-Lithuania/scripts/backgroundTransition&amp;action=raw&amp;ctype=text/javascript" type="text/javascript">
 +
    </script>
 +
  </body>
 
</html>
 
</html>

Latest revision as of 01:12, 22 October 2021

INCLUSIVITY

Header

Introduction

At Vilnius-Lithuania iGEM, we recognize the importance of diversity and inclusion within the science field. We are committed to making the synthetic biology community more open and creating a learning environment where everyone feels welcome.

On 2024 September 1st changes of article 14 of the Education Law of the Republic of Lithuania comes into force and a new inclusive education chapter begins. Every general education school should be ready to accept and educate students with disabilities. However, currently not enough measures are taken to reach this goal. We learned this from numerous calls with special pedagogues, students with disabilities and others working in the inclusivity field.

During our consultations with practitioners working with disabilities, it was often stated that negative experiences in school, pessimistic outlook coming from the teachers and lack of exposure to the inclusivity of universities discourage pupils from fulfilling their academic potential later in life. Moreover, one of our consultants, Dr. Barbara R. Heard, an associate biology professor who focuses on inclusive education, claimed, there are still many complicated areas relating to inclusive education (read the full consultation here). According to her, it is crucial to focus on changing the outlook on the problem to induce progress. This and other consultations inspired us to become the change ourselves. While planning our educational activities and thinking about the design and presentation of our project, we followed an inclusive approach.

Our main focus groups were people with vision and intellectual disabilities. First, we chose audience with visual impairments due to the fact that most of the education material is visual - it takes the form of illustrations, graphs etc. This means people with impaired vision do not have a chance to learn more specific subjects like synthetic biology. Second, individuals with cognitive disabilities were chosen due to common underestimation of their abilities. Meaning that such people might not receive information on complex yet significant topics of contemporary society like vaccines, GMO’s etc.

6th SynBio sense

As a way to make “6th SynBio sense” platform more inclusive we set several goals. First, we applied accessibility tools to the platform’s web page. As mentioned above, we made sure that the website is accessible for color blind people, by choosing the right color palette and keeping the right contrast ratio between text and background (Fig. 1).

Illustration of how our page looks originally, for people with deuteranopia, protanopia and tritanopia
Fig. 1. Accessibility adaptations on “6th SynBio sense” website

What is more, as the website contains a lot of written information, it was important for us that it is readable for everyone, therefore we applied a font changing function for people with dyslexia. (Fig. 2) We also made sound recordings of the provided information for users, who have vision deficiency. In general, we tried to keep the design of the website minimalistic and with as few distractions as possible, to keep the main focus on the augmented reality models and provided information.

Illustration comparing original text and text modified for dyslexia
Fig. 2. Modification for dyslexia on “6th SynBio sense” website

We also wanted to make 3D models accessible for the blind. To reach the goal, we teamed up with a biology teacher Gintaras Nenartavičius from the Lithuanian Center for the Development of the Blind and Visually Impaired. We learned about the most used educational tools and decided to implement this knowledge into our project. After thorough consultations with an expert teacher and 3D printing specialist, we printed 3D models of virus and protein translation as well as tactile schemes of protein synthesis, synthetic biology, genetic scissors, DNA, RNA, and SARS-CoV-2 virus. (Fig. 3) To test out the tools ourselves, we prepared a lesson for the students at the same institution. At first, we thought it would be rather challenging to educate people that lack one of the most commonly used senses. However, our experience was positive. Pupils were attentive and their teacher assisted us in handing out tactile models and explaining what is pictured there. Moreover, headings with some explanations of what is seen in the picture were provided in Braille. This simplified the process greatly and helped children to follow our lecture.

Photograph of person reading braille.
Fig. 3. Tactile schemes explaining the basics of synthetic biology

Finally, we saw potential in making “6th SynBio sense” even more inclusive by simplifying descriptions of each model to make them suitable for people with intellectual disabilities. This idea came after encountering an Istanbul convention adapted to autistic people. We contacted a representative from the National Agency for Education Inclusivity department to help us and review our adapted texts. As we found, the key things to an inclusive text are giving clear instructions on what is seen on the screen, explaining complex terms separately, adding examples from real life and keeping to the main idea of the text. We also used “Internet for everyone” [1] guide for any extensive inquires. Simplified descriptions currently are only in Lithuanian and can be accessed while previewing the text information.

Illustration comparing regular text and its version in simple language.
Fig. 4. Example of simplified description

Wiki accessibility

Our goal this year was to make Wiki clear, intuitive, and accessible.

Before digging deeper into the Wiki implementation, we decided to develop it according to WCAG documentation [2] in order to make it accessible. WCAG stands for Web Content Accessibility Guidelines. It is a document that includes many recommendations to make Web content more accessible. We set ourselves a goal to make our Wiki meet as many as possible of the WCAG A and AA level requirements. WCAG contains a rich list of specifications and in order to affirm our plan, which of them are the most sensible to realize, we organized a consultation with Jurij Nesvat - a testing engineer, specializing in testing accessibility of Web pages. Together we reviewed and confirmed our plan that we set ourselves to fulfill.

The plan included ‘A’, ‘AA’ level requirements and optional adjustments for groups with cognitive disability and dyslexia.

The ‘A’ level requirements that demanded our attention, since they were not as intuitive as the others, were: making the website accessible by keyboard only, avoiding presentation that relies solely on color, paying attention that content would not have elements causing more than three flashes per second.

The AA level requirements applied in our Wiki development were: making the website responsive to various screen sizes, introducing high contrast between pieces of text and their backgrounds, using clear headings and labels, making focus visible, making consistent navigation and identification. These requirements were the ones that we focused on, since the thoughtful implementation of them is exactly what contributes to reaching our goal related to Wiki development.

Besides the adjustments determined by WCAG protocol, we also added a couple of functionalities in the accessibility toolbar: one that introduces markings for people with cognitive disabilities and another that changes the font of the text to dyslexia-friendly. Cognitive disability profile adjustments include highlighting of the buttons, headings and links, which makes it easier to navigate through the most important parts of the content. Dyslexia-friendly customization changes the font to make the text easier to read. We chose to implement adjustments for the mentioned target groups, since these adjustments might not be applied with external software.

Wiki screencapture showing how cognitive disability profile works.
Fig. 5. Adjustments for cognitive disability profile
Wiki screencapture showing how dyslexia friendly profile works.
Fig. 6. Adjustments for dyslexia

Adaptations for colorblind

Throughout the project, one of the priorities was to make sure that it is accessible to people with colorblindness. Color vision deficiency affects approximately 1 in 12 men (8 percent) and 1 in 200 (0,5 percent) women. [3] There are several main types of color blindness: deuteranopia (red-green color blindness), protanopia (red color blindness), Tritanopia (blue-yellow color blindness). One member of our team has protanopia as well, so this adaptation was especially important for us. He helped to choose the best color palette for the whole project and checked contrast ratios between colors. Therefore the colors we chose for our visual identity are easy to distinguish for people with all major color blindness types (Fig. 7). We used these colors in all visuals used for the project, on the “6th Synbio sense” website, our wiki and educational powerpoint presentations.

Illustration of our original visual identity compared to what is seen by people with deuteranopia, protanopia and tritanopia.
Fig. 7. Comparison of how colorblind people and common-type people see the selected color palette

Despite the right choice of colors, it is essential to maintain the right contrast ratio of text and background. According to Web Content Accessibility Guidelines (WCAG) 2.1 AA rating success criterion 1.43, the visual presentation of text and images of text must have a contrast ratio of at least 4.5:1, and also, large-scale text (with at least 18 points or 14 points bold) and images of large-scale text must have a contrast ratio of at least 3:1 [2] (Fig. 8). We also applied this practice on the “6th Synbio sense” website, our wiki and educational powerpoint presentations.

Illustration of used contrast ratio in our web design.
Fig. 8. Contrast ratio evaluation

We thought about applications for colorblind people not only when creating a graphic and web design, but also when designing a prototype of our diagnostic test. As the sole color shift from blue to red may be indistinguishable and slight tone differences could slip through the eyes of the end user we included reference color circles for extra measures. If a person is infected with amebiasis, diagnostic test outside color equalize with inner membrane color in all three windows so that person could better interpret results.

Fig. 9. Colorimetric reference for diagnostic test - positive result shows as all three windows have merged colors with their corresponding outer rings

A similar effect goes to negative results - if a person is not infected or diagnostic test is not functional at the particular moment at least one of all windows will not have merged colorimetric response with outer ring.

Fig. 10. Colorimetric reference for diagnostic test - negative result shows only one red window for albumin
Fig. 11. Colorimetric reference for diagnostic test - non-functional test shows all three blue windows

These two examples perfectly show that a reference guide could enhance reading assistance for users with various visual impairments. Reading instructions (Fig. 12) are proposed implementation.

Fig. 12. Colorimetric reference for the diagnostic test - overall reading scheme

References

1.
Aginskaitė, S., Gečaitė, K., & Jonikaitis, G. (2018). Internetas visiems: prieinamos skaitmeninės informacijos rengimo vadovas. To the article
2.
Caldwell, B., Cooper, M., Reid, L. G., Vanderheiden, G., Chisholm, W., Slatin, J., & White, J. (2018). Web content accessibility guidelines (WCAG) 2.1. To the guidelines
3.
Colour Blind Awareness is a Community Interest Company. (n.d.). Colour Blindness. Colourblindawareness. Retrieved October 5, 2021. To the article