Pneuma Solutions

Thanks to @AccessOn@nfb.social for making an excellent demonstration of the new #RemoteIncidentManager app for iOS!
Check out episode 93 of Access On to hear the demonstration.
https://storage.pinecast.net/podcasts/6bf32133-3166-4b95-b747-1785b44b401d/audio/7a4c9ea5-dfaa-4161-9b41-a12ce75fd32c/AO093__Seeking_your_feedback_on_smart_glasses_backlash__RIM_for_iOS__and_more_from_our_Vendor_Showcase.mp3
Want to get in on the action? There's no better time—we're still offering free unlimited keyword sessions for the iOS app! Download RIM from the App Store today!
https://apps.apple.com/app/remote-incident-manager-mobile/id6775977908

The long-awaited iOS version of #RemoteIncidentManager gets the spotlight on this weekend's episode of @doubletap@tweesecake.social!
https://www.youtube.com/watch?v=U-gbNjFIPAU
RIM's final release is awaiting App Store approval, but don't let that stop you from kicking the tires early—our beta is still open!
https://pneumasolutions.com/remote-incident-manager/mobile-beta-signup/

Good news for #RemoteIncidentManager users:
Many of you asked. We heard you. And now, it's official.
Today, we are proud to unveil Remote Incident Manager's groundbreaking mobile companion as the next big thing in accessible, fully portable #RemoteDesktop!
Run trainings, perform technical support, or drop into your computer while out and about, directly from your mobile device.
Interested in helping shape the development of the world's first #byUsForUs mobile remote desktop solution? Fill out the form and we'll get you on board! iOS builds are ready and waiting for you all to kick the tires, with Android builds forthcoming.
https://pneumasolutions.com/remote-incident-manager/mobile-beta-signup/

Development on the Android version of #RemoteIncidentManager is moving right along. Want to be among the first to kick the tires? Fill out the interest form and reserve your spot!
https://pneumasolutions.com/remote-incident-manager/mobile-beta-signup/
We're keeping the iOS beta open post-launch, as we have some exciting features coming down the pipe. We welcome and appreciate your continued interest in helping make RIM the best it can be!

Development of #RemoteIncidentManager for iOS is going strong, and the next beta has just arrived! This version presents a helpful notice to VoiceOver users when a physical keyboard is connected. We've also implemented full support for the management dashboard, allowing you to manage machines on the go. Our AI tools hub has gone mobile as well, allowing you to ask a variety of accessibility-focused support bots a question if needed. Our login flow has been improved, allowing full support for organization accounts.
Want to try the beta and help us out? The interest form is still open! Register your interest, and you'll be up and running in no time!
https://pneumasolutions.com/rim-mobile-beta-signup

Introducing #ScribeForTVIs!
Dear TVIs,
I’m Mike Calvo, co-founder of Pneuma Solutions. I’m speaking for our whole team. Most of us are blind or visually impaired ourselves.
I grew up a blind kid in this country, the son of Cuban immigrants, and I know how hard it was to get access to what I needed. I didn’t get the support I should have. I never graduated high school.
That experience never left me.
It’s why I’ve spent most of my life building tools for this community. Through Pneuma Solutions, and through the Accessibility Is a Right Foundation, we’ve pushed hard to make sure blind people have equal access to information — not just in the U.S., but globally.
And that’s why what’s happening right now matters so much.
We’re in a different kind of crisis than we were during COVID. But it’s just as real.
Support systems are getting shaky. Funding is unpredictable. And when that happens, blind students get hit first and hardest.
Being a blind student is already hard enough. They shouldn’t have to wonder whether the systems around them are going to hold up.
You shouldn’t have to wonder either.
That’s why we’re bringing this back.
We launched Scribe for Education during COVID because students needed access immediately and the world wasn’t ready to deliver it. We’re relaunching that program now as Scribe for TVIs, focused specifically on you.
Here’s how it works
You upload the material you’ve been handed. In seconds, you get it back as:
• Screen-reader-ready HTML
• Braille-ready files (BRF — Grade 1, Grade 2, UEB, Nemeth)
• Large print
• EPUB and DAISY
• MP3 audio in natural voices
That DAISY file transfers straight to an NLS Talking Book Machine, giving your students structured navigation, indexed sections, and a way to study on the go using tools they already know.
Under the hood: 140+ document languages, 30+ braille codes, math detection with MathML, and roughly 96% automated accuracy. When a document needs a higher bar, human remediation is available with a 72-hour turnaround.
For qualified K-12 TVIs, Scribe for TVIs is provided at no cost. Not a trial. Not a promo. Annual re-verification keeps the program focused on the educators it was built for.
This is about control
It’s about not waiting days or weeks for someone else to fix something. It’s about being able to take what gets handed to you and make it accessible right now.
Because your students don’t have time to wait.
Whatever’s happening in the adult rooms, blind kids still need to read tomorrow. That’s the only thing we’re solving here.
This is our way — as members of the blind community — of stepping up and saying that no matter what’s going on around us, blind kids are going to have the information they need to learn, grow, and build their future.
For us. By us.
How to get access
If you’re a K-12 Teacher of the Visually Impaired with a valid school email, you can apply at https://pneumasolutions.com/ScribeForTVIs. We’ll verify your role and your credential and get you set up.
We’ve got your back. Let’s keep our kids moving forward.
— Mike Calvo
CEO, Pneuma Solutions

