Winter 2023 CREATE Research Showcase

December 12, 2023

Students from CSE 493 and additional CREATE researchers shared their work at the December 2023 CREATE Research Showcase. The event was well attended by CREATE students, faculty, and community partners. Projects included, for example: an analysis of the accessibility of transit stations and a tool to aid navigation within transit stations; an app to help colorblind people of color pick makeup; and consider the accessibility of generative AI while also considering ableist implications of limited training data.

CSE 493 student projects

In it’s first offering Autumn quarter 2023, CSE’s undergraduate Accessibility class has been focusing on the importance of centering first-person accounts in disability-focused technology work. Students worked this quarter on assignments ranging from accessibility assessments of county voting systems to disability justice analysis to open-ended final projects.

Alti Discord Bot »

Keejay Kim, Ben Kosa, Lucas Lee, Ashley Mochizuki

Alti is a Discord bot that automatically generates alt text for any image that gets uploaded onto Discord. Once you add Alti to your Discord server, Alti will automatically generate alt text for the image using artificial intelligence (AI).

Enhancing Self-Checkout Accessibility at QFC »

Abosh Upadhyaya, Ananya Ganapathi, Suhani Arora

Makes self-checkout more accessible to visually impaired individuals

Complexion Cupid: Color Matching Foundation Program »

Ruth Aramde, Nancy Jimenez-Garcia, Catalina Martinez, Nora Medina

Allows individuals with color blindness to upload an image of their skin, and provides a makeup foundation match. Additionally, individuals can upload existing swatches and will be provided with filtered photos that better show the matching accuracy.

Twitter Content Warnings »

Stefan D’Souza, Aditya Nair

A chrome extension meant to be used in conjunction with twitter.com in order to help people with PTSD

Lettuce Eat! A Map App for Accessibly Dietary Restrictions »

Arianna Montoya, Anusha Gani, Claris Winston, Joo Kim

Parses menus on restaurants’ websites to provide information on restaurants’ dietary restrictions to support individuals with specific dietary requirements, such as vegan vegetarian, and those with Celiac disease.

Form-igate »

Sam Assefa

A chrome extension that allows users with motor impairments to interact with google forms using voice commands, enhancing accessibility.

Lite Lingo: Plain Text Translator »

Ryan Le, Michelle Vu, Chairnet Muche, Angelo Dauz

A plain text translator to help individuals with learning disabilities

Matplotalt: Alt text for matplotlib figures »

Kai Nailund

[No abstract]

PadMap: Accessible Map for Menstrual Products »

Kirsten Graham, Maitri Dedhia, Sandy Cheng, Aaminah Alam

Our goal is to ensure that anywhere on campus, people can search up the closest free menstrual products to them and get there in an accessible way.

SCRIBE: Crowdsourcing Scientific Alt Text »

Sanjana Chintalapati, Sanjana Sridhar, Zage Strassberg-Phillips

A prototype plugin for arXiv that adds alt text to requested papers via crowdwork.

PalPalette »

Pu Thavikulwat, Masaru Chida, Srushti Adesara, Angela Lee

A web app that helps combat loneliness and isolation for young adults with disabilities

SpeechIT »

Pranati Dani, Manasa Lingireddy, Aryan Mahindra

A presentation speech checker to ensure a user’s verbal speech during presentation is accessible and understandable for everyone.

Enhancing Accessibility in SVG Design: A Fabric.js Solution »

Julia Tawfik, Kenneth Ton, Balbir Singh, Aaron Brown

A Laser Cutter Generator’ interface which displays a form to select shapes and set dimensions for SVG creation.

CREATE student and faculty projects

Designing and Implementing Social Stories in Technology: Enhancing Collaboration for Parents and Children with Neurodiverse Needs

Elizabeth Castillo, Annuska Zolyomi, Ting Zhou

Our research project, conducted through interviews in Panama, focuses on the user-centered design of technology to enhance autism social stories for children with neurodiverse needs. We aim to improve collaboration between parents, therapists, and children by creating a platform for creating, sharing, and tracking the usage of social stories. While our initial research was conducted in Panama, we are eager to collaborate with individuals from Japan and other parts of the world where we have connections, to further advance our work in supporting neurodiversity.

An Autoethnographic Case Study of Generative Artificial Intelligence’s Utility for Accessibility

Kate S Glazko, Momona Yamagami, Aashaka Desai, Kelly Avery Mack, Venkatesh Potluri, Xuhai Xu, Jennifer Mankoff

