CHRISTOPHER: Good morning, everybody. Welcome to the September edition of the ctcLink Accessibility Forum. It should be a quick meeting today. Got some updates. We got some stuff we're working on. 

Oh, I see. What's up, chat? Oh, OK. Give me just a moment. All right, Ariana. So Ariana's requesting access to type closed captions. Apologize. Monica told me there would be no closed captions today, so I wasn't prepared for that. OK, I'm going to stop sharing. I can't access that part of the controls while I'm sharing. Thanks for your patience, everyone. Be right there. 

All right. Got the assignment now for the closed captioning. Thanks for your patience, everybody. So we'll have that going here shortly. 

All right. So on the W-2 PDF-- which took us a couple of years to get them to tag it correctly, so that was a huge win-- when you're on box 13 and you're navigating in Acrobat Reader with NVDA, it reads out the check box unavailable, checked read only, Y. Check box unavailable, not checked really only, Y. 

When you're going through JAW-- using JAWS and navigating, which you've navigated to box 13. It reads out the retirement plan, colon y, check box checked, colon y for the third party sick pay. Colon y, check box checked. That extra colon y doesn't really make a lot of sense. None of the other check boxes do that. And so, that was our service request to them saying, hey, it's reading an extra colon, which is confusing. There's no need for that. 

And after lots of back and forth, they said that we only support PDFs we've tagged. And when used with Acrobat Reader using a screen reader, this tagged correctly and the user is using Adobe, or a particular screen reader where the tags are not read properly. It's a third party issue. We have similar scenarios with other browsers interacting with JAWS and NVDA or VoiceOver, where it's a vendor issue rather than PeopleSoft specific issue. 

I responded back in the SR, don't close it. You need to fix it. Don't blame Adobe. Adobe Reader is the one they recommend, but also the one that isn't working, so. I don't understand that. But I may have not been successful in getting them to fix the reading out the extra colon. It's inconvenient, but at least it's not broken, and it's tagged, so. 

Yeah, I'm a little frustrated, but, that's the update on that one. Any questions? All right. 

Some other work that we've got in progress. So the upcoming update to Campus Solutions. There is version 35, it's coming. In October, we'll be deploying it to into production. We're working on creating the Accessibility Image Overview Document at the moment, so you can see the changes that are coming in with this update. And also, Vicky, Josh and Monica came up with a testing plan schedule for the Okta dashboard signing widget and the verify updates. And so, they'll be going through that testing process soon. 

And we'll be reporting out what they find, and reporting it to Okta as well, of course. And we continue to go back and forth with Oracle and ESR as we have open. And that's our updates for this month. So, quick meeting. Free to check out any previous Accessibility Image Overview Documents, or anything else on our ctcLink Accessibility web page. 

I'm just going to continue trying to make stuff accessible and work with all our vendors, and we appreciate your time. We'll be back here again next month, on October 12. Yeah. I guess we'll go ahead and open up the floor if there's any questions, or thoughts that have come up. 

Fall quarter is about to start for everybody, so you probably want to focus on that. Probably OK to have a quick meeting right around this time. While students got coming in. Well, if there are no questions, I'll see you all next month. Have a great day, everyone. 

WOMAN: Thank you, Christopher. 

[CHUCKLING]