<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 16px; color: rgb(0, 0, 0);">
<span style="background-color: rgb(255, 255, 255);">¡Hola!</span></div>
<div id="Signature" class="elementToProof">
<p style="text-align: left; text-indent: 0px; background-color: rgb(255, 255, 255); margin: 0px;">
<span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);"><br>
</span></p>
<p class="elementToProof" style="text-align: left; text-indent: 0px; background-color: rgb(255, 255, 255); margin: 0in;">
<span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">At some point, I ended up registering for the Interagency Accessibility Forum and I forgot to share about such
opportunity with all of you. My apologies!</span></p>
<p class="elementToProof" style="text-align: left; text-indent: 0px; background-color: rgb(255, 255, 255); margin: 0in;">
<span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);"><br>
</span></p>
<p class="elementToProof" style="text-align: left; text-indent: 0px; background-color: rgb(255, 255, 255); margin: 0in;">
<span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">The forum took place yesterday and today. Great presentations. Some demos about new accessibility tools for example
for navigating physical spaces (<a href="https://www.mablemaps.com/" id="LPlnk699105" title="https://www.mablemaps.com/" style="margin-top: 0px; margin-bottom: 0px;">MABLEmaps</a> or
<a href="https://pmc.ncbi.nlm.nih.gov/articles/PMC9696753/" id="LPlnk120919" title="https://pmc.ncbi.nlm.nih.gov/articles/PMC9696753/" style="margin-top: 0px; margin-bottom: 0px;">
UNav</a>), Graphics Accessibility solution (<a href="https://inclusiocommunity.com/" id="LPlnk245380" title="https://inclusiocommunity.com/" style="margin-top: 0px; margin-bottom: 0px;">Inclusio</a>) or AI transcription enhancements for people with speech
disabilities (<a href="https://www.heardai.ai/" id="LPlnk469051" title="https://www.heardai.ai/" style="margin-top: 0px; margin-bottom: 0px;">Heardai.ai</a>). The bulk of the sessions were about the 508 annual assessment process, procurement, Accessibility
Compliance Reports, Accessibility Requirements Tool (ART) and Solicitation Review Tool (SRT)</span></p>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
Session descriptions and slide presentations available for download at <a href="https://www.section508.gov/iaaf/archives/agenda-2025/" id="OWA465f7ade-9c8e-5fb7-1515-19bfb861e80e" class="OWAAutoLink">
https://www.section508.gov/iaaf/archives/agenda-2025/</a>. Some videos might be posted once they are made accessible (captions + descriptive video).</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
<br>
</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
Below, the content of a couple of slides along with a section of the live transcript when the presenter, Jessie Weber, discussed exceptions to the rule and some of the Q&A's responses that followed</div>
<div style="text-align: left; text-indent: 0px; margin: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
<br>
</div>
<div style="text-align: left; text-indent: 0px; margin: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
<b>ADA Title 2 Web & Mobile Accessibility</b></div>
<p class="elementToProof" style="direction: ltr; text-align: left; text-indent: -0.44in; line-height: normal; background-color: rgb(255, 255, 255); margin: 7pt 0in 0pt 0.5in;">
<span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">\u2022<b>Overview:</b> Part of the Americans with Disabilities Act (ADA), focusing on state and local government services</span></p>
<div class="elementToProof" style="direction: ltr; text-align: left; text-indent: -0.44in; line-height: normal; margin: 7pt 0in 0pt 0.5in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
\u2022<b>Applicability: </b>all state and local governments (which includes any agencies or departments of state or local governments) as well as special purpose districts, Amtrak, and other commuter authorities.</div>
<div class="elementToProof" style="direction: ltr; text-align: left; text-indent: -0.44in; line-height: normal; margin: 7pt 0in 0pt 0.5in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
\u2022<b>Effective Date(s)</b>: </div>
<div class="elementToProof" style="direction: ltr; text-align: left; text-indent: -0.43in; line-height: normal; margin: 7pt 0in 0pt 1in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
\u25aaDepends on government size: (50,000+) April 2026; (special districts, >50,000) April 2027</div>
<div class="elementToProof" style="direction: ltr; text-align: left; text-indent: -0.44in; line-height: normal; margin: 7pt 0in 0pt 0.5in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
\u2022<b>Technical Standards developed</b> by the U.S. Department of Justice</div>
<div class="elementToProof" style="direction: ltr; text-align: left; text-indent: -0.43in; line-height: normal; margin: 7pt 0in 0pt 1in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
\u25aaWCAG version: 2.1 Level AA, Conforming Alternate Version (limited)</div>
<div class="elementToProof" style="direction: ltr; text-align: left; text-indent: -0.44in; line-height: normal; margin: 7pt 0in 0pt 0.5in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
\u2022<b>Enforcement & Penalties</b>: primarily DOJ, DOE (educational institutions), and others</div>
<div class="elementToProof" style="direction: ltr; text-align: left; text-indent: -0.44in; line-height: normal; margin: 7pt 0in 0pt 0.5in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
\u2022<b>Covered ICT Examples</b>: Websites (county library, public school LMS), Mobile Apps (city parking app)</div>
<div class="elementToProof" style="direction: ltr; text-align: left; text-indent: -0.44in; line-height: normal; margin: 7pt 0in 0pt 0.5in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
\u2022<b>Exceptions</b>: 1. Archived web content, 2. Preexisting conventional electronic documents, 3. Content posted by a third party where the third party is not posting due to contractual, licensing, or other arrangements with a public entity, 4. Individualized
documents that are password-protected, 5. Preexisting social media posts.</div>
<div style="text-align: left; text-indent: 0px; margin: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
<br>
</div>
<p class="elementToProof" style="text-align: left; text-indent: 0px; background-color: rgb(255, 255, 255); margin: 0in;">
<span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);"><br>
</span></p>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
<b>Live Transcript:</b></div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
<br>
</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
Let me talk about the exceptions to the new web regulation. I will preface this so I try not to repeat after each one the exceptions do not mean the public entity don't have to make these types of content accessible. What it means they don't have to ensure
right off the bat proactively all are being offered an accessible format but if somebody requests to access information and need it accessibly the public entity still has to provide it and they still have to provided in accordance with the existing Title 2
regulations which says timely basis. I will talk about each exception but I think it's important for public entities or anyone doing business with them to know entities still need a plan in place for quickly providing all of these types of documents, web content
examples, and accessible format quickly upon request. They can't sit back and do nothing in these areas.</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
The first category is archived web content, this is part of web content created before the compliance date under the new regs is kept only or reference researcher record-keeping it has to be kept in a special area for archived content and labeled as such and
there can't be any changes if you change 1 thing and that archived content, you have to make the whole thing accessible</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
The second is pre-existing conventional electronic documents, I think probably a lot of PDFs if they were available before compliance not currently being used they can remain as is until someone requests an accessible version. However if any are still being
used to apply for program or service, access program or service in any way expected to be used, this does not apply they have to be posted accessibly on the website.</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
The third exception is third-party content and this is limited. I want to be clear this is about work third party post content on a public entities website and the public entity did not ask them to do it the example is a comment on a message board. In that
example the message board itself becomes a public entity still needs to be accessible if someone posts something inaccessible in a comment the public entity is not responsible for proactively making it accessible. If someone requests it they need to make it
accessible. This does not cover anything the public entity asks the third party to put on their website so a calendar or weather widget even if the third party makes it if the public entity invites it to be on the website it needs to make sure it's accessible.</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
Fourth exception is individualized documents password-protected you can think about bank bills or individual utility bills, they cannot be documents that have to be account person secured in some way. They need to be made accessible on demand in the fifth category
is pre-existing social media posts may be for the compliance date. The others I will know there are general defenses that exist under Title 2 which is undue burden and undo administrative financial burden, would be costly or difficult that way more fundamental
alteration your asking us to make a new website fundamentally alter the services we provide I will note both defenses are difficult to meet. There has to be a statement in writing from the head of the public entity or designee explaining the rationale and
they kind of looked at the resources available, and still reach the conclusion. I can tell you from an enforcement perspective I really see public entities do that. It exists those are defenses but are challenging to establish. I will point out a couple of
things I think are notable not subject to these exception there was some debate during the proposed rulemaking process whether they ought to be exempt or not. They are not, so a big area is education, I think institutions of higher education were trying to
advocate for a wait and see students with disabilities can't we wait for them to come to us and then we will make materials accessible. And they said no, the DOJ said how long it can take to make materials accessible and students have deadlines. It's a stressful
environment so schools need to plan ahead even before a single student with a disability in roles in the school or class all digital content needs to be accessible including password-protected course materials and educational technology needs to be accessible
from the get go.</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
A public library everything needs to be accessible captioning for live audio content does not fall into an exception that needs to be happening now.</div>
<div style="text-align: left; text-indent: 0px; margin: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);">
<br>
</div>
<p class="elementToProof" style="text-align: left; text-indent: 0px; background-color: rgb(255, 255, 255); margin: 0in;">
<span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"><br>
</span></p>
<div class="elementToProof" style="direction: ltr; text-align: left; text-indent: -0.44in; line-height: normal; margin: 7pt 0in 0pt 80px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<b>ADA Resources</b></div>
<div class="elementToProof" style="direction: ltr; text-align: left; text-indent: -0.44in; line-height: normal; margin: 7pt 0in 0pt 80px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
\u2022<a href="https://www.ada.gov/resources/2024-03-08-web-rule/" id="OWA2ae3e3a3-258e-81c5-e1a6-c035d0aeeb9f" class="OWAAutoLink">Fact Sheet</a>: This document provides a high-level summary of the rule. It is designed to provide an overview of the rule\u2019s main
requirements for state and local governments.</div>
<div class="elementToProof" style="direction: ltr; text-align: left; text-indent: -0.44in; line-height: normal; margin: 7pt 0in 0pt 80px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
\u2022<a href="https://www.ada.gov/resources/small-entity-compliance-guide/" id="OWA6543d3a6-8f74-648e-d05b-6009cc077951" class="OWAAutoLink">Small Entity Compliance Guide</a>: The Department issued a guide to assist small entities in complying with the rule.</div>
<div class="elementToProof" style="direction: ltr; text-align: left; text-indent: -0.44in; line-height: normal; margin: 7pt 0in 0pt 80px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
\u2022<a href="https://www.ada.gov/resources/web-rule-first-steps/" id="OWA33e400a5-b3e9-d31c-859f-61b2f7fa969b" class="OWAAutoLink">Planning for Compliance</a>: This resource includes suggested steps that ADA Coordinators and others may want to take to prepare
their state or local governments to comply with the rule.</div>
<div class="elementToProof" style="direction: ltr; text-align: left; text-indent: -0.44in; line-height: normal; margin: 7pt 0in 0pt 80px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
\u2022<a href="https://www.youtube.com/watch?v=hkhIGSvJC2o" id="OWAb9e2280a-7ced-ed5c-b404-61a74b5f9580" class="OWAAutoLink">Webinar: Americans with Disabilities Act Title II Web & Mobile Application Accessibility Rule</a></div>
<div class="elementToProof" style="direction: ltr; text-align: left; text-indent: -0.44in; line-height: normal; margin: 7pt 0in 0pt 80px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
\u2022<a href="https://www.ada.gov/law-and-regs/regulations/title-ii-2010-regulations/" id="OWA72d85f58-8a94-8305-0538-1f98cc1fa6bf" class="OWAAutoLink">ADA Subpart H \u2014Web and Mobile Accessibility</a></div>
<div class="elementToProof" style="direction: ltr; text-align: left; text-indent: -0.44in; line-height: normal; margin: 7pt 0in 0pt 80px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
\u2022<a href="http://www.ada.gov/" id="OWA517e6a55-3360-08ec-5f1b-7d2a3f23b169" class="OWAAutoLink">www.ada.gov</a></div>
<div class="elementToProof" style="direction: ltr; text-align: left; text-indent: -0.44in; line-height: normal; margin: 7pt 0in 0pt 80px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
\u2022<b>ADA Information Line</b></div>
<div class="elementToProof" style="direction: ltr; text-align: left; text-indent: -0.43in; line-height: normal; margin: 7pt 0in 0pt 120px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
\u25aa800-514-0301 | 1-833-610-1264 (TTY)</div>
<div class="elementToProof" style="direction: ltr; text-align: left; text-indent: -0.43in; line-height: normal; margin: 7pt 0in 0pt 120px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
\u25aaM, Tu, W, F: 9:30am - 12pm and 3pm - 5:30pm ET</div>
<div class="elementToProof" style="direction: ltr; text-align: left; text-indent: -0.43in; line-height: normal; margin: 7pt 0in 0pt 120px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
\u25aaTh: 2:30pm - 5:30pm ET</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<b>Q&A</b></div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<i><br>
</i></div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<i>Could you discuss an accessible format vs. the user's preferred format? If an entity merely provides an accessible format, is that sufficient?</i></div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div class="elementToProof" style="margin: 0in 0in 0in 0.375in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Jessie Weber: Under Title II, the public entity must honor the individual's requested format--only exception is if they can show doing so would be undue burden or fundamental alteration. That's different from Titles I and III of the ADA.</div>
<div class="elementToProof" style="margin-top: 1em; margin-bottom: 1em; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<cite style="margin:0in;font-family:Arial;font-size:12.0pt">
<div class="elementToProof"> </div>
</cite></div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<i>Does the "Preexisting conventional electronic documents" exception apply to past documents provided on a public website as reference? Or is it only applicable to documents that are available in a non-web repository that people have to request?</i></div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div class="elementToProof" style="margin: 0in 0in 0in 0.375in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Jessie Weber: Content and documents provided just for reference, that haven't been updated since effective date, and are in designated "archived content" section of website are covered under archived web content exception. The preexisting conventional electronic
documents cover electronic docs in certain formats that are no longer in use, but appear on the website or mobile app. Hope that helps!</div>
<div class="elementToProof" style="margin-top: 1em; margin-bottom: 1em; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(89, 89, 89);">
<cite style="margin:0in;font-family:Calibri;font-size:9.0pt;color:#595959">
<div class="elementToProof"> </div>
</cite></div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<i>ADA Title 2 relies on the public entity to self-enforce, correct? Are there auditor or external assessor requirements? Are Trusted Testers required to be implemented or rather an option for an organization tackling accessibility?</i></div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div class="elementToProof" style="margin: 0in 0in 0in 0.375in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Jessie Weber: Title II has a private right of action, which means any individual can sue to enforce it (so long as they're directly impacted by the lack of accessibility). The DOJ and Dep't of Ed also enforce Title II.</div>
<div class="elementToProof" style="margin: 0in 0in 0in 0.375in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div class="elementToProof" style="margin: 0in 0in 0in 0.375in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Katherine Eng: Trusted Tester's test process is for Section 508 and WCAG 2.0. ADA requires WCAG 2.1, so there will be a few WCAG requirements that Trusted Tester does not test.</div>
<div class="elementToProof" style="margin: 0in 0in 0in 0.375in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<i>My question is about alternate version. If a PDF is not accessible, but we have an accessible webpage with the same information, would it be allowed?</i></div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div class="elementToProof" style="margin: 0in 0in 0in 0.375in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Jessie Weber: The Title 2 regs are pretty suspicious of conforming alternate versions of inaccessible content--recognizing that separate is typically not equal. But it's allowed where the separate version is necessary because of technical or legal limitations.
The DOJ has explained that an example of a \u201ctechnical limitation\u201d would be where \u201ctechnology is not yet capable of being made accessible\u201d and a \u201clegal limitation\u201d may exist where web content \u201ccannot be changed due to legal reason.\u201d The parameters of these
limitations may end up being developed further in the courts. Unless this applies, if none of the 5 exceptions apply, then the PDF would need to be accessible too.</div>
<div class="elementToProof" style="margin: 0in 0in 0in 0.375in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div class="elementToProof" style="margin: 0in 0in 0in 0.375in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Katherine Eng: For Section 508, an accessible web page can be considered a conforming alternate version as long as it meets the criteria, such as how a user would access the accessible version.</div>
<div class="elementToProof" style="margin: 0in 0in 0in 0.375in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<i>Hi Jessie and thank you for the good and detailed explanation. On ADA Title 2 Exception #4, the Individualized documents that are password-protected, does it violate the Equal Employment Opportunity law, that is a disable employee with a password?</i></div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div class="elementToProof" style="margin: 0in 0in 0in 0.375in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Jessie Weber: Title I applies to employment by public entities, so those rules would govern. They are quite different--requiring reasonable accommodations and an interactive process.</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<i>Any feedback on what is considered timely?</i></div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div class="elementToProof" style="margin: 0in 0in 0in 0.375in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Jessie Weber: What is "timely" under Title II is a flexible, fact-specific concept--the focus is always on providing equal opportunity though. In the context of needing course materials before a class discussion of them, "timely" would generally mean receiving
the materials before or at the same time as students without disabilities. That may differ depending on the context and how urgently the materials are needed.</div>
<div class="elementToProof" style="margin: 0in 0in 0in 0.375in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
For state gov in the US, if we have 3rd parties providing websites for services--think of Medicaid and other health coverage-- should we be asking for a VPAT and ACR at least each year to make sure that they are properly testing and resolving access issues?</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div class="elementToProof" style="margin: 0in 0in 0in 0.375in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Jessie Weber: From a legal perspective, the state gov would still be responsible for the website complying with Title II (even if created/maintained by 3rd party), so I would take a number of steps to ensure that the 3rd parties are maintaining accessible websites--required
testing, reports, contract indemnification requirements, etc.</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<i>There was a response to my question regarding making multi-function printer accessible but I lost connectivity and now I don't see the response, please resend</i></div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div class="elementToProof" style="margin: 0in 0in 0in 0.375in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Kristen Smith-O'Connor: From Laura Miller: Chapter 4 of Section 508 addresses hardware requirements and a multi-function printer would fall in that category. Additionally, functional performance criteria are a great start for all of the standards, domestic
and international. You mention audible output, but also consider tactile buttons, braille instructions, and the User interface. Also stayed tuned for a Hardware ICT Testing Baseline that is in development which will provide some guidelines for Section 508.</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<i>Thoughts on creating Accessibility Conformance Reports for gov't websites. Like using a VPAT (template) to assess a site's conformance. We were recently asked for a VPAT for a high level HTML website and are curious if others are already doing this?</i></div>
<div class="elementToProof" style="margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div class="elementToProof" style="margin: 0in 0in 0in 0.375in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Laura Miller: Jennifer, we typically recommend ACRs for tools and functionality that would be leveraged both by your users and by others. Like Login.gov (they have an ACR) or our ACR Editor tool or Training modules. Websites that change frequently would be
difficult to maintain regularly, but if forms or functionality is required by the public, testing and an ACR would be a best practice.</div>
<div style="text-align: left; text-indent: 0px; margin: 0px;"><br>
</div>
<p style="direction: ltr; text-align: left; text-indent: 0px; background-color: rgb(255, 255, 255); margin: 0in;">
<span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">Gracias,</span></p>
<div style="direction: ltr; text-align: left; text-indent: 0px; margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(118, 62, 155);">
<b>Agnes Figueroa</b></div>
<div style="direction: ltr; text-align: left; text-indent: 0px; margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(12, 100, 192);">
IT Security Manager</div>
<div style="direction: ltr; text-align: left; text-indent: 0px; margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<a href="https://bellevuec.sharepoint.com/sites/its/security/" id="OWA6f526e34-3a8d-f27b-86d2-128f2c7c251b" class="OWAAutoLink" style="margin: 0px;">Information Security Office</a></div>
<div style="direction: ltr; text-align: left; text-indent: 0px; margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<i>Information Technology Services</i></div>
<div style="direction: ltr; text-align: left; text-indent: 0px; margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Phone: 425-564-2505 | Office: B233-I</div>
<div style="direction: ltr; text-align: left; text-indent: 0px; margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Work hours: 6:30 am - 3:00 pm</div>
<div style="direction: ltr; text-align: left; text-indent: 0px; margin: 0in; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<a href="https://bellevuecollege.teamdynamix.com/TDClient/2044/Portal/Requests/ServiceDet?ID=54980" id="OWA03c16f0c-de6d-a0b1-e2fb-22fcaac591a3" class="OWAAutoLink" style="margin: 0px;">Report an IT security or Privacy Incident</a></div>
<div style="text-align: left; text-indent: 0px; background-color: rgb(255, 255, 255); margin: 0px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="text-align: left; text-indent: 0px; background-color: rgb(255, 255, 255); margin: 0px; font-family: Calibri, sans-serif; font-size: 11pt; color: rgb(36, 36, 36);">
<a href="http://bellevuecollege.edu/" title="bellevuecollege.edu" style="text-decoration: none; margin: 0px;"><img alt="Bellevue College Logo" id="image_0" width="175" height="42" style="width: 175px; height: 42px; max-width: 605px; margin: 0px;" data-outlook-trace="F:1|T:1" src="cid:ad4c9135-2cb3-4d86-b77c-6732b9097542"></a></div>
<p style="text-align: left; text-indent: 0px; background-color: rgb(255, 255, 255); margin-top: 0px; margin-bottom: 0px;">
<span style="font-family: "Segoe UI", "Segoe UI Web (West European)", "Segoe UI", -apple-system, BlinkMacSystemFont, Roboto, "Helvetica Neue", sans-serif; font-size: 8pt; color: rgb(36, 36, 36);"><br>
</span></p>
<p style="text-align: left; text-indent: 0px; line-height: 12.6pt; background-color: white; margin: 0px;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt; color: rgb(118, 62, 155);"><b>¡Sí, hablo Español!</b></span></p>
<p style="text-align: left; text-indent: 0px; line-height: 12.6pt; background-color: white; margin: 0px;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt; color: rgb(12, 100, 192);">Any pronouns will be fine.</span></p>
<p style="text-align: left; text-indent: 0px; background-color: rgb(255, 255, 255); margin: 0in;">
<span style="font-family: Aptos, sans-serif; font-size: 14pt; color: rgb(222, 106, 25);"><b><br>
</b></span></p>
<p style="text-align: left; text-indent: 0px; background-color: rgb(255, 255, 255); margin: 0in;">
<span style="font-family: Aptos, sans-serif; font-size: 14pt; color: rgb(222, 106, 25);"><b>Accessibility is not a checkbox.
</b></span><span style="font-family: Aptos, sans-serif; font-size: 14pt; color: rgb(12, 100, 192);"><b>Accessibility is a mindset</b></span><span style="font-family: Aptos, sans-serif; font-size: 14pt; color: rgb(222, 106, 25);"><b> that can lead to a very
</b></span><span style="font-family: Aptos, sans-serif; font-size: 14pt; color: rgb(12, 100, 192);"><b>powerful sense of inclusion</b></span><span style="font-family: Aptos, sans-serif; font-size: 14pt; color: rgb(222, 106, 25);"><b>.</b></span></p>
<p style="text-align: left; text-indent: 0px; background-color: rgb(255, 255, 255); margin: 0in;">
<span style="font-family: Aptos, sans-serif; font-size: 12pt; color: rgb(94, 50, 124);">~ Maayan Ziv founder and CEO AccessNow</span></p>
<p style="text-align: left; text-indent: 0px; background-color: rgb(255, 255, 255); margin: 0in;">
<span style="font-family: Aptos, sans-serif; font-size: 12pt; color: rgb(94, 50, 124);"><br>
</span></p>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
</div>
</body>
</html>