With the recent rapid rise in Generative Artificial Intelligence (GAI) tools, it is imperative that we understand their impact on people with disabilities, both positive and negative. However, although we know that AI in general poses both risks and opportunities for people with disabilities, little is known specifically about GAI in particular. To address this, we conducted a three-month autoethnography of our use of GAI to meet personal and professional needs as a team of researchers with and without disabilities. Our findings demonstrate a wide variety of potential accessibility-related uses for GAI while also highlighting concerns around verifiability, training data, ableism, and false promises.

Machine Learning for Quantifying Rehabilitation Responses in Children with Cerebral Palsy

Charlotte D. Caskey, Siddhi R. Shrivastav, Alyssa M. Spomer, Kristie F. Bjornson, Desiree Roge, Chet T. Moritz, Katherine M. Steele

Increases in step length and decreases in step width are often a rehabilitation goal for children with cerebral palsy (CP) participating in long-term treadmill training. But it can be challenging to quantify the non-linear, highly variable, and interactive response to treadmill training when parameters such as treadmill speed increase over time. Here we use a machine learning method, Bayesian Additive Regression Trees, to show that there is a direct effect of short-burst interval locomotor treadmill training on increasing step length and modulating step width for four children with CP, even after controlling for cofounding parameters of speed, treadmill incline, and time within session.

Spinal Stimulation Improves Spasticity and Motor Control in Children with Cerebral Palsy

Victoria M. Landrum, Charlotte D. Caskey, Siddhi R. Shrivastav, Kristie F. Bjornson, Desiree Roge, Chet T. Moritz, Katherine M. Steele

Cerebral palsy (CP) is caused by a brain injury around the time of birth that leads to less refined motor control and causes spasticity, a velocity dependent stretch reflex that can make it harder to bend and move joints, and thus impairs walking function. Many surgical interventions that target spasticity often lead to negative impacts on walking function and motor control, but transcutaneous spinal cord stimulation (tSCS), a novel, non-invasive intervention, may amplify the neurological response to traditional rehabilitation methods. Results from a 4-subject pilot study indicate that long-term usage of tSCS with treadmill training led to improvements in spasticity and motor control, indicating better walking function.

Adaptive Switch Kit

Kate Bokowy, Mia Hoffman, Heather A. Feldner, Katherine M. Steele

We are developing a switch kit for clinicians and parents to build customizable switches for children with disabilities. These switches are used to help children play with computer games and adapted toys as an early intervention therapy.

Developing a Sidewalk Improvement Cost Function

Alex Kirchmeier, Cole Anderson, Anat Caspi

In this ongoing project, I am developing a Python script that uses a sidewalk issues dataset to determine the cost of improving Seattle’s sidewalks. My intention is to create a customizable function that will help users predict the costs associated with making sidewalks more accessible.

Exploring the Benefits of a Dynamic Harness System Using Partial Body Weight Support on Gross Motor Development for Infants with Down Syndrome

Reham Abuatiq, PT, MSc1; Mia Hoffman, ME, BSc2; Alyssa Fiss, PT, PhD3; Julia Looper, PT, PhD4; & Heather Feldner, PT, PhD, PCS1,5,6

We explored the benefits of a Dynamic Harness System Using Partial Body Weight Support (PBWS) within an enriched play environment on Gross Motor Development for Infants with Down Syndrome using randomized cross over study design. We found that the effectiveness of the PBWS harness system on gross motor development was clearly evident. The overall intervention positively affected activity levels, however, the direct impact of the harness remains unclear.

StreetComplete for Better Pedestrian Mapping

Sabrina Fang, Kohei Matsushima

StreetComplete is a gamified, structured, and user-friendly mobile application for users to improve OpenStreetMap data by completing pilot quests. OpenStreetMap is an open-source, editable world map created and maintained by a community of volunteers. The goal of this research project is to design pilot quests in StreetComplete to accurately collect information about “accessibility features,” such as sidewalk width and the quality of lighting, to improve accessibility for pedestrian mapping.

Transit Stations Are So Confusing!

Jackie Chen, Milena Johnson, Haochen Miao, and Raina Scherer

We are collecting data on the wayfinding nodes in four different Sound Transit light rail stations, and interpreting them through the GTFS-pathways schema. In the future, we plan on visualizing this information through AccessMaps such that it can be referenced by all users.

Optimizing Seattle Curbside Disability Parking Spots

