Live Session (2026-27)

som Erik och Hampus alldeles strax ska berätta lite mer om. Stina heter jag och jag jobbar på Kös Akademi. Det är jag som har hållit i spakarna lite och skickat ut informationsbrev till er och bjudit in er till den här Kayabi-plattformen.

Det var jättebra att ni sa att ni inte har tillgång till Communityt, för det måste ni ha. Men jag ska alldeles strax presentera Anna, som är verksamhetschef på Kös Akademi. Men innan det vill jag bara säga att Kajabi är det enda som ni behöver.

Där kommer allt material att läggas ut, studiematerial, alla inspelningar, men också live-sessioner som vi sitter i just nu. Och sen är tanken att ni också ska kunna kommunicera med varandra. Det gick tidigare inte, men då ska jag se till att ordna det.

Vi är helt nya inför Kajabi, så det kan vara en del saker som vi behöver se till att åtgärda. Men jag ska se till att det funkar så fort som möjligt. För där hade jag nämligen skrivit ett meddelande som jag drar här nu också, så att ni vet om det.

Om det är så att ni ska ansöka om CSN, så tar ni de datumen som är angett i det här informationsbrevet. Ska vi se, var det någon som annat frågade?

Den kopplar på om jag skulle prata, men inte på att plocka upp ljudet av någon anledning. Och sen har den börjat, så jag kan inte koncentrera mig på det. Du får nästan gå ner.

Jaha,

det är någon som har på sin...

-Skört, jag har mjutat. -Toppen,

tack. Jag tänkte att jag kan lägga en bra app. Då tar ni de datumen, alltså gårdagens datum, alltså 12 oktober till den 12 februari.

Bryr er inte om att det är ett juluppehåll, vecka 52, vecka 53 och vecka 1, utan ange hela perioden. Även om det inte kommer att vara några lektioner under de tre veckorna så kommer det ändå vara lite självstudier. Så ta hela perioden.

Och sen är det 25 yrkeshögskolepoäng som man ska ange om man ska ansöka till CSN. Så, jag är ofta vän av ordning och CSN och myndighet och allt sånt där. Och nu har jag det dragit det tråkiga.

Så då tänker jag att jag släpper över... ...ger mikrofonen över till verksamhetschefen. Anna, varsågod.

Tack snälla, Stina. Hör ni, till en början, varmt välkomna till den här Upskill-kursen. Det är jättekul att se så många här.

Jag heter Anna Tharnberg och jobbar som verksamhetschef på Chairs Academy. Och Chairs Academy är ju ett uppbildningsbolag, helt enkelt, och en yrkeshögskola. Dels i vårt utbud har vi tvååriga yrkeshögskolor, IH-program helt enkelt.

Och sen har vi också kurser. Och en av dem har ju ni signat upp på nu. Och tack för att ni har gjort det här aktiva valet att välja oss i den uppsjö av utbud som finns där ute.

Och lite kort bara då, Vissa av er kanske känner till bolaget Chas Visual, som är ett utbildningskonsultingbolag. Är det någon som har talat om Chas Visual eller kanske jobbat för dem tidigare? Nej. Det är i alla fall en del av vår ägarstruktur.

Jag tänkte bara nämna det, för ofta är det folk som har konsultat för dem tidigare eller varit kund eller underleverantör. Jag tänkte bara nämna dem. Jag ska inte prata så jättemycket, utan jag är här för att välkomna er.

Jag hoppas att ni får en fantastisk upplevelse de kommande 15 veckorna. Och att allting går smidigt för er, framför allt i Kajabi, som är den här lärplattformen som faktiskt är ny för oss också här på Chess Academy. Är det någon som har några frågor innan vi släpper över till utbildarna, Hampus och Erik?

Det är lite läbbigt att ställa frågor i början. Mitt namn är Anna Ternberg. Har ni frågor hittar ni min mejl och telefonnummer på Tjänst Academy.

Det är bara att höra av er om ni undrar över nånting. Ni kanske är nyfikna på våra IH-program. Eller på våra andra Upskill-kurser.

Vi har sex stycken igång nu som vi börjar med här i oktober. De kommande veckorna. Så varmt välkomna till den här kursen.

Jag hoppas att ni får en grym upplevelse och att ni lär er massor med nya saker. Och se till också... Jag brukar slå ett extra slag för att nätverka lite i den här gruppen som ni har nu.

Jag är helt övertygad om att ni alla sitter på otroliga erfarenheter från tidigare yrkesliv eller det yrkesliv ni befinner er i just nu. Satsa också till att knyta lite nya kontakter. Det kan ju vara ett väldigt bra tillfälle, helt enkelt.

Jag tycker alltid att det känns lite märkligt när jag säger "one way communication". Jag är lite old school, så jag vill ju veta vilka ni är. Jag skulle ju bli jätteglad om ni kunde presentera er, men det ska ni få göra lite senare och vi har inte riktigt den tiden i dag att göra det.

Men så fint att i alla fall se era ansikten på en skärm här nu. Och jag hoppas att ni får en grymt bra kurs. Bon voyage, som man säger i Frankrike.

Jättekul att träffa er, hörrni. Jag lämnar er nu och lämnar över till Haukus.

Ja, men härligt. Tack, Anna och Stina. Och hej på er alla som är här på den här kursen.

Kul att se er, några bekanta ansikten, några som jag eller många inte känner sedan tidigare. Men Hampus heter jag och jag är en av utbildarna idag. Och jag som ni hör pratar svenska men den här kursen kommer vi ha både på en del pass på svenska och en del på engelska.

Och idag så kommer jag eftersom vi både både Erik och jag här så kommer jag switcha över till engelska så får ni dras med min lite halvknagliga engelska det här passet. Men alla andra pass när det bara är mig ni kör med så kommer det vara på svenska. But on that topic, switching to English and yeah, again, welcome to everyone.

Maybe I should say something about my cap as well. I have my VKAC cap on the web content accessibility guidelines just for this occasion here. However, it might be a bit confusing because I'm not the one who's going to talk most about the nitty gritty VKAC stuff Because that's my colleague, Eric in Germany, the Weka guru.

Introduce yourself.

All right. Yeah, so I'm Eric Eggert. I am based in Germany.

That's all correct. So full marks for you, Hampus. And yeah, I worked with W3C for seven years, or about seven years, spent like 32.

And mainly on web content accessibility guidelines, educational stuff. So things like the tutorials, which we will be looking like a lot over this course. And other educational materials.

And also helping to make the standard better. Hopefully worked out. And yeah.

And I'm going to talk a lot about standards and interpretation. And how to make sure that, like, you know, when you are asked to do, like, an accessibility review, you're making the decision that aligns with, like, how the standard is written. Instead of, like, just guessing.

Because, like, everyone can guess. But it's, you know, sometimes difficult to know if something is, like, really an accessibility barrier or it's just, like, something that you need to look at and that's more a usability thing and needs to be improved in like a different process. So yeah, that's my role.

