 Thank you for coming here. It's quite a chance for me because I was just studying here a few years ago and now I'm talking here so it's quite nice. So first something more about me. I started to use Linux in maybe 2013 or something like that but it was just a little bit because I didn't have much time. I had other studies and stuff but I continued to use it and I became much more interested maybe in 2018 on this university and from some events I managed to become a Red Hat intern and then I'm starting a job in September about all about accessibility in Fedora and similar distributions. During the years I was mainly using Arch Linux because for visual impact we usually want to have the fixes as fast as possible and we don't like waiting for stuff. But I also used Fedora and I was admiring anything Debian and such as well. But because there's a lot of specific terms in this area let's get them out of the way. So first a screen reader is a piece of software which basically tells you what's on the screen, what's the label of this button, or is this piece of text a link or a heading or something else, or is it something unknown and it just basically leads you to the text on the screen. Of course there's no magic so it can't describe for example a random image because we don't have enough AI capabilities of now, of course. But it's a very important piece of software for a visually impaired. Then we have the speech citizens which is the voice which you maybe heard or you definitely will hear here in a few moments and it basically only says what some other part of the accessibility sector tells it so it's not much intelligent but it's a very important piece of the story as well. Then there was actually a one useful special device called a Braille display which allows the visually impaired to read one line about usually 40 or 80 characters in Braille letters and it's very useful because sometimes the audio system breaks and you need to work with the computer anyway so it's very important to have some alternative output. Of course then something quite more technical. For Linux the main accessibility system is called SP2 which basically allows the applications to describe themselves in a form of a tree of some accessible objects and the screen readers can do some queries about this tree. The situation for visually impaired isn't so bad we can do a lot of things for example naturally we can use the text interfaces and the console because it's just text usually so it's pretty well accessible by even the text only consoles are accessible using speak up and friends but these kernel modules aren't in every distribution on the world so we can't use this support everywhere but that's not such a big deal because using the emulators is good as well. Web browsers have a pretty good accessibility support as well. Firefox and Chrome based things have spread by the most advanced because there are pretty big cooperation behind them so they have to develop hours for this and even Chrome now works on the looks it didn't a few years ago but it does now. Of course writing some emails or instant messaging is so accessible as well because Thunderbird is just fine and things like speech and friends as well. Of course programming editors there are many of them but not every of these is accessible as much it's quite ironic but Visual Studio Code has quite good accessibility support including intelligence and things like that and they are actually working on the story in this area as you may know from the release notes but Eclipse is good as well but it's quite complicated so I'm personally using VS Code. Playing some multimedia files is doable as well because things like VLC other players are usually simple enough so they work and labor office isn't bad as well but they have some regulations and which ones are the worst can be seen later and of course managing files we can do this as well does nothing special but there are some things which can be done but they are quite hard for example sound editing can be done but the most accessible Linux thing for this is Audacity but there are still some inaccessible areas so it's it's sad but it's true. Doing some optical character recognition is a thing which we need quite often but it's not comfortable because either the application isn't much supported and there's only a single developer behind it and similar maintenance or other things or it would be useful to use a scanner with some of these applications but it isn't and yeah then there's the story with reading PDF files. Some of these can be read by the web browser readers or evidence or something like that but it's not something we much like and of course not every PDF is accessible there are so many just image-only PDFs in the world. Playing games is it's generally issue on Linux but for visual impact there's much smaller selections of games you can probably get some going through vines but it's complicated and not done so often. Yeah if you want to create a presentation you have to basically use something like Pandoc or similar because creating some thinking in person is painful and reading it is even worse. So which problems we have? I would put them in two categories. The first is the small problems which are basically missing labels and such so if we look on this Gdonk weather thing and try to use it with a screen reader. There's the first example because there's some menu button but no user actually is interested in the technical GTK class I think but there's no A11Y label so it's a quite over forgotten thing but it's so easy to fix honestly I fixed many of these issues in Gdonk settings already. Of course but then there are more critical issues because if we look to the Gdonk calendar thing C over new panel, text, C, A, L, come on, window, show up please, C, C, A, of course when you are presenting something. I don't want for this course so basically if you want to use the current version of Gdonk calendar in Gdonk 42 as a visually impaired you can't because the days are reported just as some overlays or something absolutely inaccessible and you can't even get out of them so there are sometimes more pressing issues than a missing label. Even in weather applications it's basically impossible to read the weather so it's quite sad and much more work will be needed to fix it but because there are actually some part Linux users who don't want to fiddle with the configuration for hours with some friends we began creating a project called Fedora which is quite stupid name the Linux distribution is based on Fedora so it's the first part of the name and Agora which is a conference for visually impaired lovers of IT and stuff but if we can think of a better name or use just tell us because we need a better name than this. What we did actually did quite a few things there. We configured G2 screen reader to start automatically after login, installed some applications and it's a much more keyboard shortcut than the default so it's the controls are more straightforward and quicker for everyone. We as well started packaging some applications like the previously mentioned Lyos and other OCR stuff it's probably everything about Fedora and what you can help. First please everyone don't break things that already work. It may be simple if I say it this way but it happens too often. I saw for example a very critical bug in GTK so every GTK4 application crashed with running screen reader so it wasn't nice at all and this thing actually got to a federal release but it's fixed now fortunately so if these things wouldn't repeat it would be very very nice. When you are designing some user experience you should think at least a little about us because sometimes it's just a few lines you know the UI file which can make our life so easier so if you are using the icons you know use them but don't forget to access it with the labels. It's not so hard and if you are doing something more involved and you are not sure what to do about the experience just ask because there's so many Empire Empire who can help actually and they want to help but they just don't know on time and they are then surprised about anything and if you have some time and you want to really see how your application behaves there's nothing more exact than turning or cut the Linux screen reader on and just using the application with the keyboard and maybe with your eyes closed it's quite interesting I think and of course tell the others about us because when more developers know about these issues then there will be probably less work for people like me I actually don't believe it but I cannot be so so it's the end and if you have some questions just go forward literally just turn or the screen reader or cut before the change test the experience with the keyboard then do your work and that's the thing again and if it behaves so reasonably then you probably didn't break anything there are some cases which are really really wrong and should be automated I think but there are too many special cases so human are still needed but yeah we are working on some linting checks or something like this we don't know where but we are thinking about it the foundations actually work pretty good but the application developers have some work as well because if you for example create a button and set it an icon which is simple enough then you as visually impaired you just hear that's gtk image button and nothing else and if you add the label accessibility label it's it's quick and it helps us I think I would like to ask how how do you fill bugs on software as a user which uses it different way that most people so because I think most of creators of that software never seen impart user their creation so they have no idea how it's used and even able to test that thing so how can you show them it's unusable for you exactly what's wrong but yeah I understand that how can you report that well you can be as detailed as you can so we usually describe at least for a new project all the steps for a production of the issue but and in some projects it's enough and the developers use the steps and find out what's wrong and agree with us but yeah you have to be detailed and you have to be prepared to help the developers because you are right the majority of them didn't see visually impaired person in their lives so you have to be prepared for a longer longer conversation under the issue of course you have to use the correct reporting channel which is usually okay but some issue trackers are quite annoying for example redhead but by the way isn't the best of these are fortunately okay thank you yeah yeah just talk to me I will be there thank you