Live Session (2026)

There we go. Welcome back to this week's Chess Academy course. This is week number four, if I am not mistaken. And today is all about site structure and page structure, which is a very important topic as you can imagine. Um I mean you already went through tutorial videos so I I I guess I made it clear that it's important because like this is the content that people actually like read and like interact with and like orient themselves in. So yeah I wanted to ask if there are any questions about the the videos that that I posted, anything that That we need to talk about from that any questions that came up. Going going on. Okay. Um doesn't look like it. If you have any questions, you know, you can always like interrupt. or put it into chat or whatever. Yeah, I want to show a little bit about like page structure in practice. And this is also an opportunity. Like if you have a website that I should look at for page structure. structure, you know, you can ask me that as well. Um this is as always the attempt to make this like you know interactive and like show you some of the different different things that that we can do. Um yeah, gonna share my screen. There we go. So this is the Way website which I helped create so I you know I know my way around a little bit But I want you to show a couple of things that we can do. So first I did so this is the Vivaldi browser, so it's not not polypain because I want to show you a little bit of like what other different tools can do. And especially some of the book markets. We already talked about book markets last time we talked but I want to show some more and let me show the bookmarks bar. There it is. Oh it still has the stuff from last time in it That's not what I want to do. Delete, delete, delete Perfect. So one of the things you know is landmarks of course. So if we go here and go to landmarks, not landmans, landmarks. We can get this navigate like a screen reader user tool. I thought there was another one that was specifically for landmarks, but not here. But here in Paul J. Addams Bookmarket. collection there actually is one that is for landmarks landmarks bookmarked we drag that up and now we have it in here as well and then there is also Andy which is our accessibility name and description inspector as it is officially called and it's also a wonderful bookmarklet that we can use so we track them all up here and now we can look at the page structure here on the Way website. So if we click the landmarks bookmarklet we see that we have the navigation here at the top. Then we have a header, we have a navigation inside of that, search inside of that, another navigation, and then we have the main menu here Um and yeah, there are a couple of headers in there that shouldn't be highlighted because they're not real landmarks. Um yeah, and then there is a footer at the bottom, so that's awesome. So you have all your your normal landmarks. now you can see that there are multiple nav elements in here. And I can actually make the window a little bit smaller. I think that's better to see. Multiple navigations in here, like three things and the thing is if you have like three navigations and you don't name them they will be in the list of landmarks and a screen reader will just announce them as like navigation, navigation, navigation, which is not super helpful, right? So what we want to do, we want to name them and they are named on this page. Um but this bookmarklet doesn't show you. So this is one of the big like things that you should like remember. Not every bookmarklet shows not every tool shows every like everything that is important. So if we reload and take the navigate like a screen reader. bookmarklet from letools. com. it is a little bit different, so you get this overlay and it basically shows you what is on the page. So for landmarks you have a nav that is that has the name Skiplink and Language Selector that's are there on the top Then you have a header area, then inside of that you have meta and search, which is a very general and really like bad naming but like it's it's sometimes difficult to like give things a good name. And in these cases like The best thing to do is to make sure that it is a consistent name. Um, you know, even if the person needs to like figure out, okay, what's going on here Um, you know, if on every page it says meta and search is the that menu, then it's not a problem, right? They can explore it and say like, oh yeah, I'm interested in this or I want to skip it all the time And then we have the main navigation. Now, as you can see, we just use main as the accessible name, and navigation comes from the from the landmark from the the structure there. So you don't need to say main navigation because then it would be announced as main navigation navigation, which is like Not super helpful. And then we have the main content, which is basically the rest of the page apart from the footer, and then inside we have different sections that are also named. So that way you actually get a really nice like overview of like what is on the page when you're losing when you're using landmark navigation, but of course ah and it doesn't show the footer for some reason. I wonder if that's just doesn't scroll enough. Oh yeah there it is on the bottom Don't know what's happening there. Huh. Interesting. There it was foot aside. So yeah and then of course screen reader users can also navigate by headings so you get the h1 h2 h3 and so on to the to the bottom of the screen and really gives you like a good high-level overview of like the individual things in there like Landmarks are for the big picture view, like what sections are on the page, and then you have the other view that that you can use yeah, I'm gonna answer the the question in the chat in a second, because it's actually quite interesting but quite complicated. Um Screen readers of course can also navigate by links, so that's nice. and then form controls so you have the search search box here at the top and then you have a missing label button. That's bad. Like who programmed this? I programmed this, but I think it's it's like I think that's wrong thing that happens here, but I now have to look at it inspect. Oh, I think this needs a roll image to actually work. I don't know. Should should work like this too. Um but apparently the bookmarkler doesn't recognize it because it's not not the most standard way to do it. Um So let's bring up the landmarks bookmarkled again. why does it say header? where we had headings as a landmark. Is this a bug or is it intentional? So That there are headers in these sections, that's intentional because when you're using headers in sections and To say it exactly, it's outside of sec like inside of sectioning content. So this is inside of a section this header now is not a landmark for the whole page, but it's just a header for this section. So the idea is that this header here and we can inspect that too. this header which goes around the heading level two, it's actually quite redundant, and should probably shouldn't do that. Um But that this basically now applies to this section here. Um and there's of course using an area labeled by that points at the H2, so it's it doesn't really do anything in this case it's more so you have like a a wrapper maybe also for the Or the subtitle. This is actually not what I'm having here. Yeah, this is the title. Yeah, and there used to be a subtitle here at the top. So to group that, maybe we did use the header. I think that was a dumb idea. And I sh we shouldn't have done it back in the day, but this was also like almost ten years ago. And we thought we would do more with like headers in sections and stuff like that So yeah, it's not not something that I would recommend doing. but it's also not wrong. next question is can't you make that header into an H1? Well it is a H2 already. So it's just like inside, so you have something else to do. Ah I don't even know if we're using it. if if we did use it maybe there was a reason for it I think this is just a thing that shouldn't be there So yeah, what was the reason for having a header? I think it was just styling like here at the top. Maybe let me see inspect Yeah, here we have with heading and a subtitle. And they are basically grouped in the header. So the idea was that you could group something inside of the header. Um these days I would just use div or something like that because it doesn't like It doesn't have any functionality for screen readers or other assistive technology users. So it's basically yeah relatively redundant. Should also not, if we look at the accessibility tree, I think it probably doesn't show up. Oh yeah, it says section header here. This is a new thing that now exists that didn't exist back then. So maybe we're just ahead of our time. Um but basically this if we remove the area labeled by here. basically points to this heading to make this the title of the of the landmark right so if we remove this I think we want to remove it all completely. I think then the new way that this should happen. Yeah. So now we have a generic section here, I don't know why it's generic. Um and then it has section header. Well oh because it's because the This text comes from the bookmarklet, so it's all also in there. Um so it has the section header text heading. and is now labeled by no it's not labeled by because it's not like if if there's no explicit label It doesn't like use that but doesn't basically doesn't say it's a section. So yeah, you don't want to do that. Long talk. This was very confusing, and I'm sorry for that. Like, don't use headings when it's not in the as a banner landmark. So that's that's the what what I recommend. And then don't don't confuse your students like I do. That's I think that's a good good way to to do it. Um there's Andy, which is a really nice tool that now looks a little bit broken. Let's try it again. Yes, this is much better. Now we can scroll. And basically it has these modules like focusable elements, links button structures, color contrast, hidden content and iframes. And structures will also give you like 19 headings You can look at the list of the headings, so that's useful. And it points at the individual things. Ah pretty pretty good the landmarks as well are basically the same thing and you can just hover over the landmark and then get like information which is you know quite quite nice. Um I think it does tries to do a little bit l much in like that little space at the top but to see like okay what are the landmarks and what do I need it's it's pretty pretty neat so yeah I like I like Andy and you can basically also use the arrow key here to go through the individual landmarks. So this is the search form, then you have the navigation. with the ARIA label main and you can also see like what the inner text is if you need that and you can see here what the andy output is. So this is basically like What would a screen reader user say? Well it would say main navigation, right? Yeah, and then you can go through these individual landmarks. It also thinks that these headers are landmarks. Yeah, don't don't look at that. I guess I have to send in a pull request to remove those. Because now they're they're annoying. Um Yeah, so so that those are the tools, some of the tools that I want to show and I sh I showed them last time, right? So I I think they they work very well like here if you look at the Access Lab website which I always like to show it's basically the same thing, it's much more simple Oh it says no landmarks found on page, but that's also not true. Like we do have the nav and now the notification is gone. I don't know what that's about. Um then we have the main here And then we have a footer at the bottom, and that's usually what you would expect, right? Those three fundamental things ahead, navigation, main, and footer. I think we have a navigation here as well. Yes, navigation main. Yeah. And basically because this only has in the header only has the logo and then the rest of the navigation like you don't need to have a header or a banner role right it's totally fine to say like oh this one UI is enough. Especially like screen reader users probably will not often search for the header section, right? they want it to navigate so they go to the navigation directly. Um yeah, it's it's b basically this is like where it's a lot up to you what you think is the best for your specific use case, right? Um What else did I want to show? Oh, I want to go to the before and after demo because of course. Um And there you have, you know, the prototypical thing of like inaccessible stuff. So if we click let's take the headings bookmarklet instead. Headings Where did I put it? I'll put it to the right. Um and then I click on the headings bookmarket. That was the wrong link that I dropped at the top. I didn't sleep well and I think it's noticeable. So this is the install link. We want to drag the U up Do it. You're kidding me today? I have to click on this and then track this up. I dragged the other one up and that worked fine, so I have no idea. There we go. Oh, and of course I overwrote the before and after demo. So if we click headings, we see that only this top heading, which is basically outside of the website is a heading. So none of the actual content here has a heading. And that's obviously problematic because you can't navigate through it. You don't get any information on like what the different sections are and and stuff like that. But if we go to the accessible one and click the headings are we see that it starts with welcome to city lights and then it has like every section has like nice headings here as you would expect them and the and I would ye love to use show you landmarks. but if you look at landmarks there are none because this was developed before there were landmarks like widely available so so it just didn't do it. Um but yeah theoretically you want to have, you know your banner landmark here at the top this would be a good you know because the navigation is here on the left you would say this is the banner you might say like this is navigation that has a accessible name of like quick navigation or quick and and then getting the navigation from the role Then you have the main navigation here on the left, the main here in the center, and then a side maybe on the right, complementary. roll on the right and then you know you have a footer here at the bottom maybe and then you have like all the different landmarks in there as well Yeah, and I think I showed that last time, , when we We were here like if I look into the developer tools and then inspect You basically have these diffs that have no that are not connected to what is underneath them. So heat wave is here and then you have the next one is the n man gets nine months in violin case. So I ha you have the reading order is heat wave linked to temperatures, and then it goes to Men gets nine months in violent case and then you get lack of brains hinders research and it's like basically in Instead of like being heading and then teaser text, it's all the headings and then all the teaser text, which also means that here at the bottom this these story containers are all one after the other. and so, you know, you will read them as a user you will read them one after the other. So you have After three years of effort, city scientists now agree that the primary cause of the 202 2003 heat wave was hot air from our mayor These kinds of crimes need more creative, effective punishments. For example, we could require compulsitory brain donations. Huge drop off in Brainonations due to the great success of slow traffic safe streets policy. So, you know, that's why structure is so important. So so you don't get like stuff like this where you basically like instead of like following the focus order on the page, , or like the reading order that you see visually, , you don't have the same reading order for assistive technologies and you know This is something that I noticed today in a current website. Like, you know, and in this case it was made with like a Wizardic tool, so what you see is what you get. Um and I I can I can probably say that it was Figma and it has like a table at the top and the reading order was First row right column, then first row left column, and then it went to the left column in the bottom row and the right column in the bottom row and then it basically went up the the table and I was like yeah that's not That's not good. Like and it happens so easily in these WYSIWYG editors where you can just move around stuff and they don't follow a logical reading order. So that's a very problematic thing that still happens, and especially if like content creators, people who create websites g have too much power over the order and and look of the websites. Um yeah, so that's Andy. We can look at the Andy here too. It also has the focusable elements thing So I don't think I showed that last time in polypane, but Andy has a similar thing where you press tap order and it will put like numbers on things that can be tapped to so you can see like oh you go one two three four five four and then it goes five six seven 8 probably 9, 10, 11, 12, and then it goes like into the main page, and then you have 13, 14, 15, 16, 17, 18, and so on and so forth. Um and that's the inaccessible version. So even there, like at least you know, you you you can see that the focus order goes like this. and then 22, 23, 24 to the more links. And that's obviously bad. So if we go to the accessible home page and use Andy again then click on tab order we see that the top is the same and then you have 14 15 16 for the button here and then it goes through navig left navigation and then it's 20 and 21 22 23 24 25 and that gives you already like the feeling that you're not going horizontal over the headings and the the teaser text, but you go from the heading to the to the link and that also means that you in addition follow the focus order and follow the reading order usually through this like it's not one hundred percent because it could be shenanigans in the code. Um but for most pages if the focus order makes sense like this you will also not have like a lot of problems with other stuff. Any questions so far while I drink a drink No? Okay. Um yeah, so that's basically Andy and and how it works. Yeah, it has a lot of other things as well, like images links and buttons so you get all the the good stuff yeah there's not a problem here So yeah, it is a really good tool and all these bookmarklets are. But there are also a couple of browser plugins that I want to show you. And let's go to the Access Lab website again. And the first one is the X Core Tool. The Xdev tool, which was very transparent here, so that actually does nothing from the menu here, but is all in the developer tools So we inspect page source. No, that was the wrong thing. directing on the X, yes. Inspect instead of view page source. and then you have here Click this away. You have here the different tools like elements, console, sources, network, performance, memory, application, security And then here there's also Lighthouse Recorder and Xdev tools on the right. And you can move those around like you want to. So if you're doing a lot of accessibility stuff With def with XdevTools you want to put it on the front and then you want to like say, oh, I'm another and start testing and we don't know we don't want to do any pro stuff. Um And then you click on full page scan. That's the only mode you have is a free that's included for free. Um it's also the only thing you really need. The rest is all upsells and like additional things. Um So yeah, I don't I don't don't feel that's super useful, especially just for trying it out and finding things. So here we have like one issue on the Access Lab website. Um To see what that is. Elements must only use permitted ARIA attributes. Ooh, we haven't talked about ARIA yet. But yeah, that's not that's not what we want. Um so yeah, but it's in this case it also doesn't have any impact, I think. but yeah it's a b basic like scan, automated scan, finds about 40% of all accessibility issues. if we go to the The inaccessible before and after demo homepage and we run it. Then we get forty-four issues, which feels much more like along the the right lines. Just note they do have best practices here and you always want to set them to off. The best practices that X dev tools proposals are often misleading and like take a lot of effort for like very little gain so I I think the best thing to do is switch them off and let the let it run in the like basically very strict mode And then you have like, you know, the color contrast issues over here, and then you can like that so three penguins here on the right. This is not enough contrast and even gives you like some like how how you can fix it as well, right? So it's a it's a very good tool. Um also goes into like if you don't have alternative texts, what are your your options? and gives you like an option like selected options of what you what you want to do So that's XDevTools and it's a 100% automated tool, so you can there's not a lot you can do, at least not with out paying for it. Like they do have these guided tests. Um and like also AI stuff, which is notoriously bad at accessibility, unfortunately. Um And then there's also accessibility in s insights for web. Um and that's basically a tool by Microsoft that helps you with doing manual tests that are assisted by automated tests. So in this case, like What you want to do is like a fast pass or quick assess or an assessment or ad hoc tools. So ad hoc tools are basically you're not using accessibility insights at all. That's the way you can like check for color. Like it has this gray filter on it, which is pretty nice. Um it you can you can show the headings, you know this is not this is all n not new, you already know that. Can so show accessible names for things it can show things that need review. tap stops So this would put like little nubbins in there. Landmarks of course, we talked about those. Automated checks. basically checks all of the automated testable stuff. So it's it's a really good tool and you can use these either individually or like something that might be interesting for when you're doing your your exam or like other stuff or you're doing something for work. You can click on like let's say quick access quick assess, which is completely a different thing. And it opens a new window I will share now with you too. And then that basically gives you like a step-by-step Quick access thing, so you have automated checks and we run that again on the page and it will say oh 33 image alt things, one select name, one HTML haslang, and stuff like that. Um Then you can click to the second and it says keyboard navigation and basically asks you does keyboard navigation work? So this is something that you need to test and it gives you like a how-to-test guide, which is really nice You can switch the helper off or on. Now I have it switched on. And basically what we see is that we don't see the helper. Which is weird. Oh no, I think you tap and then it yeah, then it puts the the things on there, like I thought they were numbered, but maybe that's not the thing. And now we see that like the focus gets blurred and that like basically removes the the little like circle that indicates of where we're tabbing. of course at the bottom it's Pretty straightforward. So yeah, it's a very very nice tool so you know that like things are tempable. And in this case, I would say this is a fail because we we know that there is an issue there Then you click on link purpose and you can run through that and and basically say, oh, this link info that's a pass. To pass this pass and this fail. It's very detailed like that. I think it's probably useful when you start out. but yeah, it's it's a good thing to guide you through. question When will X dev tools offer WCHAC 2. 2 AA? They already do. Um it just showed WCHAC 2. 1 double A in there because I think that specific rule was introduced with WCEC 2. 1. I don't know if 2. 2 if there are any like automated testable rules Um I don't have the list of of of tests that X tests in my head, unfortunately. but I think they d already cover some some WickHack 2. 2 stuff especially probably target size. So we can quick look at the X core So Xcore is basically the command line version of the Xdev tools. So if you want to run it in your CDCI integration, you can use this. And and they have all the tests in here as well. under I would say under test right act rules Um yeah, there are all the tests and and you can basically like look at them. They're in JavaScript format and basically shows what you can do. So in this case, to do I don't know. Don't actually know how this works because I haven't looked at this for many years. like behind the behind the scenes. But it's it's pretty well documented and everything. So if you want to like write your own tests that you run with this. You can actually do that and it is pretty pretty good like that. Um how could we see if there's wicked two puntu stuff? Wicked to two That work? No, that only looked at the file names. Let's try this. Yeah, here's get target size is is one of the the requirements and there are wickek 2. 2 rules. So it's just like they just show like basically where it gets introduced in in WCAG Which, you know, is a decision I think I would probably mostly put both tags in, but that's not how they roll And who am I to like question anything? Um but yeah, it's it's a really good tool, , and I especially like that their goal is No what is it how do they say it? zero false positives. So you if the something So if you have an accessibility issue, it will say like yeah this is an accessibility issue but it will not it it will not do like false alarms or something like that. So that's it's really good. And false positives are of course failures in in WCHG. Like it's it's a little bit like top of of like it's topsy turvy Yeah, I really, really like those tools. Um Anything else? What did I show for oh for page structure? I like to to talk about page structure on basis of Wikipedia a lot, , because I think it's actually pretty nice that they have that they have such a good like organization in there like the actual text so let's get to something that is a little bit more complicated here So so you have your table of contents which is which is really nice so you can actually skip through the the page. So If you're not using screen reader, you can't go by headings, right? Even if you are using the keyboard. And this way you have the a way to go to the different pages. Um and then they have of course a lot of links inside of the paragraphs which is pretty cool. and these are tables on the right. at least they should be. Last time I looked they were. Let's do right click, developer tools inspect. And then we see yes, these are tables. So there's a clear association between like the table heading and the the content in there and it makes all sense in you know if you inline it basically then yeah, it has a lot of headings, of course, like premise, that's a heading, history is a heading and here there are a couple of quotes. I don't think they are like properly block quotes Because that's a little bit dicey, I think, in most. Oh, they actually are. That's pretty cool. So they are block quotes. Let's scroll where they are. Here they are. And then they use a paragraph inside of the block quote for the actual quote, , and and a div at the at the bottom to basically like indicate who the author is of that block quote. So that's actually pretty good. And yeah, so so that gives everything a structure. It's very clear like where does a quote start you know both visually as well as like in the when you're using a screen reader that's awesome then yeah, here you have like a a panel. And yeah, if you have more headings in there. is there anything else that I want to show? Yeah, yeah, yeah. You just have a map. I think that probably doesn't have like a good text alternative because it should basically say, you know, all of the world. But China and Greenland and the Antarctic. So It's fun. And then you know you get these like different different subtitles and it's all very clear like if you're using a screen reader to go through it Um pretty nice. No, there's nothing nothing in this right side appearance thing that I want to use. Um yeah, and so so that's basically like the archetypal like what web structure can look like. And of course this is not like marketing and like making sure it looks good necessarily but just like purely what is the content of the page and you can see that For these types of things they're using real tables, so they really nicely work out or or like at least for screen reader user it's very easy to know what belongs to you. Um it's always a question do you really need a table here? Would a list or a nested list not work as well because you're usually not going to like compare things. right. So for example, like the episode counts, that's just a data point. But you wouldn't say like, oh Um I need to compare this to this to this. You know, it's not like you have a spreadsheet or something like that. so yeah, I don't I don't know. Um But it's certainly pretty nice. Um anything else yeah, I mean one of the things is that Wikipedia has a lot of footnotes, so you have the footnotes here at the bottom. And you can like tap through them and will basically go to the top where the footnote was used. So if you only have like one reference, you press return You go back to where you are. I don't know where that would be. Oh, there at the top right. And then you press on the footnote and you jump back so you can you know what's going on And then if it's used twice the reference, then you have like these A and B superseded sections that you can use. So this would be back here and then you go to B and this is like here at the bottom. This E and then you go you go back down. So it really helps you to like to navigate through and that's like you know might not be the most useful thing to do when you are just writing marketing copy or doing like presentational more presentational stuff but like if you're writing an article or if you if you have other needs in in terms of like annotations and stuff, this is this is a really useful way to do it. and Wikipedia does a lot of things, right? Not all of the things because who does? Um but this is this is pretty good. Um Yeah, these are basic expand collapse things. Not a not a big deal. -huh. Anything else. Yeah, they use a lot of lists, of course. Um and we can look at Andi for this which This uses CSP of course, so it blocks in putting JavaScript inside of the page. So this is one of the big oh it's good that this happens Um because this is something that can happen with the book marklets. Like if I click on the landmarks bookmarklet, oh that actually w works. Um because it inserts the JavaScript directly on the page or the the CSS in this case. But if you put JavaScript and you point at other URLs like here, this goes to SSA. gov. Um it will often block this and not show up because of security Right, so you don't have something from another website that can just get like your data or anything in there. So that's that's a goal, that's why we have these client-side scripting things that sometimes happen. Um Let's say some some things do only things on the site, so they basically put the JavaScript directly on the site. but some like Andy basically say like oh take the JavaScript from this third party website and then it doesn't work. Um and if you're using a browser plugin like X or or the accessibility insights That's usually not a problem. So if we go to inspect element and then run the xdev tools It takes a while because it's a pretty complex page. But it should just work. Or maybe it doesn't. You can do it You cannot do it. A way to stop this Nope. Let's try a reload here It does not like the big page and now it's even frozen. So that's good. Um It might be more of a browser issue, to be honest. So let's close the tab and then try it again. Right not to be on the s citation. Oh yeah, it's right click Used to be when you click on the icon it X devTools also did something, but that's not the case anymore. Trying it again, analyzing the page It doesn't look good. It's interesting. I leave it in in the background and I'm gonna start polypain and get you over there to the There we go. This is still running. Um and PolyPane does have X built in. If I click on accessibility here. Hello? And then analyze page for accessibility issues. This should also take a few moments, so I'm just trying to benchmark If this is going if any one of those is going quicker. It doesn't really look like this. I mean yeah, it's a fairly substantial page, but it's also like Not the most thing, but here we go. Like oh this found seventy-seven issues. Um Oh yeah, yeah, I don't know why it says we cag 2. 1AA here. It should also find triple A things. I don't know if that's A settings thing? It shouldn't. Oh, it is. Huh. See You owe this is this is why there are no like bad questions. there are only only good questions because now I learned that I should have said this before And then it even says a hundred and nine issues, which is quite a lot of issues. Um and it's a lot of contrast. alternative texts, links that don't have ta discernible text. let's see what that is. Yeah, it's basically links with images inside of them. And then there are touch targets that need to be bigger. So that's the WCHAC 2. 2 contribution here. Can I jump to what is affected? Yeah, I can inspect element. Yeah, but there's this is no no, that doesn't apply. So this this would be a false negative. Um, so they they said they don't have false positives, so they don't show you an error when there is no error. Um Or they d they don't show show you no error when there is an error, but like this is like, yeah, this is not 24 pixels high, but it also doesn't need to be because it's all text. next to each other. I don't I don't think that applies. Um but it's difficult to automatically test. And the same goes for here in polypane where it finds all these as well. But I think they also don't have the Wik 2. 2 things in there. So I have to ask why that is Um yeah. That's why you always have to double check your results for these tools. Like sometimes they just make like the best. assumption for for things but but for this I would not fail a website for because they're in list elements and I think that's that's fine. So Yeah, dort polypane Showed the other tools. Yeah, I think that's about all I wanted to show you today. Like relatively short thing, but I also think like Page structure and and site structure is not like the most in-depth topic. So if you have any questions, speak up now. And if not, I'm going to give you back like an hour of your time, which is awesome. and the videos for next week should be online and I also made sure to to record this locally. So If if Zoom plays nice with me, we should have the recording online quicker than last time. sorry for the delay back then That wasn't intentional. yeah. And thank you very much for attending. Take care. See you around. Thank you, Eric. Bye. Bye. Thank you. Bye.