CHRISTOPHER SORAN: Already started. 

MONICA OLSSON : OK. Sounds good. 

CHRISTOPHER SORAN: All right. Good morning, everybody. I'm Christopher Soran, application support manager. Appreciate you coming for the October edition of our ctcLink Accessibility Forum. All right. We're going to go ahead. So we're going to be talking about Campus Solutions 38, Okta, and some Oracle updates today. So for the CS 38 Image, I'm going to go ahead and turn it over to Josh. 

JOSH GIHA: All right. Can you hear me? 

MONICA OLSSON : Yep. We can now Josh. 

JOSH GIHA: Awesome. Good morning, everyone. My name is Josh Giha, and I'm part of Christopher's team. And I'll be sharing with you today the latest updates that went into production as of Saturday. This is for the Campus Solution Image 38. 

A lot of these fixes or a lot of the adjustments that they made in Campus Solutions, CS, 38 Image pertain to WCAG 2.2, specifically 2.5.8 success criteria, which deals with target size minimums. And what that basically entails is controls and buttons and things should have a minimum of 24 pixels of space in between each other, but this pertains only to their fluid pages. 

And when you turn on screen reader mode on a non-fluid page like the Classic or Classic Plus pages, we still see the links are pretty close together, but on the fluid pages and with screen reader mode turned off, they've done a lot of work to address the target size minimum requirement. 

So in these following navigations, the changes that were included are increased spacing between hyperlinks and interactive controls. Also, improved spacing for the Address Type selections, updated Student Center layout, as well as an added visible label for the Currency field on the Holds page. 

So for the Student Center and under the Student Center home page, Personal Information, Address Edit page, and under Student Center Holds, these are the screenshots that show the differences. So on this Edit Address page, they've added a new link. 

And that link allows you to change your country from United States, as well as they've addressed some spacing with the buttons. So before, they had this OK button on its own and not really aligned with the Cancel button. And they've addressed that in this image. 

On the Holds page-- or there's a table here, and on the table 1 of the column headers was missing. So that has been added. It was the Currency Code column header. And for the next few navigations, it's further WCAG 2.2 enhancements-- improve focus visibility and control spacing for the pages, as well as an updated shared style use for the Faculty Center pages. 

So the next few navigations will be going through, they evaluate Transfer Credit, Browse Course catalog, My Academics, and under Faculty Center, My Schedule. So under Course History, they've updated the spacing for the column headers. Under the Faculty Center, View My Schedule, they had these unnecessary bullet marks next to the term. So they've removed those now. 

And they've now moved to a more consistent and repeatable search criteria. So now the search results appear in the same places for all these pages, whereas sometimes they would show up at the bottom, sometimes they would show up at the top. Now, they're all at the top. 

Under student Self Service, Academic Records and Milestones, there was a pop-up modal that would show more details for the student's milestone. Those tabs were not keyboard-navigable before. So now, they've updated that, and it now shows the appropriate focus when you're on a different tab within that modal. And that's it for that. 

So moving on to the next fix. This is under the Student Services Center. Previously, they had these buttons labeled simply Go. And it didn't give the user any information on where they were going to. Now, the button is appropriately label to show what-- to say what section it's going to, and it no longer says Go. It says Proceed to other academic information or Proceed to whatever that button points to on this page because there's several of these Go buttons. 

Moving on to the Faculty Center, View My Schedule, Exam Schedule page. They resolved screen reader heading inconsistencies. They removed blank columns exposed in accessibility tools. They corrected grid accessibility markup, as well as invalid grid error that would sometimes show, as well as just improved overall screen reader announcements for the Exam Schedule page. 

So here is an example of how before, they would have these double headers. That would just confuse the user. So they've removed that now. And it's down to a single header as it should. And here's the example of the table that has been enhanced. More 2.2 adjustments. 

This stays into the Faculty Center, and under Gradebook, Class Cumulative Grades, they have aligned the Select Grade Roster field and labeled with proper spacing. So here's an example screenshot of that page with the correct alignment. Under the Faculty Center, View My Schedule, there was a Calendar View option that I guess previously, some would sometimes not load properly. So after this fix, it now loads properly and it is keyboard-navigable. 