And yeah, happy to have you all here and looking forward for the next three months.

Yep. And I think it's like the sixth or seventh time we have this course. So hopefully we We've kind of been able to tweak it and get the material as interesting and as good as possible.

As Stina mentioned, the new thing for us is this platform, Kayabi. And there might be some hiccups in the beginning, but we'll sort them out as we go. But yeah, have some patience with us regarding that.

We'll also, during the course, I think, look at maybe the accessibility of the platform to, because I'm hoping to, at the end of the course, be able to kind of email Kayabi and be like, "Hey, we had this accessibility course in your platform and these are some things you can tweak." We found a couple already, but yeah, hopefully they can improve us after this course.

That would be nice.

It would be nice. I guess it's often get pleasantly surprised by like if you communicate in a good way around around the kind of improvements that can be made. Many companies want to improve.

Anyway, I'm going to share some slides so that we keep on track and introduce this course. Let me do that. You're also going to get to introduce yourselves in the chat shortly so So, because we're also interested in who you all are and what you work with and why you want to take this course and so on.

But yeah, sharing the intro slides. Not at the end, there we go. And maybe I'll put you guys on another screen over here so I can see you.

Thanks for having your webcams on. That makes it easier for us to kind of see or if you're really interested in what we're talking about. You should also note that there is a raise hand function if you want to use that to kind of call on our attention or you can just unmute and talk if you wish.

There's also chat function here in the interface. But yeah, welcome to this course. We are in this session doing an intro to accessibility in the next like 15 weeks or so, we'll have a theme each week and you'll get the sessions beforehand to watch and then we'll kind of meet and do Q and A's and practice and do exercises and stuff.

We'll talk about that more shortly. But on the screen, you see two images to the right on the slide. And yeah, maybe I'll do a short quiz here.

And if someone knows like what the top right thing is, there's like under the keyboard, there's this black bar looking thing with white dots and blue buttons. Anyone know what that's?

I know what it is.

Yeah, okay, Eric. But anyone else know what it is or what it's for? Yeah, let's see.

Guessing for blind people?

Yeah, guessing for blind people. Cool, yeah, correct. It's something used by blind people.

"Skärmläsare" is someone said with a question mark. It's not the screen reader per se, but it will communicate the same thing as the screen reader us. So you can see like the person seems to be kind of touching the white small dots there.

So that's braille or punkt skrift in Swedish. Yeah. And it's called a refreshable braille display in English or a punkt skrift display in Swedish.

So basically it connects to your device. It could be your computer like here, but it could also be your phone or tablet or whatnot. and TV for instance and you can read with your fingers what's on on the screen so maybe you'd go to Chess Academy site and it would say welcome to Chess Academy heading level one for instance then you'll press some button and move forward and you'll read the next line or next heading or jump to an image or similar and then with the blue buttons the big blue buttons you can type using using Braille.

So that's pretty cool. We're going to talk about how to make interfaces that work well with Braille displays and screen readers and other assistive technologies.

Maybe it's good to say that Braille displays is basically a combined keyboard, as you said, like you can type in Braille, like there's specific Braille things that you do with the the four fingers, but it's also a display. So when you use your screen reader on your computer, it can translate that not only into audio output, which is usually what you think about when you think screen reader, but it can also like communicate with the braille display and then say like, you know, just put, puts it out into the braille display and the refreshable comes from like, it's not just static, but it refreshes with like, you know, each line or something like that. So just for a little bit of context.

Good point. Good point. I was at like Accessibility Scotland, the conference and I was speaking at that conference and the guy before me had one of these, a bit smaller one, but like as a necklace around himself.

So when he switched slide, he could kind of read what was on the slide using his hands on this kind of a braille display that he had as a necklace, which I thought was pretty cool. Some people have like a headphone or AirPod or something in their ear and kind of listen what's on. But yeah, he felt that was smoothest.

Can use them in a variety of ways. The bottom right image here is a person with a motor impairment. And then you usually see things like joysticks.

Here he has a joystick by his chin and sensors. Maybe this one can sense his eye movements head movements or things like that. And it's also very awesome how technology can make people much more independent and you'll see how people can communicate, run businesses and so on just using small movements they have in their, let's say, eyes or chin or whatnot.

So technology is a big enabler and there's lots of great things that have come with the kind of technological advancements, but we also have a lot of problems with inaccessible interfaces out there that make it less efficient or even some interfaces might not be accessible at all to some users. And that's what we're here to start identifying and fixing and so on. But yeah we'll start this course by saying hello to all of you humans.

But we've had some issues with robots joining our education so we'll just start off with a simple quiz to make sure you're all not faking you're humans. So just like open the chat and please write which squares here show road signs so that we can kind of move on with the course here. So in the chat just write which squares show road signs please.

Find the chat. Can we get some Answers none, no, no one, zero, null. Yeah, this is getting suspicious, Eric.

Maybe we only have AI bots here or something. Luckily we have another alternative which is common with these types of puzzles. You don't seem to be able to kind of visually understand this image.

So you can take an audio version. you can press this headphone. So we'll take an audio version.

It's not one that we have made up. It's one we've kind of copied from Google, I think. So just write the following message in the chat, please.

I'm hoping I'm sharing sound. There should be sound here. You'll hear it twice to make sure that it's clear to you.

Oh no. Yeah, there we go. All right. So just, yeah, please just write that message.

You heard it twice.

As a human myself, I feel very confident.

All right, yeah, someone had an F too much at the end there. Darn it. Now, of course, you're welcome to this course anyway.

We're making a point here of these CAPTCHAs, which they are called CAPTCHAs. And Daniel, who is a colleague of ours, he'll join the session and explain why he hates CAPTCHAs more than you do. And it's annoying for anyone.

It kills kind of conversions. Viewer people will buy stuff or register or sign up if you have a cap job. But from an accessibility standpoint, it's going to be even more frustrating and annoying, as you can imagine.

Daniel has 1% vision. We can hint about that. Also just saying my six-year-old is at home playing some educational game here at the side and I think he's going to be fine and have cats that are meowing all the time. It's cognitive overload for me.

The educational game of metal drums.

No, hopefully not.

All right,

so but moving on we have this session at a glance. We're gonna do an intro to accessibility and we're gonna talk about what accessibility is and why it's important. Get to know each other a bit at least through the chat. Talk about the core structure and then Eric, you will do a fly over of VK, which you will deep then in like week two, I think.

Week three.

Week three. All right, Eric, can you start by introducing yourself a bit more deeply?

Even more. I think people are already sick of me talking about myself. So yeah, I started out as a web developer and for me, I still think that's the best baseline for doing accessibility work.

But we know that not everyone here is a developer. But we usually have a very broad spectrum of people attending. Which is awesome.

Because accessibility is in every like section, in every sector that, you know, that we go and we talk mostly about web development because that's like our thing. But also for app development and other things. Like accessibility needs to be thought of at every step of the way.

So while my background is developing, I hope we can structure this. I think Compass is better than I in that, to allow you to get an insight into accessibility with any background. But I'm a web developer.

