CHRISTOHER SORAN: Good morning, everyone. Welcome to the December edition of the Accessibility and ctcLink Open Forum. I'm Christopher Soran, the application support manager. We'll go ahead and get rolling to that. All right, so Ariana, I got you assigned to do the closed captioning. Let me know. Do you have any questions? Let's get rolling. So we're going to talk a little bit about Okta, little bit about Human Capital Management Image 53, and a couple of updates to some Oracle service requests. 

All right. So first on deck is the Human Capital Management Image 53 accessibility image overview document or IOVD if you like acronyms. I'm going to go through all the new accessibility changes that came in with this latest image. So this image was diploid in on November 22 in production. So all these changes are currently live. 

All right. So that's interesting. All right. So in Manager Self Service on the Team tile, when the page loaded the focus incorrectly landed on the Get Employee button on the Enter Time page. So it's a two-panel layout. On the left side, you got all the Navigation, Options, Menu choices, and then the right side where that page loads. 

So since the focus is landing on the last button on the right side, on screen of yours, obviously had difficulty navigating the page. It's not where the focus should start. And so what I'm showing at the bottom of the page is a screenshot highlighting the Get Employees button in that right panel where the focus landed prior to Image 53. And then after Image 53, displaying on the screen is a screenshot of the Team Time page highlighting the Back button. So the focus correctly lands on the Back to Manager Self-service button in the top banner, and then you can work down the page. 

So starting on the far right bottom of the pages. It's a nice little fix. Another focus fix. So in Employee Self-service on the Payroll tile if you go to paychecks, and so you're going to view your paycheck. Prior to Image 53, when the page-- when the View Paycheck page opened, the focus shifted to the top right to the Exit button, the Close button of the page. And the bottom of the page, I'm displaying a screenshot highlighting the Exit button in the top right on the View Paycheck page. 

And at the top of the screen is a screenshot. I'm displaying the View Page at page after Image 53, highlighting that the focus now correctly lands on the first field of the page. So to make navigating that page a lot easier. Focus is the focus this time around. So another focus indicator. 

So in Employee Self Service and the Time tile and the Enter Time page, in the prior to Image 53, when you went to the Submit button, it wasn't clear where the focus was that you had the focus on the Submit button. And so when I'm displaying here at the bottom here, is a screenshot highlighting that the Submit button, just appears as it does when the page loads, even though the focus is on that. 

Let's scroll down here. And now after Image 53, the focus indicator is-- there's a dotted line border around the Submit button. So now, you can tell that focus is shifted there. Another thing that was fixed. So if you're in Employee Self Service and you go to the Payroll tile and you go to the Direct Deposit tile and you go to Add an Account. So if you want to add a new direct deposit account, there are several fields on the page that are required. 

I'm going to scroll down. And so what I'm displaying now is showing the Add Account. And the asterisks next to Payment Method Account Type and Deposit Type is highlighted, showing that those are required fields. Now, there are actually-- nickname is only field on this page that isn't required. So there's other required fields that aren't being indicated. So that's definitely confusing, especially if you think you can skip over field and you can't. 

Scroll down here. And so now after Image 53, what I'm displaying is a screenshot of the Add Account page after the update showing the asterisks next to the routing number, account number, retype account, and amount of percent. So now, all the required fields properly show the asterisks. So there's also on another Employee Self Service update, if you go to the Payroll tile and then you go to Compensation History page, there's a little I indicator button next to the Apply and Reset buttons. And so hovering over that gave you information. 

It says press Enter for the details of Apply and Reset, which that isn't really much details. Apply and Reset are pretty self-explanatory. So what I'm showing here is a screenshot prior to the update, where it's highlighting the little I indicator you can hover over next to the Apply and Reset buttons. We'll just press Enter for details Apply and Reset. And what I'm displaying, the screen is now a screenshot of that compensation history page, showing the Apply and Reset buttons with the I indicators removed. So just extra redundant information. If you want to apply your changes, click Apply. If you want to reset the form say Reset. That's fixed as well. 

