mstdn.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A general-purpose Mastodon server with a 500 character limit. All languages are welcome.

Administered by:

Server stats:

15K
active users

#screenrecording

0 posts0 participants0 posts today

Recording the screen is a sore point of Raspberry Pi OS as only a handful of hard to find tools work under Wayland and most are command line only. Botspot's Screen Recorder is a new tool that glues a GUI to the others and adds useful functionality such as recording a webcam feed and the screen at the same time.

github.com/Botspot/botspot-scr

The only alternative is Vokoscreen-NG which is more limited:

linuxecke.volkoh.de/vokoscreen

Best all-in-one screen recording utility for Wayland wlroots compositors, similar to SimpleScreenRecorder - Botspot/botspot-screen-recorder
GitHubGitHub - Botspot/botspot-screen-recorder: Best all-in-one screen recording utility for Wayland wlroots compositors, similar to SimpleScreenRecorderBest all-in-one screen recording utility for Wayland wlroots compositors, similar to SimpleScreenRecorder - Botspot/botspot-screen-recorder

#BlindTech friends, especially #WindowsUsers, I need to vent and ask if you've had similar experiences! 😓

I just had a maddening interaction with the WinCam screen recording app. Here's what happened:

1. Opened WinCam settings
2. Started tabbing through options
3. Didn't realize I was on the hotkeys tab
4. Suddenly, my #ScreenReader got stuck in an edit box for assigning a shortcut to start recording
5. Nothing would get me out - not even using my mini touchscreen display
6. I tried using the JAWS Touch Cursor shortcut and even the special app keys on my wireless keyboard, but WinCam just assigned them as new shortcuts!
7. Finally had to use a wireless mouse, moving and clicking randomly until I escaped the edit box

This lack of keyboard accessibility in that specific area is infuriating! Interestingly, other than this issue, the WinCam app is very accessible overall.

Have any of you encountered similar "keyboard traps" or accessibility issues in any software, not just recording apps? How did you handle it?

What strategies do you use when you get stuck in an inaccessible part of an application? Any clever workarounds or tools you've found helpful?

Also, I'm curious: Can anyone recommend other accessible screen recording apps for Windows? I bought a WinCam license for usability testing, thinking it was the most accessible option, but I'd love to know if there are other good choices out there.

I'm particularly interested in hearing from other Windows users, but all experiences are welcome. Let's share our knowledge and maybe help developers understand our needs better!

#Accessibility #AssistiveTech #BlindProgrammer #SoftwareAccessibility #KeyboardNavigation #UserExperience #a11y #VisuallyImpaired #AdaptiveTechnology #InclusiveDesign #DigitalAccessibility #AssistiveSoftware #BlindnessAwareness #AccessibleSoftware #KeyboardTraps #ScreenRecording #UsabilityTesting #JAWS #ScreenReaderChallenges #blind @mastoblind @main

Continued thread

So, thanks to all the replies, I’ll be redoing a bunch of my work tomorrow using OBS.

So, in short: if you want to record screencasts and you care about the quality of your work: DO NOT USE THE BUILT-IN GNOME SCREEN RECORDER. It outputs low quality videos and you cannot change the qualiy.

Use OBS instead.

*le sigh*

G’night!

Not sure whether it was Streamyard or Firefox or my OS to blame but it seems the transitions came out horribly choppy in the screen sharing recording of my talk from Groningen on Tuesday so here we are…

*le sigh*

(I’ll try to have the transitions I recorded locally edited in and the video up sometime today.)