Wendy Bu, Cole Anderson, Anat Caspi

The project is born out of a commitment to enhance the quality of life for individuals with disabilities in the city of Seattle. The primary objective is to systematically analyze and improve the allocation and management of curbside parking spaces designated for disabled individuals. By improving accessibility for individuals with disabilities, the project contributes to fostering a more equitable and welcoming urban environment.

Developing Accessible Tele-Operation Interfaces for Assistive Robots with Occupational Therapists

Vinitha Ranganeni, Maya Cakmak

The research is motivated by the potential of using tele-operation interfaces with assistive robots, such as the Stretch RE2, to enhance the independence of individuals with motor limitations in completing activities of daily living (ADLs). We explored the impact of customization of tele-operation interfaces and a deployed the Stretch RE2 in a home for several weeks facilitated by an occupational therapist and enabled a user with quadriplegia to perform daily activities more independently. Ultimately, this work aims to empower users and occupational therapists in optimizing assistive robots for individual needs.

HuskyADAPT: Accessible Design and Play Technology

HuskyADAPT Student Organization

HuskyADAPT is a multidisciplinary community at the University of Washington that supports the development of accessible design and play technology. Our community aims to initiate conversations regarding accessibility and ignite change through engineering design. It is our hope that we can help train the next generation of inclusively minded engineers, clinicians, and educators to help make the world a more equitable place.

A11yBoard for Google Slides: Developing and Deploying a Real-World Solution for Accessible Slide Reading and Authoring for Blind Users

Zhuohao (Jerry) Zhang, Gene S-H Kim, Jacob O. Wobbrock

Presentation software is largely inaccessible to blind users due to the limitations of screen readers with 2-D artboards. This study introduces an advanced version of A11yBoard, initially developed by Zhang & Wobbrock (CHI2023), which now integrates with Google Slides and addresses real-world challenges. The enhanced A11yBoard, developed through participatory design including a blind co-author, demonstrates through case studies that blind users can independently read and create slides, leading to design guidelines for accessible digital content creation tools.

“He could go wherever he wanted”: Driving Proficiency, Developmental Change, and Caregiver Perceptions following Powered Mobility Training for Children 1-3 Years with Disabilities

Heather A. Feldner, PT, MPT, PhD; Anna Fragomeni, PT; Mia Hoffman, MS; Kim Ingraham, PhD; Liesbeth Gijbels, PhC; Kiana Keithley, SPT; Patricia K. Kuhl, PhD; Audrey Lynn, SPT; Andrew Meltzoff, PhD; Nicole Zaino, PhD; Katherine M. Steele, PhD

The objective of this study was to investigate how a powered mobility intervention for young children (ages 1-3years) with disabilities impacted: 1) Driving proficiency over time; 2) Global developmental outcomes; 3) Learning tool use (i.e., joystick activation); and 4) Caregiver perceptions about powered mobility devices and their child’s capabilities.

Access to Frequent Transit in Seattle

Darsh Iyer, Sanat Misra, Angie Niu, Dr. Anat Caspi, Cole Anderson

The research project in Seattle focuses on analyzing access to public transit, particularly frequent transit stops, by considering factors like median household income. We scripted in QGIS, analyzed walksheds, and examined demographic data surrounding Seattle’s frequent transit stops to understand the equity of transit access in different neighborhoods. Our goal was to visualize and analyze the data to gain insights into the relationship between transit access, median household income, and other demographic factors in Seattle.

Health Service Accessibility

Seanna Qin, Keona Tang, Anat Caspi, Cole Anderson

Our research aims to discover any correlation between median household income and driving duration from census tracts to the nearest urgent care location in the Bellevue and Seattle region

Conveying Uncertainty in Data Visualizations to Screen-Reader Users Through Non-Visual Means

Ather Sharif, Ruican Zhong, and Yadi Wang

Incorporating uncertainty in data visualizations is critical for users to interpret and reliably draw informed conclusions from the underlying data. However, visualization creators conventionally convey the information regarding uncertainty in data visualizations using visual techniques (e.g., error bars), which disenfranchises screen-reader users, who may be blind or have low vision. In this preliminary exploration, we investigated ways to convey uncertainty in data visualizations to screen-reader users.

UW News: How an assistive-feeding robot went from picking up fruit salads to whole meals

November, 2023

