[ATcoord] Recording and transcript from WaTech USER-01 policy session (May 5, 2025)

[Carrie Powell]

Hello Accessible IT Coordinators,
Many thanks to all who could join the discussion earlier this week with Tav=
ares Terry (DEI Director at WaTech) on Digital Accessibility Policy USER-01=
<https://watech.wa.gov/sites/default/files/2025-01/USER%20-01%20Digital%20A=
ccessibility%20Policy.pdf>.


  *
The discussion included policy requirements, alignment with ADA Title II, s=
tate-level work, and strategies for compliance.
     *
If you would like to join the WA Digital A11y Community of Practice, please=
 email:  tavares.terry at watech.wa.gov<mailto:tavares.terry at watech.wa.gov>
     *
As Tavares mentioned, WaTech and the WA Digital A11y CoP are supporting the=
 WA Department of Enterprise Services (DES) project to update statewide acc=
essibility training. Courses will be available through the WA State Learnin=
g Center DES SumTotal app later this year.

  *
For anyone unable to attend Monday's meeting, the chat log and the text tra=
nscript from that session are attached to this email, and a link to the SBC=
TC & WaTech Policy USER-01 meeting recording is included below: https://sbc=
tc.hosted.panopto.com/Panopto/Pages/Viewer.aspx?id=3Dbeeb03f7-5a50-4ba9-85b=
8-b2d7016e691e

Thank you!

[Title: SBCTC logo - Description: Compass]Carrie Powell

PMO Team Project Manager
Washington State Board for Community and Technical Colleges

cpowell at sbctc.edu<mailto:cpowell at sbctc.edu> =95 o: 360-704-1830 =95 c: 360-=
261-4840

sbctc.edu<https://sbctc.edu/> =95  Facebook: @WASBCTC =95  Bluesky: @sbctc.=
edu



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ctc.edu/pipermail/atcoord_lists.ctc.edu/attachments/2025=
0508/0a2296b9/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Outlook-Title_ SBC.png
Type: image/png
Size: 11853 bytes
Desc: Outlook-Title_ SBC.png
URL: <http://lists.ctc.edu/pipermail/atcoord_lists.ctc.edu/attachments/2025=
0508/0a2296b9/attachment-0001.png>
-------------- next part --------------
00:13:05	Monica Olsson (she/her):	Here is the agenda for today:
00:13:11	Monica Olsson (she/her):	Information to be Covered by Watech=20
Policy overview and summary of changes=20
Explanation of how the policy aligns with ADA Title II requirements and WA =
specific compliance timelines=20
State-level enterprise accessibility work=20
Accessibility testing services (state contract)=20
Training and support opportunities (Community of Practice, IMPA events, and=
 Department of Enterprise Services training)
00:18:07	Kevin:	Well said. Thank you
00:24:54	Amy Rovner (she, her, hers):	Answer when you have time...re: Archi=
ving - working to get clarity on how existing policy/guidelines apply to Ca=
nvas content. Any guidance here or just work with State Archivists?
00:26:35	Mary Gerard (she, her, hers), BTC:	I am so grateful for this conve=
rsation! An OCR attorney said we did not need to address employee access. I=
t's the right thing to do!
00:27:15	Tavares J. Terry (he/him) WaTech:	Inclusive design | WaTech
00:27:34	Amy Rovner (she, her, hers):	Reacted to "I am so grateful for..." =
with =E2=9D=A4=EF=B8=8F
00:27:53	Tavares J. Terry (he/him) WaTech:	Technology Policies and Standard=
s Waiver Procedure | WaTech
00:28:39	Tavares J. Terry (he/him) WaTech:	USER -01 Digital Accessibility P=
olicy.pdf
00:29:07	Amy Rovner (she, her, hers):	Release the krackens! LOL
00:29:14	Mary Gerard (she, her, hers), BTC:	Reacted to "Release the kracken=
s..." with =F0=9F=A4=A3
00:29:20	Kevin:	Reacted to "Release the krackens..." with =F0=9F=A4=A3
00:29:22	Rose Madison:	Reacted to "Release the krackens..." with =F0=9F=98=
=82
00:29:46	Michael Hanscom:	Reacted to "Release the krackens..." with =F0=9F=
=90=99
00:30:22	Vicki Walton - SBCTC (they/them):	Reacted to "Release the krackens=
..." with =F0=9F=98=82
00:30:47	mhatch:	Reacted to "Release the krackens..." with =F0=9F=90=99
00:31:05	Brian Culver (he/him/his):	Reacted to "Release the krackens..." wi=
th =F0=9F=90=99
00:32:32	Tavares J. Terry (he/him) WaTech:	State Government Records Retenti=
on Schedules | WA Secretary of State
00:34:56	Betsy Zahrt Geib:	Replying to "Answer when you have..."

I also have this question. Can someone provide guidance on whether course c=
oncludes meet the exemption criteria?
00:35:13	Monica Olsson (she/her):	1. Archived web content
Web content that meets all four of the following points would not need to m=
eet WCAG 2.1, Level AA:
The content was created before the date the state or local government must =
comply with this rule, or reproduces paper documents or the contents of oth=
er physical media (audiotapes, film negatives, and CD-ROMs for example) tha=
t were created before the government must comply with this rule, AND
The content is kept only for reference, research, or recordkeeping, AND
The content is kept in a special area for archived content, AND
The content has not been changed since it was archived.
Example: A water quality report from 1998 that a state has stored in an =E2=
=80=9Carchive=E2=80=9D section of its website and has not updated would pro=
bably fall under the exception. The exception would also probably apply to =
handwritten research notes or photos that go with the 1998 water quality re=
port that the state scans and posts to its website in the archive section.
00:47:17	Taija Tevia-Clark (Bellevue College):	For those of us who have fac=
ulty unions, good to make sure this training requirement is in the next con=
tract
00:47:34	Monica Olsson (she/her):	Replying to "For those of us who ..."

That is a good point
00:48:49	Amy Rovner (she, her, hers):	Replying to "For those of us who ..."

We have been able to require the training (for FT faculty) b/c this is a fe=
deral law we need to comply with. I think that is written into the contract=
 but broadly so we have been able to use for Title IX, Accessibility, etc. =
We do pay PT faculty for attending this kind of required training though. S=
o complex!
00:49:09	Amy Rovner (she, her, hers):	Reacted to "For those of us who ..." =
with =F0=9F=91=8D
00:52:40	Kevin:	There are also at least three colleges in the system that h=
ave accessibility in faculty contract
00:54:03	Michael Hanscom:	Reacted to "There are also at le..." with =F0=9F=
=91=8D=F0=9F=8F=BB
00:54:36	Amy Rovner (she, her, hers):	Reacted to "There are also at le..." =
with =F0=9F=91=8D=F0=9F=8F=BB
00:54:56	Cecilia Macias:	Yes please!
00:54:58	Michael Hanscom:	Replying to "There are also at le..."

Ours is currently in negotiation for updates=E2=80=A6
00:58:39	Michael Hanscom:	(Since it=E2=80=99s public info) The current lang=
uage for Highline is =C2=A7304 (page 39) of this contract =E2=80=94=C2=A0I =
can update with the revised language for the contract in negotiation once w=
e have it a little more settled. https://www.sbctc.edu/resources/documents/=
colleges-staff/my-employment/faculty-collective-bargaining-agreements/highl=
ine-2022-2025.pdf
00:58:49	Agnes Figueroa:	Item #5, pg. 2: "Effective July 1, 2029, in additi=
on to the requirements set forth in this policy for covered technology, all=
 content and tools that employees or users need to perform essential job du=
ties, access information, or participate in programs must be accessible or =
content owner is responsible for providing individuals with disabilities eq=
uivalent access"  I would like a second for clarification.
00:59:07	Tavares J. Terry (he/him) WaTech:	tavares.terry at watech.wa.gov
01:02:31	Michael Hanscom:	I have to bounce to another meeting. Thanks all! =
Thanks Tavares!
01:02:33	Kevin:	Thanks for this. This provided great information and resour=
ces. I appreciate you all.
01:03:05	Amy Rovner (she, her, hers):	Thank you so much Tavares!
01:03:07	Vicki Walton - SBCTC (they/them):	Wonderful conversation!!  Thank =
you, Tavares.
01:03:55	Bryan Fauth (he/him/his):	Thank you, Tavares!
01:03:56	Tavares J. Terry (he/him) WaTech:	Reacted to "Thank you, Tavares!"=
 with =F0=9F=91=8D=F0=9F=8F=BE
01:04:04	Tavares J. Terry (he/him) WaTech:	Thank you all for having me.
01:05:02	Christian Campbell (he/him/his):	Thank you Tavares!
01:05:30	Cecilia Macias:	Thank you!
01:05:39	Tavares J. Terry (he/him) WaTech:	Reacted to "Wonderful conversati=
..." with =F0=9F=91=8D=F0=9F=8F=BE
-------------- next part --------------
WEBVTT

1
00:00:03.390 --> 00:00:05.930
Monica Olsson (she/her): Okay, alrighty.

2
00:00:06.060 --> 00:00:13.320
Monica Olsson (she/her): We should be recording. So good morning. Accessibl=
e. It coordinators across our beautiful Ctc system.