Under Self Service, Transfer Credit, Evaluate My Transfer Credit. So student self service. When they would go to this little mini form for the Evaluate Transfer Credit, there would be-- the screen reader would announce things that were not visible on the page. For example, the group box would be announced even though it was not visible on the page, which would be confusing for users. So they've addressed that and it no longer reads out objects that are not visible on the page. 

Moving on to our next fix. This is under staff administration-- Curriculum Management, the Fluid Class Search, Class Index Preprocess. If you traverse through the application content using the tab button, the tab focus was not moving in a predictable manner. It now moves correctly. 

And moving on to the next 2.2 adjustment. This is under student Self Service, Campus Finances. This is financial aid. For the View Financial Aid, as well as Accept/Decline Awards page, they've updated spacing and link controls to meet the target size requirements. 

These are very-- a lot of these were very hard to tell where they made this spacing adjustments because they were only one or two pixels adjusted. So you would have to basically compare the page in an app design to find the actual pixel adjustments. 

But in this example for the Financial Aid award summary, it's a little clear in where they've added the spacing for the individual links. And they've also updated the spacing within the column headers on the table itself. And that brings us to the end of our CS 38 accessibility fixes. Do we have any questions about any of what I went over? 

MONICA OLSSON : This is Monica. I don't know if I have questions. I'm just taking in the list. I think it's an impressive amount of things that have been improved in this particular image release. And in particular, looking at visible focus, target size, controls being consistently located in the same location across pages, improvements to how grids are now navigable and functioning. Like that's a lot of design improvements. 

So I don't know if we've seen this amount in previous image releases. And the fact that you, Josh, you're going through those release notes and looking at these accessibility fixes and enhancements is just really beneficial to this community. So thank you for doing that and giving this report. 

I'm wondering if from your perspective as a developer, are you feeling happy with this particular image release when you were going through and verifying those fixes? What's your take on this work? 

JOSH GIHA: I'm still a little bummed about there being two completely different versions, like the screen reader mode on is-- 

MONICA OLSSON : Yeah-- 

JOSH GIHA: A lot different than screen reader mode off. I'm still bummed about that. I feel like they're making improvements to make the screen reader mode off fluid pages accessible as well, but they still tell users that use screen reader devices to leave it on. So I'm a little torn with that. As far as all the fixes that came in with this release, it was a little difficult to find some of them, like what was actually fixed. 

But overall, I'm happy where it's going. I believe the CS 38 laid a lot of groundwork for the Faculty Center to be improved. So when our current Faculty Center is heavily customized. But I can imagine in a few years, we might be able to integrate some of the new features that are available to us for Faculty Center into our current Faculty Center. 

MONICA OLSSON : Thank you. 

VICKI WALTON: This is Vicki. I want to try to get an understanding of how this works. So are those issues that got fixed-- are those the events that you presented to PeopleSoft and they finally got to them to fix them or are you consistently testing and sending the information that you're finding that needs to be fixed? I just want to understand why sometimes there's a few fixes and other times there's a lot of fixes. So I just wanted to understand the process of how that works. 

JOSH GIHA: Christopher, you are a better person to answer this question. 

CHRISTOPHER SORAN: So yeah. So the-- 

MONICA OLSSON : I know. 

CHRISTOPHER SORAN: Oh, is that-- 

MONICA OLSSON : Right. It's a combo. 

JOSH GIHA: Yeah, definitely. 

CHRISTOPHER SORAN: Yeah, it's a combo. So anytime we see it, we report it. Any time an issue is reported to us, we're going to report that. And also, with every image comes a list of bug fixes. And so we look through those for anything accessibility related, and then we try and see if we have enough information to be able to report out on that or test it. 

If we don't have enough information, then we ask for more information to know what this is impacting. And obviously, finding a single pixel difference is a little too detailed for the-- but we had that information was in the bug fix. 

JOSH GIHA: And some of them are reported from us. Some of them are also reported from other institutions. There's a lot of Texas. And I think some schools in Boston are very active when it comes to reporting accessibility bugs as well. So we're not alone in the fight to make this a more accessible platform. 

VICKI WALTON: Well, it's encouraging. Appreciate all you guys do. Thank you for that explanation. 

JOSH GIHA: Yes. 

CHRISTOPHER SORAN: Yeah. 

JOSH GIHA: All right. That's it for me. I'll hand it back off to Christopher. 

CHRISTOPHER SORAN: All right. I'll need to patch notification. So if I randomly disappear, it's because this patch is being pushed on my system and I can't. Hopefully, I can stay. 

