Sign in to view Eric’s full profile
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Sign in to view Eric’s full profile
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Cleveland, Ohio, United States
Sign in to view Eric’s full profile
Eric can introduce you to 3 people at Igalia
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
2K followers
395 connections
Sign in to view Eric’s full profile
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
View mutual connections with Eric
Eric can introduce you to 3 people at Igalia
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
View mutual connections with Eric
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Sign in to view Eric’s full profile
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Websites
- Personal Site
-
http://meyerweb.com/
- Complex Spiral Consulting
-
http://complexspiral.com/
- An Event Apart
-
http://aneventapart.com/
About
Welcome back
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
New to LinkedIn? Join now
Activity
2K followers
-
Eric Meyer reposted thisEric Meyer reposted this🎙️ New Episode of Igalia Chats Interop 2026: Spec-tacular Alignment. Eric Meyer and Brian Kardell chat about the annual launch of the Interop project... https://lnkd.in/ed6e886D
-
Eric Meyer reposted thisEric Meyer reposted thisThe web team at Kraken is growing again, and we are in search of a talented designer who has a strong understanding of frontend code to join my team. If you know someone who would be a great fit or have any recommendations, please reach out. I'm biased, but I think we have a really great team. For more details, check out the job listing: https://lnkd.in/e8Zw-Det
-
Eric Meyer reposted thisEarly last year I ventured out on my own again, taking on contract design work after a long stretch away. Not long after, I settled on a name to work under, and now I’m excited to share that name and a website to go along with it: Loud Room. The name is inspired in part by my time in Brooklyn working in shared spaces with friends, but honestly, I also just liked the sound and look of it. It feels a little mysterious and kinetic, and the rhythm of two four-letter words is handy for a logo. Once I managed to reclaim the domain from a squatter, it felt like everything had aligned. Loud Room is me, and it may always be just me. As I wrote last year, I want to stay small to get closer to the work and create space for quality. I want to work directly with clients who care about craft and want to dig into the details of where their projects could go. I bring deep experience across many types of design, including branding, product, publishing, and marketing. I enjoy wearing all of those hats, whether on a one-off project or as a founding designer helping companies that are just starting out. I’m aiming to work with local clients when possible, as well as organizations trying to make the world better. I’m trying to build something sustainable, and I want to work with people who are doing the same. With so much upheaval in the world, I want to put my energy into useful work and relationships that help people, even in small ways. When projects need more hands, I pull in trusted colleagues to help, something I’ve already done a few times since last year. I’m enjoying the energy of reconnecting with other freelancers and supporting one another along the way. A New Website: The Loud Room website is intentionally minimal right now. It’s less a portfolio and more a statement of purpose, something to put out into the world. The site will evolve over time, and I’ll add work samples as projects wrap up. For now, I’m comfortable with the simplicity and the small amount of friction in asking someone to read a few paragraphs. I had a blast creating the logo and making a simple static website without any frameworks. I can’t stop using HEX Franklin, and I’ve always wanted to make a site with a randomizing color palette. I tried to ensure that each color scheme maintains enough contrast for basic accessibility, and love the bit of chaos when a garish palette shows up. I’ve also moved all of my font designs under Loud Room, which will now serve as my foundry. I admire the multidisciplinary models of companies like Coudal Partners, Panic, and Young Jerks, and I want Loud Room to be a place where I can experiment, play, and make things that don’t fit neatly into one category. Fonts are the focus right now, but not the limit. If you care about craft, working closely with humans, and not having generic design spat out by a machine, consider me for your next project. https://loudroom.com/Eric Meyer reposted thisSay hello to Loud Room, a small design practice focused on craft, learning, and human relationships. https://loudroom.com/
-
Eric Meyer reposted thisEric Meyer reposted thisMy book, Accessibility For Everyone, is now free and online as a website. https://lnkd.in/dyN59U9i The book was first published by A Book Apart in 2017 but it holds up! It covers web accessibility for designers, developers, content folks, and really everyone who works in tech. Even though the book is nearly nine years old, I get regular requests for where to buy it, and universities and colleges still include it on their reading lists. I’ll add the audiobook files to the site in the next few weeks. And I’m considering other platforms and formats that might make Accessibility For Everyone easier to access. Please let me know if you have a preference, I’m still not 100% sure where’s best to focus my time.
-
Eric Meyer shared thisWe had fun.Eric Meyer shared thisIf you missed it live, you can watch James Stuckey Weber & Miriam Suzanne's chat with Eric Meyer about Anchor Positioning now on the Winging It show. Includes: - Emerging patterns - Rough edges - Will Anchor Positioning be baseline? - What's next for Anchor Positioning? https://lnkd.in/gNJsfKYn #css
-
Eric Meyer reposted thisEric Meyer reposted this🎙️ New Episode of Igalia Chats: Accessibility and the Free Labor Funnel Brian Kardell and Eric Meyer chat with their colleagues Alice Boxhall and Valerie Young about the challenges facing standards and accessibility. https://lnkd.in/edYT-xxv
-
Eric Meyer reposted thisEric Meyer reposted this🎙 New Episode of Igalia Chats: RIP XSLT? Igalia's Brian Kardell and Eric Meyer chat with Liam Quin about a recent issue in WHATWG regarding the removal of XSLT https://lnkd.in/e3ZzaqjG
-
Eric Meyer reposted thisEric Meyer reposted this"Standards, Inc: Inside the new, old organization with Seth Dobbs" Last week Brian Kardell and Eric Meyer spoke with Seth Dobbs on the Igalia podcast. They discussed W3C, how Seth became CEO and the Vision for W3C: Seth: "So the principles help emphasize what's important in operating and running and making the day to day. But the core vision, there's four key pieces that are the core vision of the World Wide Web. First is that the web is for all humanity. Second is that the web is designed for the good of all people. Third is that the web must be safe to use. And fourth, there is one interoperable, World Wide Web..." Eric Meyer: "...even if it's the first vision statement that W3C has ever had. It's almost saying, 'Well, this is what we've been doing. This has been the vision. We've just written it down now" https://lnkd.in/gSiC8VPu
-
Eric Meyer shared thisI was surprised by how many things Chrome (and browsers in general) have intentionally removed over the years, and heartened to hear more about the process that goes into removing anything. You might be as well; give it a listen!Eric Meyer shared this🎙️ New Episode of Igalia Chats Unshipping: How (and when) to break web features Brian Kardell and Eric Meyer chat with Google's Rick Byers about willingness to change and even unship features https://lnkd.in/eWNMBcN3
-
Eric Meyer liked thisEric Meyer liked this🎙 New Episode of Igalia Chats: RIP XSLT? Igalia's Brian Kardell and Eric Meyer chat with Liam Quin about a recent issue in WHATWG regarding the removal of XSLT https://lnkd.in/e3ZzaqjG
Experience & Education
-
Igalia
********* ********
-
******* ****** **********
********* **********
-
****
**********
-
**** ******* ******* **********
**** ******* undefined
-
-
********* **** ******
**** ****** undefined ***
-
View Eric’s full experience
See their title, tenure and more.
Welcome back
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
New to LinkedIn? Join now
or
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Honors & Awards
-
Web Platform Award 2015
O'Reilly Media
Languages
-
American Sign Language (very basic)
-
Organizations
-
Membership, International Academy of Digital Arts and Sciences
-
- Present
Recommendations received
4 people have recommended Eric
Join now to viewView Eric’s full profile
-
See who you know in common
-
Get introduced
-
Contact Eric directly
Other similar profiles
-
Alex O'Byrne
Alex O'Byrne
Money Monster - Fully automated and transparent trading system
7K followersMiami Beach, FL -
Nick Brandt
Nick Brandt
I have spent the past 30 years managing SaaS projects, remote teams, and hiring globally.<br><br>I am a developer by trade, with extensive experience in recruitment and team management. I continue to develop and specialize in AI and ML web and mobile applications.<br><br>My previous experience now enables me to offer our clients at Thankz a wealth of hands-on expertise.<br><br>My interests include travel, photography, art, working out at the gym, and cooking.
25K followersPorto
Explore more posts
-
Accesera
1 follower
How do you write alt texts for scientific figures? It’s one of the hardest accessibility tasks: charts, diagrams, and multi-panel figures often have dense information, and the people adding descriptions are frequently DSO staff, accessibility specialists, librarians, editors, or remediation teams—not the original authors or subject experts. That’s exactly why we built SciAlt by Accesera: to support a practical workflow for creating science-figure descriptions that are clearer, more consistent, and easier to produce at scale. Even if you are a researcher, you will benefit significantly from using SciAlt to write alt text for your publications. Start a free trial — generate up to 5 science-figure alt texts per month at no cost. https://lnkd.in/gXAicWa8 I’d love to hear your approach: when you write science-figure alt text, what do you do first? #Accessibility #DigitalAccessibility #A11y #AltText #ImageDescription #AccessibleSTEM #ScienceCommunication #DataVisualization #AccessibleDocuments #AccessiblePublishing #WCAG #Section508 #AssistiveTechnology #InclusiveDesign #HigherEdAccessibility
1
-
Ka Li
Georgia Institute of… • 273 followers
I'm glad to see BIK taking a strong stance against accessibility overlays on websites. These overlays don't make websites more accessible. They end up offering a poorer user experience and makes debugging accessibility issues more challenging for developers as they unnecessarily add an additional layer of complexity. https://lnkd.in/eTBpNErY
15
-
Judy Nollet
Creative and organized… • 1K followers
A recording of Nathanial Hilliard's wonderful presentation, "JavaScript for the Rest of Us," is available online. He also compiled an incredible list of resources. This is aimed at #Storyline users, but I think this would be helpful for anyone who's interested in (yet perhaps a bit afraid of) learning JS. Thanks, Nathanial, for putting so much effort into helping the Articulate community! https://lnkd.in/gd5znBQT
4
2 Comments -
Accessible.org
153 followers
Screen reader testing is essential to an accessibility audit, but what environment combinations should you use? In the Medium article below, I outline Accessible.org's default environments. Clients can always opt for more, but we use WebAIM screen reader survey data to choose popular environment combinations that have far reaching impact. Medium link: https://lnkd.in/gX7WEyyS #ScreenReaderTesting #AccessibilityAudits #AccessibilityAudit #WCAGAudit #DigitalAccessibility #WebAccessibility
-
WebCraft
1K followers
💥 Let’s be honest: most “web accessibility solutions” don’t actually work. Accessibility Overlays?!?!? My Custom-AI Remediation Engine calls the overlay code — "garbage in, garbage out." 🙅♀️ They’re band-aids, with false promises of healing— and too often, they make things worse. As a U.S. Department of Homeland Security Trusted Tester, I’ve seen firsthand how overlays can destroy otherwise functional code. Here’s the truth: 🧩 Assistive Technology was never built to work with broken markup or lazy code. 💸 Manual audits are ridiculously expensive — and the moment you deploy new code, they’re already obsolete. 🐢 The entire approach is reactive, not preventative. That’s why WebCraft, the company I founded, built something different: an AI-powered Accessibility Firewall. 🛡️♿⚙️ Think of it like a WAF (Web Application Firewall) — but for Inclusion. It sits in front of your website and actively remediates accessibility issues in real time, before they ever reach your users. Our Proof of Concept is established already. This isn’t about flagging errors. It’s about preventing them automatically — making the web accessible instantly and keeping it that way without trapping developers in an endless loop of fixes. 💭 I’d love your thoughts: What’s the most ridiculous “fix” you’ve seen from an accessibility overlay? Developers, what’s your biggest frustration with the current state of #a11y? Let’s fix accessibility at the root — not just patch it. #WebAccessibility #AI #SaaS #TechInnovation #Developer #Inclusion -Steph F. (Stephanie F.) CEO/Founder of WebCraft Technical Engineer of The World's First Accessibility Firewall (accessibilityfirewall .com launching next month) Image ID: A person smiling warmly in a well-lit room with long, light-blonde braids, wearing a black top. Behind them, there’s a colorful painting featuring flowers and a starry sky, vertical blinds letting in natural light, and a lamp with glowing bulb-shaped lights on a desk.
29
10 Comments -
assistive.consulting
300 followers
🧾 Your archive is massive. Your accessibility budget isn't. ✅ Solution: Accessible Archive From Pneuma Solutions 🔗 https://lnkd.in/eEe5c3nZ 📅 ADA Title II Deadline: April 24, 2026 🔗 https://title2.info/ State & local governments (population 50,000+) must ensure websites, mobile apps, and digital documents comply with WCAG 2.1 Level AA. Universities, libraries, and public agencies share the same reality: decades of PDFs/scans in “permanent” archives, and a legal + ethical obligation to make them accessible. Manually remediating millions of files isn't a strategy; it's an open liability. That's why Pneuma Solutions built Accessible Archive. 🎯 Built For University/academic libraries; public libraries/state archives; museums/cultural institutions; government agencies/records offices; large enterprises with document management systems full of old PDFs. If you own legacy content + accessibility (or lawsuits), it's for you. 🧠 Just-In-Time Accessibility Traditional: “Remediate everything up front, or not at all.” Slow, expensive, usually cut halfway. ✅ New Model: 📄 User requests a doc (catalog/DMS/portal). 📄 It converts that file to accessible formats: HTML, tagged PDF, MP3, braille, large print. 📄 Result is cached. 📄 As the engine improves, the same file can be auto-reprocessed to a higher standard. 👉 You stop paying to fix documents nobody reads. ⚙️ Fits Your Existing Stack Add an “Accessible version” button in your catalog/repository/intranet. Click → your system calls the API; user picks a format; delivery in seconds/minutes, not weeks. Deploy in cloud (general collections) or on-prem/private appliance (content stays inside your network). All traffic is encrypted; you control what's retained beyond caching + audit evidence. 📊 Compliance, With Receipts Not just files: timestamps, pipeline/version info, and input/output hashes to prove which file became which accessible version. Align with WCAG + PDF/UA, and show auditors/regulators what you did at scale. 💰 Economics Shift From high cost/page x small subset → low cost/page x documents people actually use. You eliminate one-off remediation projects, reduce backlog + accommodation response times, and make measurable monthly progress. ✅ For Leaders of Large Collections If a person with a print disability browsed your archive today: how many docs could they use, and what proof shows systemic progress (not just complaints)? If that answer is uncomfortable, pilot one collection/repository and see what happens when accessibility becomes a service that runs every time someone clicks “Accessible version.” Pneuma Solutions Access Information News Top Tech Tidbits
1
-
Top Tech Tidbits
151 followers
🧾 Your archive is massive. Your accessibility budget isn't. ✅ Solution: Accessible Archive From Pneuma Solutions 🔗 https://lnkd.in/eEe5c3nZ 📅 ADA Title II Deadline: April 24, 2026 🔗 https://title2.info/ State & local governments (population 50,000+) must ensure websites, mobile apps, and digital documents comply with WCAG 2.1 Level AA. Universities, libraries, and public agencies share the same reality: decades of PDFs/scans in “permanent” archives, and a legal + ethical obligation to make them accessible. Manually remediating millions of files isn't a strategy; it's an open liability. That's why Pneuma Solutions built Accessible Archive. 🎯 Built For University/academic libraries; public libraries/state archives; museums/cultural institutions; government agencies/records offices; large enterprises with document management systems full of old PDFs. If you own legacy content + accessibility (or lawsuits), it's for you. 🧠 Just-In-Time Accessibility Traditional: “Remediate everything up front, or not at all.” Slow, expensive, usually cut halfway. ✅ New Model: 📄 User requests a doc (catalog/DMS/portal). 📄 It converts that file to accessible formats: HTML, tagged PDF, MP3, braille, large print. 📄 Result is cached. 📄 As the engine improves, the same file can be auto-reprocessed to a higher standard. 👉 You stop paying to fix documents nobody reads. ⚙️ Fits Your Existing Stack Add an “Accessible version” button in your catalog/repository/intranet. Click → your system calls the API; user picks a format; delivery in seconds/minutes, not weeks. Deploy in cloud (general collections) or on-prem/private appliance (content stays inside your network). All traffic is encrypted; you control what's retained beyond caching + audit evidence. 📊 Compliance, With Receipts Not just files: timestamps, pipeline/version info, and input/output hashes to prove which file became which accessible version. Align with WCAG + PDF/UA, and show auditors/regulators what you did at scale. 💰 Economics Shift From high cost/page x small subset → low cost/page x documents people actually use. You eliminate one-off remediation projects, reduce backlog + accommodation response times, and make measurable monthly progress. ✅ For Leaders of Large Collections If a person with a print disability browsed your archive today: how many docs could they use, and what proof shows systemic progress (not just complaints)? If that answer is uncomfortable, pilot one collection/repository and see what happens when accessibility becomes a service that runs every time someone clicks “Accessible version.” Pneuma Solutions Access Information News Top Tech Tidbits
1
-
Mind Vault Solutions, Ltd.
89 followers
🧾 Your archive is massive. Your accessibility budget isn't. ✅ Solution: Accessible Archive From Pneuma Solutions 🔗 https://lnkd.in/eEe5c3nZ 📅 ADA Title II Deadline: April 24, 2026 🔗 https://title2.info/ State & local governments (population 50,000+) must ensure websites, mobile apps, and digital documents comply with WCAG 2.1 Level AA. Universities, libraries, and public agencies share the same reality: decades of PDFs/scans in “permanent” archives, and a legal + ethical obligation to make them accessible. Manually remediating millions of files isn't a strategy; it's an open liability. That's why Pneuma Solutions built Accessible Archive. 🎯 Built For University/academic libraries; public libraries/state archives; museums/cultural institutions; government agencies/records offices; large enterprises with document management systems full of old PDFs. If you own legacy content + accessibility (or lawsuits), it's for you. 🧠 Just-In-Time Accessibility Traditional: “Remediate everything up front, or not at all.” Slow, expensive, usually cut halfway. ✅ New Model: 📄 User requests a doc (catalog/DMS/portal). 📄 It converts that file to accessible formats: HTML, tagged PDF, MP3, braille, large print. 📄 Result is cached. 📄 As the engine improves, the same file can be auto-reprocessed to a higher standard. 👉 You stop paying to fix documents nobody reads. ⚙️ Fits Your Existing Stack Add an “Accessible version” button in your catalog/repository/intranet. Click → your system calls the API; user picks a format; delivery in seconds/minutes, not weeks. Deploy in cloud (general collections) or on-prem/private appliance (content stays inside your network). All traffic is encrypted; you control what's retained beyond caching + audit evidence. 📊 Compliance, With Receipts Not just files: timestamps, pipeline/version info, and input/output hashes to prove which file became which accessible version. Align with WCAG + PDF/UA, and show auditors/regulators what you did at scale. 💰 Economics Shift From high cost/page x small subset → low cost/page x documents people actually use. You eliminate one-off remediation projects, reduce backlog + accommodation response times, and make measurable monthly progress. ✅ For Leaders of Large Collections If a person with a print disability browsed your archive today: how many docs could they use, and what proof shows systemic progress (not just complaints)? If that answer is uncomfortable, pilot one collection/repository and see what happens when accessibility becomes a service that runs every time someone clicks “Accessible version.” Pneuma Solutions Access Information News Top Tech Tidbits
1
-
Email Markup Consortium
872 followers
Here's the top 10 issues from the 2024 Accessibility Report as we count down to the release of Email Markup Consortium's 2025 Accessibility Report. 8️⃣ Missing <title> 34.95 % of emails ship with no document title. Tabs, screen‑reader navigation and “view‑in‑browser” pages all get harder. Fix it today → drop a concise <title> tag at the top of your HTML. Using the subject line works if it’s descriptive. Hit “Follow” to make sure you know about the 2025 Email Markup Consortium Accessibility Report as soon as it comes out on May 15! #HTMLemail #Accessibility
19
-
Pneuma Solutions
204 followers
🧾 Your archive is massive. Your accessibility budget isn't. ✅ Solution: Accessible Archive From Pneuma Solutions 🔗 https://lnkd.in/eEe5c3nZ 📅 ADA Title II Deadline: April 24, 2026 🔗 https://title2.info/ State & local governments (population 50,000+) must ensure websites, mobile apps, and digital documents comply with WCAG 2.1 Level AA. Universities, libraries, and public agencies share the same reality: decades of PDFs/scans in “permanent” archives, and a legal + ethical obligation to make them accessible. Manually remediating millions of files isn't a strategy; it's an open liability. That's why Pneuma Solutions built Accessible Archive. 🎯 Built For University/academic libraries; public libraries/state archives; museums/cultural institutions; government agencies/records offices; large enterprises with document management systems full of old PDFs. If you own legacy content + accessibility (or lawsuits), it's for you. 🧠 Just-In-Time Accessibility Traditional: “Remediate everything up front, or not at all.” Slow, expensive, usually cut halfway. ✅ New Model: 📄 User requests a doc (catalog/DMS/portal). 📄 It converts that file to accessible formats: HTML, tagged PDF, MP3, braille, large print. 📄 Result is cached. 📄 As the engine improves, the same file can be auto-reprocessed to a higher standard. 👉 You stop paying to fix documents nobody reads. ⚙️ Fits Your Existing Stack Add an “Accessible version” button in your catalog/repository/intranet. Click → your system calls the API; user picks a format; delivery in seconds/minutes, not weeks. Deploy in cloud (general collections) or on-prem/private appliance (content stays inside your network). All traffic is encrypted; you control what's retained beyond caching + audit evidence. 📊 Compliance, With Receipts Not just files: timestamps, pipeline/version info, and input/output hashes to prove which file became which accessible version. Align with WCAG + PDF/UA, and show auditors/regulators what you did at scale. 💰 Economics Shift From high cost/page x small subset → low cost/page x documents people actually use. You eliminate one-off remediation projects, reduce backlog + accommodation response times, and make measurable monthly progress. ✅ For Leaders of Large Collections If a person with a print disability browsed your archive today: how many docs could they use, and what proof shows systemic progress (not just complaints)? If that answer is uncomfortable, pilot one collection/repository and see what happens when accessibility becomes a service that runs every time someone clicks “Accessible version.” Pneuma Solutions Access Information News Top Tech Tidbits
-
Dr. Kirk Adams
56 followers
🧾 Your archive is massive. Your accessibility budget isn't. ✅ Solution: Accessible Archive From Pneuma Solutions 🔗 https://lnkd.in/eEe5c3nZ 📅 ADA Title II Deadline: April 24, 2026 🔗 https://title2.info/ State & local governments (population 50,000+) must ensure websites, mobile apps, and digital documents comply with WCAG 2.1 Level AA. Universities, libraries, and public agencies share the same reality: decades of PDFs/scans in “permanent” archives, and a legal + ethical obligation to make them accessible. Manually remediating millions of files isn't a strategy; it's an open liability. That's why Pneuma Solutions built Accessible Archive. 🎯 Built For University/academic libraries; public libraries/state archives; museums/cultural institutions; government agencies/records offices; large enterprises with document management systems full of old PDFs. If you own legacy content + accessibility (or lawsuits), it's for you. 🧠 Just-In-Time Accessibility Traditional: “Remediate everything up front, or not at all.” Slow, expensive, usually cut halfway. ✅ New Model: 📄 User requests a doc (catalog/DMS/portal). 📄 It converts that file to accessible formats: HTML, tagged PDF, MP3, braille, large print. 📄 Result is cached. 📄 As the engine improves, the same file can be auto-reprocessed to a higher standard. 👉 You stop paying to fix documents nobody reads. ⚙️ Fits Your Existing Stack Add an “Accessible version” button in your catalog/repository/intranet. Click → your system calls the API; user picks a format; delivery in seconds/minutes, not weeks. Deploy in cloud (general collections) or on-prem/private appliance (content stays inside your network). All traffic is encrypted; you control what's retained beyond caching + audit evidence. 📊 Compliance, With Receipts Not just files: timestamps, pipeline/version info, and input/output hashes to prove which file became which accessible version. Align with WCAG + PDF/UA, and show auditors/regulators what you did at scale. 💰 Economics Shift From high cost/page x small subset → low cost/page x documents people actually use. You eliminate one-off remediation projects, reduce backlog + accommodation response times, and make measurable monthly progress. ✅ For Leaders of Large Collections If a person with a print disability browsed your archive today: how many docs could they use, and what proof shows systemic progress (not just complaints)? If that answer is uncomfortable, pilot one collection/repository and see what happens when accessibility becomes a service that runs every time someone clicks “Accessible version.” Pneuma Solutions Access Information News Top Tech Tidbits
-
Access Information News
56 followers
🧾 Your archive is massive. Your accessibility budget isn't. ✅ Solution: Accessible Archive From Pneuma Solutions 🔗 https://lnkd.in/eEe5c3nZ 📅 ADA Title II Deadline: April 24, 2026 🔗 https://title2.info/ State & local governments (population 50,000+) must ensure websites, mobile apps, and digital documents comply with WCAG 2.1 Level AA. Universities, libraries, and public agencies share the same reality: decades of PDFs/scans in “permanent” archives, and a legal + ethical obligation to make them accessible. Manually remediating millions of files isn't a strategy; it's an open liability. That's why Pneuma Solutions built Accessible Archive. 🎯 Built For University/academic libraries; public libraries/state archives; museums/cultural institutions; government agencies/records offices; large enterprises with document management systems full of old PDFs. If you own legacy content + accessibility (or lawsuits), it's for you. 🧠 Just-In-Time Accessibility Traditional: “Remediate everything up front, or not at all.” Slow, expensive, usually cut halfway. ✅ New Model: 📄 User requests a doc (catalog/DMS/portal). 📄 It converts that file to accessible formats: HTML, tagged PDF, MP3, braille, large print. 📄 Result is cached. 📄 As the engine improves, the same file can be auto-reprocessed to a higher standard. 👉 You stop paying to fix documents nobody reads. ⚙️ Fits Your Existing Stack Add an “Accessible version” button in your catalog/repository/intranet. Click → your system calls the API; user picks a format; delivery in seconds/minutes, not weeks. Deploy in cloud (general collections) or on-prem/private appliance (content stays inside your network). All traffic is encrypted; you control what's retained beyond caching + audit evidence. 📊 Compliance, With Receipts Not just files: timestamps, pipeline/version info, and input/output hashes to prove which file became which accessible version. Align with WCAG + PDF/UA, and show auditors/regulators what you did at scale. 💰 Economics Shift From high cost/page x small subset → low cost/page x documents people actually use. You eliminate one-off remediation projects, reduce backlog + accommodation response times, and make measurable monthly progress. ✅ For Leaders of Large Collections If a person with a print disability browsed your archive today: how many docs could they use, and what proof shows systemic progress (not just complaints)? If that answer is uncomfortable, pilot one collection/repository and see what happens when accessibility becomes a service that runs every time someone clicks “Accessible version.” Pneuma Solutions Access Information News Top Tech Tidbits
-
AT-Newswire
20 followers
🧾 Your archive is massive. Your accessibility budget isn't. ✅ Solution: Accessible Archive From Pneuma Solutions 🔗 https://lnkd.in/eEe5c3nZ 📅 ADA Title II Deadline: April 24, 2026 🔗 https://title2.info/ State & local governments (population 50,000+) must ensure websites, mobile apps, and digital documents comply with WCAG 2.1 Level AA. Universities, libraries, and public agencies share the same reality: decades of PDFs/scans in “permanent” archives, and a legal + ethical obligation to make them accessible. Manually remediating millions of files isn't a strategy; it's an open liability. That's why Pneuma Solutions built Accessible Archive. 🎯 Built For University/academic libraries; public libraries/state archives; museums/cultural institutions; government agencies/records offices; large enterprises with document management systems full of old PDFs. If you own legacy content + accessibility (or lawsuits), it's for you. 🧠 Just-In-Time Accessibility Traditional: “Remediate everything up front, or not at all.” Slow, expensive, usually cut halfway. ✅ New Model: 📄 User requests a doc (catalog/DMS/portal). 📄 It converts that file to accessible formats: HTML, tagged PDF, MP3, braille, large print. 📄 Result is cached. 📄 As the engine improves, the same file can be auto-reprocessed to a higher standard. 👉 You stop paying to fix documents nobody reads. ⚙️ Fits Your Existing Stack Add an “Accessible version” button in your catalog/repository/intranet. Click → your system calls the API; user picks a format; delivery in seconds/minutes, not weeks. Deploy in cloud (general collections) or on-prem/private appliance (content stays inside your network). All traffic is encrypted; you control what's retained beyond caching + audit evidence. 📊 Compliance, With Receipts Not just files: timestamps, pipeline/version info, and input/output hashes to prove which file became which accessible version. Align with WCAG + PDF/UA, and show auditors/regulators what you did at scale. 💰 Economics Shift From high cost/page x small subset → low cost/page x documents people actually use. You eliminate one-off remediation projects, reduce backlog + accommodation response times, and make measurable monthly progress. ✅ For Leaders of Large Collections If a person with a print disability browsed your archive today: how many docs could they use, and what proof shows systemic progress (not just complaints)? If that answer is uncomfortable, pilot one collection/repository and see what happens when accessibility becomes a service that runs every time someone clicks “Accessible version.” Pneuma Solutions Access Information News Top Tech Tidbits
-
The Blind Visionary
13 followers
🧾 Your archive is massive. Your accessibility budget isn't. ✅ Solution: Accessible Archive From Pneuma Solutions 🔗 https://lnkd.in/eEe5c3nZ 📅 ADA Title II Deadline: April 24, 2026 🔗 https://title2.info/ State & local governments (population 50,000+) must ensure websites, mobile apps, and digital documents comply with WCAG 2.1 Level AA. Universities, libraries, and public agencies share the same reality: decades of PDFs/scans in “permanent” archives, and a legal + ethical obligation to make them accessible. Manually remediating millions of files isn't a strategy; it's an open liability. That's why Pneuma Solutions built Accessible Archive. 🎯 Built For University/academic libraries; public libraries/state archives; museums/cultural institutions; government agencies/records offices; large enterprises with document management systems full of old PDFs. If you own legacy content + accessibility (or lawsuits), it's for you. 🧠 Just-In-Time Accessibility Traditional: “Remediate everything up front, or not at all.” Slow, expensive, usually cut halfway. ✅ New Model: 📄 User requests a doc (catalog/DMS/portal). 📄 It converts that file to accessible formats: HTML, tagged PDF, MP3, braille, large print. 📄 Result is cached. 📄 As the engine improves, the same file can be auto-reprocessed to a higher standard. 👉 You stop paying to fix documents nobody reads. ⚙️ Fits Your Existing Stack Add an “Accessible version” button in your catalog/repository/intranet. Click → your system calls the API; user picks a format; delivery in seconds/minutes, not weeks. Deploy in cloud (general collections) or on-prem/private appliance (content stays inside your network). All traffic is encrypted; you control what's retained beyond caching + audit evidence. 📊 Compliance, With Receipts Not just files: timestamps, pipeline/version info, and input/output hashes to prove which file became which accessible version. Align with WCAG + PDF/UA, and show auditors/regulators what you did at scale. 💰 Economics Shift From high cost/page x small subset → low cost/page x documents people actually use. You eliminate one-off remediation projects, reduce backlog + accommodation response times, and make measurable monthly progress. ✅ For Leaders of Large Collections If a person with a print disability browsed your archive today: how many docs could they use, and what proof shows systemic progress (not just complaints)? If that answer is uncomfortable, pilot one collection/repository and see what happens when accessibility becomes a service that runs every time someone clicks “Accessible version.” Pneuma Solutions Access Information News Top Tech Tidbits
-
BlueIrisIQ™
4K followers
📊 🏛️ More than 80% of accessibility issues in government aren’t on websites — they’re buried inside documents. With ADA Title II now requiring WCAG‑compliant PDFs, agencies need a scalable way to fix backlogs and prevent new non‑compliant files. ✅ We break down a four‑step approach that works with existing repositories like SharePoint, CMS libraries, Box, and OneDrive. ➡️ https://ow.ly/Ny2l50Yip6H
9
-
Accessibility On-Demand™ (AoD™)
109 followers
Great to see organizations expanding their accessibility capabilities and helping clients address digital inclusion at scale. As accessibility expectations and regulatory pressure continue to grow, scalable approaches to document accessibility are becoming essential. #DigitalAccessibility #WCAG #InclusiveTechnology #Accessibility #Enterprise #PrivateSector #AccessibilityOnDemand #AoD
1
-
National Network for Equitable Library Service
601 followers
Are you interested in accessibility metadata? The W3 Community Group has published the “Accessibility Metadata Display Guide for Digital Publications 2.0” guidelines. Accessibility metadata details the features of digital publications like visual adjustments, image descriptions, and screen reader compatibility, which are valuable for everyone to understand. The guidelines outline how to present accessibility metadata for end users so they can find and read the books with the accessibility features they need. You can read the report here: https://lnkd.in/e8fYEXdk
3
-
AltText.ai
101 followers
Hot take: "we added an accessibility overlay" is no longer a legal defense. The Domino's case made it pretty clear that overlays don't satisfy ADA requirements. Courts want structural fixes (like, in the actual code). And here's the stat that should get your attention: 96.3% of websites fail basic WCAG tests 😱🤯 That's not a niche compliance issue. That's almost every website on the internet. Meanwhile, AI search engines (ChatGPT, Perplexity, Claude) are crawling the web and reading alt text to understand your images. No alt text = invisible products. Accessibility and AI visibility used to be separate conversations. They're not anymore. Scan your site free to understand how many images are missing alt text → https://bit.ly/4sXdzB7
1
Explore top content on LinkedIn
Find curated posts and insights for relevant topics all in one place.
View top contentOthers named Eric Meyer
-
Eric Meyer
Berkeley, CA -
Eric Meyer
Greater St. Louis -
Eric Meyer
United States -
Eric Meyer
Luxembourg -
Eric Meyer
Greater Sacramento
803 others named Eric Meyer are on LinkedIn
See others named Eric Meyer