3
00:00:13.430 --> 00:00:30.479
Monica Olsson (she/her): Today is Monday, May 5.th Thank you for being here=
 and joining us. Thank you to Varus for being here from Watec and joining u=
s. We're grateful that we were able to reschedule this session with you to =
talk about Washington State's digital accessibility policy.

4
00:00:30.934 --> 00:00:47.090
Monica Olsson (she/her): We are going to record today's session. So this wi=
ll be available for review after today. And you can share with your team me=
mbers who maybe weren't able to make it. We do have Zoom's auto captioning =
turned on.

5
00:00:48.110 --> 00:00:52.900
Monica Olsson (she/her): and I think I might be the only one from

6
00:00:53.030 --> 00:01:07.480
Monica Olsson (she/her): my little project team here, so I'll be doing my b=
est to moderate chat while Tavares is speaking with you all. If you know if=
 there's some sort of like emergency, feel free to unmute yourself and let =
me know you need help.

7
00:01:08.337 --> 00:01:11.800
Monica Olsson (she/her): So the purpose of today's session

8
00:01:11.970 --> 00:01:25.610
Monica Olsson (she/her): is for us to talk with Tavares, Terry from Watec. =
And I will turn it over to him soon to introduce himself. He's a wonderful =
human being that does really important critical Dei work

9
00:01:25.730 --> 00:01:27.619
Monica Olsson (she/her): in our State.

10
00:01:28.150 --> 00:01:37.050
Monica Olsson (she/her): And he is going to talk to us about Washington Sta=
te's digital accessibility policy, which we now refer to as user dash 0 1

11
00:01:37.240 --> 00:01:43.190
Monica Olsson (she/her): formerly known as Policy 188, which has recently g=
otten a little bit of a facelift.

12
00:01:44.128 --> 00:02:03.760
Monica Olsson (she/her): So we're going to talk about what those changes ar=
e, how it aligns with title, 2 requirements with web accessibility, how? Wh=
at the differences are. So there's things in our own state policy that are =
different than our title, 2 update

13
00:02:04.170 --> 00:02:06.159
Monica Olsson (she/her): rules and regulations.

14
00:02:06.340 --> 00:02:31.169
Monica Olsson (she/her): I've also asked Tavares to let you know a little b=
it about the State level enterprise, accessibility work that's being done. =
The statewide community of practice on digital web accessibility that's ope=
n to folks to join and participate in other unique, you know, opportunities=
 or resources as well. So that's what's on deck

15
00:02:31.480 --> 00:02:32.720
Monica Olsson (she/her): for today.

16
00:02:34.960 --> 00:02:58.590
Monica Olsson (she/her): and feel free to put questions or comments in the =
chat, Tavara, I'll let you tell people how, how you, what like, what your c=
omfort zone is. You know. My experience of you is that you're you're you're=
, you know. You're fairly relaxed in these settings, and that people can as=
k questions in real time. But I'll let you set that stage, and we'll go ahe=
ad and turn it over to you. Now.

17
00:02:59.220 --> 00:03:07.562
Tavares J. Terry (he/him) WaTech: Hey? I appreciate that. Good morning, eve=
ryone. I hope everyone can hear me. Okay, my name is Tavares Terry, as you =
heard.

18
00:03:08.030 --> 00:03:12.549
Tavares J. Terry (he/him) WaTech: I'm our director of diversity, equity, ac=
cess, and inclusion at Watech.

19
00:03:12.970 --> 00:03:18.669
Tavares J. Terry (he/him) WaTech: Before that I spent 10 years with Dshs in=
 a number of different roles

20
00:03:18.950 --> 00:03:37.129
Tavares J. Terry (he/him) WaTech: Dei work, legislative work, home and comm=
unity service offerings, things that had to do with contracting you name it=
. It seemed like I had my hand in it. Great learning lessons. I am a certif=
ied diversity executive as well as a certified diversity professional.

21
00:03:37.130 --> 00:03:49.070
Tavares J. Terry (he/him) WaTech: and all that really means is, I spent som=
e time to not come and tell you my opinion about stuff, and just use facts =
so that we can move things forward and make things more equitable in our st=
ate and in our own lives.

22
00:03:49.320 --> 00:04:01.520
Tavares J. Terry (he/him) WaTech: I have a master's in public administratio=
n from the Evergreen State College, so go, greeners for any of you out ther=
e. I'm originally from the State of Georgia, although I've lived in Washing=
ton most of my life.

23
00:04:01.899 --> 00:04:10.510
Tavares J. Terry (he/him) WaTech: It's a Georgia bulldog thing for me if yo=
u can't see. I make it known all of the time, but I love the state that I l=
ive in and work for.

24
00:04:11.440 --> 00:04:39.899
Tavares J. Terry (he/him) WaTech: I'm sorry I didn't get to make it to the =
last meeting. I'm happy you all were able to reschedule here as far as inte=
raction. I'm just gonna give you my take on this. I absolutely hate when pe=
ople just sit there and lecture to a group of people for an hour and no one=
 has any input. So if there's questions or statements that need to be made.=
 Let's just jump on in there and have an interactive conversation. I think =
that's the only way that we get things moving forward.

25
00:04:40.157 --> 00:04:50.189
Tavares J. Terry (he/him) WaTech: If things are are getting a little bit, y=
ou know, too long in the tooth, if you will, I will slow some things down, =
just so we make sure that we get to as many people as we can.

26
00:04:50.703 --> 00:05:13.190
Tavares J. Terry (he/him) WaTech: But that's enough about me. I'm here to t=
alk to you about accessibility and what's going on with our state as far as=
 digital accessibility and some of the things that are surrounding it. So w=
hat I'm gonna start with is, I'm gonna go backwards to go forward. If that'=
s okay with everybody, and I'll I'll try to give this history lesson quick.=
 So most of you are aware that we had

27
00:05:13.830 --> 00:05:19.209
Tavares J. Terry (he/him) WaTech: policy 188, which was our digital accessi=
bility policy in the State of Washington.

28
00:05:19.430 --> 00:05:22.169
Tavares J. Terry (he/him) WaTech: I am the owner of that policy. Well.

29
00:05:22.390 --> 00:05:26.280
Tavares J. Terry (he/him) WaTech: the newer version of that policy which is=
 user. o, 1.

30
00:05:26.727 --> 00:05:32.469
Tavares J. Terry (he/him) WaTech: I have no idea why the name changed. It's=
 something that happened in a process while I was here.

31
00:05:32.730 --> 00:05:46.180
Tavares J. Terry (he/him) WaTech: It was one of those things where I was li=
ke. I'm not asking questions about that. We've got bigger things to worry a=
bout, and it had to do with some realignment, with policies and things like=
 that. So that's the big secret there. If anybody's wondering, I don't know

32
00:05:46.690 --> 00:05:56.080
Tavares J. Terry (he/him) WaTech: The policy itself is very important. Ther=
e are a lot of great people that were involved in this work before I was ev=
er here.

33
00:05:56.634 --> 00:06:01.369
Tavares J. Terry (he/him) WaTech: That really did the things necessary to g=
et that policy up and running.

34
00:06:01.530 --> 00:06:17.766
Tavares J. Terry (he/him) WaTech: And, as you all know, which essentially j=
ust means, let's make everything as equitable, as accessible as we can for =
everyone without having these major barriers and roadblocks. So the Departm=
ent of Justice

35
00:06:18.910 --> 00:06:31.789
Tavares J. Terry (he/him) WaTech: sent out a rule under title 2 that was ef=
fective. June 24th of 2024, and that had to do with the Wcag level. For our=
 our digital assets, etc.

36
00:06:32.137 --> 00:06:50.190
Tavares J. Terry (he/him) WaTech: One thing to know about that is that when=
 that rule came out towards the end of 2024, or I'm sorry, beginning of 202=
4 into 2023 somewhere where we started hearing about it from a policy stand=
point. When I'm talking about policy 1, 88. Here

37
00:06:50.260 --> 00:06:55.220
Tavares J. Terry (he/him) WaTech: we were already in compliance. We had alr=
eady required the Wcag levels.

38
00:06:55.558 --> 00:07:12.100
Tavares J. Terry (he/him) WaTech: That we're being asked for. And all of th=
is and that. That's from a policy standpoint. Now, the actual story about t=
hat. No, we weren't in compliance, as many of you know, across the board. A=
nd there's a number of reasons for that. Right. Stop me, if you've heard th=
is one before.

39
00:07:12.440 --> 00:07:30.510
Tavares J. Terry (he/him) WaTech: It's a budgetary thing we can't address t=
hat right now. Oh, we don't have employees that need that type of stuff. So=
 we don't need to worry about it. Oh, well, we can do things with an equiva=
lent alternative. So we don't need to worry about making things accessible.=
 Now

40
00:07:30.970 --> 00:07:45.870
Tavares J. Terry (he/him) WaTech: all of those things were great excuses th=
at were used, but they were terrible for the end users and for the people t=
hat we purport to to serve. So what we've been doing is working with agenci=
es and local governments and things like that

41
00:07:46.040 --> 00:07:53.799
Tavares J. Terry (he/him) WaTech: in terms of what they need to do to come =
into compliance with the policy. And I'm going to be honest.

42
00:07:54.440 --> 00:08:02.810
Tavares J. Terry (he/him) WaTech: I'd say a good 90% of the agencies that w=
e've come in contact with are on board, and they want to do the right thing.

