Last week, DOJ came out with a proposed rule for title II entities with respect to mobile apps and their Internet sites, here. Certainly big news, so we are going to talk about it. As usual, the blog entry is divided into categories and they are: purpose of proposed rule, need for the rule, and benefits of the rule; the text of the proposed rule; and 60+ questions. Please note that my thoughts/takeaways/questions appear underneath the applicable section of the proposed rule.

 

I

Purpose of Proposed Rule, Need for the Rule, and Benefits of the Rule

 

  1. DOJ since 1996, consistently has taken the viewpoint that title II of the ADA applies to all services, programs, and activities of the public entities, including those provided by the way of the web.
  2. Governmental entities use apps and websites all the time and members of the public frequently access governmental entities through their website and through associated apps in a myriad of different ways. Therefore, it is critical to ensure that people with disabilities can access web content and mobile apps quickly, easily, independently, and equally (the proposed rule contains numerous examples of the ways that people access governmental entities by way of the web and mobile apps).
  3. While many public health mandates addressing Covid-19 are no longer in place, durable changes to State and local governmental entities operations and public preferences necessitating greater access online services, program, and activities remain and are likely to be permanent.
  4. Millions of individuals in the United States have disabilities affecting their use of the web and mobile apps. Many of those individuals use assistive technology, such as speech recognition and screen readers, to enable them to navigate websites or access information contained on those websites.
  5. Voluntary compliance with the web content accessibility guidelines has not resulted in equal access for people with disabilities.
  6. DOJ and other federal agencies have taken enforcement action against public entities regarding the lack of access for people with disabilities to their websites.
  7. Web Content Accessibility Guidelines 2.0 has been consistently used by DOJ as the basis for settlements.
  8. A 2021 study found that 71% of county websites did not conform to Web Content Accessibility Guidelines 2.0 and the remaining 29% only partially conformed to the standards. Given the minimal progress in web accessibility over the last 20 years, DOJ does not expect compliance with Web Content Accessibility Guidelines 2.1 level AA to improve significantly in the absence of a rule.
  9. The rule will foster increased independence, flexibility, and dignity for persons with disabilities when accessing the services, programs, and activities of title II entities electronically.
  10. The rule will foster increased privacy for persons with disabilities when accessing the services, programs, and activities of title II entities electronically.
  11. The rule will reduce frustration experienced by people with disabilities when accessing the services, programs, and activities of title II entities electronically.
  12. The rule will decrease the need for persons with disabilities to rely on others while they attempt to access title II entities by ways of electronic means.
  13. The rule will increase program participation for persons with disabilities.
  14. The rule will increase civic engagement and inclusion.
  15. The rule will increase certainty about what constitutes an accessible website under the ADA and potentially reduce litigation.

 

II