And so those are the updates, the accessibility related updates that came in with Image 53. 

VICKY: Hey, Christopher, this is Vicki. Does the screen reader announce those required fields? 

PADMA: Yes. This is Padma. Yes. 

VICKY: OK. So when the focus lands in a field, it lets the screen reader know that is required. 

PADMA: That's correct. 

VICKY: OK, cool. Thank you. 

CHRISTOHER SORAN: Yeah, thanks [INAUDIBLE]. Yeah, any other questions on this? Sounds good. Here's slides for you, Vicky. 

VICKY: I guess that's me and Josh. So we are going to be doing some accessibility testing on the Okta dashboard in conjunction with Okta verify. We've had some updates with the system. And so we are now performing our accessibility evaluation to make sure that it meets the accessibility standards. 

So Josh, when we're in the dashboard, Josh navigates with NVDA and I navigate with [INAUDIBLE] And then when we're on the Okta verify app, Josh navigates with TalkBack on an Android and I navigate with voiceover on iOS. So we will be getting that done and submitting our reports when we're concluded. Anything else you want to add, Josh? 

JOSH: I'll also be testing Mac OS. 

VICKY: Oh Yeah. 

JOSH: It's a little bit different than iOS, I found. Yeah, that's about it. 

VICKY: OK, thank you. OK, I think that's it. Any questions? 

CHRISTOHER SORAN: Yeah, any questions? 

[CHUCKLES] 

JOSH: Let you know what we find. 

CHRISTOHER SORAN: All right, a couple of Oracle service requests. So in Image 53 the Oracle supposedly delivered a fix on the Benefits Summary when you're in small form factor. So if you're on your phone, the horizontal scroll bar is missing. And so they claim they fix it, and they didn't. So we had to submit a new service request letting them know that it didn't work. Please try again. And then in-- so in Firefox, and then there's another one. So in Firefox, the Calendar button gets read as Button and not Calendar Button. And it gets read correctly in any chromium based browsers. 

So that's a workaround is to not use Firefox for any calendar related features. But we have opened, I think, free service requests with Oracle on this one. And they tried just closing the bug without letting us know that the bug was closed and they weren't going to fix it. And I'm pretty frustrated by that. So we-- Padma has been very persistent and I think opened a third SR. So thanks to our good work, we're continuing to push them to actually fix it. I told them that was just unacceptable. You can't just excuse-- they said it was because it was Firefox. It's Firefox's fault. 

Like, well, if you support Firefox then fix it. So I got-- yeah, it seems like they're going to get it actually. They're reviewing the case again. So hopefully we've convinced them that they need to fix it. So we'll continue to be persistent until we get all the fixes. So yeah. That's all we had on the agenda for today. 

SPEAKER: I have a question. I'm curious to know how you find these errors? Are they mostly people submitting tickets or are your team assigned a certain area of people soft and they continue to monitor it? And then when they find an issue, they submit it? 

CHRISTOHER SORAN: I almost never get a ticket with an accessibility issue. Almost all of these issues are found by our team. 

SPEAKER: Wow. Good job you guys. That takes persistence. So kudos to you. 

CHRISTOHER SORAN: Yes, we appreciate Josh and Pam very much. They do great work. 

SPEAKER: Yeah, definitely. That's all I had. 

CHRISTOHER SORAN: Yeah, sounds good. And if anybody sees anything, please let me know. We're happy to pressure Oracle to fix things. Or if there's some customization we can do to make it work, like on a custom page, we can work on that as well. So yeah, please let us know if you hear anything from any students or staff and it's not working. And let us know if you want to talk about any particular topics in future meetings. We'll get those on the agenda. 

And these slides, as well as the image overview document that I just went through, those are all on the ctcLink Accessibility web page. And our next meeting is on January 13th. Yeah, I appreciate everybody's time. Thank you for coming today. Happy holidays to everybody. 

VICKY: Thank you, Christopher, and everyone else. 

PADMA: Thank you.