43
00:08:02.810 --> 00:08:26.929
Tavares J. Terry (he/him) WaTech: What most of them have been dealing with =
is what we see often is that the can has been kicked down the road so far t=
hat it's such an undertaking now that it's almost overwhelming. But one thi=
ng that I want to stress, and I stress throughout this process of updating =
our policy is that budgetary constraints could not be an excuse for us not =
to do the things that we need to do.

44
00:08:27.160 --> 00:08:56.860
Tavares J. Terry (he/him) WaTech: for people have the the basic rights that=
 they're afforded, and for us to say that we want to be an equitable State =
government. We got to put our money where our mouth is, if you will, and ac=
cessibility is one of those areas. So, as you heard as well in our state, w=
e have a large community of practice for digital accessibility. I think the=
 last I checked. We have about 263, or 270

45
00:08:57.130 --> 00:09:17.750
Tavares J. Terry (he/him) WaTech: or so members now. Not all of them are ac=
tive, but all of them are at least paying attention, because I do get some =
emails and things like, Oh, I've seen this. I heard that I want to share th=
is, which is great. Through that we have our accessibility cop, which we ca=
ll digital allies and that group

46
00:09:18.070 --> 00:09:19.750
Tavares J. Terry (he/him) WaTech: did a lot of work

47
00:09:20.020 --> 00:09:37.630
Tavares J. Terry (he/him) WaTech: coming together so that we could update w=
hat was formerly policy 188 to user 0 1. What those updates did was reinfor=
ce what the Doj was saying in terms of what the appropriate Wcag level is a=
nd things of that nature.

48
00:09:37.630 --> 00:09:59.599
Tavares J. Terry (he/him) WaTech: We did look for some areas where we neede=
d to have some exceptions to this policy and depend on equivalent access in=
 that area. At that time, when this update was happening, we're thinking th=
ings like Gis maps and some other historical data that was going to be hard=
er to make accessible going back?

49
00:10:01.350 --> 00:10:15.509
Tavares J. Terry (he/him) WaTech: So what you'll know about that? Those exc=
eptions include web content that meets the 4 of these 4 points it was creat=
ed before the date of our state or local

50
00:10:15.640 --> 00:10:35.159
Tavares J. Terry (he/him) WaTech: time that our state or local government h=
ad to comply with the rule of the Doj. So we did update that date in the po=
licy so that people didn't feel like, oh, I have this whole storm on me, an=
d I'm already behind. We updated it to the date that they were asking for i=
n the new policy to give some people some wiggle room there.

51
00:10:35.653 --> 00:10:45.480
Tavares J. Terry (he/him) WaTech: Also content. That's kept for reference r=
esearch or record keeping. So some of these things. This is where the Gis m=
apping data conversation came up

52
00:10:45.570 --> 00:11:10.740
Tavares J. Terry (he/him) WaTech: in terms of what is available. We needed =
to look at what can be archived, because, to be honest with you, we need st=
ate agencies to take archiving seriously for a matter of privacy as well as=
 accessibility. We weren't doing that. And when I say we, I'm not pointing =
to one agency or not, I'm pointing to us as a collective enterprise we were=
 not doing a good job of archiving

53
00:11:10.940 --> 00:11:11.810
Tavares J. Terry (he/him) WaTech: of.

54
00:11:11.870 --> 00:11:21.479
Tavares J. Terry (he/him) WaTech: and so we needed to address that, and the=
n also content. That hadn't been changed. Since that time, that it was arch=
ived.

55
00:11:21.530 --> 00:11:46.510
Tavares J. Terry (he/him) WaTech: There were pre-existing, conventional ele=
ctronical documents that needed to meet the following points, documents tha=
t are word processing, presentation, Pdf spreadsheet files. So basically an=
ything that that we're providing out there. Those were available on local g=
overnment websites, mobile apps before the date that we're talking about he=
re in 2024, and.

56
00:11:46.510 --> 00:11:54.449
Monica Olsson (she/her): Terry, this is Monica. I'm sorry to interrupt you,=
 but I think you mentioned a compliance deadline that's, you know, slightly=
 different than what

57
00:11:55.150 --> 00:11:57.860
Monica Olsson (she/her): is stated in the.

58
00:11:57.860 --> 00:11:59.250
Tavares J. Terry (he/him) WaTech: I'm gonna get to that.

59
00:11:59.250 --> 00:12:07.219
Monica Olsson (she/her): Okay, I'm receiving a couple of private chats. Ask=
ing for clarification. And so rather than me, individually typing, I'm just.

60
00:12:07.220 --> 00:12:07.779
Tavares J. Terry (he/him) WaTech: Oh, no! No!

61
00:12:07.780 --> 00:12:14.350
Monica Olsson (she/her): Just letting you know. I think some folks are like=
, what what's which? What are we going after? What's the difference.

62
00:12:14.350 --> 00:12:33.350
Tavares J. Terry (he/him) WaTech: Yeah. So what what I was doing was going =
backwards so we could go. Because what always happens is, I start where we =
are. Now and then people start bringing up dates from before, and things li=
ke that, and then we confuse the conversation. So I will get to that point =
right now. So what we have in our policy

63
00:12:33.350 --> 00:12:58.179
Tavares J. Terry (he/him) WaTech: in terms of compliance, and what you've s=
een with the Doj rule has to do with April of next year. That would be 2026=
. We all on the same page there just want to make sure. Got some head nods =
things like that. Okay, the Doj rule for Title 2 was effective as of June 2=
4, th 2024. So that was the date that I was referencing. When the Federal g=
overnment finally said.

64
00:12:58.180 --> 00:13:05.839
Tavares J. Terry (he/him) WaTech: this is what you have to do, and the 26, =
th 2026 date is when you have to do it by

65
00:13:05.840 --> 00:13:29.399
Tavares J. Terry (he/him) WaTech: from that standpoint from a policy standp=
oint only. We were already in compliance because we already required this t=
hrough policy 188. It was just the actuality that we weren't getting at yet=
. So with that in mind, and with knowing these dates, we have been working =
with State agencies as they plan on what their remediation is for this.

66
00:13:29.400 --> 00:13:39.659
Tavares J. Terry (he/him) WaTech: We have a waiver policy. I want to be cle=
ar about what the waiver means. Waiver does not give you the the magic thin=
g to go. Oh, we don't have to do it because we got a waiver.

67
00:13:39.660 --> 00:14:03.219
Tavares J. Terry (he/him) WaTech: A waiver simply is saying, Hey, here are =
some of the challenges that we're having. Here's how we plan to remediate t=
hose challenges and then working with us at watch to make sure that those a=
re reasonable. So something that would be unreasonable. That would come acr=
oss the desk is, I would get a waiver. Notice that said, Hey, we've looked =
at our systems, and this, this, this and that are not in compliance. But

68
00:14:03.220 --> 00:14:05.490
Tavares J. Terry (he/him) WaTech: we'll have that all done by 2030.

69
00:14:05.820 --> 00:14:34.179
Tavares J. Terry (he/him) WaTech: That's absolutely not. That's way too far=
 out. We can do things before that. That's again kicking the can down the r=
oad. Which is the problem of of how we got here now, because, as you are up=
dating a policy and things of that nature, you should always look for oppor=
tunities where there can be improvement, one glaring omission that we've al=
ways had in our policy. Up to user. Oh, one being approved

70
00:14:34.180 --> 00:14:42.629
Tavares J. Terry (he/him) WaTech: is that internal systems for communicatio=
n were not being subjected to the policy. So what that meant was

71
00:14:42.710 --> 00:14:52.880
Tavares J. Terry (he/him) WaTech: from a hypocritical standpoint. We, as a =
State. We're saying, everyone who comes to do business with the State of Wa=
shington. We need to make sure that's accessible.

72
00:14:52.940 --> 00:15:21.180
Tavares J. Terry (he/him) WaTech: But you great people that we say that we =
want to work for us and look at us as an employer of choice. It doesn't mat=
ter if the things that you work with are accessible because we could hide b=
ehind things like reasonable accommodation, or, again, some kind of equival=
ent access. But I'm sorry in the work group. We made this point clear. As w=
e were talking, no one should have to ask for reasonable accommodation to s=
ee something like an emergency notification

73
00:15:21.450 --> 00:15:29.430
Tavares J. Terry (he/him) WaTech: or things of that nature. Okay. So what w=
e had to do was take a look in the mirror and address the hard fact of

74
00:15:29.800 --> 00:15:43.169
Tavares J. Terry (he/him) WaTech: utilizing that, hey? Us opening up to say=
ing that by 2029, we also will have our internal components be accessible, =
will open us up to litigation.

75
00:15:43.300 --> 00:15:44.110
Tavares J. Terry (he/him) WaTech: Oof

76
00:15:44.260 --> 00:15:48.810
Tavares J. Terry (he/him) WaTech: folks, I'm going to tell you right now. W=
e are the state of Washington. We get sued every day.

77
00:15:49.000 --> 00:15:55.420
Tavares J. Terry (he/him) WaTech: Okay, so we cannot run from things that a=
re our responsibility simply because litigation may happen.

78
00:15:55.430 --> 00:16:08.669
Tavares J. Terry (he/him) WaTech: And taking the approach that because we h=
adn't been sued by employees or potential employees, you know, trying to ge=
t with the State because it hadn't happened yet that it wouldn't happen, wa=
s misguided in nature.