The Proposed Rule Text (my thoughts//takeaways/questions appear within).

PART 35—NONDISCRIMINATION ON THE BASIS OF DISABILITY IN STATE AND LOCAL GOVERNMENT SERVICES

  1. The authority citation for part 35 continues to read as follows:

Authority: 5 U.S.C. 301; 28 U.S.C. 509, 510; 42 U.S.C. 12134, 12131, and 12205a.

Subpart A—General

  1. Amend § 35.104 by adding definitions for Archived web content, Conventional electronic documents, Mobile applications (apps), Special district government, Total population, WCAG 2.1, and Web content in alphabetical order to read as follows:

Definitions.

* * * * *

Archived web content means web content that—

(1) Is maintained exclusively for reference, research, or recordkeeping;

(2) Is not altered or updated after the date of archiving; and

(3) Is organized and stored in a dedicated area or areas clearly identified as being archived.

* * * * *

Conventional electronic documents means web content or content in mobile apps that is in the following electronic file formats: portable document formats (“PDF”), word processor file formats, presentation file formats, spreadsheet file formats, and database file formats.

* * * * *

Mobile applications (“apps”) means software applications that are downloaded and designed to run on mobile devices, such as smartphones and tablets.

* * * * *

Special district government means a public entity—other than a county, municipality, or township, or independent school district—authorized by State law to provide one function or a limited number of designated functions with sufficient administrative and fiscal autonomy to qualify as a separate government and whose population is not calculated by the United States Census Bureau in the most recent decennial Census or Small Area Income and Poverty Estimates.

* * * * *

Total population means the population estimate for a public entity as calculated by the United States Census Bureau in the most recent decennial Census or, if a public entity is an independent school district, the population estimate as calculated by the United States Census Bureau in the most recent Small Area Income and Poverty Estimates.

* * * * *

WCAG 2.1 means the Web Content Accessibility Guidelines (“WCAG”) 2.1, W3C® Recommendation 05 June 2018, https://www.w3.org/​TR/​2018/​REC-WCAG21-20180605/​ [ https://perma.cc/​UB8A-GG2F]. WCAG 2.1 is incorporated by reference elsewhere in this part (see § 35.200 and 35.202).

Web content means information or sensory experience—including the encoding that defines the content’s structure, presentation, and interactions—that is communicated to the user by a web browser or other software. Examples of web content include text, images, sounds, videos, controls, animations, and conventional electronic documents.

Subpart H—Web and Mobile Accessibility

  1. Add new subpart H to read as follows:

Subpart H—Web and Mobile Accessibility

35.200

Requirements for web and mobile accessibility.

35.201

Exceptions.

35.202

Conforming alternate versions.

35.203

Equivalent facilitation.

35.204

Duties.

35.205–35.209

[Reserved]

Requirements for web and mobile accessibility.

  • A public entity shall ensure that the following are readily accessible to and usable by individuals with disabilities:

(1) Web content that a public entity makes available to members of the public or uses to offer services, programs, or activities to members of the public; and

(2) Mobile apps that a public entity makes available to members of the public or uses to offer services, programs, or activities to members of the public.

Thoughts/takeaways/Questions: the standard is readily accessible and usable. What does that mean? Currently, title II litigation, as well as a title III litigation for that matter, turns on whether there is meaningful accessibility for a particular person with a disability.

(b) Requirements

(1) Effective two years from the publication of this rule in final form, a public entity, other than a special district government, with a total population of 50,000 or more shall ensure that the web content and mobile apps it makes available to members of the public or uses to offer services, programs, or activities to members of the public comply with Level A and Level AA success criteria and conformance requirements specified in WCAG 2.1, unless the public entity can demonstrate that compliance with this section would result in a fundamental alteration in the nature of a service, program, or activity or in undue financial and administrative burdens.

(2) Effective three years from the publication of this rule in final form, a public entity with a total population of less than 50,000 or any public entity that is a special district government shall ensure that the web content and mobile apps it makes available to members of the public or uses to offer services, programs, or activities to members of the public comply with Level A and Level AA success criteria and conformance requirements specified in WCAG 2.1, unless the public entity can demonstrate that compliance with this section would result in a fundamental alteration in the nature of a service, program, or activity or in undue financial and administrative burdens.

(3) WCAG 2.1 is incorporated by reference into this section with the approval of the Director of the Federal Register under 5 U.S.C. 552(a) and 1 CFR part 51. All approved incorporation by reference (“IBR”) material is available for inspection at the U.S. Department of Justice and at the National Archives and Records Administration (“NARA”). Contact the U.S. Department of Justice at: Disability Rights Section, Civil Rights Division, U.S. Department of Justice, 150 M St. NE, 9th Floor, Washington, DC 20002; ADA Information Line: (800) 514–0301 (voice) or 1–833–610–1264 (TTY); website: www.ada.gov. For information on the availability of this material at NARA, visit www.archives.gov/​federal-register/​cfr/​ibr-locations.html or email fr.inspection@nara.gov. The material may be obtained from the World Wide Web Consortium (“W3C®”) Web Accessibility Initiative (“WAI”), 401 Edgewater Place, Suite 600, Wakefield, MA 01880; phone: (339) 273–2711; email: contact@w3.org; website: www.w3.org/​TR/​2018/​REC-WCAG21-20180605/​ [ https://perma.cc/​UB8A-GG2F].

Thoughts/takeaways/questions:

  1. WCAG is not static. I know there has been talk about a WCAG 3.0 that might have a radically different look. What happens as the WCAG evolves?
  2. Level AA and level A both need to be complied with.
  3. The years a title II entity has to comply depends upon the population of where the title II entity is and not the population of what the particular title II entity serves.
  4. Undue financial and administrative burden is going to be very difficult to show because you look to the entire resources of the title II entity and because a high-level person in the governmental entity will have to certify that such a burden exists. Further, everything short of undue financial and administrative burden must be done first.

Exceptions.

The requirements of § 35.200 of this chapter do not apply to the following:

(a) Archived web content. Archived web content as defined in § 35.104 of this chapter.

(b) Preexisting conventional electronic documents. Conventional electronic documents created by or for a public entity that are available on a public entity’s website or mobile app before the date the public entity is required to comply with this rule, unless such documents are currently used by members of the public to apply for, gain access to, or participate in a public entity’s services, programs, or activities.

Thoughts/takeaways/questions:

  1. This particular provision deals with conventional electronic documents created by or for a public entity available on the website or mobile app for the date the public entity is required to comply with the rule. After that date, those conventional documents need to be accessible to persons with disabilities.

(c) Web content posted by a third party. Web content posted by a third party that is available on a public entity’s website.

(d) Linked third-party web content. Third-party web content linked from a public entity’s website, unless the public entity uses the third-party web content to allow members of the public to participate in or benefit from the public entity’s services, programs, or activities.

Thoughts/takeaways/questions:

  1. The second clause is critical. That is, third-party web content has to be accessible to persons with disabilities if the third-party web content is being used to allow the members of the public to participate in or benefit from the public entity’s services, program, or activities.
  2. The DOJ specifically says when talking about this particular section that a public entity may not delegate away its obligations under the ADA. See also this blog entry.

(e) Public postsecondary institutions: password-protected course content. Except as provided in paragraphs (e)(1) and (2) of this section, course content available on a public entity’s password-protected or otherwise secured website for admitted students enrolled in a specific course offered by a public postsecondary institution.

(1) This exception does not apply if a public entity is on notice that an admitted student with a disability is pre-registered in a specific course offered by a public postsecondary institution and that the student, because of a disability, would be unable to access the content available on the public entity’s password-protected or otherwise secured website for the specific course. In such circumstances, all content available on the public entity’s password-protected or otherwise secured website for the specific course must comply with the requirements of § 35.200 by the date the academic term begins for that course offering. New content added throughout the term for the course must also comply with the requirements of § 35.200 at the time it is added to the website.

(2) This exception does not apply once a public entity is on notice that an admitted student with a disability is enrolled in a specific course offered by a public postsecondary institution after the start of the academic term and that the student, because of a disability, would be unable to access the content available on the public entity’s password-protected or otherwise secured website for the specific course. In such circumstances, all content available on the public entity’s password-protected or otherwise secured website for the specific course must comply with the requirements of § 35.200 within five business days of such notice. New content added throughout the term for the course must also comply with the requirements of § 35.200 at the time it is added to the website.

(f) Public elementary and secondary schools: password-protected class or course content. Except as provided in paragraphs (f)(1) through (4) of this section, class or course content available on a public entity’s password-protected or otherwise secured website for students enrolled, or parents of students enrolled, in a specific class or course at a public elementary or secondary school.

(1) This exception does not apply if the public entity is on notice of the following: a student with a disability is pre-registered in a specific class or course offered by a public elementary or secondary school and that the student, because of a disability, would be unable to access the content available on the public entity’s password-protected or otherwise secured website for the specific class or course. In such circumstances, all content available on the public entity’s password-protected or otherwise secured website for the specific class or course must comply with the requirements of § 35.200 by the date the term begins for that class or course. New content added throughout the term for the class or course must also comply with the requirements of § 35.200 at the time it is added to the website.

(2) This exception does not apply if the public entity is on notice of the following: a student is pre-registered in a public elementary or secondary school’s class or course, the student’s parent has a disability, and the parent, because of a disability, would be unable to access the content available on the password-protected or otherwise secured website for the specific class or course. In such circumstances, all content available on the public entity’s password-protected or otherwise secured website for the specific class or course must comply with the requirements of § 35.200 by the date the term begins for that class or course. New content added throughout the term for the class or course must also comply with the requirements of § 35.200 at the time it is added to the website.

(3) This exception does not apply once a public entity is on notice of the following: a student with a disability is enrolled in a public elementary or secondary school’s class or course after the term begins and that the student, because of a disability, would be unable to access the content available on the public entity’s password-protected or otherwise secured website for the specific class or course. In such circumstances, all content available on the public entity’s password-protected or otherwise secured website for the specific class or course must comply with the requirements of § 35.200 within five business days of such notice. New content added throughout the term for the class or course must also comply with the requirements of § 35.200 at the time it is added to the website.

(4) This exception also does not apply once a public entity is on notice of the following: a student is enrolled in a public elementary or secondary school’s class or course after the term begins, and the student’s parent has a disability, and the parent, because of a disability, would be unable to access the content available on the public entity’s password-protected or otherwise secured website for the specific class or course. In such circumstances, all content available on the public entity’s password-protected or otherwise secured website for the specific class or course must comply with the requirements of § 35.200 within five business days of such notice. New content added throughout the term for the class or course must also comply with the requirements of § 35.200 at the time it is added to the website.

(g) Individualized, password-protected documents. Conventional electronic documents that are: (1) about a specific individual, their property, or their account; and (2) password-protected or otherwise secured.

Thoughts/takeaways/questions:

  1. I find the password protection exceptions a bit strange because they go against the principles of universal design. Basically, if an educational institution has a password protection system in place, it doesn’t have to worry about accessibility for persons with disabilities so long as it is not on notice that a person with a disability is taking that class or needs that password. Same for parents. Universal design would suggest that you always focus on disability accessibility. It will be interesting to see how this plays out.
  2. The exception puts a premium on the person with the disability or the parent notifying the public entity of the need for an accommodation due to a disability. In dealing with this principle, remember magic words are not required.
  3. DOJ in their discussion of this particular section of the proposed rule talks about whether a person would be unable because of a disability to access the content posted on the password-protected website for that class or course. It goes on to say that the phrase “unable to access,” is intended to cover situations where a student’s disability would limit or prevent their ability to equally access the relevant content. DOJ also uses “on the basis of,” in this document as well. The two concepts arguably mean the same thing. See this blog entry.
  4. There are specific timing requirements as to when the material appearing in the password-protected course must be made accessible to persons with disabilities.

Conforming alternate versions.

  • A public entity may use conforming alternate versions of websites and web content, as defined by WCAG 2.1, to comply with § 35.200 only where it is not possible to make websites and web content directly accessible due to technical or legal limitations.

Thoughts/takeaways/questions:

  1. The DOJ makes clear that this is not a favored approach and should only be used rarely.
  2. Separate but equal is not a thing and DOJ recognizes that. See also this blog entry where the Department of Transportation specifically ruled out such an approach.
  3. This particular provision bears watching to see if separate but equal becomes a thing. DOJ actually has a specific question it seeks common on with respect to this issue (see the 60+ questions section below).

(b) WCAG 2.1 is incorporated by reference into this section with the approval of the Director of the Federal Register under 5 U.S.C. 552(a) and 1 CFR part 51. All approved incorporation by reference (“IBR”) material is available for inspection at the U.S. Department of Justice and at the National Archives and Records Administration (“NARA”). Contact the U.S. Department of Justice at: Disability Rights Section, Civil Rights Division, U.S. Department of Justice, 150 M St. NE, 9th Floor, Washington, DC 20002; ADA Information Line: (800) 514–0301 (voice) or 1–833–610–1264 (TTY); website: www.ada.gov. For information on the availability of this material at NARA, visit www.archives.gov/​federal-register/​cfr/​ibr-locations.html or email fr.inspection@nara.gov. The material may be obtained from the World Wide Web Consortium (“W3C®”) Web Accessibility Initiative (“WAI”), 401 Edgewater Place, Suite 600, Wakefield, MA 01880; phone: (339) 273–2711; email: contact@w3.org; website: www.w3.org/​TR/​2018/​REC-WCAG21-20180605/​ [ https://perma.cc/​UB8A-GG2F].

Equivalent facilitation.

Nothing in this subpart prevents the use of designs, methods, or techniques as alternatives to those prescribed, provided that the alternative designs, methods or techniques result in substantially equivalent or greater accessibility and usability of the web content or mobile app.

Duties.

Where a public entity can demonstrate that full compliance with the requirements of § 35.200 would result in a fundamental alteration in the nature of a service, program, or activity or in undue financial and administrative burdens, compliance with § 35.200 is required to the extent that it does not result in a fundamental alteration or undue financial and administrative burdens. In those circumstances where personnel of the public entity believe that the proposed action would fundamentally alter the service, program, or activity or would result in undue financial and administrative burdens, a public entity has the burden of proving that compliance with § 35.200 would result in such alteration or burdens. The decision that compliance would result in such alteration or burdens must be made by the head of a public entity or their designee after considering all resources available for use in the funding and operation of the service, program, or activity, and must be accompanied by a written statement of the reasons for reaching that conclusion. If an action would result in such an alteration or such burdens, a public entity shall take any other action that would not result in such an alteration or such burdens but would nevertheless ensure that individuals with disabilities receive the benefits or services provided by the public entity to the maximum extent possible.

 

Thoughts/takeaways/questions:

 

  1. When an individual on the basis of a disability cannot access or does not have equal access to a service, program, or activity through a public entity’s web content or mobile app that conform to WCAG 2.1 level AA, the public entity still has the obligation to provide the individual an alternative method of access to that service, program, or activity unless the public entity can demonstrate that the alternative methods of access results in a fundamental alteration in the nature of the service, program, or activity or in an undue financial and administrative burden.
  2. Just because an entity is in full compliance with the rule’s web or mobile app accessibility standard, that does not mean it has met all of its obligations under the ADA or other applicable laws.
  3. Remember, the ADA always requires an individualized analysis.

 

III

60+ questions

 

  1. The proposed rule contains over 60 questions for people to comment on. The questions are quite elaborate. Accordingly, considering the thousands and thousands of comments likely to come in on this rule, the need for DOJ to evaluate those comments, and then the need to formulate a final rule based upon the comments that come in, one wonders whether this proposed rule will not suffer the same fate as the Obama proposed rules depending upon the 2024 election results. Is there simply enough time to complete the process? I am not so sure.
  2. Now is the time for anyone interested or affected by the proposed rule to get in their comments. You have 60 days from August 4 to submit those comments. Once a rule becomes finalized, it is much harder to affect the rule.
  3. The 60 questions include the following topics:
    1. Whether DOJ should craft a more flexible definition of what is a conventional electronic document or stick with their list, which is exhaustive and focuses on specific file types.
    2. Whether any refinement to the definition of web content is in order.
    3. Is there a technical standard or performance standard other than WCAG 2.1 that the DOJ should consider? (I am doubtful that such a thing exists unless you want to look to the European Union).
    4. What are the compliance costs and challenges that small public entities would face in conforming with the rule and what resources do such entities have to comply with the rule. A related question is whether a different WCAG version or conformance level should be required for small public entities or for a subset of such entities.
    5. How do public entities use social media platforms and how do members of the public use content made available by public entities on their social media platforms and what are the barriers people with disabilities encounter.
    6. Several questions going to the viability of the tiered approach to when entities must comply with the rule and whether something other than population size might be used as the standard.
    7. With respect to live audio content and captioning of same, whether the DOJ should consider a different compliance date. Also, what types of live audio content do public entities and small public entities post and what are the costs associated with same.
    8. How do public entity currently manage content maintained for reference, research, or record-keeping.
    9. What is the impact of the exceptions on people with disabilities and how will foreseeable advances in technology affect those exceptions.
    10. What types of external mobile apps if any, do public entities use to offer the services, programs and activities to members of the public, and how accessible are those apps. (For example, the town that I live in uses a third-party mobile parking app).
    11. Any issues relating to accessibility of digital books and textbooks that DOJ should consider when finalizing the rule. Any impact of the rule on libraries.
    12. With respect to the exceptions, how difficult is complying with the rule if the exceptions are not there at all.
    13. Just how far do educational institutions go with the utilization of password-protected websites and mobile apps with respect to students and parents. Several other related questions.
    14. Do elementary and secondary schools have a system allowing a parent with a disability to provide notice of their need for an accessible class or course content (they absolutely should if they don’t already).
    15. The kind of individualized conventional electronic document that public entities make available and how are they made available. What is the difficulty of making those documents accessible.
    16. How significant is the separate but equal risk.
    17. How is compliance to be measured. Are there particular approaches that are better than others.
    18. What should be considered sufficient evidence to support an allegation of noncompliance with the technical standard for purposes of enforcement actions and what should be considered in that process. A slew of related question regarding how actual compliance will be determined.