In tests with this set of actions, the robot picked up the foods more than 80% of the time, which is the user-specified benchmark for in-home use. The small set of actions allows the system to learn to pick up new foods during one meal. UW News talked with co-lead authors Gordon and Nanavati, both doctoral students in the Paul G. Allen School of Computer Science & Engineering, and with co-author Taylor Kessler Faulkner, a UW postdoctoral scholar in the Allen School, about the successes and challenges of robot-assisted feeding. The team presented its findings Nov. 7 at the 2023 Conference on Robotic Learning in Atlanta.

An assistive-feeding robotic arm attached to a wheelchair uses a fork to stab a piece of fruit on a plate among other fruits.

The Personal Robotics Lab has been working on robot-assisted feeding for several years. What is the advance of this paper?

Ethan K. Gordon: I joined the Personal Robotics Lab at the end of 2018 when Siddhartha Srinivasa, a professor in the Allen School and senior author of our new study, and his team had created the first iteration of its robot system for assistive applications. The system was mounted on a wheelchair and could pick up a variety of fruits and vegetables on a plate. It was designed to identify how a person was sitting and take the food straight to their mouth. Since then, there have been quite a few iterations, mostly involving identifying a wide variety of food items on the plate. Now, the user with their assistive device can click on an image in the app, a grape for example, and the system can identify and pick that up.

Taylor Kessler Faulkner: Also, we’ve expanded the interface. Whatever accessibility systems people use to interact with their phones — mostly voice or mouth control navigation — they can use to control the app.

EKG: In this paper we just presented, we’ve gotten to the point where we can pick up nearly everything a fork can handle. So we can’t pick up soup, for example. But the robot can handle everything from mashed potatoes or noodles to a fruit salad to an actual vegetable salad, as well as pre-cut pizza or a sandwich or pieces of meat.

In previous work with the fruit salad, we looked at which trajectory the robot should take if it’s given an image of the food, but the set of trajectories we gave it was pretty limited. We were just changing the pitch of the fork. If you want to pick up a grape, for example, the fork’s tines need to go straight down, but for a banana they need to be at an angle, otherwise it will slide off. Then we worked on how much force we needed to apply for different foods.

In this new paper, we looked at how people pick up food, and used that data to generate a set of trajectories. We found a small number of motions that people actually use to eat and settled on 11 trajectories. So rather than just the simple up-down or coming in at an angle, it’s using scooping motions, or it’s wiggling inside of the food item to increase the strength of the contact. This small number still had the coverage to pick up a much greater array of foods.

We think the system is now at a point where it can be deployed for testing on people outside the research group. We can invite a user to the UW, and put the robot either on a wheelchair, if they have the mounting apparatus ready, or a tripod next to their wheelchair, and run through an entire meal.

For you as researchers, what are the vital challenges ahead to make this something people could use in their homes every day?

EKG: We’ve so far been talking about the problem of picking up the food, and there are more improvements that can be made here. Then there’s the whole other problem of getting the food to a person’s mouth, as well as how the person interfaces with the robot, and how much control the person has over this at least partially autonomous system.

TKF: Over the next couple of years, we’re hoping to personalize the robot to different people. Everyone eats a little bit differently. Amal did some really cool work on social dining that highlighted how people’s preferences are based on many factors, such as their social and physical situations. So we’re asking: How can we get input from the people who are eating? And how can the robot use that input to better adapt to the way each person wants to eat?

Amal Nanavati: There are several different dimensions that we might want to personalize. One is the user’s needs: How far the user can move their neck impacts how close the fork has to get to them. Some people have differential strength on different sides of their mouth, so the robot might need to feed them from a particular side of their mouth. There’s also an aspect of the physical environment. Users already have a bunch of assistive technologies, often mounted around their face if that’s the main part of their body that’s mobile. These technologies might be used to control their wheelchair, to interact with their phone, etc. Of course, we don’t want the robot interfering with any of those assistive technologies as it approaches their mouth.

There are also social considerations. For example, if I’m having a conversation with someone or at home watching TV, I don’t want the robot arm to come right in front of my face. Finally, there are personal preferences. For example, among users who can turn their head a little bit, some prefer to have the robot come from the front so they can keep an eye on the robot as it’s coming in. Others feel like that’s scary or distracting and prefer to have the bite come at them from the side.

A key research direction is understanding how we can create intuitive and transparent ways for the user to customize the robot to their own needs. We’re considering trade-offs between customization methods where the user is doing the customization, versus more robot-centered forms where, for example, the robot tries something and says, “Did you like it? Yes or no.” The goal is to understand how users feel about these different customization methods and which ones result in more customized trajectories.