79
00:16:08.670 --> 00:16:31.759
Tavares J. Terry (he/him) WaTech: so we had some really tough conversations=
. We had to look ourselves in the mirror and understand we weren't the main=
 character, but we were the villain in some areas, and we did some things t=
o shore up that policy. So again, what we've added to the policy. Besides, =
the Doj dates for 2026 also include internal communication components

80
00:16:31.760 --> 00:16:33.739
Tavares J. Terry (he/him) WaTech: by 2029. Now.

81
00:16:34.380 --> 00:16:43.539
Tavares J. Terry (he/him) WaTech: because we're fallible, I do have to shar=
e this with you as well, when we 1st proposed doing the internal systems, p=
eople's heads exploded.

82
00:16:43.660 --> 00:16:49.489
Tavares J. Terry (he/him) WaTech: and I know why, because I made the mistak=
e. I didn't separate out

83
00:16:49.560 --> 00:17:04.999
Tavares J. Terry (he/him) WaTech: a timeframe of when we should do internal=
 versus external right. So we had this date that was coming like tomorrow i=
n 2026. And then here I am, as the policy owner like. And we're gonna do th=
is other stuff. And people were like

84
00:17:05.000 --> 00:17:24.770
Tavares J. Terry (he/him) WaTech: how? Because we're already buried in term=
s of what we haven't done to the current policy. And now you're adding this=
. So we had to do some separation there. So if you, any of you on this call=
 went through that anxiety as the policy was getting updated. I truly apolo=
gize for that. That was my oversight. And hopefully, that's more clear now

85
00:17:24.770 --> 00:17:36.110
Tavares J. Terry (he/him) WaTech: in terms of the policy. And and what's go=
ing on as I can imagine, there are probably a lot of questions about, hey? =
What can we do

86
00:17:36.482 --> 00:17:53.930
Tavares J. Terry (he/him) WaTech: to get ready for this? Does wall tech hav=
e any assistance that they can provide, and I'm gonna put something in the =
chat right now and then. I want to open it up for questions and conversatio=
n. We do have a team that works with inclusive design here at watch.

87
00:17:54.260 --> 00:18:02.920
Tavares J. Terry (he/him) WaTech: Wendy and her team are great about a lot =
of different things. I also had mentioned that there is a waiver procedure

88
00:18:02.920 --> 00:18:26.240
Tavares J. Terry (he/him) WaTech: in terms of letting us know what the plan=
s are. If we're not going to be in compliance. Or if if a part may not be i=
n compliance right at 2026, because often what's happening is 85, 90% of pe=
ople's stuff is going to be in compliance on time. But there are some thing=
s that are not, some things that that we need to address as well. So I want=
 to make sure that you have

89
00:18:27.260 --> 00:18:55.510
Tavares J. Terry (he/him) WaTech: how you can put for that waiver procedure=
 as well. I do want to forewarn you that we have a a new policies manager w=
ho's looking at updating how we deal with waivers and things like that in t=
he system that we use. So some things may be a bit delayed. If you find tha=
t you're having some delays in anything you're asking for, please just send=
 me a message or through channels through Monica, and we'll make sure

90
00:18:55.590 --> 00:19:03.409
Tavares J. Terry (he/him) WaTech: that we get that all taken care of for yo=
u. And then what was the last thing that I wanted to say before

91
00:19:03.850 --> 00:19:14.959
Tavares J. Terry (he/him) WaTech: you probably want to stop listening to me=
 talk. Oh, I also wanted to. Just put in a link to the policy itself in cas=
e people didn't have that.

92
00:19:15.370 --> 00:19:18.289
Tavares J. Terry (he/him) WaTech: Okay. So that's how we got here.

93
00:19:18.500 --> 00:19:21.109
Tavares J. Terry (he/him) WaTech: Now I want to know, what do we need to ta=
lk about.

94
00:19:21.670 --> 00:19:27.985
Monica Olsson (she/her): Hey, Tavares? This is Monica. Before I re-release =
everyone onto you.

95
00:19:28.989 --> 00:19:48.060
Monica Olsson (she/her): I there's a few things that I want. I want to say =
just as I'm following some some questions and comments in the chat, but als=
o I'm so glad that you mentioned the Wendy's team at your agency and put a =
hyperlink into the inclusive design work through wall tech. So,

96
00:19:48.730 --> 00:19:59.655
Monica Olsson (she/her): Amy, you've released the krakens. Okay, so I, this=
 is a plug for for the for Wendy and her team and the services that Watec c=
an provide.

97
00:20:00.260 --> 00:20:29.859
Monica Olsson (she/her): Kevin from Seattle colleges who's on the call, and=
 I met with Wendy to learn about the accessibility and usability testing se=
rvices that wall tech manages that we all can. It's, you know, it's not fre=
e. You have to identify your own budget for this work for these services, b=
ut that we can use these services. And the reason why Kevin and I were in c=
onversation with Wendy is, we're working, you know, with a variety of peopl=
e to try to explore.

98
00:20:29.860 --> 00:20:33.750
Monica Olsson (she/her): How do we get some testing done on these edtech

99
00:20:34.420 --> 00:20:49.459
Monica Olsson (she/her): applications that faculty are bringing into canvas=
 through Lti that have at the at this point in time. Little to no, you know=
 oversight by the college. We need to know what is in there. You know how m=
any

100
00:20:49.910 --> 00:21:18.020
Monica Olsson (she/her): students are using it and what it is. And so what =
we learned is that wall tech holds a contract with a variety with a 3 or so=
 vendors that provide accessibility and usability testing, you know, for a =
a set fee, and we ended up meeting, I think, with at least 2 of those, you =
know, different teams to explore their approach and practice as we are. Wor=
king through this project.

101
00:21:18.280 --> 00:21:32.748
Monica Olsson (she/her): And I was really impressed. And what I what I like=
, and what I liked about this, too, is, it's it's an option for us to remem=
ber when when you know we don't necessarily have that

102
00:21:33.609 --> 00:21:59.460
Monica Olsson (she/her): personnel in house that can do that type of work w=
ith that technical expertise. And because Wall Tech already went through al=
l the work to. You know the contracting work. It means that it you don't ne=
cessarily have to go through like an Rfp process to identify an external ve=
ndor to enter a contract with to do some of that work. So I wanted to say t=
hose those things

103
00:21:59.950 --> 00:22:09.180
Monica Olsson (she/her): And then the other. The other thing I wanted to ju=
st briefly mention is, there was. There's a conversation I'm having in priv=
ate chat around

104
00:22:09.763 --> 00:22:18.749
Monica Olsson (she/her): like canvas, archiving retention policies and prac=
tices. And I think there's there's like 2. There's 2 streams of

105
00:22:18.940 --> 00:22:27.097
Monica Olsson (she/her): 2 streams of activity. We need to be mindful at th=
e same time. So Amy reminded me that you know Washington State. We have our=
 own like

106
00:22:27.620 --> 00:22:28.370
Tavares J. Terry (he/him) WaTech: Privacy.

107
00:22:28.370 --> 00:22:43.064
Monica Olsson (she/her): Like in re in retention requirements. That our ins=
titutions need to be mindful of when removing or archiving content. But the=
 other piece I wanted to to make sure people understand is

108
00:22:43.520 --> 00:23:12.969
Monica Olsson (she/her): and to caution, we don't want to use our archiving=
 a digital asset as a way to get around ensuring something's accessible. An=
d the the Department of Justice Ruling has a very specific technical defini=
tion of when an electronic document or something meets archiving archival s=
tatus. So if you're working with your, you know, canvas

109
00:23:12.970 --> 00:23:28.819
Monica Olsson (she/her): administrator and your faculty trying to make some=
 tough decisions on like basically prioritizing the work right? So like, wh=
at do we need to critically make sure is accessible now, and moving forward=
 versus what can we

110
00:23:29.303 --> 00:23:41.120
Monica Olsson (she/her): set aside for for later or not worry about at all.=
 We need all need to be very familiar with how the Department of Justice is=
 defining archived web content

111
00:23:41.330 --> 00:23:50.030
Monica Olsson (she/her): if your content meets that definition and you stor=
e it properly, then you're following the ruling.

112
00:23:50.250 --> 00:24:08.129
Monica Olsson (she/her): That's different than retention policy for Washing=
ton State. So there's 2 things that we need to be clear on and thinking thr=
ough when working with our canvas teams and our faculty on, you know, remov=
ing or saving instructional content.

113
00:24:08.440 --> 00:24:11.660
Monica Olsson (she/her): And, Amy, you're nodding so hopefully, I like, sai=
d that

114
00:24:11.980 --> 00:24:15.539
Monica Olsson (she/her): captured our brief comments back and forth accurat=
ely.

115
00:24:15.540 --> 00:24:22.760
Tavares J. Terry (he/him) WaTech: No, that, and that that's a great thing t=
o bring up, because I think sometimes what people conflate with

116
00:24:23.170 --> 00:24:35.982
Tavares J. Terry (he/him) WaTech: Watec is, what is our statutory responsib=
ility to lead in technology versus what is the agency responsibility in ter=
ms of archiving their content?

117
00:24:37.000 --> 00:24:44.490
Tavares J. Terry (he/him) WaTech: where this came up? In the conversation. =
In updating the policy was again about

