 Okay, welcome. This is Jenkins user experience meeting today is December the 7th. And attending is Tim Jakob. We have Jake Leon with us. We have Christina with us and we have myself, Alexander Brandes. Okay, first item on the agenda. First item on the agenda are security reviews for UX requests by Tim. I don't know. I haven't really been following too closely where it was supposed to review if they were going to continue the process. I think the main ones got unblocked. Yeah, he added a comment to last week's meeting that the security team meets every Friday and make sure that they don't miss anything we ping them for. Okay, yeah, there's only two sitting with needs security review currently. And one closed, which I'll remove it from. And yeah, the two that are sitting there aren't really not active or likely to move forward anytime soon, I think. Yeah, I think the item from the last meeting was likely just for the TPJ SPR. It wasn't hold for a very long time. It was a lot. It was more than that. It was a whole bunch of them. It was, I think it was maybe three or four that were been stuck for a while and there was probably 10 to 15 sitting there. So it looks like it looks like they've sorted it out now. It's a much better start. Yeah, that's good. And it was last week's meeting. The next topic are user feature flags status report from Vadek. I think that didn't happen a lot from last meeting. At least the PR is almost in the same state since then. Yeah, just taking a look at the feature flag PR from Vadek there wasn't much progress from last meeting. I guess a few general things we really need to talk about. But yeah, things didn't change much since then. The next point are web components and Jenkins UX from Torsten but he isn't here today. So, yeah, I don't think we can add a lot to that. He submitted a PR to Jenkins. There happened, they didn't have much a lot with the PR. Currently the build is failing and there is no, there's no proof of concept or something that we could take a look at right now, just on the PR itself. He basically added everything he was talking about in last meeting. But that's basically it I think. Yeah, we didn't, we didn't take a close look at the PR yet. I guess on the comments. The next part is the Yahoo UI removed from Jan and Tim. First delivered and last week's weekly release. Yeah, and we have apparently a draft PR for that. That is a follow up that adds more as I see. Yeah, it gets rid of the Yahoo UI menus. And yeah, I see for like, drop the menus. And so on by that is still a draft. There's a lot of tests failing as the reason it's in draft. I think quite a few functionally I think it works but yeah. Yeah. Moving to the Yahoo UI removal. I think that was this week's release yesterday's release where we fixed at least Jan fixed several regression from the initial PR that cost low that cost regression with loading pages, taking at least 10 or more seconds caused by the TPJ SPR. But this, this has been fixed by now. And we're going to go there on. Your X improvements by Jan and Tim. I haven't had time really to work on anything. My limited time right now is stuck on dependable PRs. Yeah, we have quite a few of them. Yeah, taking a lot of time. Yeah, that's true. Do you have anything outside of the agenda. This is basically a quick addition around accessibility and of the UX specialist group is the appropriate place for that or if you have a separate accessibility. Yeah. I don't remember which client provided it but we had a list of accessibility issues for WCGA compliance. And she wasn't sure the status I went through and she directed me to use kind of the CI dot Jenkins auto since that was presumably I think the baseline for for what's recent. But look, wasn't great. There were a lot of issues. How, what's the best way to kind of get that, those issues back into the community, or is there a effort ongoing, kind of the major ones, the ones that I see as kind of the most. The biggest roadblocks to someone who would be trying to navigate with accessibility issues is, you know, the new, the new breadcrumb menu. How there's those little, you know, sub dropdowns between each layer. Yeah. Yeah. So if you were to navigate board, keyboard down into select one of those, you know, what you want to call them the menus within each breadcrumb layer, if you navigate down a keyboard through them, a keyboard to the last input, where I would typically expect that, you know, I keep tabbing it close that menu and bring me up to the next item in the tab order, the breadcrumb bar. Currently it spits you out in page. There's a few issues like that of like the the tab order being maintained on on keyboard navigation. What's the best way to get that feedback. Yeah, it shows really somewhat someone to review the document and I think there should be some labels for it because it's there's been a number of these audits before. I'm just trying to say the problem. So on, there's always this impulse to just use kind of the browser extensions or automated tools for the accessibility checks, and they don't find a lot of the major navigational issues. So it's good for identifying like that all of your alt tags are there that the color contrast is okay but they kind of those tools fall apart when it comes to auditing, like the keyboard navigation which is kind of one of the more important pieces of of a site being accessible that someone can navigate through it. I don't know how best to. It really needs someone to just review and raise issues labeled appropriately maybe maybe even adding it to the UX dashboard. Then the. So there's the. Wow. There's a very new dashboard for it that shows them the ones I've got favorited a UX regressions and UX newbie friendly which some of these might show up on there but I'm just saying maybe is there exists. Yeah, so some Jerry barely loads for me so I can't I can't really contribute much and anything to do with your which has not been helping for me. Just does does not load. We don't have to solve it today but it's just something to think about kind of the best way to both. So I think the so there's an accessibility label and labels equals. I think we have the UX regression over time dashboard and we have the open UX regressions which are untrived. We have no real dashboard or an epic to track actual feedback on what we do. Unless I'm not following the dashboard. Yeah, I mean the dashboards probably I mean this group we don't have a UX overall dashboard this is just a like a. Kind of it's a bug dashboard which I mean the accessibility might fit into but I probably want to label it separately as well. So I've sent a link and a couple links in the chat so the first one should show up things with the accessibility label on it. It shows open ones as close ones as well. Let me fix that and resolution is isn't any kind of prioritization. So I've just I've just changed it to only show open ones there's only 12 open at the moment. Because there's definitely some areas of low hanging fruit that if they were addressed, it would go a long ways towards so much about accessibility compliance to is demonstrating good faith that like they are being dealt with and triaged and. So there's in core itself stuff like that would be. Yeah, in core itself is only nine that are open. But yeah that would be the way. Okay. And then possibly another. Well, maybe another area on the on a dashboard or something just so people see them. Yeah, anyone can anyone can report the issues. Okay, I'll add some, at least like preliminary, some of the big pieces start there. Yeah they're quite good and things like a hack type of vest and that sort of things, or in hack things because they're general, a lot of them can be fairly straightforward to fix quite quickly. That's it, like a lot of it is just like that where you feel like the lap the the absence of like just like a QA test plan. It's just to make sure that they're the testing's been done before it's committed but. Yeah, I see only grazed a few a while ago they're there. They're not very actionable because they don't have. They don't have specifics in them. So if I could just show you examples of not very good bug reports. Just sending links. So these are a couple that aren't very good, because they say it has some space or images it doesn't say where they are. This is there is an order to say it's hard to navigate with a keyboard where it's not actionable. I would probably close either close status won't fix or repurpose it. I mean this is the core of what I would probably. Yeah, no I agreed these are poor. I would probably add it with kind of some it also adds some. There's not. There's not always a great understanding about what exactly this. The requirements are for each level of accessibility compliance. So I think it would probably be helpful if in the bug report I include some kind of where it's happening and what it would look like examples of what it would look like resolved. This things like even the build queue in the bottom left sidebar. If you have 80 items there you have to keyboard. There's just traps everywhere like you have to tab through to get to your content you would have to tab through all 80 of the items in that build queue before your cursor took you to the main content of the, you know, the main content area. So it's just like adding some bypass. Some hidden bypass. I just tried and you can't actually do it. You can't navigate through the build executor status to the main area. It's constantly it's constantly refreshing. So it's not actually possible to tab through unless it's unless it's basically empty. Yeah, so what you'd probably do what you want to do in that case is under the build queue header with the hidden area tags put a jump to main content area that's only available on the board. Yeah. And just let people bypass those areas similarly when you first start to have age. Keep them from having to go through that whole top area do like a skip to navigate skip to content area. But I'll make some tickets and just include some examples that may be helpful. And then I assume people can post questions and comments in the thread. Do they tag the original bug poster. And they will I think when you create them you should get automatically subscribed. Okay, cool. All right, we'll start there and then we can revisit how that process works. And revise it as needed. Yeah, fix the navigate fixing the keyboard navigation. And all of the likes. There's a hierarchy of what's most important as far as accessibility goes and the nav keyboard navigation part is one of the biggest like all tags on space or things like that those are nice to have but if you don't have the kind of the navigation result that's kind of, you know, not worth the effort to fix, fix that with the bigger pieces broken. So, cool. Yeah, that sounds good so far. I have over all a very high amount of you X rated issues but they're also there's also a pretty high amount of it's just like these, which are basically not felt properly and don't allow any try it or anything further to investigate. My new issues that I if I when I create the new issues. And I linked to related issues to like capture all of these little orphan tickets that are kind of half baked so that when the proper ticket for keyboard navigation is done and these will be closed. I would probably just close. Okay, those ones. And anyone close them. Yeah, anyone. Okay, okay. So, I'll make a note in the description that the creation of that ticket closed, whatever and whatever whatever just just say so I replaced with this one. Yeah, so probably should probably go through all these old issues and probably close them all if they're no longer actually affect anything given so much changed from basically 2020 to now. Yeah. So, I don't think that these epics or these issues are much of use anymore, unless they actually refer to something that is still in use. Well, should I just revise that epic. Like, I just, I just discovered this epic I didn't know about that before. I intentionally didn't link the epic. Quickly reading over it. We don't, we don't no longer have any green balls or red balls or anything like that so. Yeah, this is not up to date. And I'll edit it. No, I guess personally I would just create new issues and then if you've got time close these issues as well. But I would focus on new action of all issues. Fair enough. Priority minor. Okay, that's all I've got on that. Yeah, thanks. Does anyone else have anything to add to the agenda. No. No. Okay. It's basically the same agenda from last week's remarks meeting because I don't have to add anything either. So, I think that that it's today. Okay. So, um, before the end of that fight, then I will stop the recording.