What should the public understand about robot-assisted feeding, both in general and specifically the work your lab is doing?

EKG: It’s important to look not just at the technical challenges, but at the emotional scale of the problem. It’s not a small number of people who need help eating. There are various figures out there, but it’s over a million people in the U.S. Eating has to happen every single day. And to require someone else every single time you need to do that intimate and very necessary act can make people feel like a burden or self-conscious. So the whole community working towards assistive devices is really trying to help foster a sense of independence for people who have these kinds of physical mobility limitations.

AN: Even these seven-digit numbers don’t capture everyone. There are permanent disabilities, such as a spinal cord injury, but there are also temporary disabilities such as breaking your arm. All of us might face disability at some time as we age and we want to make sure that we have the tools necessary to ensure that we can all live dignified lives and independent lives. Also, unfortunately, even though technologies like this greatly improve people’s quality of life, it’s incredibly difficult to get them covered by U.S. insurance companies. I think more people knowing about the potential quality of life improvement will hopefully open up greater access.

Additional co-authors on the paper were Ramya Challa, who completed this research as an undergraduate student in the Allen School and is now at Oregon State University, and Bernie Zhu, a UW doctoral student in the Allen School. This research was partially funded by the National Science Foundation, the Office of Naval Research and Amazon.

For more information, contact Gordon at ekgordon@cs.uw.edu, Nanavati at amaln@cs.uw.edu and Faulkner at taylorkf@cs.washington.edu.


Excerpted and adapted from the UW News story by Stefan Milne.

Virtual Traffic Stop App Aims to Ease Tensions, Aid Communication

October 2, 2023

The designers of the Virtual Traffic Stop app aim to ease tensions and prevent misunderstandings between drivers and law enforcement during traffic stops. For Hard-of-Hearing or Deaf drivers, the app can be used to communicate with law enforcement via chat during the video. Users can add family members and invite them to the chat for additional assistance.

A Gainesville Florida K-12 school has announced their endorsement of Virtual Traffic Stop and has encouraged parents and their children to sign up and start using the app. Currently, the app is being used by the University of Florida and Gainesville Florida police departments.

If your community is interested in using the app, contact Dr. Juan E. Gilbert, a former CREATE Advisory Board member and Chair of the Human-Centered Computing Department at the University of Florida, by calling 352-392-1527 or emailing juan@ufl.edu.

Proposed Federal Accessibility Standards: CREATE’s Guide to Reviewing and Commenting

A proposal for new digital accessibility guidelines for entities receiving federal funds was released for review by the U.S. Department of Justice on August 4, 2023. Anyone affected by these guidelines had until October 3, 2023 to comment.

  • CREATE’s official response, in collaboration with colleagues within the UW and at peer institutions, is posted on the DOJ site temporarily.
  • The response is available as an accessible and tagged PDF document (53 pages).
  • If you have any questions, reach out to CREATE at create-contact@uw.edu.

August 2023 announcement

Note that the comment period has ended.

The U.S. Department of Justice (DoJ) is proposing new requirements for digital accessibility for the Americans with Disabilities Act (ADA). Their goal is to provide public entities with clear and concrete standards for how to fulfill their obligations under the Americans with Disabilities Act Title II Regulations. The goal of these new standards is to ensure public entities provide equal access to all services, programs, and activities that are provided via the web and mobile apps. 

These standards impact mobile apps, websites, and course materials created by and for government bodies, including public schools (K-12 and universities), and public services of all kinds.

Below, we have tried to summarize some of the most important aspects of the proposed rule and to explain them. However, in summarizing we have naturally emphasized things we think are important. Some of the topics the rule touches on that we summarize below include the proposed timeline for making digital content accessible; the proposed rules impacting K-12 and college/university course content; what standards should be met for digital content to be accessible for websites, apps, and live audio captioning; and how compliance should be assessed

Note that submitted comments are publicly available online at: DOJ-CRT-2023-0007 on www.regulations.gov.

roposed rule, but the DOJ has asked a number of very specific questions that you might want to comment on.

Notable questions, highlighted

We highlight several of the DOJ questions below, labeled with the Question # that the DOJ uses for them. You will see that we present these questions out of order – we present them in the order that made sense to us when we summarized this proposed rule. You can read the whole proposed rule and all the questions, in order, on the posting of Docket (DOJ-CRT-2023-0007) on www.regulations.gov. Sometimes we write Question to Consider before a question; these are questions we think you might want to comment on even though the DOJ did not ask about them.