The following thread is being posted in the interest of clarification and transparency:
We at Pneuma Solutions operate a document remediation platform called #ScribeForDocuments, often additionally referred to as scribeit.io (its main website address). If you are a visually impaired iPhone user, you may have also ran into an app called ScribeMe, which is a mobile application performing similar functionality. The existence of an ap with similar functionality and a confusingly similar title has led to confusion among many users. In light of this, we offer the following clarifications for you, our current and future users.
1. Our Scribe service is currently available by way of the web presence - https://scribeit.io - as well as browser extensions for Chrome and Firefox. The Scribe website will detect the browser being used, automatically offering you a direct link to the extension in the browser's marketplace.
2. We do not currently operate any mobile applications utilizing the Scribe platform. ScribeMe, an altogether different application, does not utilize the Scribe platform and is unrelated. As such, if you are a user who received news of an application called ScribeMe going dark and subsequently returning, rest assured our own Scribe offering has been, and continues to remain, fully operational.

On April 20, 2026, the U.S. Department of Justice officially extended the compliance deadlines for ADA Title II web and mobile accessibility.
If you serve a population of 50,000 or more, your new deadline is April 26, 2027.
If you are under that threshold, you are now looking at April 26, 2028.
A lot of people are reacting to this as relief.
I wouldn’t.
Before we even get into what this means operationally, it is worth saying something that should be obvious but often gets lost in these conversations.
The frustration from the blind community is real.
We are not talking about something new here. The ADA has been around since 1990. The first serious conversations about digital accessibility at this level started well over a decade ago. And even the most recent rulemaking process has already been years in the making.
So when people hear “extension,” the reaction is not academic. It is personal.
We have been waiting.
That part deserves to be acknowledged.
At the same time, we also have to deal with the reality of where things actually stand today.
Let’s talk about what changed, and what didn’t.
First. The requirement didn’t move
The expectation is still the same. State and local governments are required to make their web content and mobile applications accessible.
That has not changed.
All that moved is the date on the calendar.
Second. This doesn’t slow down the serious players
If you were already working toward compliance, this extension does not change your trajectory.
If anything, it gives you room to do it right.
Instead of rushing to hit a deadline, you can focus on building something that actually works long term. That means looking at workflows, not just one-time fixes. It means thinking about how content gets created, not just how it gets remediated.
The organizations that understand that will keep moving.
Third. A lot of organizations are going to waste this time
This is the part nobody likes to say out loud.
Some agencies are going to treat this like a pause button.
They will push it down the priority list. They will revisit it “next quarter.” They will assume a year is a long time.
It is not.
When you are dealing with thousands or millions of documents, legacy systems, multiple departments, and ongoing content creation, a year disappears fast.
And two years is not much better if you are starting from scratch.
Fourth. Accessibility at scale is not a last-minute project
This is where a lot of people get it wrong.
Accessibility is not just about fixing a backlog. It is about changing how things get done going forward.
If your strategy is “we’ll clean everything up before the deadline,” you are setting yourself up for the same problem again the day after you finish.
Real compliance means:
• Integrating accessibility into your workflows
• Having a way to handle new content automatically
• Dealing with archives without trying to boil the ocean
That takes planning. It takes the right infrastructure. And it takes time.
Fifth. The broader signal is not “slow down”
While DOJ extended the Title II timeline, the overall direction is moving the other way.
Lawmakers are actively pushing to expand accessibility requirements across modern communication, video, and emerging technologies. The expectation is not that accessibility becomes easier or optional. It is that it becomes more embedded, more enforceable, and more aligned with how people actually live and work today.
In other words, timelines may shift, but expectations are increasing.
Sixth. This is probably not happening again
Let’s be honest.
The DOJ extended these deadlines because the gap between expectation and reality was too big to ignore.
They are not going to keep doing that.
At some point, the conversation shifts from “we need more time” to “why haven’t you done this yet?”
You do not want to be on the wrong side of that conversation.
Final thought
If this extension gives you the space to build a real, sustainable approach to accessibility, it is a good thing.
If it becomes an excuse to wait, it is going to make the problem worse.
This is not a question of if this gets done. It is a question of how and when you choose to deal with it.
If you are trying to make sense of what this means in practical terms, there has been some pretty good discussion happening over at Title2.info. It is worth a look if you want this broken down without the legal fog.
And if you are already deep in this and realizing the scope is bigger than expected, you are not alone. This is a hard problem. It is also one that doesn’t get easier the longer you wait.