118
00:24:45.080 --> 00:24:49.449
Tavares J. Terry (he/him) WaTech: things that are available on websites that

119
00:24:49.840 --> 00:25:19.399
Tavares J. Terry (he/him) WaTech: aren't old enough in research where they =
should be archived. But they're asked for just enough where they need to be=
 available. And how do? How do those things become accessible? That's 1 exa=
mple of that, because it's easy just to say, well create an archive area an=
d then throw everything in that. And then that's how people get around acce=
ssibility. Right? That's that was never the intent of what we were going fo=
r. So it is important to understand what is, what is your agency use

120
00:25:19.560 --> 00:25:34.799
Tavares J. Terry (he/him) WaTech: of of the material? And you know, like, h=
ow often is it requested. And then agencies need to have that prioritizatio=
n exercise if they will, because that's a part. What we can't tell for you,=
 you know, like what's important, what's not important.

121
00:25:35.350 --> 00:25:37.380
Tavares J. Terry (he/him) WaTech: I see a hand of Amy.

122
00:25:38.500 --> 00:25:43.130
Amy Rovner (she, her, hers): This is, yeah. Sorry. This is Amy Rubin from s=
horeline, just following up on the archive

123
00:25:43.470 --> 00:25:50.209
Amy Rovner (she, her, hers): archiving versus the Reten records. Retention.=
 Yeah, I was specifically referring to the records retention.

124
00:25:51.760 --> 00:26:01.810
Amy Rovner (she, her, hers): and so, if we want clarity on, I I see they ju=
st updated the policy in April. So I'm quickly scanning it to see if they a=
nswered the questions we have. But yeah, there's some canvas

125
00:26:01.930 --> 00:26:09.930
Amy Rovner (she, her, hers): where does canvas fit into the language they u=
se in that policy or guidelines. But do we work with a State archivist? Tha=
t was what I

126
00:26:10.080 --> 00:26:23.870
Amy Rovner (she, her, hers): might. It seems like those are the people we w=
ould ask for real clarity on. We have a canvas class from 2,012. Should we =
still have that campus classes, you know, and and I know every college is s=
ort of trying to figure out the process themselves. And so

127
00:26:24.060 --> 00:26:28.550
Amy Rovner (she, her, hers): I'm like, let's figure it out once for 34. And=
 then, yeah, so.

128
00:26:28.550 --> 00:26:39.749
Monica Olsson (she/her): Yeah, that's a great question, Amy, do you have th=
oughts on that? Tavares? Because, yeah, higher. Ed has some unique situatio=
ns with content that maybe sit outside other state agency examples.

129
00:26:39.750 --> 00:27:06.589
Tavares J. Terry (he/him) WaTech: They do, and and that's where I would say=
, if you don't have you know your own person who's working on records and t=
hings like that which everybody should. But I know the realities of stuff a=
nd 5% other duties is assigned and doing more with less. And all of those g=
reat things. I would work with. With our state sources, then with that to g=
ain what that clarity will be, because again.

130
00:27:06.900 --> 00:27:08.509
Tavares J. Terry (he/him) WaTech: even within

131
00:27:09.190 --> 00:27:37.949
Tavares J. Terry (he/him) WaTech: within your environment there. What 1 1 s=
chool is looking at may be different than another in terms of you said some=
thing from 2,012. Right? Well, there may be something from 2,012 that has t=
o do with disaster. Recovery that's very relevant still to what we're doing=
 today as opposed to. Here's how we made things accessible in 2012, which m=
ay be out of date, or or things like that, or have may have been replaced w=
ith newer information.

132
00:27:43.000 --> 00:28:05.159
Monica Olsson (she/her): So, Amy, I'm hearing. So I saw that Tavares put a =
link. State government records retention schedules in our chat. I will capt=
ure that for everyone, and I heard state, or I heard Tavares say, Amy, that=
 yes, working with state archiving resources could be an appropriate soluti=
on. If the college doesn't have internal resources to help think through

133
00:28:05.460 --> 00:28:06.699
Monica Olsson (she/her): that process.

134
00:28:14.220 --> 00:28:19.869
Tavares J. Terry (he/him) WaTech: Feel like y'all are trying to take it eas=
y on me. Come on, now. My energy is flowing.

135
00:28:22.021 --> 00:28:37.680
Kevin: I have a question. Amy. You mentioned the other day that about train=
ing requirements? And that so I just. I did just a quick search. I I went p=
rior to this meeting. I went to the

136
00:28:38.442 --> 00:28:51.119
Kevin: policy and that I couldn't find. I mean, it says they need access to=
 in that. But, Amy, you mentioned the other day potential frequency of annu=
al training.

137
00:28:51.120 --> 00:28:51.600
Amy Rovner (she, her, hers): Yeah.

138
00:28:51.873 --> 00:28:55.980
Kevin: So I would like clarity on that, because I can't find it in the lang=
uage.

139
00:28:56.140 --> 00:29:00.510
Kevin: And frequency.

140
00:29:01.377 --> 00:29:12.830
Kevin: tracking responsibility and stuff like and potential resources. This=
 is something like, you know, like, we're trying to catch up on. And

141
00:29:13.600 --> 00:29:25.250
Kevin: well, I wanna yeah, I have potentially other comments and questions =
depending on the answer to to the question around what are the training req=
uirements, and how frequent are those requirements.

142
00:29:25.540 --> 00:29:26.709
Monica Olsson (she/her): I know what they are.

143
00:29:26.710 --> 00:29:27.130
Monica Olsson (she/her): Alright!

144
00:29:28.772 --> 00:29:33.360
Amy Rovner (she, her, hers): Tavares can answer because he's the owner of t=
he policy. But item 9

145
00:29:33.490 --> 00:29:40.580
Amy Rovner (she, her, hers): B agencies will require and document annual di=
gital accessibility, awareness, training for all employees

146
00:29:40.770 --> 00:29:53.210
Amy Rovner (she, her, hers): see. Agencies will require and document additi=
onal training for roles with a larger impact on it. Accessibility such as s=
oftware development agencies will determine and document, the frequency of =
the training.

147
00:29:53.860 --> 00:30:01.790
Amy Rovner (she, her, hers): so that one caught me by surprise, and I was s=
canning through it. I don't know like a month ago, I'm like, oh, no. Whoops=
ies. So yeah.

148
00:30:01.790 --> 00:30:04.889
Tavares J. Terry (he/him) WaTech: Or everyone freaks out about that. That w=
as another

149
00:30:05.270 --> 00:30:10.709
Tavares J. Terry (he/him) WaTech: really important topic that we discussed =
as a work group in updating the policy.

150
00:30:11.461 --> 00:30:31.600
Tavares J. Terry (he/him) WaTech: So you'll see the number right before tha=
t. 8. It says, watch will sponsor annual digital accessibility, awareness, =
training. So what that sponsor is a fancy word of saying that we're going t=
o support des efforts agency efforts to develop trainings. If we find outsi=
de vendors things like that

151
00:30:31.600 --> 00:30:53.370
Tavares J. Terry (he/him) WaTech: that look like a good enterprise solution=
, we're gonna support that. We're not developing the training in house at W=
atec. But we are having a hand in working with the accessibility groups in =
terms of what that looks like. So right now, our accessibility cop is actua=
lly talking about not only trainings, but communications about all of this =
stuff. So

152
00:30:54.430 --> 00:31:06.820
Tavares J. Terry (he/him) WaTech: another area where I think we can shore u=
p is that we had put out information through the Cabinet level leadership a=
nd the deputies in the State agencies

153
00:31:07.010 --> 00:31:09.279
Tavares J. Terry (he/him) WaTech: about what these requirements were

154
00:31:09.390 --> 00:31:36.919
Tavares J. Terry (he/him) WaTech: what was upcoming where we were. Our posi=
tion as a state. What this all looks like, that surprisingly, did not trick=
le down to everyone. So we are going to take another shot at this. We're go=
ing to put some communications together about who's on first.st What's on? =
Second, all of the good questions that people have had, how we can identify=
, like the training aspect. What will happen through the learning center?

155
00:31:36.920 --> 00:31:39.549
Tavares J. Terry (he/him) WaTech: Do you all have access to the learning sy=
stem?

156
00:31:39.550 --> 00:32:07.510
Monica Olsson (she/her): Yes, this is Monica. I'm gonna jump in. So you guy=
s, there's there's something very exciting in development, because I think =
it could present itself as a scalable training solution and a very trackabl=
e one, perhaps not a perfect solution, but definitely, some something in ad=
dition to our micro courses that are supported by Svtcc, my agency that we =
can use whatever my agency's acronym is

157
00:32:08.672 --> 00:32:17.920
Monica Olsson (she/her): so and I learned this and when I attended the comm=
unity of practice meeting a week or so ago. So

158
00:32:17.920 --> 00:32:38.289
Monica Olsson (she/her): there, there's a group of great smart people right=
 now in our state working to update and roll out accessibility, training mo=
dules managed through Des to part of enterprise services in the Washington =
State Learning Center. So that's like, through some total, I believe

159
00:32:38.290 --> 00:32:50.170
Monica Olsson (she/her): we all have likely been inside there at 1 point or=
 another in our career for required state training, that you know our Hr. O=
ffices track for employees.