Why submit comments?

The DOJ is still trying to decide exactly what the rule should say, how quickly public entities should improve digital accessibility, and what exceptions to allow. For example, the current rule states that course content posted on a password-protected website (such as a learning management system (LMS) like Canvas) does not have to be made accessible until a student with a disability needs access to that content. If a student registers for the course, or transfers into it, then the course content has to be made fully accessible to all disabilities by the start of the term or within 5 days (if the term has already started). In addition, the course needs to stay accessible over time.

If you agree with this, you might want to say so in your comments, because someone else might think this is unreasonable, and the DOJ should hear from both sides. But you might disagree, in which case you should also comment.  

What are the new standards about?

These standards affect web content and mobile apps. These are very broadly defined and include almost any digital content that is important to interacting with public entities. 

Web content is defined as “information or sensory experience that is communicated to the user by a web browser or other software. This includes text, images, sounds, videos, controls, animations, navigation menus, and documents.” It also includes things like web content posted on social media apps, to the extent possible (for example, if the app supports it, the public entity should add image descriptions to images it posts).


Question 1: The DOJ’s definition of “conventional electronic documents” consists of an exhaustive list of specific file types. Should the DOJ instead craft a more flexible definition that generally describes the types of documents that are covered or otherwise change the proposed definition, such as by including other file types (e.g., images or movies), or removing some of the listed file types?


Mobile applications, or “apps,” are defined as “software applications that are designed to be downloaded and run on mobile devices such as smartphones and tablets.” A public entity may use a mobile app that someone else designed and built (an “external mobile app”); in this case it still needs to be accessible. 


Question 25: What types of external mobile apps, if any, do public entities use to offer their services, programs, and activities to members of the public, and how accessible are these apps? … should [these apps be exempt]? If so, should this exception expire after a certain time, and how would this exception impact persons with disabilities.


Timeline for making web content and mobile apps accessible

Almost any content or app that is important to interacting with a public entity has to be made accessible within 2 years of the date when the rule becomes official, regardless of whether a disabled person asks for it or is known to be using that content or app. For public entities that serve a small number of people (<50,000), the proposed deadline is 3 years. For example, a small county police department in a county with <50,000 people would have 3 years. However only truly independent entities qualify for this exception. For example, the same policy department in a county with >50,000 people would only have two years; similarly a small public school in a large county would only have two years.

If a public entity feels this would be too costly, under the proposed rule they must prove this and they still have to do as much as possible, “to the maximum extent possible” to support their disabled constituents.


Question 4: What compliance costs and challenges might small public entities face in conforming with this rule? … [do they have internal staff for addressing accessibility? If they have recently addressed accessibility, how much did that cost?]

Question 5: Should the DOJ adopt a different WCAG version or conformance level for small entities or a subset of small entities?


Exemptions

The new rule does include some exceptions, meaning it allows some content to be inaccessible. However, when a disabled person needs the inaccessible content, existing regulations implementing title II of the ADA may come into effect, typically requiring the content to be made accessible.

Exemptions

The new rule does include some exceptions, meaning it allows some content to be inaccessible. However, when a disabled person needs the inaccessible content, existing regulations implementing title II of the ADA may come into effect, typically requiring the content to be made accessible.

Archived and pre-existing non-web documents

The following exemptions are intended to reduce the burden of the new rule for large collections of rarely used documents:

  • Archived content not in active use
  • Pre-existing non-web documents

The DOJ has several questions about these exemptions (see Questions 15, 16, 17, 18, 19, and 20) which relate to how such content is currently used, where it is posted, and how these exemptions would impact people with disabilities.


Course content

Generally speaking, course content (such as a public syllabus or handout) has to be made accessible. However, course content inside a password protected website such as a learning management system (for both K-12 schools and colleges/universities) is exempted if the content is only available specifically to admitted students enrolled in the relevant course (and disabled parents, in the case of K-12 materials). 

Once an institution knows, or should have known that a student (or, for K-12 courses, parent) with a disability is enrolled in the course, “all existing course content must be made fully accessible by the [start of the academic term] for that course… New content added throughout the term for the course must also comply… at the time it is added to the website.”