If you don't understand something, if I use some language that you think is too complicated, you know, just call me out. I'm happy to explain stuff again. That's what we accessibility people do anyway, always.

When I got into web standards, that was my first array into accessibility was via web standards. So I joined HTML5 working group when that was a thing. I worked on microformats a little bit, like all of these nice early web standards in the early 2000s, something around that.

And then in 2008, I started with like really focusing in on accessibility. I lived in Vienna, in Austria, back in the day. And they had a lovely community of accessibility people there.

Like a lot of disabled people of like every variety. And so I felt very welcome and very included there. And then in 2010, I moved back to Germany.

And I won the golden prize, the golden bee, as it was called, for in a community project. for making a website accessible. So we were like, I want to say seven or eight people.

And we worked together and everyone had their specialty. And then we made a really good website that was really nice. And then three years later, they tore it down because it wasn't, I don't know, they didn't have taste, I guess.

That's also when I started my little web Web consultancy, focus on accessibility and in 2013 I started to work with the W3C's web accessibility initiative. And those are the people doing the web content accessibility guidelines, WCAG. And yeah.

Created educational material. We will work a lot with the tutorials. You will see the quick reference, which is an awesome way to like pare down WCAG into what you really need at that time.

So we will look at that. And I had the, you know, amazing chance to work at W3C on all those like very interesting projects that also gave me the superpower, like being bitten by a spider and shooting webs. That's not something I can do.

That's not what World Wide Web, despite the name, is doing for you. But the superpower is actually that you can ask me about any resource on W3C.org, or W3.org, and I probably can pinpoint it to you in, like, less than two minutes, which is, like, it's an amazing superpower. It's very much more niche than shooting spider webs, but it's useful.

And then I worked with Knowbility. They basically split some of my time to W3C, which I was very thankful. And yeah, and I worked with them.

And they are a US nonprofit. So I got to learn all the ins and outs of the American market and like, you know, how does it look when like the city of Los Angeles gets sued and stuff like that. And that was a lot of fun, but also like a lot of time difference.

So I was very glad when I found X's Lab in 2022. And that's, you know, where I got to know Hampus. And he wrote me into doing this.

So that's basically what's going on. And yeah. And we're doing all the things at Access Lab that accessibility companies do.

Audits, training, education, you know, specific coaching, all of the things. And this is basically part of our community outreach, helping to like, you know, create the accessibility people of the next generation. And also like making sure that a lot of people just have like the basic understanding of accessibility that is so often missing.

Yeah. And that's me.

Perfect. will get to know you better the next coming months as well.

Yeah, you learn to hate me. Learn to, hopefully, appreciate what I have to say.

You're very good at the nitty gritty and very charming and a good teacher. That's a good combination, I think.

You always say that.

Yeah, I do, I do. It's true, it's true. All right, so me, Hampus, here an image of me carrying my kid he was not six years old, but maybe, I don't know, six weeks old.

And becoming a parent, realizing like, "Wow, you've got a lot of accessibility barriers that come with it." For instance, you have like motor impairments. A large part of the day, you're tired and make more mistakes all the time.

And you're interrupted constantly. I need ramps and door openers and stuff when I'm out and about and subtitles when I put the kid to sleep, etc. So all this to say like accessibility will be something that doesn't just benefit people with permanent disabilities but people with temporary ones or contextual ones as well. But yeah I've been in the accessibility space for I guess my entire career since 2012 after having gone to KTH studying computer science and getting to learn nothing about accessibility for five years even though I was like focused on human computer interaction which is interesting in itself like why why there's so little in higher education on this topic but yeah this course might be one of the puzzle pieces solving solving that hopefully I also run a meetup together with a bunch of other people at the Stockholm Accessibility Meetup, T12T, you might have heard of it.

If you haven't, it's a great community, just like Erik, you mentioned Vienna, right, having a good accessibility community, Stockholm, and I think Malmö now has started one as well. So there are a bunch of communities around this called T12T. why is it called T12T and why do you sometimes see A11Y and some of these abbreviations. We'll talk about that shortly but there are lots of abbreviations in accessibility which is strange because abbreviations are not that accessible in themselves.

We'll talk more about the T12T things shortly. I also want to brag I have some certifications and it's not just about bragging it's to say that you guys after having taken this course will be well on your way if you want to certify yourself so there's this organization called IAAP or IAAP that have accessibility certifications web accessibility specialist certified professional accessibility core competencies, accessible document specialist and so on. And if you want to know more about those and kind of what you need to maybe complement this course with, then you can talk to me during the course.

I'm also one of the co-founders of AccessLab, like Eric mentioned, we do all the accessibility related stuff, user test, I user test a lot as well. And since a couple of months Our previous CEO had a kid that's about that big now. As in the photo, so I've taken on the CEO role, vd-rollen as well.

But we're a small company, I like doing educations and being out and about with clients. So trying to keep the CEO stuff to a minimum. Alltså, nu vet ni oss lite mer.

Vi kommer försöka att lära er lite bättre genom några frågor i chatten. Så jag slutar delning och jag frågar några frågor genom chatten. So, yep, please bring up the chat.

I'll ask the question and paste it in the chat as well. So beginning with what's your role and workplace, for instance, UX designer, Ving, or developer between jobs or yeah, whatnot. So there you go.

Let's write some answers in the chat.

Some people have been trapped in the chat. I have read.

Yeah, I saw that too.

I couldn't get back. I hope you can still hear us. I mean, that would be nice. If not, enjoy your life in the chat, please.

It makes it more important for us to kind of explain visually what's on the slides and not assume people see it, which we try and do anyway. All right.

We have to transcribe everything.

What do we have? So lots of UX designers from Sphinx, Web Bureau, Concede, we have Project Manager, Mirror, Product Owner, Landshypotek, BIM Manager, cool. UX Designer, Developer, Frontend Developer, Frontend, Frontend, UX, Web Developer, Coop, Earth People, Advanza, newly-examinated Fullstack Developer, cool.

Kommunikationsledare, KTH, utvecklare, SBAB, QA, ingenjör, konstdirektör, framtidsutvecklare, UX/UX, framtids UX /UX, så det verkar som en ganska kommunerad del med många utvecklare, många designare och sedan QA och som management roll och så vidare och kommunikation Utvecklingsenheten, habilitering, Region Skåne, det är fint. Jag glömde att nämna att du kan ställa frågor i svenska om du vill Cool, vi har en bra möjlighet att hoppas att vi får lära oss varandra mer under kursen we're going to talk about an optional but appreciated workshop that we'll have in a couple of weeks in Stockholm that I encourage people to try and get to if you have the opportunity Thank you, I'll ask the second of three questions and no I didn't manage to copy it correctly. But it's have you worked with accessibility previously?

And for instance, you can answer no, barely anything, just a little bit, a lot. We'll see.