MONICA OLSSON : Hopefully, you stay for 10 more minutes. 

CHRISTOPHER SORAN: There's no pause update button. That's interesting. There you go. Yes. Okta. 

MONICA OLSSON : OK. I can take this one. So I think we're all familiar with what Okta is in this room. So for our college guests, Okta is a MFA-- so multi-factor authentication tool-- that is used across our system connected to signing in securely to ctcLink. And then depending on your institution's choice in MFA tools and process, you may also be using Okta for other applications as well, like we are at the State Board. 

And about a year ago, a group of us at the State Board, mostly the people in this room, we began attending monthly accessibility check-ins with folks from Okta as we became increasingly aware of accessibility issues and screen reader experience hardships when going through the MFA authentication process. And they've made considerable progress over this time, talking with them and working with them. 

The update today on this slide is to let everyone know that they very recently in the last week published all new completed and updated VPAT or ACR reports for their product. And so there's 1, 2, 3, 4, 5, 6, 7 reports shown in that list that got published, including the Sign In Widget et cetera. And they are mapped to WCAG 2.2 AA. 

I am not saying all of these items meet 2.2 AA, but they have been evaluated and mapped against WCAG 2.2 AA. And Okta partnered with DQ as a third-party accessibility auditor to help them evaluate their platform and make those reports. And that, I think, is a good choice for them to do so. I hope they continue with that kind of partnership. 

I've cruised through them at a high level. I haven't read them in super nitty gritty detail. Vicki's looked at them all, I think, a little bit closer under the hood. And it's notable that some improvements have been made from the last round of VPATs, but there are still several areas where they state partially supports, with examples of what is not meeting that particular success criteria. 

And there's some areas that we would consider critical or foundational criteria to meet, particularly if it's at the A level. So we'll be bringing up our takeaway questions or follow up questions at our next accessibility meeting with Dr. Folks. And it sounds like we just got switched to a new main contact person. So we'll need to reestablish that little bit. So that's the update there. 

You are welcome to-- anyone is welcome to read these ACRs as well and send in questions or feedback if you feel moved to do so. But we're aware that that information is there, we're looking at it, and we'll be discussing it at our next meeting as well. 

VICKI WALTON: Monica, this is Vickie. I just want to say that for anybody that's familiar with DQ doing these accessibility conformance reports, they always get a scope. So in those accessibility conformance reports, they list the pages that they have tested. It's not a full blown the whole gamut. So which is fine because they're really good about choosing the most important areas that need to be tested. So I just wanted to mention that. 

MONICA OLSSON : Thank you. 

CHRISTOPHER SORAN: Thanks. So we have had a couple of-- one or two over the years-- accessibility contacts at Oracle, and Oracle laid off a bunch of people in September, and those folks got caught in it, unfortunately. So we've always worked through reporting our issues through the service desk tickets with Oracle. 

These folks have been those back end help people move stuff along, get the manager to look at something, to get a ticket solved, or get it higher up in the queue. So it'll be different without them. We'll be working through the SRs. They'll certainly be hearing from us if I'm not getting the responses I'm looking for. So our commitment certainly hasn't changed. But some things get longer as we lost our contact. So folks know. 

Yeah. And then we had a form for folks to submit forum ideas, but you can just email us. 

MONICA OLSSON : Yeah 

CHRISTOPHER SORAN: It's just-- 

MONICA OLSSON : The web form was a neat idea because we thought, if a lot of people were using it, it's an organized way to receive questions or feedback, but it was not being used for what the purpose of the form was. So the only response submissions we were receiving were from people who could not log into ctcLink and needed technical support help from their college. 

So it wasn't anything to do with disability-related accessibility issues necessarily. So we retired the form, but we're still here. So our college participants, when you have a accessibility-related question or a request or comment related to ctcLink that you want to discuss with us or at the forum, you can still provide that to us, just not through the form. 

CHRISTOPHER SORAN: Thanks, Monica. All right. We got the ctcLink Accessibility web page where you can go find the Image Overview document that Josh went over, as well as all the others. And our next meeting is in November. Yeah. 

MONICA OLSSON : Same time, same Zoom link. Thank you, everybody. 

VICKI WALTON: Thank you. 

CHRISTOPHER SORAN: Next time, everybody. Have a great week. 

MONICA OLSSON : Bye