<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
Hi!</div>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
If the form stays in Excel, in order to make the form accessible, you’re going to have to protect all of the text and force the screen readers to only access either the active X, legacy form controls, or content controls.</div>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
This means someone using a screen reader will not have access to any of the text in the form, including instructional text.</div>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
Additionally, within the past five or six years, screen readers, such as JAWS or NVDA, are not reading the tool tips for active X form controls or legacy form controls accurately.</div>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
I am a word MVP and these types of forms often crash word, and or the adaptive technology.</div>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
Content controls, if they are available in Excel, are also not accessible. They were never designed to be accessible. They are keyboard traps, and none of the tool tips or instructions that would be in a content control are accessible to the screen readers
or text to speech tools.</div>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
I did take a look at the form and you have designed it. Well, using topic changes/headings and keeping the tables small.</div>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
For this form, the most accessible route is going to be either PDF or HTML.</div>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
The advantage of tagged accessible PDF is that the end user will be able to read the instruction text and the tool tips for the form controls. They will also be able to archive a copy of the form on their computer and fill it out at their leisure, as well as
maintaining an archive copy.</div>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
As a way of introducing myself to this list, I am on the ISO committee for establishing the PDF standards and the PDF accessibility standards and have over 25 years experience in PDF, PDF forms, and accessible Microsoft Office content.</div>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
Hope this helps.</div>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
If you have any other questions, please feel free to ask me.</div>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
<br>
</div>
<div dir="ltr" style="font-family: Aptos, Aptos_MSFontService, -apple-system, Roboto, Arial, Helvetica, sans-serif; font-size: 12pt;">
Cheers, Karen</div>
<div id="ms-outlook-mobile-body-separator-line" dir="ltr"><br>
</div>
<div id="ms-outlook-mobile-signature">
<div dir="ltr">Sent from my mobile device!</div>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> athen-list <athen-list-bounces@mailman22.u.washington.edu> on behalf of Monica Olsson via athen-list <athen-list@u.washington.edu><br>
<b>Sent:</b> Thursday, July 24, 2025 5:30:35 PM<br>
<b>To:</b> 'Access Technology Higher Education Network' <athen-list@u.washington.edu>; educause-itaccess@connectedcommunity.org <educause-itaccess@connectedcommunity.org><br>
<b>Subject:</b> [Athen] Advise for complex PDF form</font>
<div> </div>
</div>
<style type="text/css" style="display:none">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div class="x_elementToProof" style="font-family:"Century Gothic",sans-serif; font-size:11pt; color:rgb(0,0,0)">
Hello,</div>
<div class="x_elementToProof" style="font-family:"Century Gothic",sans-serif; font-size:11pt; color:rgb(0,0,0)">
<br>
</div>
<div class="x_elementToProof" style="font-family:"Century Gothic",sans-serif; font-size:11pt; color:rgb(0,0,0)">
I am requesting guidance on accessibility best practice for a specific complex fillable form.</div>
<div class="x_elementToProof" style="font-family:"Century Gothic",sans-serif; font-size:11pt; color:rgb(0,0,0)">
<br>
</div>
<div class="x_elementToProof" style="font-family:"Century Gothic",sans-serif; font-size:11pt; color:rgb(0,0,0)">
Please see the attached form in PDF. There is a lot going on with tables, calculations, columns, etc.</div>
<div class="x_elementToProof" style="font-family:"Century Gothic",sans-serif; font-size:11pt; color:rgb(0,0,0)">
<br>
</div>
<div class="x_elementToProof" style="font-family:"Century Gothic",sans-serif; font-size:11pt; color:rgb(0,0,0)">
The document owner is experimenting with <span class="x__Entity x__EType_OWALink x__EId_OWALink x__EReadonly_1" style="display:inline-block">
<span><span><span><a data-loopstyle="linkonly" data-ogsc="" class="x_OWAAutoLink x_none" id="OWAf6666286-9e11-8877-36ab-8fdd04ffc0e5" rel="noopener noreferrer" href="https://sbctcedu-my.sharepoint.com/:x:/g/personal/djilek_sbctc_edu/EexcANs86ktOrX1mE0dUUlcBtXej-d_wJ_rDOaiKk_ViIg?e=LfgNDX" originalsrc="https://sbctcedu-my.sharepoint.com/:x:/g/personal/djilek_sbctc_edu/EexcANs86ktOrX1mE0dUUlcBtXej-d_wJ_rDOaiKk_ViIg?e=LfgNDX">using
Excel for the form</a></span></span></span></span>, rather than PDF. In one sense, this may make editing the source document easier, and Excel may handle calculations better. On the other hand, I worry about the user experience in this format.</div>
<div class="x_elementToProof" style="font-family:"Century Gothic",sans-serif; font-size:11pt; color:rgb(0,0,0)">
<br>
</div>
<div class="x_elementToProof" style="font-family:"Century Gothic",sans-serif; font-size:11pt; color:rgb(0,0,0)">
What is your advice on how best to remediate this form? My gut tells me to stick with PDF...</div>
<div class="x_elementToProof" style="font-family:"Century Gothic",sans-serif; font-size:11pt; color:rgb(0,0,0)">
<br>
</div>
<div class="x_elementToProof" style="font-family:"Century Gothic",sans-serif; font-size:11pt; color:rgb(0,0,0)">
Do folks have insight on the accessibility of web-based form tools like Gravity Forms or Form Assembly? </div>
<div class="x_elementToProof" id="x_Signature">
<div class="x_elementToProof" style="font-family:"Century Gothic",sans-serif; font-size:11pt; color:rgb(0,0,0)">
<br>
</div>
<div class="x_elementToProof" style="font-family:"Century Gothic",sans-serif; font-size:11pt; color:rgb(0,0,0)">
Thank you!</div>
<div class="x_elementToProof" style="font-family:"Century Gothic",sans-serif; font-size:11pt; color:rgb(0,0,0)">
Monica</div>
<p class="x_elementToProof" style="background-color:white; margin:0in; font-family:Aptos,sans-serif; font-size:12pt">
<span style="font-family:Calibri,sans-serif; font-size:11pt; color:rgb(32,31,30)"> </span></p>
<p class="x_elementToProof" style="text-align:left; background-color:white; margin:0in; font-family:Aptos,sans-serif">
<span style="font-family:"Franklin Gothic Book","Avenir Next Condensed",sans-serif; font-size:12pt; color:rgb(0,32,96)"><b>Monica M. Olsson (she/her/hers)</b></span></p>
<p class="x_elementToProof" style="text-align:left; background-color:white; margin:0in; font-family:Aptos,sans-serif">
<span style="font-family:"Franklin Gothic Book","Avenir Next Condensed",sans-serif; font-size:12pt; color:rgb(0,32,96)">Policy Associate – Accessible IT Coordinator</span></p>
<p class="x_elementToProof" style="text-align:left; background-color:white; margin:0in; font-family:Aptos,sans-serif">
<span style="font-family:"Franklin Gothic Book","Avenir Next Condensed",sans-serif; font-size:12pt; color:rgb(0,32,96)">Washington State Board for Community and Technical Colleges</span></p>
<p class="x_elementToProof" style="text-align:left; background-color:white; margin:0in; font-family:Aptos,sans-serif">
<span style="font-family:"Franklin Gothic Book","Avenir Next Condensed",sans-serif; font-size:12pt; color:rgb(0,32,96); background-color:white">•Email:
</span><span style="font-family:"Franklin Gothic Book","Avenir Next Condensed",sans-serif; font-size:12pt; color:blue"><b><u><a class="x_OWAAutoLink" id="OWAc6d7c9af-ce08-3c70-b8f4-38868f9338a2" target="_blank" href="mailto:molsson@sbctc.edu" style="color:blue; margin-top:0px; margin-bottom:0px">molsson@sbctc.edu</a></u></b></span><span style="font-family:"Franklin Gothic Book","Avenir Next Condensed",sans-serif; font-size:12pt; color:rgb(0,32,96)"><b> </b>•
Phone: 360-704-3922</span></p>
<p class="x_elementToProof" style="margin:0in; font-family:Aptos,sans-serif"><span style="font-family:"Franklin Gothic Book","Avenir Next Condensed",sans-serif; font-size:12pt; color:black"> </span></p>
<blockquote class="x_elementToProof" style="margin-left:0.8ex; padding-left:1ex; border-left:3px solid rgb(200,200,200)">
<p class="x_elementToProof" style="background-color:white; margin:0in; font-family:Aptos,sans-serif; font-size:12pt">
<span style="font-family:Calibri,sans-serif; color:rgb(36,36,36)"><b><i>The power of the Web is in its universality.</i></b></span></p>
<p class="x_elementToProof" style="background-color:white; margin:0in; font-family:Aptos,sans-serif; font-size:12pt">
<span style="font-family:Calibri,sans-serif; color:rgb(36,36,36)"><b><i>Access by everyone regardless of disability is an essential aspect.</i></b></span></p>
<p class="x_elementToProof" style="text-align:left; background-color:white; margin:0in; font-family:Aptos,sans-serif; font-size:12pt">
<span style="font-family:Calibri,sans-serif; font-size:11pt; color:rgb(36,36,36)">Tim Berners-Lee, W3C Director and inventor of the World Wide Web</span></p>
</blockquote>
</div>
</div>
</body>
</html>