I think it's always interesting when we have these different people from different places that makes it super easy, you know, because you don't have any, like, and I say that all the time. Like, there are no silly questions or there are no dumb questions. You can always ask anything.

This is a complicated topic. Your job might not have concentrated on it. It looks like a lot of people have a little bit of experience, which is awesome.

But some things are also like unlearning and learning how a good approach is for certain questions. And so if you do something in a certain way, feel free to say, hey, I do this and that way. And what do you think about that approach?

And we will probably say, yeah, that's also a good way to work. Right? There's never this one, or rarely this one answer that is like perfect for everyone.

Nice. Nice. Yeah.

So kind of a split with most people, I think saying they've worked with it a little bit. Some people saying barely anything and that's completely fine. And some people saying a lot or in periods I've done it a lot or so on. So I think previous courses we've been At least no one has come and shouted at us being like, "Oh, it didn't give me anything because I already knew it all."

And no one has said like, "Oh, it was too hard, too difficult. I didn't understand a thing." So I think we have something for everyone.

It feels like if you have done this a lot previously, then do come with your own kind of perspectives on things things and share what you've done in the past and maybe some concrete examples and stuff or ask your in-depth questions and that's been kind of appreciated in previous sessions as well. Yeah, everyone is welcome.

And because it's asynchronous, like if you see something and you say like, oh, I already know this, I feel very comfortable, you know, feel free to skip it. that's totally fine. We don't see what you look at, right?

So feel free to say, "Oh, I think I feel comfortable about that." But you might find some nuggets or some approaches that might be new and that can always be useful. I do that all the time, especially when I work with younger colleagues and they come like, "Oh, I found this new tool." And I'm like, "I've never seen this."

and then I go like, yeah, now I've learned something, you know, so it's always nice to learn.

Nice. All right, perfect. Final question.

What are your hopes for this course? And again, you can write in Swedish if you wish to write in Swedish. I'll translate.

Hopes and dreams. I had them too.

All right, Michaela is first saying deepen my knowledge. Please sort of become an accessibility specialist Amelia. Yeah I think that's one of the bra saker om detta område eller det är trögt men jag tror att det är bra för dig att nivån är generellt ganska låg ute i mellan människor som arbetar med IT på accessibilitet så du blir en slags expert eller specialist ganska snabbt.

Okej, vad har vi mer? Lär dig hur du kan audita eller tillgänglighetsgranska Some. Great.

Yeah, we'll focus a lot on that. Feel confident in accessibility. Getting a mindset, finding a way of working with it.

Perfect. We're going to talk a lot about ways of working and creating an accessibility culture and that sort of thing. To know enough to be able to work it confidently.

Yeah, similar. Have a good foundation to stand on. Maybe getting some tools to convince others to make changes.

Yeah, tools in the form of arguments and stuff and we'll do some concrete tools to do the audits and reviews as well. Learn more, get more in-depth, accessibility means to work with, yeah, understanding and updated information. Yeah, there's a lot of things going on in the accessibility space and I know Erik for instance you have like yeah some stuff on the WCAG 2.2 guidelines which is not new but it's a new in a form sense that legal documents will start using those shortly.

So yeah we'll be doing some of that. Creating accessible website feel more confident everyday work deepen knowledge nice overview how to do an accessibility audit in 2026. Yeah not much has changed but you can maybe be more efficient in in doing them with some tools accessibility how I can use it to my work deeper knowledge yeah yeah just reading through if there's anything new receive answers to my questions based on practical hands-on experience experience yeah and we're gonna mention this shortly that apart from the videos you're gonna get and the sessions that we have together, there are also bookable one-on-one sessions, which you can use if you want to show something that you're working on and like, yeah, I thought about doing this.

Is that the right way forward? And so on. So you'll have that opportunity.

Yeah, I think the format that we have is like, especially for the people who say like, oh, I have some knowledge, I have like deep knowledge. I think our format is so, the good thing that I've heard from people who did this before, this is not like, you know, oh, we are so great, but we are. But this is what we hear is that, you know, we try to manage that people can get to a new level if they want to, but also can get a better foundation at the level where they are if that's their goal, right?

I mean, there will be stuff, especially towards the end, that's very technical, very in depth, where for some of you, you will say, like, oh, this is something that I need to have heard of, but I don't need to know or remember the nitty gritty, you know, for the next ten years and that's totally fine. Stuff also changes a lot over time and a lot of stuff also stays the same. I will talk about WCAG in a bit.

So we try to make this broad and give you individual but also in the group avenues to ask questions and get more insight.

final one I want to highlight is the last one. Linnea said I want to be like get stronger or I guess more attractive on the market and update myself and I think it's I might be living in a bubble maybe the accessibility bubble but it's it feels to me that accessibility is Det är allt mer vanligt att se det i jobb-advertens, och som behov i förhandlingar, som upphandlingar, och behovna är mindre vaga och mer på poängen, och de kan även säga att du har turer, det är väldigt bra om du har en certifikation och så vidare. Så jag tror att det är en bra tid att ta det här kurset på det här momentet med allt som händer. And we're going to talk about the legal landscape and so on in a week or two.

I agree. And it looks like, you know, and I mean, we work for, or with our own accessibility consultancy. So doing external work for a lot of companies.

But what we see is that a lot of companies are bringing that expertise inside, which is very interesting for us. Also a little bit scary, of course. But the interesting thing is, we have had a couple of colleagues over the last year or so who were specifically hired with the accessibility background into positions outside of Access Lab, inside of companies that don't focus on accessibility.

And that's also super good. like, yeah, there are like, you know, a handful of accessibility professionals, you know, in for like compared to like developers and stuff. But if you learn about accessibility and you go back and you just do it, that impact is so much greater than, you know, or like, you know, greater than stuff that we can do in a two-month project or something like that.

So yeah, I think this is a great time to learn about this. would become ever more important. And yeah, it's great.

Yeah. Thanks for engaging in the chat. We're hoping to get as much engagement as possible, even though, I mean, the format is difficult when it's like remote and stuff, but appreciate very much if you guys write stuff in chat or raise your hands and comment and share stuff, even though we're not in the same kind of classroom setting.

We're shortly going to take a break but I think we can go maybe for five more minutes before that. I'll share my screen again and talk about this strange accessibility acronym. So we have A11Y and 11 looks like else so we usually say "ally" but "ally" what?

But it's 11 letters between the a and the y in the word accessibility. I think it's called like a numeronym in Swedish. You see sometimes I18N I think for internationalization like long words that you want to say a lot or write a lot and then you can shorten it that that way.

So that's A11y. And then of course the community here in Sweden T12T. It's Tillgänglighet but there are 12 letters between the T's in that word. So that's why we often talk about T12T or have the T12T.si site and meetup group. Okay highly recommend But what is accessibility and why is it important on a high level?

Well, I mentioned it already. Disabilities or impairments can be permanent, temporary or situational. For instance, Stephen Hawking had a permanent motor impairment.

