<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="13" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://mail.dhd752groupproject.digital.uic.edu/exhibits/show/universal-design-disabled-doct/item/13?output=omeka-xml" accessDate="2026-04-21T19:31:47+00:00">
  <fileContainer>
    <file fileId="11">
      <src>https://mail.dhd752groupproject.digital.uic.edu/files/original/9041a20f76ba658c79419668ba9502f4.jpeg</src>
      <authentication>89d2d424a1087df51d8b26aad999c343</authentication>
    </file>
  </fileContainer>
  <collection collectionId="5">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="57">
                <text>Literature on Universal Design and the Built Environment</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="66">
                <text>This collection addresses existing literature that deals with universal design in the built environment as well as in relation to material objects. While not dealing exclusively about the intersection of disabled doctors and universal design, this collection hopes to point audiences to books that may serve as starting points for disabled doctors as well as the able-bodied community around them to start thinking about what it would mean and what it would look like for disabled doctors to have their voices heard and consequential in the altering and changing of medical environments such as hospitals, clinics, rehabilitation centers, and more.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="1">
    <name>Text</name>
    <description>A resource consisting primarily of words for reading. Examples include books, letters, dissertations, poems, newspapers, articles, archives of mailing lists. Note that facsimiles or images of texts are still of the genre Text.</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="58">
              <text>&lt;em&gt;Accessible America: A History of Disability and Design&amp;nbsp;&lt;/em&gt;by Bess Williamson (NYU Press, 2019)</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="59">
              <text>Bess Williamson</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="60">
              <text>NYU Press</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="80">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="81">
              <text>Academic book</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="83">
              <text>&lt;span&gt;Have you ever hit the big blue button to activate automatic doors? Have you ever used an ergonomic kitchen tool? Have you ever used curb cuts to roll a stroller across an intersection? If you have, then you’ve benefited from accessible design—design for people with physical, sensory, and cognitive disabilities. These ubiquitous touchstones of modern life were once anything but. Disability advocates fought tirelessly to ensure that the needs of people with disabilities became a standard part of public design thinking. That fight took many forms worldwide, but in the United States it became a civil rights issue; activists used design to make an argument about the place of people with disabilities in public life.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span&gt;In the aftermath of World War II, with injured veterans returning home and the polio epidemic reaching the Oval Office, the needs of people with disabilities came forcibly into the public eye as they never had before. The US became the first country to enact federal accessibility laws, beginning with the Architectural Barriers Act in 1968 and continuing through the landmark Americans with Disabilities Act in 1990, bringing about a wholesale rethinking of our built environment. This progression wasn’t straightforward or easy. Early legislation and design efforts were often haphazard or poorly implemented, with decidedly mixed results. Political resistance to accommodating the needs of people with disabilities was strong; so, too, was resistance among architectural and industrial designers, for whom accessible design wasn’t “real” design.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span&gt;Bess Williamson provides an extraordinary look at everyday design, marrying accessibility with aesthetic, to provide an insight into a world in which we are all active participants, but often passive onlookers. Richly detailed, with stories of politics and innovation, Williamson’s&amp;nbsp;&lt;/span&gt;&lt;em&gt;Accessible America&lt;/em&gt;&lt;span&gt;&amp;nbsp;takes us through this important history, showing how American ideas of individualism and rights came to shape the material world, often with unexpected consequences. (NYU Press)&lt;/span&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="48">
          <name>Source</name>
          <description>A related resource from which the described resource is derived</description>
          <elementTextContainer>
            <elementText elementTextId="84">
              <text>&lt;p style="margin-left: 28.35pt; text-indent: -28.35pt;"&gt;&lt;i&gt;Accessible America&lt;/i&gt;. NYU Press. (2019, July 2). Retrieved April 30, 2022, from &lt;a href="https://nyupress.org/9781479894093/accessible-america/"&gt;https://nyupress.org/9781479894093/accessible-america/&lt;/a&gt;.&lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