Coming up at 2:00 PM this afternoon: Tune in to General Session II of the #NFB26 National Convention. You won't want to miss an exciting speech from our very own @Mike@social.pneumasolutions.com, directly following the Presidential Report.
Tune in via the following link:
http://cast.az-streamingserver.com:8590/stream
Alternatively, ask your Amazon device to "Open Nation's Blind".
OR access the station from your prefered accessible content consumption device!

**Update: Recent findings indicate this issue appears to have been resolved.**
Attention all #RemoteIncidentManager users, particularly those on #XFinity or #Comcast internet plans:
We have been made aware of, and been able to reproduce, an issue impacting downloads of the RIM installer when on XFinity networks.
It has come to our attention that XFinity's XFi Advanced Security has falsely-flagged the url for our RIM download endpoints as unsafe. This has resulted in failed attempts to download the RIM installer. Even in cases where the initial installer itself successfully downloads, the installer fails to fetch the data, thus resulting in a silent termination.
We are in communications with XFinity's escalations team and are doing our level best to ensure this issue's resolution as quickly as possible. Meanwhile, here are some immediate take-aways:
1. We wish to assure each and every one of you that Remote Incident manager is certifiably secure, with a security-by-default, privacy-first design from the outset. We as a company actively hold a SOC 2 Type II certification, which requires strict compliance with rigorous security standards. If you are a user who currently has a copy of RIM installed, rest assured that the program remains safe to use. What's more, existing installations are not impacted, and as such remain fully operational. This appears to only impact new installs, particularly under Comcast/XFinity service.
2. If you are in immediate need of a RIM installer and are impacted by this issue, we have found non-XFinity cellular hotspots or any other form of secondary network outside of XFinity to be an effective workaround. Download and run the installer while off of your main network. Once RIM has been installed, you can re-enable your main internet and continue to use RIM normally.
3. We encourage any impacted XFinity customers to submit unblock requests via their provided contact form. In order to do this:
A. Visit:
https://spa.xfinity.com/check_url_status
B. Enter the following URL:
https://rim.pneumacdn.net
C. Solve the Google re-captcha (no QR code required for this one), then click the "Submit" button. you will unfortunately not receive a confirmation of submission, so wait about ten seconds.
D. Navigate to and activate the line that says "clickable a request for re-assessment . ".
E. Fill out the resulting form that appears. the URL field should pre-populate. If not, enter:
https://rim.pneumacdn.net
before submission.
We apologize for the inconvenience and are again doing our best to ensure a quick resolution.

If you’re a state or local government entity serving a population of 50,000 or more, your #ADA #TitleII document accessibility deadline is April 24, 2026.
For organizations with large document archives, the biggest risk right now is not remediation. It is starting remediation without understanding what the archive actually contains.
That is why Pneuma Solutions is offering a Free Archive Readiness Assessment, which includes a representative 1,000-page remediation sample taken from your own documents.
Find out more: https://pneumasolutions.com/get-your-free-archive-readiness-assessment/
Contact us to book an assessment: https://pneumasolutions.com/contact/