160
00:32:50.530 --> 00:32:57.100
Monica Olsson (she/her): So those are not live yet, but my understanding is=
 those are going to be rolled out.

161
00:32:57.370 --> 00:33:00.540
Monica Olsson (she/her): you know, relatively soon. Is that correct, Tavare=
s?

162
00:33:00.540 --> 00:33:03.689
Monica Olsson (she/her): Yes, hopefully, maybe this summer, sometime.

163
00:33:03.690 --> 00:33:16.060
Tavares J. Terry (he/him) WaTech: That's what we're shooting for. I've got =
some meetings coming up here in the next week or so so that we can nail dow=
n some more timelines. But that's what we're shooting for with.

164
00:33:16.510 --> 00:33:24.489
Tavares J. Terry (he/him) WaTech: with the dates that people are looking at=
 coming up so quickly. We want to make sure that the training is available

165
00:33:24.710 --> 00:33:31.820
Tavares J. Terry (he/him) WaTech: and not put cart before the horse if you =
will, so that we should have some information.

166
00:33:31.990 --> 00:33:36.868
Tavares J. Terry (he/him) WaTech: I wanna say, about that coming out probab=
ly towards the end of the month,

167
00:33:37.200 --> 00:33:37.730
Monica Olsson (she/her): Yeah.

168
00:33:37.750 --> 00:33:38.809
Tavares J. Terry (he/him) WaTech: Timeline's gonna look.

169
00:33:38.810 --> 00:33:39.400
Monica Olsson (she/her): Yeah.

170
00:33:39.760 --> 00:34:06.240
Monica Olsson (she/her): And my, what I heard, too, Tavares, during that co=
mmunity of practice is it's gonna you know, it's gonna cover topics that we=
're all relatively familiar with, like, you know, accessible documents, acc=
essible communications, etc. But what I what I also heard, that might set t=
hese apart from our micro courses, that our agency supports and make it a l=
ittle bit more scalable for for your all institutions is that these modules=
 are going to be.

171
00:34:06.240 --> 00:34:21.620
Monica Olsson (she/her): you know, 1520, 30, 40=C2=A0min modules also. That=
's what I that's what I heard. I don't know if that's promised the other be=
auty beautiful part, in my opinion about these these trainings being throug=
h the learning center. Is that

172
00:34:23.080 --> 00:34:48.939
Monica Olsson (she/her): your your college's Hr offices, or whoever is the =
learning Center administrator for your college can track completion. There'=
s a mechanism to track completion. So we have someone in our Hr office here=
. You know, we have a 3 person Hr team, but we have one, you know person in=
 our Hr office here. That's our dedicated learning Center, Lc.

173
00:34:48.940 --> 00:35:05.959
Monica Olsson (she/her): Administrator. And that person can help track the =
completion of these modules by Sbctc employees, and and it's not impossible=
 to do, you know, in in the, in canvas, with our micro courses

174
00:35:07.240 --> 00:35:13.680
Monica Olsson (she/her): our, you know, our agency's been helping the Seatt=
le colleges to kind of do their own thing with the courses.

175
00:35:13.830 --> 00:35:40.029
Monica Olsson (she/her): but I think it could be easier through some total,=
 because the mechanisms already set up there, and I think that these module=
s are going to be shorter than the micro courses. So our micro courses. I'm=
 proud of them. Chef's kiss. Okay, but they're definitely take, you know, a=
 few hours per module for someone to complete. And if you're if you're look=
ing to scale this, as you know.

176
00:35:40.280 --> 00:36:02.500
Monica Olsson (she/her): college-wide required training this, this other th=
ese other trainings through Gs might be the way to go, and I'll share that.=
 The agent, my agency's accessibility task force we just announced to our, =
to our agency at our all staff meeting that we're going to be using these t=
rainings for required

177
00:36:02.500 --> 00:36:12.600
Monica Olsson (she/her): staff training at the agency. So that. And that's =
how we're going to approach this and track it, using the tool available to =
us through some total.

178
00:36:14.400 --> 00:36:20.179
Kevin: Thank you all for that. That. So I'm assuming, then, that

179
00:36:20.400 --> 00:36:23.870
Kevin: the trainings that are being created will

180
00:36:24.250 --> 00:36:36.199
Kevin: then align, with which it makes sense and will, but also comply with=
 the necessary requirements of this. Of this you know.

181
00:36:37.880 --> 00:36:40.760
Kevin: User. Oh, one policy.

182
00:36:41.140 --> 00:36:45.949
Tavares J. Terry (he/him) WaTech: Yes, in terms of accessibility to the tra=
inings. Is that what you're? Yes.

183
00:36:45.950 --> 00:37:01.969
Kevin: Well, yeah. And I assume that, like the way I need to explain it to =
my compliance person just to prepare them is, it's it's going to be similar=
 to title 9 training. It's an annual required training that has to be track=
ed and required of all employees.

184
00:37:02.360 --> 00:37:03.060
Tavares J. Terry (he/him) WaTech: Yes.

185
00:37:03.320 --> 00:37:17.109
Kevin: Okay, great. They're gonna love me. I'm excited. But like I mean, we=
 have, we have active push back against even title 9. And by when I say act=
ive, like actively

186
00:37:17.480 --> 00:37:18.300
Kevin: like

187
00:37:18.740 --> 00:37:31.280
Kevin: people, groups of people telling other groups of people not to compl=
ete the training unless you get paid. So like this is, and this is one of t=
he things like that. We.

188
00:37:34.220 --> 00:37:35.520
Tavares J. Terry (he/him) WaTech: Sorry you went on mute.

189
00:37:36.510 --> 00:37:52.399
Kevin: I don't know what just happened anyway. Yeah. So this is, this will =
be. This will be added to that. I'm excited that it is a requirement, and I=
 appreciate that it's going to be created by other folks that will comply.

190
00:37:52.620 --> 00:37:54.040
Kevin: and it can be tracked.

191
00:37:54.520 --> 00:38:00.380
Tavares J. Terry (he/him) WaTech: Kevin. I'd like to just address what you =
said there about the pushback.

192
00:38:00.530 --> 00:38:06.270
Tavares J. Terry (he/him) WaTech: so as you can imagine, most of the things=
 that I do get some form of pushback right?

193
00:38:06.952 --> 00:38:09.979
Kevin: Not at all. Yes, I can imagine.

194
00:38:09.980 --> 00:38:14.840
Tavares J. Terry (he/him) WaTech: Well, you know, as we move things forward=
, we have to

195
00:38:15.040 --> 00:38:32.540
Tavares J. Terry (he/him) WaTech: be able to engage in these conversations =
without the rhetoric and the emotions that come along the the talking point=
s that we hear maybe nationally about. You know, why are these things neede=
d? Blah blah! It creates division this and that, and one of the questions t=
hat I simply ask people

196
00:38:32.860 --> 00:38:36.429
Tavares J. Terry (he/him) WaTech: when that pushback is happening is what p=
revents you

197
00:38:36.990 --> 00:38:52.199
Tavares J. Terry (he/him) WaTech: right, not. What do you feel prevents you=
? Because when you say feel, then you're giving them permission to tell you=
 why their emotions say they're right, and that we shouldn't have to do thi=
s. But what actually prevents us from making equitable environments.

198
00:38:52.330 --> 00:39:20.390
Tavares J. Terry (he/him) WaTech: What do you lose? I mean, when people hav=
e to think about it in that manner? It takes away a lot of the quote unquot=
e. Bs, if you will, that becomes the reasons why we can't do stuff and why =
we get back to what I was talking about earlier. Oh, we'll just kick the ca=
n down the road. I'll let the next leadership group deal with that, or what=
ever accessibility is all of our responsibility. The same way, equity is ok=
ay. But when people are allowed to

199
00:39:21.060 --> 00:39:26.060
Tavares J. Terry (he/him) WaTech: utilize rhetoric or or talking points to

200
00:39:26.515 --> 00:39:35.560
Tavares J. Terry (he/him) WaTech: dehumanize or to take away basic rights, =
we have to stop, and we have to face that head on. So my simple question is=
, what prevents you?

201
00:39:36.230 --> 00:39:41.250
Tavares J. Terry (he/him) WaTech: So I'm just giving that for people that n=
eed it. And if people want to have a conversation like that

202
00:39:42.020 --> 00:40:01.850
Tavares J. Terry (he/him) WaTech: more in depth when that comes up, I'm hap=
py to join those conversations and and kind of lead that not saying that yo=
u don't have your own people that that can do wonderful in that. But it's 1=
 of those things that we have to get out of our own way sometimes, and not =
just depend on the well. This is the way we've always done it.

203
00:40:02.460 --> 00:40:24.979
Kevin: I appreciate that again, being in an academic setting. I just. And i=
t's not that I want to push back against that, even because I completely ag=
ree. When we deal with issues around contracts that we have with groups of =
people that state whether or not they need to be paid for certain things.

204
00:40:25.100 --> 00:40:42.280
Kevin: Their pushback is, what do I lose this time and money right like tha=
t is their answer to your question, and we just have to be prepared to resp=
ond like and that and I, you know, again, really in

205
00:40:43.070 --> 00:40:45.760
Kevin: in favor of this.

206
00:40:46.040 --> 00:41:09.459
Kevin: but also the context of our reality, working at institutions where l=
arge powers of or, you know, communities that have contractual obligations =
signed between, you know, between institutions, and that we cannot also ign=
ore that. And just say.