Now he passed away a couple of years ago, but you might have noticed him like how he communicates using a synthetic voice like a robotic voice and he controlled his computer using just this sensor on his cheek that he could move up and down and then kind of select stuff on his device and communicate or surf the web or whatnot, write books. We're gonna look more in into detail on how that's done. It's called switch control, brytarstyrning.

But yeah, if you had a permanent disability, then you can have a temporary one. You broke your arm skiing for instance, and for a couple of weeks or months you have limited mobility and might not be able to use a keyboard or a computer mouse the way you are used to. And then we have situational ones as well.

I think we have some keyboard things coming through for one. I'll mute the microphone there. Then you have situational impairments as well.

Like me carrying my kid and for a certain situation I have motor impairment. And even though the length of a period of time you have these impairments differ and they might also differ the kind of challenges you have physically, many of the things you do in interfaces to make them accessible for these different kind of people or scenarios are similar. So for instance, all of these, in all of these scenarios, writing or inputting text will take longer, it will be more tedious, you'll maybe avoid it, you'll make more mistakes and so on.

So what's one accessibility thing that can be beneficial to all of these users? Well, för att skapa ticket online. And then if you have this like, oh, you only have two minutes to do it, then there's no way to extend that time and it's unclear that you're going to get thrown out.

And that's going to be an accessibility barrier. And if you solve that, it's going to be make the site more accessible to these users and to others. Like having a shorter form or clearer time limits will benefit everyone, not just users with impairments.

And I think Försäkringskassan, which I saw someone was taking this course from that organization.

That's me, hello Anastasia here.

Hey Anastasia and you've had some other colleagues taking this course throughout the years. I think Åsa was maybe the first one.

That's right, that's right.

Also Holmberg whose name is down there as well. But you guys have done a great matrix here for different disability categories and permanent, temporary or situational things. So for instance with vision you have permanently lowered vision, you might have an eye infection or you have some sunlight on your screen.

And for all of these users good contrast, large text etc will be important and you can have that for hearing, speech, motor, cognition as well like you have a permanent concentrational impairment like ADHD or something or you're burned out and like for a couple of months or something you have trouble with concentration or reading or understanding or whatnot. I think it's the most common source of sick leave in Sweden as well. Or you could just be stressed or in an open office landscape and so on.

So I think this is great. It shows how if we focus on people with like the permanent disabilities we'll get something that's good for other users in different situations or periods of their life. And to the right here, there's this note saying digital services should work and it's like without sight or with limited sight, without being able to perceive color, without hearing, with limited hearing, without speech, with limited strength or function in your hands, with tremors, if you're sensitive to kind of flimmer, blinking stuff, and with cognitive impairments.

And this is not something that Försäkringskassan have just like, oh, let's let's put this here. It's straight from the European standard for accessible IT or ICT. So it's like, why is this standard here?

Well, it's to make sure that digital solutions work for these users. So if you want to condense everything we're doing into a single list, I think this list is a good a good one.

Yeah, I think so too. But one of the traps that these types of things have, like it looks like these are all separate disabilities. But of course, someone who is blind can be stressed.

And someone who, you know, or someone who has a hearing impairment might have, you know, a throat infection and can't speak, you know. So, that's one of the big things that, you know, you might want to take, to think about sometimes is that, oh, these can all happen at the same time, right? Your vision can be impaired, your hearing, your speaking, your motor, and your cognition, their cognitive abilities can be, and can, you know, different people in different, on a different spectrum can have different disabilities.

So I think that's always interesting to keep in the back of your head. And I saw that we had a hands up, but I think...

Yeah, that was me. I was thinking about a funny situational one. Like if you're tipsy standing on the train when it's a bit shaky, that's a funny one.

Yeah, yeah, yeah. Great, great. Love that.

Yep, shortly gonna go on a break. Just want to say that this poster, if you are getting all of these slides there on Kayabu, you can look at where they are. There's this link to this where you can get this poster in like A0 and A1 formats, like really big if you want to have it on your office or by your workplace or hand it out to colleagues or something.

I think it's a great thing that you guys at Försäkringskassan have done. But yeah let's take a break. We'll meet again in just over 10 minutes so let's take a break till five past. I'll put that in the chat as well if someone forgets.

See you soon.

No. Silence.

All right. I hope you guys had a good break. We'll do the second hour of this session, where we'll finalize the intro to accessibility part.

Eric will give the flyover of VIA CAG as well. And we're gonna talk a bit about the core structure and tools and stuff we have here in the course. So that's the plan.

Okay. All good.

I would say that though.

All right, so this is where we left things off with this great matrix. Another way of looking at accessibility or perspective on it is like designing for more difficult scenarios, let's say where you have like your kids screaming around you and you just wanna be done with, I don't know, grocery shopping online or whatnot. If you design for that situation and it will improve the experience for everyone.

So even if you're like at the cozy fireplace and really relaxed and stuff you'll not hurt anything from things being too intuitive or easy to find or frictionless. if we design for people who have low vision for instance and it will be fine even if you have great vision. However if you do it the other way around things will not work out.

Do we have some sound creeping through? I think yeah all right. That brings us to an important concept called inclusive design, includer in the design.

And we'll have a definition here. So it's the design of mainstream products and or services that are accessible to and usable by as many people as reasonably possible without the need for special adaptation. So some key things here is mainstream products.

We don't want a separate product for accessibility. It's been tried by many companies throughout the years. I think one of the more famous ones involves an airline company that made a booking flow that was mainstream and then another booking flow for blind people and said, "Hey, this other booking flow is super great for blind people. We've tested it with screen readers and we made all the great contrasts and everything, but they got sued both in the US and in I think Norway and got in legal trouble having to pay a bunch of fines for that.

You're not supposed to have separate, they call separate but equal solutions, but it's not equal because you have to find a separate solution and people who use assistive technologies will just like anyone else google like buy a flight ticket and not think like oh buy a flight ticket for blind people no it should be mainstream products.

Yeah also that doesn't really make any good like they wouldn't even be connected to like the same domain so like yeah just through a search index it would just hide it.

Exactly, so you wouldn't find it. I think back in the day you had these like mobile sites, so you had like sgj.se and then you had to go like mobile.sj.se for the mobile side and it doesn't make sense because you kind of stumble into the regular one and now with responsive design and everything it's like you go to one place and the same thing should be held true for for accessibility as well, or inclusive design.

And then it was like, you know, you had like special offers on the main site and then they weren't like super obvious on the accessible version and that, you know, that's not good. So there's a lot of ideas that people have of like how disabled people are supposed to interact with content and almost all are wrong. The idea is that everyone should be able to use every site.

And of course there are edge cases where that's not possible. Like if you're a music streaming service, you will not have like, I don't know, sign language versions of every song because that's, you know, the product that you get is something that you sell from someone else. But it's like, technically should be like one product for everyone, right?

Yeah, and that's a great segue into another important thing in this definition is that it doesn't say it should be accessible to everyone. No, it says it should be accessible to and usable by as many people as reasonably possible. So that's, you're going to aim to get to as many people as reasonably possible, but it would be lying to yourself and everyone else if you said, yeah, it's going to be accessible to every person on earth.