Under today’s interpretation of the ADA, transferring to a course during the add/drop period or from a waitlist often means that the course is less accessible. The DOJ guidelines address this, requiring in these cases that course material is made accessible within five business days of the student’s enrollment. The DOJ also requires “auxiliary aids and services… that enable the student with a disability to participate” while a course is being made accessible. Notably, the relevant material would need to be fully accessible to all disabilities, “not merely the criteria related to that student or parent’s disability.

Importantly, the obligation to make the course content accessible is “ongoing for the duration of the course” and “as long as that content is available to students on the password-protected course website.” It is not clear whether this applies to future offerings of the same course, as typically use of an LMS involves creating a “new” password-protected site for each offering.

The DOJ has a lengthy analysis of tangible and intangible benefits of this ruling, as well as expected costs. They estimate that “By the end of year four (two years after postsecondary schools begin to remediate course content), 96 percent of courses offered by public four-year and postgraduate institutions and 90 percent of courses offered by community colleges will have been remediated. They further estimate that postsecondary institutions will finish remediation on their own to preempt requests in the following year.” They have similar estimates about K-12 education.


Question to consider: Should the “the duration of a course” apply to a single offering of a course for a single term, or all offerings of that course in all terms (even if a separate LMS site, with a separate password, was created for each offering)? How might this impact the likelihood that most courses are fully accessible within four years?

Question to Consider: Do  you agree that the proposed rule will increase course accessibility to include 96% of courses? How might the variable representation of people with disabilities across fields impact this? For example, people with disabilities are particularly under-represented in STEM fields, where diagrams and math equations are often particularly inaccessible. What could be changed about the proposed rule to make this prediction more likely to come true?


The DOJ also has several questions; we highlight some of them below. We have combined the questions for K-12 and post-secondary educational institutions by referring to [public educational institutions] since the primary difference is that parents with disabilities trigger the need to make documents in the case of K-12 education only. 


Question 27 & 36: How difficult would it be for [public educational institutions] to comply with this rule in the absence of this exception?

Question 28 & 37: What would the impact of this exception be on people with disabilities?

Question 33 & 42: How long would it take to make course content available on a public entity’s password-protected or otherwise secured website for a particular course accessible, and does this vary based on the type of course? Do students need access to course content before the first day of class? How much delay in accessing online course content can a student reasonably overcome in order to have an equal opportunity to succeed in a course, and does the answer change depending on the point in the academic term that the delay occurs?

Question 35 & 44: Should the DOJ consider an alternative approach, such as requiring that all newly posted course content be made accessible on an expedited time frame, while adopting a later compliance date for remediating existing content?


This includes third party content. For example, a website for practicing math problems provided, if required to complete coursework, would need to be accessible. The rules do not specifically mention textbooks. However the DOJ asks:


Question 26: Are there particular issues relating to the accessibility of digital books and textbooks that the DOJ should consider in finalizing this rule? Are there particular issues that the DOJ should consider regarding the impact of this rule on libraries?

Question to Consider: Has textbook accessibility been a barrier to accessing courses? What are some examples of problems you’ve encountered? How common are these problems? What could help?


Other exemptions

The DOJ also exempts linked 3rd party information (if it is not providing a direct service) and individualized, password-protected documents (such as personal utility bills). However it specifies that if these documents have deadlines associated with them, and are not accessible, they need to adjust their deadlines “to ensure that a person with a disability has equal access to its services, programs, or activities.” The DOJ asks about whether proper processes are in place:


Question to Consider: How might a delay in receiving an accessible document affect you? For example, could it affect whether you receive care services, money for food, or healthcare services that could cause harm if delayed? If you think this is a concern, what would be a reasonable deadline for receiving these documents?

Question 46: Do public entities have adequate systems for receiving notification that an individual with a disability requires access to an individualized, password-protected conventional electronic document? What kinds of burdens do these notification systems place on individuals with disabilities and how easy are these systems to access? Should the DOJ consider requiring a particular system for notification or a particular process or timeline that entities must follow when they are on notice that an individual with a disability requires access to such a document?


How is “accessible” defined?

The ADA has always included digital accessibility. However, a lack of specific standards in the past has left public entities to define for themselves what compliance looks like. The result has been a lack of consistent attention to accessibility. According to the DOJ, “voluntary compliance … has been insufficient in providing access.”

Now, the DOJ is requiring public entities to follow the Web Content Accessibility Guidelines (WCAG)version 2.1, at the AA level. This is a carefully tested web standard which has recently been expanded to touch on mobile accessibility needs as well. 