207
00:41:09.580 --> 00:41:15.540
Tavares J. Terry (he/him) WaTech: And and that's great. But I I promise you=
 we can come up with 5 to 10 other areas.

208
00:41:15.540 --> 00:41:16.380
Kevin: Oh, yeah.

209
00:41:16.550 --> 00:41:18.269
Tavares J. Terry (he/him) WaTech: Things voluntarily

210
00:41:18.380 --> 00:41:29.920
Tavares J. Terry (he/him) WaTech: without. Oh, are you paying me for this o=
r this and that? That would fit the same scenario? So another question that=
 I've always asked in regard to Dei in general, because, again.

211
00:41:30.050 --> 00:41:35.729
Tavares J. Terry (he/him) WaTech: I've heard pushback before, to nobody's s=
urprise, is what other aspect of your job

212
00:41:35.900 --> 00:41:41.359
Tavares J. Terry (he/him) WaTech: do you? Do you, or are you allowed to pus=
h back on? That's required?

213
00:41:41.520 --> 00:41:51.049
Tavares J. Terry (he/him) WaTech: Right? Like, we have required security tr=
aining. We have required sexual harassment training required. Fill in the b=
lank, right respectful work. But whatever the case may be.

214
00:41:51.820 --> 00:42:14.589
Tavares J. Terry (he/him) WaTech: so why, why do we just pick and choose wh=
ere we're going to say, oh, this is how we're going to push back, not to be=
 confrontational right, but just to get to some kind of resolution. Unions =
are are a great asset for us. Contracts are a great asset for us, but we ha=
ve to be able to communicate with each other when we kind of hit those hair=
y areas and make sure we can get through.

215
00:42:17.080 --> 00:42:36.288
Monica Olsson (she/her): Amy said something helpful in the chat, and I'm wo=
ndering if it's shoreline specific. But, she said, we have been able to req=
uire the training. And I think you're referring to accessible training for =
full time faculty, because this is a federal law that we need to comply wit=
h. And I think it's written broadly into the contract.

216
00:42:36.920 --> 00:42:47.390
Monica Olsson (she/her): to be able to use like for title, 9, accessibility=
, etc. We do pay part time faculty for attending this kind of required trai=
ning, though so complex.

217
00:42:47.390 --> 00:43:07.160
Monica Olsson (she/her): So I'm wondering, Amy, if you have any additional =
thoughts to share. So it sounds like there's some required training languag=
e that's covered in your full time. Faculty contracts that where accessibil=
ity could kind of land its little like find its home more easily into. But =
then those part time faculty are a little bit of a different.

218
00:43:07.640 --> 00:43:13.300
Monica Olsson (she/her): a beast, and there's and there there's money or ex=
change involved. There.

219
00:43:13.300 --> 00:43:39.775
Amy Rovner (she, her, hers): Yeah, 100% and that's just for attending the t=
raining. And so I know I don't know if every college has like a day of lear=
ning, or we only have one a year. We've opening week. We have a day of requ=
ired training. And then we just had day of learning last Friday, and so I w=
as able to force my way in. So we had 90=C2=A0min workshop that all of camp=
us had to attend. I had one for faculty and one for staff and admin and

220
00:43:40.240 --> 00:43:54.870
Amy Rovner (she, her, hers): you know we had. I don't know 300 people atten=
d which I was shocked, but that you know it's built into their work day. I =
mean, they have. It's a contract day they have to attend. So our campus get=
s to dictate what happens on that day. So that was a really great way to

221
00:43:55.150 --> 00:44:20.180
Amy Rovner (she, her, hers): force the training on people which they mostly=
 came to willingly. But there is that next step that I know everyone is thi=
nking about is the implementation of that training. So yeah, they went to a=
 90=C2=A0min workshop. They learned how to do some things, but now they nee=
d to go into their classes and do that work, and that's where it is. It can=
 be a heavy lift. It depends how terrible the content is in the 1st place, =
and we get that question a lot.

222
00:44:20.430 --> 00:44:47.860
Amy Rovner (she, her, hers): And the President answered it recently to say,=
 this is a very important rule. We need to become into compliance. Budgets =
are a mess right now we're going to prioritize the best we can, and he kind=
 of left it open that maybe we can figure out some sort of something stipen=
d structure I don't know. For the 1st class they fully make accessible, and=
 then we check. I mean again. It is complicated, and it'll get really expen=
sive if we have to pay for every single class

223
00:44:47.980 --> 00:45:00.738
Amy Rovner (she, her, hers): and part timers are paid. I don't know what ou=
r contract rate is now 62, 50 an hour to be at that day of learning. If the=
y chose to attend, they're not even required to attend. So yeah, it's comp =
like I said, it's complex. It's

224
00:45:01.290 --> 00:45:05.730
Amy Rovner (she, her, hers): It's quite a puzzle. And because it could be h=
ours and hours and hours of work to remediate a class.

225
00:45:06.010 --> 00:45:06.730
Tavares J. Terry (he/him) WaTech: Yeah.

226
00:45:06.950 --> 00:45:07.720
Amy Rovner (she, her, hers): Yeah.

227
00:45:10.960 --> 00:45:20.680
Amy Rovner (she, her, hers): can I say one more thing? This is Amy again, c=
an we share some of that contract language out in this group? I see, Kevin =
said, there are at least 3 colleges that have accessibility in the faculty =
contract. One of the

228
00:45:20.790 --> 00:45:23.410
Amy Rovner (she, her, hers): best things to do is to share that language.

229
00:45:23.410 --> 00:45:24.100
Monica Olsson (she/her): Yes.

230
00:45:24.100 --> 00:45:27.329
Amy Rovner (she, her, hers): So that people don't even know what they're as=
king for. So.

231
00:45:27.330 --> 00:45:52.819
Monica Olsson (she/her): So if folks are comfortable, said maybe sending th=
at to me directly, I can package it up for our our listserv, our closed ema=
il Listserv. Don't know if Michael Hands comes on the call here, but I'm pu=
tting High line on the spot, because I know Highline is, for sure an exampl=
e that successfully put in accessibility requirements into the faculty cont=
ract within the last handful of years. So.

232
00:45:52.820 --> 00:45:59.010
Kevin: I want to say Clark and Mark Cascadia, maybe I.

233
00:45:59.010 --> 00:45:59.780
Michael Hanscom: Ryan.

234
00:45:59.780 --> 00:46:00.100
Kevin: That.

235
00:46:00.100 --> 00:46:00.930
Monica Olsson (she/her): Recently presented.

236
00:46:01.680 --> 00:46:02.430
Kevin: No.

237
00:46:02.570 --> 00:46:03.320
Monica Olsson (she/her): Now.

238
00:46:03.320 --> 00:46:10.580
Bryan Fauth (he/him/his): No, I it's been discussed, but there's nothing of=
ficially in the contract.

239
00:46:10.580 --> 00:46:15.940
Kevin: Okay. Okay, yeah. I can't remember who the 3rd is. Then I will.

240
00:46:16.620 --> 00:46:22.100
Kevin: Maybe Clover Park. I don't know. I want to say it starts with a C. F=
or some reason.

241
00:46:22.920 --> 00:46:43.589
Michael Hanscom: This is Michael from Highline. Yeah, we got ours in at the=
 last. The last time we did the contract 3 years ago this year. We are curr=
ently in negotiations. And so we're updating the language a little bit due =
to the title. 2 changes from what we originally had. I have a meeting on Fr=
iday where we made our suggested changes. They're coming back with some

242
00:46:43.690 --> 00:46:53.430
Michael Hanscom: with their own suggestions, and we're saying why, but so I=
 don't think there's a danger of it coming out. It's just figuring out the =
exact language

243
00:46:53.870 --> 00:46:56.600
Michael Hanscom: they're asking for a little more time to get things done.

244
00:46:57.050 --> 00:47:12.670
Monica Olsson (she/her): Okay. So I I don't think Clark's on the call today=
, but I can reach out to Clark and see if they're willing to share, Michael=
, when Highline is in a more comfy space with the language. If you wouldn't=
 mind sharing with me, I'd like to package it up for this group.

245
00:47:12.870 --> 00:47:18.120
Monica Olsson (she/her): We do have just about 5=C2=A0min left. So.

246
00:47:18.868 --> 00:47:32.320
Monica Olsson (she/her): Tavaris, I want to make sure people know how to jo=
in or participate in some way the community, the the statewide community of=
 practice, if they if they want to.

247
00:47:33.130 --> 00:47:36.380
Monica Olsson (she/her): And there was something else. But I'm having a bra=
in fart. So let's start there.

248
00:47:37.020 --> 00:47:46.469
Tavares J. Terry (he/him) WaTech: Okay? So as I mentioned before, we do hav=
e a statewide accessibility, digital accessibility, community of practice.

249
00:47:46.921 --> 00:47:51.879
Tavares J. Terry (he/him) WaTech: Our charter. And everything does say, we =
have a focus on digital accessibility.

250
00:47:51.920 --> 00:48:20.039
Tavares J. Terry (he/him) WaTech: We are aware, though, that there is one a=
rea in terms of language access where that is going to start to cross over.=
 So when the group when we restarted the group last year, we really were on=
 the focus of digital accessibility. But as I brought up to the group. And =