For instance, most websites are not accessible to my six-year-old who can't read and that's by kind of design. He's not the target audience for that site because he's too small. And there are people with disabilities that can't use technology at all or had a colleague who has a sister with intellectual and motor impairments that and she uses technology like an eye tracker but it's like four things on her screen it's like tired hungry or something like that and she she looks at different kind of symbols to communicate but she's not surfing your website and you wouldn't reach her however just because you don't reach her doesn't mean you try and reach as many people as reasonably possible.

And finally without the need for special adaptation. So we'll get into this shortly as well or in I don't know if we'll get to it this this session but otherwise in a week or so but having like separate buttons to activate some kind of accessibility mode is not very good for multitude of reasons. I like this tweet by Billy Gregory who said when user experience doesn't consider all users it should be called some users experience or sucks.

So if you're a UXer you can after this course consider yourself a real UXer and if you like maybe your colleagues are just sucks UXers. Yeah, I thought that was on point. And finally, another quote from Mary Patch Reddable from IBM said, "For people without disabilities, technology makes things easier.

For people with disabilities, technology makes things possible." I think this is super clear, for me at least, having done so many user tests and interviews over the years, that most of the people you meet are like super positive around technology. Like at least if they've had, let's say a vision impairment for over 20 years, they'll tell you how much, how big a change the technological advancements have been in their kind of independence and ways of going about things in life and being kind of like having the opportunities to to do certain jobs and so on.

So that's it's it's pretty cool what technology can do but it's also very sad to see the simple issues that block people from using different interfaces that are there because of Ja, vanligtvis oberoende eller inga bra processer eller förlust av kunskap. Och också ett tema vi kommer att ha i, jag tror, kanske veckan tre eller något, "Accessibility is no longer optional". Vi har "European Accessibility Act" eller Tillgänglighetsdirektivet and we have the web directive doslagen.

The first one is for private sector, the second one is for public sector and there's a lot of new kind of requirements and you have to try and get your head around them and what you need to do for documentation and so on but the overall message is clear from the European Union that it's not only the physical environment that needs to be accessible. I saw someone working with physical accessibility by the way in the chat in the answers and that's been kind of a requirement for many many tens of years. But it's also the digital environment that needs to be made accessible.

All right moving more towards the core structure. Hoppas jag har uppdaterat denna bild som är korrekt. Vi får se.

En regelbar vecka fungerar så här. Tysdagar av förra veckan kommer en videosäsong eller videosäsonger att publikeras på Kayabi, ofta runt 30-60 minuter av innehåll. Det kan vara på temat VCAG or designing accessibility or laws or yeah whatnot there'll be a theme each week.

Then the the Tuesday of the kind of current week we'll have a two-hour live tutoring in a whole group so basically meeting in this way that we're doing now. We'll be doing questions and answers. We'll be testing interfaces.

We'll kind of apply the theory that you've gotten through the videos. So let's say we've talked about keyboard navigation in one of the videos. Then we'll maybe try out a couple of different sites with keyboard navigation.

We'll do some exercises. Everyone tries it out and we'll share what worked, what didn't work and yeah how do you And then also on Tuesdays, so most things happen on Tuesdays in this course, but after the whole group live tutoring we have this bookable tutoring time. I have a slide on that shortly, but that's optional, but you can book like 20 minute sessions with Eric or me.

And anytime you'll be able to use the community on Kayabe for quicker everyday communication, eller så snart ni alla har blivit lämpliga där. Jag hörde att det var några problem på moment, men det borde löpas snart. Så i princip, de videorna du har, vad det säger är att du har en vecka att se videorna och sen har vi en säsong på den temat där vi använder kunskapen om videon.

None of this is something you have to be like these live sessions you don't have to come to them you can watch them after the fact we'll record the group sessions we'll not record an individual tutoring time but we'll record the group sessions however you will get out you'll get most out of this course if you come there if you engage if you ask questions or kind of do the exercises during them and so on. So really encourage you to if you have the opportunity to mark those Tuesdays times as like this is the accessibility course time and come to the sessions. But you don't have to. You can take everything, what did you say, Erik?

Asynchronous. Is that the word?

>> Yeah, exactly. There has been a question in the chat. Is there a specific time they will be be released on Tuesdays?

Would love to block it in my calendar if possible. Yes. So basically what we do is after -- so what we have scheduled and let's see if that works with the new system.

Right? No promises. If you see that it doesn't get released on Tuesday, please ping us and we will make sure that we manually release it.

But the goal is that it's getting released at 3, 15, 15 o'clock, you know, basically when the time for the live session ends, we release the next week. So you can concentrate on that. Also over the Christmas period, we will release a couple of sessions early.

So you know, if you have time during Christmas, you want to do it early, you can do that. So we want to give you that flexibility. but also want to guide you through and throw everything on top of you at the same time because that's not good.

Nice. And these individual tutoring sessions that you can book, it's basically individual coaching from Eric or me. It should be Eric or me.

be like the weeks that I do the live session with everyone and have released the videos and so on it will be with me and vice versa. And there you can ask questions about let's say concrete issues you have, strategic challenges, course content or anything else on your mind. And you book the tutoring through a Google Sheets link that's at the top of the Kayabe course, I think.

Correct.

Yeah. And yeah, maybe show you how that looks. Share this tab instead.

And basically, like, there are 15 minute sessions spread out across the week. So week one, now there's nothing but next week, it will be with me and Helena, Lina and Jonas booked some sessions there and there are three left. We will, you can't book them like too close to the actual time so I think we at least I check this at the beginning of the day of that day and then I kind of plan for that accordingly so book it at least the day before.

But if you really want it during the day, you can message us and leave like, "Oh, can I have this session?" And we'll be able to answer you. Do that on the community thing there in KAB.

Yeah. There has been a question in chat. So are we talking about video recording of the previous weeks or some other type of content?

So videos that have been released before. You know, and usually what we do is we set the stage in the videos and then in the live session, in the live tutoring, we explain or we show it like how it's done in practice. So you have a little bit more like a different perspective.

This is also the place where you have time to answer, to ask questions. You can also answer questions if you want to. And that's what we're talking about for the Bookable Tutoring.

that's totally your time. If you want to, you know, if you have something that like bothers you in your work, or if you think like, oh, I want more context for this or for that, that's basically very open topic wise for you to ask.

Yeah. So you don't have to do any booking or anything to go to the live tutoring in group thing, or things like this, like watching the videos or going to the group tutoring. You just do that.

show up and or do it when you want but it's the bookable tutoring time that's optional here at three to five that we were talking about that sheet thing. And then I also mentioned it shortly and I think it's been in the send outs before the course. There's a on-site workshop October 17.

Is it October 17? I think I haven't, have I updated that? That might, is it October? It'll be November.

November, right? Yeah. It's like, yeah.

October

17 is in four days. Yeah, I'm like, November 17th. Almost got it.

