Minulej tejden vysla recenze Metroplexu v Pevnosti. Jo, ten brak od Neon Suns, kterej ma spousta lidi v literature za shitty samonaklad. Porad nemuzu uverit tomu, ze je mezi ostatnima knihama z velkejch nakladatelstvi, ktery zamestnavaji randal lidi. Je to neuveritelny...
🇨🇿 Český paradox - průměrný Čech se má objektivně skvěle, ale subjektivně se cítí mizerně. 🇨🇿
Zde jsou 4 klíčové indexy o České republice: 🥇 Nejmenší procento lidí ohrožené chudobou v EU. 🌍 12. nejbezpečnější země světa. 🌍 25. nejvíce prosperující země světa. ☹️ 2. nejpesimističtější země světa.
Takže objektivně jsme na tom opravdu dobře, zásadně lépe než většina světa. Subjektivně ale lidé v ČR mají pocit, že "všechno stojí za prd" a "bude hůř".
Dává to smysl, protože naši spokojenost jen cca z 10 % ovlivňují vnější podmínky, ale zbylých 90 % dělají vnitřní faktory jako genetika a vzorce našeho myšlení.
Jak píše v jedné ze svých knih Pavel Vosoba: "Socialismus zanechal hluboké stopy. Některé věci nás naučil tak dokonale, že se jich zbavíme až za několik generací. Věty typu nejde to, to se nedá, to se nepodaří, protože... jsou ve slovníku nejen nás, dospělých."
Svět se koupe v omamné vůni šeříku a já dnes objevila další poklad jara - kvetoucí rybíz! 🌸🤍 Tyhle momenty, kdy se člověk zastaví a vnímá tu krásu jara, jsou k nezaplacení. 🤍🌸 Krásný jarní den všem! #jaro #šeřík #rybíz #květy #jarnímoment
Požiar bŕzd sa nerozšíril do interiéru vozidla hromadnej dopravy. Nedostal sa tam ani dym. Pre porovnanie, keď horia brzdy na železničnom vozni, neraz sa
I hate to be picky, but I feel the naming convention will still confuse people. Web ≠ native, even if many principles apply, web content ≠ native UI, etc. On top of that, we have web views inside each platform which have their unique behaviors because they are ≠ full mobile browser experience. I hope that one day either WCAG will be renamed to something more generic or there will be some sort of mobile UI Accessibility GUidelines that will act as a separate standard. (1/2)
@vick21 I believe/think that the next version of WCAG will/should be technology agnostic and the terms/framing of the requirements will/should be applicable to digital content/UI of most, if not all flavours
Dnes jsem si byl prohlédnout Farinovu zatáčku, památný úsek Masarykova okruhu, kde v roce 1949 havaroval italský jezdec Farina a zemřeli přitom 2 mladíci. Mezi milovníky závodů a Masarykova okruhu asi známá informace. Co se už ale moc neví, že jeden z těch kluků, Václav Hejtman, byl z mé vsi #Kobylnice, a byl úplně prvním pohřbeným na nově postaveném kobylnickém hřbitově. 2. října odpoledne se konalo otevření hřbitova a hned nato následoval pohřeb, kterého se zúčastnilo kolem 1500 osob. #Farina
Asi jen málo lidí si dneska dokáže představit, že by se ulicemi obydlených měst mohly rychlostí blížící se dvěma stům kilometrů v hodině prohánět závodní automobily sledované z chodníků špalíry diváků.
Čtvrtek: Ukrajina a Spojené státy podepsaly dohodu o nerostech. Co jsou hlavní body, na kterých se obě strany dohodly? Tak primárně: 1) Ukrajinské nerostné bohatství zůstane ve vlastnictví Ukrajiny. 2) Bude zřízen speciální investiční fond pro rekonstrukci Ukrajiny, do kterého budou obě strany přispívat stejným dílem a obě budou mít v radě fondu stejný počet zástupců. 3) Ukrajina nebude kompenzovat Spojené státy za již poskytnutou pomoc. 4) Pokud by se ukázalo, že smlouva bude bránit Ukrajině ve vstupu do EU, pak smlouva okamžitě pozbude platnosti. 5) Ukrajina bude do fondu odvádět 50 % z výnosů nových investic do těžby nerostů, plynu a ropy. Spojené státy budou aktivně vyhledávat nové investory a investiční prostředky a ani jedna strana nebude vložené prostředky danit. Dohodu už posvětila ukrajinská vláda a brzy o ní bude hlasovat ukrajinský parlament. Celkově jde o diametrálně odlišný dokument, než jaký do jednání přinesly Spojené státy. Teď se ukáže, jestli dohoda dokáže zajistit mír pro Ukrajinu. A ještě se stalo tohle facebook.com/dnesnaukrajine.cz…: 1/4
Čtvrtek. Ukrajina a Spojené státy podepsaly dohodu o nerostech. Co jsou hlavní body, na kterých se obě strany dohodly? Tak primárně: 1) Ukrajinské nerostné bohatství zůstane ve vlastnictví Ukrajiny....
Měl jsem víc trénovat. V posledním kopci přišla krize. Měl jsem se dřív najíst. Ale možná ani to by nepomohlo. Už se netřepu, dostávám zpátky barvu a bolí mě...no, nebolí mě snad jen jazyk. 😅 Mějte lepší nápady! (Druhé kolo zítra 😜) #tateriJedou 🦽
Hello! We're the team that builds and supports Mastodon, alongside the community. Today, we wanted to share an update on our organisation. blog.joinmastodon.org/2025/05/…
Looks like Corporate #infosec has made it's choice.
#RSAC is filled with talks embracing AI and making it "secure".
And they invited and encouraged the Trump regime to spread its disinformation - fully sanctioned and encouraged by the conference leadership(and by conference attendees who laughed at the regime's jokes and lies and issued no challenges or stands during the talk).
With the ostracization of #ChrisKrebs by industry and the full embrace of Kristi Noem as a speaker, this was the moment that infosec made its bed.
@NVAccess I wonder if there are some features like this one where the default setting should be changed for new installations? Trying to set laptop layout automatically comes to mind as well, but some things have changed since 2007.
@Jage Desktop / Laptop keyboard layout largely depends on both personal preference, and what type of keyboard you have. These days there are laptops with full size keyboards, and external keyboards without a number pad, so it would be hard to try to guess what would be best - hence why it is one of the things we ask during a new install.
@NVAccess There are definitely many permutations. For instance I use a full size keyboard with a numpad and still opt for laptop layout in NVDA.
I suppose usage statistics could come into it though. If 90 percent of users were switching to laptop, 98 percent enabling the caps lock as a modifier, and 84 percent turning off screen layout, those would be pretty strong numbers that I just made up out of nowhere. @Jage
@NVAccess @Jage I used to be one of these strange people that used desktop layout even on a laptop without a num pad, back in the days when most laptops let you use num pad keys (even with num lock off) by using the FN key. These days, most laptops seem to have dropped support for this, so I switched to laptop layout a few years ago and now I tend to think that way even when I'm using a desktop keyboard.
@jcsteh @NVAccess Ya perhaps laptop layout was not the best example. But I wonder what are the most common settings that a new user who knows a tiny bit would change.
@NVAccess @Jage Defaults have been changed in the past. For example, the default synth was changed to OneCore. But yeah, I think real usage statistics is the real path forward if defaults like this are to be changed. Of course, then there's the question of priority, developer time and relative impact...
@jcsteh @NVAccess @Jage I always default to laptop layout. I think a few years ago I tried to push an idea to set it as default for NVDA but as I recall there were issues with laptop layout for international users who pushed back and so it was left as is except for adding easy setting for it in future startup screen.
@valiant8086 @NVAccess @Jage The original laptop layout was also much different, simulating the num pad on letter keys rather than using the arrow keys. I can't remember when we redesigned it, but that was probably a tricky change to socialise.
@Jage Absolutely. I'm not sure it's too far one way for any particular settings, and there are quite a lot which many people have firm views one way or the other about. But could be worth us looking into more statistics gathering on
@Sean Randall @NV Access @Kara Goldfinch @James Scholes I guess switching it off might affect performance and it reflows the document not respecting how the author has designed it. I am using the default setting i.e. browsing with screen layout turned on.
@cachondo I do agree with that. While the advantages and use cases described in this thread are valid, on balance I think it's probably a poor default. @KaraLG84 @NVAccess
@simon @KaraLG84 Not wanting to colour the results, but honest question: how do you deal with it?
E.g. you encounter a group of links or radio buttons all on the same row. To activate/check a particular one, do you then just switch to quick navigation keys to jump through them?
@pvagner @cachondo @NVAccess @KaraLG84 The document is reflowed regardless, and screen layout is not a 100 percent faithful representation of how a page looks.
Passwords must have a minimum length of 8 characters
Passwords must have a maximum length of 30 characters
Passwords must contain a minimum of 2 digits
Passwords must contain a minimum of 2 letters
Password must be different than the last one use…
Chef. Spy. Lover. Legend. Here is your first taste of Carême.Carême — Streaming April 30 on Apple TV+ https://apple.co/_Careme“Carême” follows the thrilling ...
Spotify has just submitted its app update including links out to the web for payment, here’s how it will change the experience 9to5mac.com/2025/05/01/spotify…
As part of our volunteer-driven accessibility initiative in GNOME Calendar, and for the first time in the 10+ years of Calendar's existence, we finally completed and merged the first step needed to have a working calendar app for people who rely on keyboard navigation. This merge request in particular makes the event widgets focusable with navigation keys (arrow left/up/right/down) and activatable with space/enter. This will be available in GNOME 49.
Most of GNOME Calendar's layout and widgets consist of custom widgets and complex calculations, both independently and according to other factors (window size, height and width of each cell, number of events, positioning, etc.), so these widgets need to be minimal to have as little overhead as possible. This means that these widgets also need to have the necessary accessibility features reimplemented or even rethought, including and starting with the event widgets.
We also hope to get other parts of GNOME Calendar accessible before GNOME 49, but I can't promise anything at the moment. We did start working with making the month view accessible: gitlab.gnome.org/GNOME/gnome-c…
This implements button functionality to make it able to focus and activate it. This also sets the appropriate accessibility role and labels/descriptions. Related:
Continuing our volunteer effort to make GNOME Calendar fully accessible with a keyboard (see thread for context), we fixed a major bug that was causing the focus to disappear into the abyss when the user tried to tab into the month view in merge request !576. This means, as of this commit, events should now be completely functional and accessible within the month view. Additionally, the merge request changes the keyboard and focus behavior within the month view: Events can only be cycled using arrow buttons, the focus can't escape the month view with arrow buttons, and entering/exiting the month view can only be done with tab. These improvements will be available on GNOME 49.
Accessibility on Calendar has progressed to the point where I believe it's safe to say that, as of GNOME 49, Calendar will be usable exclusively with a keyboard, without significant usability friction!
There's still a lot of work to be done in regards to screen readers, for example conveying time appropriately and event descriptions. But really, just 6 months ago, we went from having absolutely no idea where to even begin with accessibility in Calendar — which has been an ongoing issue for literally a decade — to having something workable exclusively with a keyboard and screen reader! :3
Huge thanks to @nekohayo for coordinating the accessibility initiative, especially with keeping the accessibility meta issue updated; Georges Stavracas for single-handedly maintaining GNOME Calendar and reviewing all my merge requests; and @tyrylu for sharing feedback in regards to usability.
All my work so far has been unpaid and voluntary; hundreds of hours were put into developing and testing all the accessibility-related merge requests. I would really appreciate if you could spare a little bit of money to support my work, thank you 🩷
After two weeks of writing, revising, and trying to make everything as digestible as possible, I finally published "GNOME Calendar: A New Era of Accessibility Achieved in 90 Days", where I explain in detail the steps we took to turn GNOME Calendar from an app that was literally unusable with a keyboard and screen reader to an app that is (finally) accessible to keyboard and screen reader users as of GNOME 49!
There is no calendaring app that I love more than GNOME Calendar. The design is slick, it works extremely well, it is touchpad friendly, and best of all, the community around it is just full of wonderful developers, designers, and contributors worth …
There is no calendaring app that I love more than GNOME Calendar. The design is slick, it works extremely well, it is touchpad friendly, and best of all, the community around it is just full of wonderful developers, designers, and contributors worth …
I don't really understand how pushing buttons to the bottom follows typical GNOME design. It is absolutely confusing and jarring. Shame this app is consistently inconsistent
@lecroix74 it doesn't follow GNOME's design on purpose. GNOME's HIG works pretty well for simple apps, but it starts becoming infeasible for complex apps such as Calendar
After two long and painful years, several design iterations, and more than 50 rebases later, we finally merged the infamous, trauma-inducing merge request !362 on GNOME Calendar.
The calendars list in the quick-add popover has undergone accessibility improvements, providing a better experience for assistive technologies and keyboard users (to a limited extent). Specifically: tabbing from outside the list will focus the selected calendar in the list; tabbing from inside the list will skip the entire list; arrow keys automatically select the focused calendar; and finally, assistive technologies now inform the user of the checked/selected state.
Admittedly, the quick-add popover is currently unreachable via keyboard because we lack the resources to implement keyboard focus for month and week cells. We are currently trying to address this issue in merge request !564, and hope to get it merged for GNOME 50, but it's a significant undertaking for a single unpaid developer. If it is not too much trouble, I would really appreciate some donations, to keep me motivated to improve accessibility throughout GNOME and sustain myself: tesk.page/#donate
It's already available in the current nightly flatpak version. It is so nice to be able to use the new event quick-add popover, with no extra swirly pages etc. to pick the target calendar. Very efficient! 😌
Thanks to @TheEvilSkeleton for their patience and sisyphean rebasing of that much awaited merge request over the past 2 years 🫡
The thing that makes me really happy, probably as much as receiving donations themselves, is people are actually donating through Liberapay rather than the proprietary alternatives.
Just a few months ago, I had no idea how to set up Liberapay and gave up on it, because I got overwhelmed. A friend nudged me to reconsider it. I tried to set it up again, and got it properly set up this time. They were the first donor in Liberapay, and eventually, more and more people started to donate via Liberapay, surpassing GitHub Sponsors and Ko-fi.
Seriously, thank you @Liberapay for the wonderful platform, and to my friend who motivated me to set it up again!
Do note that the screen recording attached won't have any alt text, to avoid redundancy. Everything written below is a detailed explanation of the experience, and the recording is essentially a visual demonstration:
- When entering the month view with Tab, focus is set to the first event widget, and pressing Tab will focus the next event widget horizontally. - Ctrl+Tab will move focus to the month cell located at the focused event widget. Ctrl+Arrow will move focus to the edges of the view. - When out of boundaries horizontally, the focus moves onto the other side of the view. - When out of boundaries vertically, the view will automatically scroll to that direction. - Shift+Arrow will move focus and initiate selection; pressing arrow keys will select ranges of cells, and letting go of Shift will display the new event popover. - When a month cell has overflowing events (as in, there are not enough event widgets that can fit inside the month cell), pressing tab will focus the overflow button, and activating it will show a list of events.
This goes without saying: If you have some money to spare, I would genuinely appreciate it. I am not getting paid a single dollar from the work I'm doing (I wish I did).
At the time of writing this post, the merge request for making the month view accessible is sitting at around 500 lines diff, but that diff will only get bigger and bigger. A good portion of that time is also spent with my eyes closed with a screen reader. It takes a lot of time and energy to understand how everything connects in GNOME Calendar and researching about accessibility in a calendar app.
Thank you for the great work. I think it would be great if we could also have a GUADEC 2025 workshop on GTK/Libadwaita accessibility since that’s often overlooked.
Welcome to GUADEC 2025 GUADEC is the GNOME community’s largest conference, bringing together hundreds of users, contributors, community members, and enthusiastic supporters for a week of talks and workshops.
Daniel Stenberg joined the show to talk about curl and libcurl and how he has spent at least 2 hours every day for the past 17 years working on and maintaining curl.
Don't forget to sign up for OpenInfra Forum on May 22 in #Stockholm to come and hear me blab about #curl. Or just extract some stickers from me and listen to the others instead.
**Update: 121/150 anmälda.**
**Update: Efterfesten är full 45/45 anmälda. 7 i kö.**
Hej allihopa!
Goda nyheter! Open Infra Forum firar 10 år, så den här
Live the bleeding edge life and take curl-8.14.0-rc1 for a test spin for us!
Thanks to users testing our rc builds, we can reduce the regression risk once we ship the actual *real* release on May 28. Today I shipped the rc1. There will be two more rc builds before the release.
Lots of good talks were given at this year's #LinuxAppSummit — but the 24 hours of livestream footage are a little messy to navigate. I've extracted the talks into individual videos, created branded thumbnails and posted them on the LAS YouTube channel for easy browsing and sharing. Enjoy:
The Linux App Summit (LAS) brings the global Linux community together to learn, collaborate, and help grow the Linux application ecosystem. Through talks, pa...
💬 Matrix isn’t just a chat protocol — it’s a platform for rich, interactive experiences! In this session, Kim Brose @HarHarLinks how to enhance Matrix with widgets, bots, and integrations, making your chats more dynamic, productive, and fun at #FOSSASIASummit2025
Matrix is more than just a chat protocol—it’s a platform for rich, interactive communication. In this talk, Kim Brose (aka HarHarLinks) will explore how to t...
☁️ Microsoft getting nervous about Europe's tech independence
"The Cloud Act grants US authorities access to cloud data hosted by US companies. It does not matter if that data is located in the US, Europe, or anywhere else."
Gaming while blind is the highest difficulty. I like challenging experiences with intense naratives. Like The Last Of Us, or Alt Frequencies!Specs: I5-13600K, RX 3050, 16GB DDR4, Keycron K4 keyboard, PS5 controller and Madcats fightstick.
This is a repository of apps to be used with your F-Droid client. Applications in this repository are official binaries built by the original application developers, taken from their resp. repositories (mostly Github, GitLab, Codeberg).
Welcome to OurBlind Join Us Reddit Discord Lemmy Who We Are OurBlind is a community of blind and visually impaired people, their family and friends, and allies, from around the world.
Remember #Movuary, when I and @FreakyFwoof posted a track made with Ableton Move for every day in February? Well, this is both of our birth months. I, in particular, don't have lots to celebrate, so instead, I've decided to give away all the Ableton bundles from that project, except one, because I accidentally deleted it. So, for anyone who has Avleton Note or Ableton Move, you can play these just as they were created, modify them, study them, make them more interesting... For those with Ableton Live, you can import them, but they may not come out sounding exactly the same, because Live converts it to it's own format, and there are differences in the libraries. Anyway, have fun... borris.me/audio/movuary2025/Ab…
Archos
in reply to Milan Hubáček • • •Samozřejmě ostatní fotky jsou také super.