we're seeing now, with the advent of AI translations on systems, or somethi=
ng that we need to be talking about as well because of

251
00:48:21.180 --> 00:48:47.590
Tavares J. Terry (he/him) WaTech: thoughts about accuracy, you know, dialec=
t all of those things, and making sure it's a real resource plus. There's n=
ot a continuity right now with that. So as language access works. Now, we a=
lso have a statewide contract for that. So an agency would reach out to a v=
endor on that statewide contract, get documents translated into the dialect=
s or languages that are needed, and then that would go out to the Resident.

252
00:48:47.680 --> 00:49:08.699
Tavares J. Terry (he/him) WaTech: or whoever is needing that again. With th=
at advent of AI and the different AI that people are using. We're finding t=
hat people have that available right there on their website. Oh, you need t=
his translated hit a button, and you're seeing that happen while all of tho=
se are accurate. So that's going to be the next on the horizon of things th=
at we need to deal with.

253
00:49:09.000 --> 00:49:36.779
Tavares J. Terry (he/him) WaTech: and we need wonderful brains like yours t=
o be involved. So we do have our statewide community of practice. You all c=
an send me an email. If you'd like, I will put my email address into the ch=
at. Now, if you would like to join that if you're outside of our shared ten=
ant. We'll have to set up a guest account for you, but that's not hard to d=
o at all. So just email me with your name

254
00:49:37.350 --> 00:49:41.149
Tavares J. Terry (he/him) WaTech: and how to contact you and anybody else t=
hat you would like

255
00:49:41.725 --> 00:49:48.769
Tavares J. Terry (he/him) WaTech: involved in that. And we'll get those acc=
ounts set up for you. Our community of practice last year met

256
00:49:49.090 --> 00:50:02.029
Tavares J. Terry (he/him) WaTech: 4 times. So once a quarter, we've committ=
ed to meeting once a month. Now, because we are growing more, things are ha=
ppening. We need to be there for each other, so all are welcome. We try to =
make it a good time.

257
00:50:02.180 --> 00:50:16.920
Tavares J. Terry (he/him) WaTech: As we're getting through a lot of things.=
 The time goes quick, I notice. If you're hearing my ring thing, I'm sorry =
my dog keeps running around the yard. I don't know if you can hear it or no=
t. So I just want to apologize for that. But I'm hearing it, and I'm like d=
istracted by it.

258
00:50:18.400 --> 00:50:42.329
Tavares J. Terry (he/him) WaTech: But yeah, please come out again. We just =
got done with updates to the policy late last year. This year we're looking=
 at implementation. How we can all support each other communicate about wha=
t that looks like. Find those paths forward and whatever's on the horizon. =
From there we're gonna tackle together, great group of people. And I welcom=
e you to join.

259
00:50:42.330 --> 00:50:56.828
Monica Olsson (she/her): Thank you so much, Tavares. And I see your emails =
in the chat. So I will summarize all this information for people. Kevin, I =
see your hand. Just a sec. So Contact tavares to join the community of prac=
tice.

260
00:50:57.340 --> 00:51:11.670
Monica Olsson (she/her): and more information is going to be coming out of =
that group for the for, for the those training modules that are going to be=
 live in the the Washington State Learning Center soon, Kevin, what's your =
comment? And then, Agnes, I see your hand is up as well.

261
00:51:11.890 --> 00:51:21.000
Kevin: Just a real quick comment. And the fact that I would advocate for so=
me level. I know we're talking about digital accessibility, but some level.=
 If we're going to have a required training about

262
00:51:21.659 --> 00:51:43.660
Kevin: outside of the digital accessibility world. Specifically, I think ab=
out faculty in regards to accommodations and room setups and stuff like tha=
t. If we're gonna have an opportunity to have required training, it would b=
e great to have it be as holistic as possible versus a micro focus of this =
topic. So anyway, just throwing that out there.

263
00:51:44.310 --> 00:51:46.140
Monica Olsson (she/her): Thank you, Kevin. Agnes.

264
00:51:51.540 --> 00:51:52.159
Monica Olsson (she/her): there you are!

265
00:51:52.614 --> 00:52:10.780
Agnes Figueroa: My question might require more time. We have right now, and=
 it's clarification on item 5, where it says that by July 29.th All content=
 tools that employees need to perform. Essential job duties must be accessi=
ble and

266
00:52:11.180 --> 00:52:24.759
Agnes Figueroa: not all tools are web based tools. So I'm just one clarific=
ation are are we talking about? Let's say, my Hvac software, that I have 2 =
or 3 employees working on it is that the level that we are referring to her=
e.

267
00:52:25.460 --> 00:52:33.489
Tavares J. Terry (he/him) WaTech: So when you're saying working on it or wo=
rking with it, cause the distinction is tools that people are utilizing to =
do their job.

268
00:52:33.990 --> 00:52:39.969
Agnes Figueroa: I will be working on with the tool, using that tool in orde=
r to control the Hvac system. For example.

269
00:52:41.790 --> 00:52:51.770
Tavares J. Terry (he/him) WaTech: Yeah. So if there's a need for them to do=
 that. And then they okay, let me say it this way. So as people procure too=
ls.

270
00:52:52.374 --> 00:53:17.029
Tavares J. Terry (he/him) WaTech: And this is part of what we get into with=
 procurement as well as in the standard. We need to be making sure that tho=
se tools are are accessible, going forward to these levels. Now, in terms o=
f tools that you're utilizing now. That's a conversation to have with the v=
endors. But yes, the expectation is, if these are tools that people are uti=
lizing to do their job, then they need to be accessible.

271
00:53:17.320 --> 00:53:20.380
Tavares J. Terry (he/him) WaTech: And of course there's gonna be degrees of=
 things to that. So.

272
00:53:20.380 --> 00:53:25.508
Agnes Figueroa: Because we have tools that have been purchased as buildings=
 have launched over the years.

273
00:53:25.850 --> 00:53:26.290
Tavares J. Terry (he/him) WaTech: Yeah.

274
00:53:26.290 --> 00:53:28.281
Agnes Figueroa: Those tools are really old.

275
00:53:28.680 --> 00:53:29.090
Tavares J. Terry (he/him) WaTech: Yeah.

276
00:53:29.090 --> 00:53:35.483
Agnes Figueroa: You know. So we can fix new buildings. But the older buildi=
ngs is kind of like, okay,

277
00:53:36.010 --> 00:53:48.620
Tavares J. Terry (he/him) WaTech: Yeah. And that's where we have to have th=
ose conversations about prioritization. And also about, you know, is this a=
 tool that we can work with the vendor up to update is this something that =
we need to look at in the futures of

278
00:53:48.860 --> 00:54:09.010
Tavares J. Terry (he/him) WaTech: as a future procurement? Like if, as we'r=
e looking to replace legacy systems, we should be looking at accessibility =
within those systems, not the old. Well, it's mostly good. So we're gonna r=
oll with it and then keep mandating that down the road so a little more com=
plex than I can answer right here. But I'd love to get into that with you a=
 little bit.

279
00:54:09.010 --> 00:54:29.520
Monica Olsson (she/her): Agnes, I also. This is Monica. I know we're out of=
 time, and people are leaving. But I I wanted to say, and I think it's crit=
ical to think about to prioritize. So this what the item that you're reques=
ting, you know, clarity on is Washington State specific? It's not the title=
 to Doj ruling

280
00:54:30.280 --> 00:54:51.080
Monica Olsson (she/her): but prioritize tool, like communication system and=
 tools that all college employees are required to use to some degree to be =
an active employee of the college. So communication access those types of t=
hings. That's where I would really start and prioritize

281
00:54:51.080 --> 00:55:00.460
Monica Olsson (she/her): there when we get into very niche specific. You kn=
ow, roles that people are hired for that might require

282
00:55:00.950 --> 00:55:05.990
Monica Olsson (she/her): really specific proprietary hardware or tools like=
 that.

283
00:55:06.050 --> 00:55:11.849
Monica Olsson (she/her): The Tavares is, and I am not suggesting that lies =
with outside accessibility requirements.

284
00:55:12.170 --> 00:55:28.840
Monica Olsson (she/her): But there may be different limitations that are ju=
st reality, in fact, of the the nature of the tool itself. And so I heard T=
avara suggest, you know that's a conversation with with the vendor, or, you=
 know, future procurement, improvement

285
00:55:29.285 --> 00:55:51.449
Monica Olsson (she/her): discussion as well. But I would, when thinking abo=
ut that requirement in Washington State, I would prioritize. What are the s=
ystems that everyone's required to have access to? No matter their job? Thi=
s, the the level of specific, you know, niche level of their job. And think=
 about that first, st then kind of go from there.

286
00:55:52.250 --> 00:55:54.220
Monica Olsson (she/her): Tavares. Is that a fair statement.

287
00:55:54.220 --> 00:56:01.481
Tavares J. Terry (he/him) WaTech: Yeah, it was a very fair statement, and I=
 think it will keep us all from looking like me and pulling the rest of our=
 hair out.

288
00:56:03.030 --> 00:56:14.910
Monica Olsson (she/her): Alright, my friends, we are a few minutes over and=
 thank you to the group that has stuck stuck stuck with us. Thank you Tavar=
es for your time. I really appreciate it. I'm gonna go ahead and pause. Our=
 recording.