Sorry guys for the scare. It's November 17th at three o'clock to six o'clock. It's going to be in Stockholm at Chas Academy near Globen.

And the reasons to come is you get to try out assistive tech. You'll meet me and other, you guys will get to meet and kind of network. You'll meet also an assistive tech user, a screen reader user who will come.

I'm not exactly sure who yet last time it was a guy named Filip. It might be Tova or Daniel or we'll see exactly who joins that session but you'll get to see that in action and interact with that person. We'll have some after work and free candy and a bunch of fun things.

Again it's not something you have to do is completely voluntary but from previous experience a lot of people who have taken this course have kind of said that this was one of the highlights of the course so if you have the opportunity to to come then please come. You will meet free candy.

Maybe that's a system technology user.

Maybe. And finally before Eric, your VKug flyover. Just want to say that we'll divide up the content a bit.

I will talk a lot about the fun stuff that you always say, Eric. I get the fun stuff and you get the techy, boring stuff. But design, user testing, ways of working, and building an accessibility culture, and cognitive accessibility, and so on. And you, Eric, you will take VKug, the ARIA standard, code examples etc etc. You will do yours in English, I'll do mine in Swedish and many feel maybe your sessions Eric are more challenging than mine especially if you're not the developer.

Know that it's totally okay if you don't get all the nitty-gritty details just like you mentioned earlier Eric. You have heard about concepts and so on that you don't need to know the details about. I don't know if you want to add something there, Eric.

No, that sounds about right. Do we want to really quickly talk about the examination at the end?

Yeah.

Because I just look at the slides and we don't have any slides for that. So, yeah, basically at the end, we will ask you to do a high level review of a website that you pick. So that could be your employer's website, that could be your website, whatever.

And yeah, that's and we have some documentation on how to do it, what we want you to check. That's all on the platform and should be already visible to you. So yeah, feel free to look into that.

And as we go towards the end. Usually there are some of the lighter topics like content and stuff like that. I usually take time in the live session to go over the examination and what's the requirement and how to submit it.

Because that's going to be new this year as well. So we need to take a look into how we're going to organize that. But yeah, that's going to happen.

Just a heads up that there will be a final thing that you're going to submit. And then we're going to say, yeah, you're great.

>> Nice. And just showing this, I think this is how it looks from your end. I've turned on the student preview mode.

So this is K-ABI if you haven't been in there. Here we're in week one. Shortly this is gonna be published for next week which will be keyboard navigation and input.

But here week one we have the slides, we have the book tutoring time, we have articles and extra material that you want. This is like, you can read up on these things or watch these perspective videos and so on. So you'll be able to see that.

But if we back up and we go to the last week, we see the examination and you can actually already go in here. It's not super clear, you can click on these things, which is strange.

It's not.

But you can click on them. And here we have like, yeah, what you do, what you're gonna do for the examination, because we need to be able to give you a grade in this course. And I wouldn't focus too much on this the first couple of weeks, but it could be nice to like read through if you wanna prepare yourself for the final thing.

We know that some people are anxious of like, oh, what's going to come at the end, you know? And so we try to make everything as early as possible, you know, at least for this type of thing. As I said, like for the other materials, we try to like feed it to you so you don't get overwhelmed.

You know, yeah. And then I can share my screen and talk a little bit about WCAG. That's the plan.

I just want to share the, so this is next, not next week, but the week after that, Which will be also a Monday session, because I have other things, worse things to do on Tuesday, sorry. And so, that's when the WCAG 2 stuff is happening on a Monday for once. And basically what you will see is that when you click into one of the sessions, you get the videos on the right.

And in this case, it's three lessons and you get three videos. And later we will have sessions that have much more content in it. So you will have all the videos and at least in my sessions I also have one video where all the videos are basically one after the other.

So if you want to or you feel like, you know, just putting it on like your phone or something like that or listen to it like a podcast for like repetition reasons or something like that. You can do that and you don't have to click, you know, continue, continue, continue. So that's a good thing on how to use this. And now I have to remind to make this self publish because you can't preview it when you self publish it.

So that's fun. New technology. All right.

And now I will talk to you a little bit about WCAG. So this is basically the preview for the session in two weeks which goes much deeper into the whole web content accessibility guidelines topic. And, yeah.

So this is the very brief overview. This is basically giving you all the terms and the things, links and stuff like that into your hands. So if you want to look something up, you already have heard of it.

So it's a little bit trying to like, you know, not just push you into the black void of like, here are all the WCAG things and you have to work through them immediately. So yeah. Let's talk a bit about the web content accessibility guidelines.

WCAG is the acronym. Yes, we love our acronyms. And it consists of web content or concentrates on web content because it was developed by W3C's web accessibility initiative.

And the accessibility guidelines part is pretty self-explanatory. But remember that, like, the base, the initial genesis of it is for content on websites. And nowadays it's used all over the place, right?

For apps, for machines, you know, for ATMs, stuff like that. So it's going, you know, it's pretty impressive where you can find WCAG and its principles and everything. Everywhere.

You might see this logo. Which is the W3C logo and the web accessibility initiative logo. And Web Accessibility Initiative, we sometimes call it WAI.

And that was founded in 1997. A lot of people that take this course have not been born regularly. So we recognize that that can happen.

Which makes me also feel -- well, it makes me feel quite old. Sometimes you also see this logo, which is the old one with the W3C, where that wasn't bit clearer what it is. And W3C started with these two people.

At least the way it started with these two people. On the left, it's Tim Berners-Lee. When I worked at W3C, he was my boss.

He's also the original web developer in terms of like he developed the World Wide Web. So whenever you're using a website or, you know, writing a website or doing anything like that. He's the guy who invented it all in 1998 -- in 1989.

And then he founded the World Wide Web Consortium in 1994. And accessibility was added in 1997. So really quick after like, okay, we have to bring this on a professional level.

We have to fund this consortium that That makes sure that every browser can actually access all the files on the internet and that they can all communicate with each other. Accessibility was like basically right there immediately. Because the idea was that the web is a medium that can reach everyone.

Regardless of disability and stuff. And so Judy Brewer on the right, who was my direct, like, boss when I worked at W3C, she has led Waze since its inception in 1997. And after 25 years, she retired in 2022 from W3C. Did a lot of stuff.

sure that, like, you know, when people talk about laws and stuff like that, that WCAG is always there as, like, the standard to reference to. And there was a lot of, like, you know, political work involved, right? Where I go, like, I don't care about other people and what they think.

Like, you can't do that if you lead such an organization. You have to make sure that, like, this appeals to everyone. And so they started WAI way in 1997.

And two years later, boom, there's web content accessibility guidelines 1.0. It's the first result of the newly formed WAI. I don't want to go into much detail because this is now a historical artifact.

The web that is described in there has nothing to do with what we are using today. But it's really fascinating. If you read through it, and I would -- well, can't say I recommend it.

But if you're curious, take a look at it. Many of the ideas were really good that are in there. But they were very focused on the web technology as it was at that time.