Question 3: Are there technical standards or performance standards other than WCAG 2.1 that the Department should consider? … If so, what is a reasonable time frame for State and local compliance with WCAG 2.2 and why? Is there any other standard that the Department should consider, especially in light of the rapid pace at which technology changes?


The DOJ notes that “the Access Board’s section 508 standards include additional requirements applicable to mobile apps that are not in WCAG 2.1 [including]: interoperability requirements to ensure that a mobile app does not disrupt a device’s assistive technology for persons with disabilities (e.g., screen readers for persons who are blind or have low vision); requirements for mobile apps to follow preferences on a user’s phone such as settings for color, contrast, and font size; and requirements for caption controls and audio description controls that enable users to adjust caption and audio description functions.


Question 8: Is WCAG 2.1 Level AA the appropriate accessibility standard for mobile apps? Should the Department instead adopt another accessibility standard or alternative for mobile apps, such as the requirements from section 508 discussed above?


The DOJ also notes that this includes captioning of “live audio,” such as in real-time presentations. They note that many meetings have moved online since the start of the COVID-19 pandemic, making live audio captioning “even more critical for individuals with certain types of disabilities to participate fully in civic life.” Proper live audio captioning includes speaker identification as well as accurate transcription of spoken text, sound effects, and other significant audio. Live audio captioning of this sort cannot be automated, and the DOJ is concerned about costs. They ask:


Question 13: Should the Department consider a different compliance date for the captioning of live-audio content in synchronized media or exclude some public entities from the requirement?

Question 14: What types of live-audio content do public entities and small public entities post? What has been the cost for providing live-audio captioning?


Finally, the DOJ notes that “WCAG 2.1 can be interpreted to permit the development of two separate websites—one for individuals with relevant disabilities and another for individuals without relevant disabilities—even when doing so is unnecessary and when users with disabilities would have a better experience using the main web page.” They rightly point out that this raises “concerns about user experience, segregation of users with disabilities, unequal access to information, and maintenance”. Thus the proposed rule explicitly states that parallel development of a separate website, document or app is “permissible only where it is not possible to make websites and web content directly accessible due to technical limitations (e.g., technology is not yet capable of being made accessible) or legal limitations (e.g., web content is protected by copyright).”  They go on to ask:


Question 49: Would allowing [a separate alternate version of a website, document, or app] due to technical or legal limitations result in individuals with disabilities receiving unequal access to a public entity’s services, programs, and activities?


How will compliance be measured?

The DOJ has many questions about the best way to measure compliance. The DOJ acknowledges that a public entity might reasonably not be in full compliance with all of WCAG 2.1’s AA standards at all times. This is because web content changes frequently, assessments may not always agree, and may include thousands of pages of content, making compliance more difficult than ensuring access to, say, “a town hall that is renovated once a decade…. The Department also believes that slight deviations from WCAG 2.1 Level AA may be more likely to occur without having a detrimental impact on access than is the case with the ADA Standards. Additionally, it may be easier for an aggrieved individual to find evidence of noncompliance with WCAG 2.1 Level AA than noncompliance with the ADA Standards, given the availability of many free testing tools and the fact that public entities’ websites can be accessed from almost anywhere.” 

They discuss several alternatives that could allow for the necessity of slight deviations and short periods of noncompliance while still promoting high compliance overall, including a percentage-based standard (which may be difficult to implement, and may need to weight different aspects of WCAG 2.1 differently to achieve equity); a standard based on policies for feedback, testing and remediation (which may be inconsistently applied); or “organizational maturity” meaning the organization can show it has a robust accessibility program in place (which may not translate to full accessibility or compliance). They solicit commentary on compliance: 


The DOJ asks what evidence an allegation of noncompliance requires (Question 50); Whether organizational feedback practices, testing policies, remediation practices, or organizational maturity should matter in assessing compliance (Questions 51, 55, 58). The DOJ also asks about what specific feedback practices, testing policies, remediation policies, and level of organizational maturity are needed (Questions 52, 53, 54, 59). They also ask:

Question 62: Should the Department address the different level of impact that different instances of nonconformance with a technical standard might have on the ability of people with disabilities to access the services, programs, and activities that a public entity offers via the web or a mobile app? If so, how?


To conclude, the DOJ’s proposed rule covers a number of topics that are of great importance to people with disabilities. We strongly urge you to comment on the rule.

If you have any questions, reach out to CREATE at create-contact@uw.edu.