Which was also just growing. So the working group was like, yeah, we did a great thing here. But also this is a thing that will be outdated really, really quickly.

Like in the early 2000s and the late 90s, the web changed so much, so quickly, that they felt, oh, we need to start on something that replaces this right away. And they did that. And it was called WCAG 2.0.

Which was published on December 11th, 2008, which is just nine years after the first one. And yeah, that just how long it took, right? Collecting all the data.

There was a really scramble in 2006 where someone looked at the draft that was out there at that time and was like, "This is no good." And they had to change a lot of stuff. talks about this anymore.

But it's a very fascinating part of web history, I guess, these days. But that was not the end of WCAG 2. Because like they knew, like, okay, this is not like very like focused on technology.

But it's It's now more general, but we also need to move on and see what, you know, what didn't we get to in the first version? What can we add? For example, for WCAG 2.1, which came out in 2018, it was already clear that there were so many more things that you need to think about, like mobile phones.

You know, when WCAG 2 started in 2008, there was barely a mobile phone around, right? The iPhone was launched in 2007. So this couldn't foresee all the different things.

A lot of people thought, like, oh, a touch screen phone, this can never be accessible. Which it is completely accessible, right? Or as accessible as you can make it.

But yeah, so it took a long time. It took ten years until the WCAG 2.1 came out. And it had, like, all the mobile stuff in it.

It had some cognitive stuff in it. It had, like, a good number of things in it. But that wasn't the end, too.

In 2023, web content accessibility guidelines 2.2 came out. that added like stuff. Stuff that is very interesting, but also is, you know, when you do testing and stuff like that, it's very niche, it's getting very into like, oh yeah, in specific instances, this is a good idea and it's important that we have this.

But in other instances, it's like, you know, a very light touch to WCAG 2.1. I don't think it has been as much of a revolution that 2.1 versus 2.2 was, 2.0 was. And currently, like this was in 2023, now it's 2026.

And for a number of years, even before WCAG 2.2 came out, W3C has been started to work on the new version of the guideline, like the new major version of the guideline. That's WCAG 3. Very imaginative name.

And actually they are not called web content accessibility guidelines anymore. This is apparently an old slide. That I didn't find the issue.

It's now called W3C accessibility guidelines. So they could keep the WCAG abbreviation. And the idea was that this would publish in 2028.

Now it's more like 2031, maybe. I'm not too sure. But they're working on this.

And this will be, you know, will basically throw away a lot of what you will learn in In terms of like direct structure and information of the standard that we have right now. All the things that you will learn will cover WCAG 3 as well. Because like the needs for disabled people are the same.

You know, text alternatives when they need when they apply and stuff like that. That will always be the same requirements. It will just be in a different package or it will be like how you measure it will be different.

But in general, everything you learn here and that's why we do this in depth baseline, making sure that you have the solid foundation will travel into WCAG 3. It will help with EN and stuff like that. Okay.

some questions in the chat. And it complies to accessibility standards begin to become law. Something that needs to be adhered to.

So we will talk about this over the next few weeks. Basically what is mostly applicable for people in this course is for public companies. So companies basically business to consumer companies.

And that's 2025. In July, end of July 2025. There was the deadline for the European accessibility act.

But we will talk about that in the future. Yeah. Oh, Hampus already answered that.

Yeah. I mean, I might have uploaded an old version of the PDF where it says 2026. for web content accessibility guidelines three because stuff gets pushed back all the time.

And I can update the slides after this. So sorry for the confusion. Yeah.

Updating the slides every year. All right. So web content accessibility guidelines are based on four foundational principles.

Perceivable, operable, understandable and robust. Perceivable is basically that you can see or hear or feel something. So you have multiple ways to perceive information.

Operable means that you can operate user interfaces, making sure that you can identify buttons and push them and use them with the keyboard and they work. Understandable is more for like understanding interfaces, error messages, stuff like that. And then we have robust which is basically make it technologically sound or technically sound that the website or app works with assistive technology.

Yeah. This is like really the big picture. In two weeks you will learn a lot more about that.

There's additional information out there. So there's the WCAG standard, which we will look mostly at. And then there's the understanding WCAG pages.

Those are explainers for different, for each of the different success criteria. So you have, you know, examples and context and a little bit of more explanation for it. They are very useful.

Then there are also WCAG techniques, which are less useful. And those are basically code examples to meet WCAG. But not every technique, you don't have to use those techniques.

You can usually also reach conformance to WCAG in a different way. Just like the big overview. But there are examples and they are good.

It's good to have them for understanding. And at the end, I would recommend to look at the web content accessibility guidelines overview which basically gives you the whole like overview on what the guidelines are and how they work together and a little bit more of like going from one version to the other. Like what have been the changes.

We will look at WCAG 2.2 for all of the course because that's that only makes sense. Because that's the current standard and also now coming into the EN 301549, which is the European standard that applies to, you know, all of the business to consumer companies and websites and apps. And also to the public companies.

You know, your municipalities, your, you know, state created apps and stuff. So it's pretty exciting that WCAG 2.2 finally gets in there. Hopefully by the end of the year.

And yeah. You will have all of that knowledge by the end of the course. And that's everything I have.

Any more questions? Yeah, I just want to say, like, you know, if you find, like, things where it says question mark on it or it says, like, you know, this is in the future, those dates can always change. We -- this might be a secret, but we're not re-recording every video for every course.

So some of those videos might be, you know, a year or two old. So don't worry too much about it, but feel free to say like, "Hey, what's the deal with those numbers?" Because then we can make those updates.

Yeah. Yeah. We have a couple of more minutes if we have some reactions or questions or reflections.

We can take those now. You can write them in the chat, raise your hand. Also, meanwhile, while you consider that, I just want to say so what will happen next is that hopefully in 14 minutes the videos for next week will be released on Kiabi.

You can watch those whenever you'd like but preferably before next Tuesday at 1 o'clock when we meet and practice those and like I mentioned it will be on keyboard navigation it will be with me and the videos will be in Swedish and the session will be in Swedish as well och jag tror att det borde vara högst på din prioriteringslista också kanske kolla ut de artiklar vi postade för den här veckan som en optional läsning, men vi har väljat tre saker som jag tror är väldigt bra att kolla ut under början av kursen också tänk på att fråga din boss eller göra resurser för onsida-workshop i november vackert, det verkar inte som om vi har händerna ställda eller frågor i chatten då ger vi alla 13 minuter av deras liv tillbaka och grattis till alla på det And we'll, yeah, just say, yeah, great to kick this off. Nice to meet you all. And I'm hoping for a couple of nice months together with you and going forward.

Right.

Yeah, thank you very much. Thank you for doing this. Really appreciate the interest in like accessibility and stuff. So, because like, you know, not lots of people don't do it. So you're always happy to see that there are people still want to do it.

All right. >> All right. Let's wrap up. See you guys. Bye-bye.

>> Bye.

>> Bye. Thank you.