No Stress Web Success is a friendly, practical podcast for leaders who want to understand web accessibility, WCAG, and maintaining a secure, compliant website without getting buried in the technical language. New episodes publish twice a week, with clear explanations and manageable steps you can take to your website and digital content.

In our first episode of No Stress Web Success, we introduce the Accessibility for Humans series that will break down WCAG accessibility standards in easy to manage pieces, starting this week with WCAG 1.1, or often called "ALT Tags".
We'll explain what the guidance is, who is affected by it, and what quick steps you can take to help make your website more accessible to those with various needs.

Welcome to the No Stress Web Success podcast from Fivepenny Web Studio.  This is our series, Web Understood. After a short intro to our studio, we'll discuss cookie notifications and policies, how they affect you both positively and negatively, and what you should be aware of when it comes to compliance and data.
If your website is using website analytics and advertising trackers, this is an episode you don't want to miss. 

What happens when important information on your website is delivered through audio? In this episode of No Stress Web Success, Accessibility for Humans, we explain WCAG 1.2 and why time-based audio content should include an accessible alternative, such as a transcript.
You’ll learn what time-based audio is, when transcripts are needed, what to check on your website, and how providing text alternatives helps more people access your content, including visitors who are deaf or hard of hearing, prefer reading, or cannot listen in their current environment.
We’ll also discuss practical examples for nonprofit and marketing websites, including podcasts, audio testimonials, recorded messages, and embedded media.
Learn how to apply this WCAG principle with clear, approachable guidance from Fivepenny Web Studio.
Topics covered:
WCAG 1.2 and time-based audio
Audio alternatives and transcripts
Captions vs. Subtitles
Common website accessibility barriers
Want to learn more?  Visit us at fivepennyweb.com
 

WordPress websites are powerful—but they can also be vulnerable when core software, plugins, themes, or page builders aren’t kept up to date.
In this episode of No Stress Web Success, we discuss recent WordPress Core and Elementor Builder vulnerabilities and the practical steps you can take to better protect your website. We’ll cover how to check your WordPress and Elementor versions, inventory your user accounts and access permissions, confirm that your backups are working, and clarify who is responsible for maintaining and securing your site.
We’ll also talk about an important question many website owners overlook: Do you know what to do if your website needs to be restored—and who would handle it?
For help getting organized, contact me at Fivepennyweb.com and ask for the Website Inventory Checklist. It’s a simple way to document your website, accounts, access, backups, and responsibilities before an emergency happens.

In Episode 5 of No Stress Web Success: Accessibility for Humans, we explain how to make important visual information in audio and video accessible on your website. We’ll look at WCAG 1.2.1, 1.2.3, and 1.2.5, and explore when to use descriptive transcripts or audio description. Then, try a simple review of one video on your website.

With the conversations around Squarespace, Wix, Shopify, Webflow and more, are the rumors of WordPress' pending demise accurate, and should your organization be concerned?
On this episode of No Stress Web Success, we discuss just this.  We look at the recent reports from W3Tech and HTTP Archive to see just where the stats stand.  Of course, not everything is black or white, so we'll look at the gray area as well.
Join us for our latest episode, and if you would like to view the reports yourself, you can find the W3Tech report at: https://w3techs.com/technologies/overview/content_management and GravityKit's post with the HTTP Archive data at: https://www.gravitykit.com/wordpress-market-share-2026/ 
As always, feel free to visit us at fivepennyweb.com with your questions, or leave us a review of this podcast to let us know how we're doing.

A page can look beautifully organized and still be a jumble to someone who can’t see it. In this episode of Accessibility for Humans, we explain WCAG 1.3.1, Info and Relationships, in plain language for nonprofit leaders and small teams who manage their own websites. You’ll learn how to check that your page areas, main content, headings, and lists are built the way they look, with simple things you can try today, no coding required. 
Resources: 
Free Chrome extension: WAVE Evaluation Tool
Free Chrome extension: Silktide Accessibility Checker
Have a question or a page you’re wrestling with? Reach out to us at fivepennyweb.com, and if you find No Stress Web Success helpful, leave feedback on the podcast wherever you listen.
 

Securing Your Nonprofit’s WordPress Website
Your nonprofit’s website is where donors give, volunteers sign up, and the people you serve look for help. If you manage it yourself, keeping that WordPress website secure is part of protecting your mission, but you don’t have to be a developer to do it.
In this episode, Lisa walks executive directors and small marketing teams through the essentials of a secure nonprofit website in plain language. You’ll learn why hosting matters, how to enforce HTTPS, which features to disable (like XML-RPC) and which to restrict instead (the REST API), how to set up two-factor authentication and much more. Some of these you can do this afternoon, and some you can hand to your host or web professional.
The 10-point checklist
Choose a WordPress-focused host with backups and a firewall.
Force HTTPS on every page, and use a hosted payment processor for donations.
Keep WordPress core, plugins, and your theme updated.
Delete unused plugins and themes, and vet the ones you keep.
Review your users, remove old accounts, and use the lowest role needed.
Turn on two-factor authentication, starting with administrators.
Limit login attempts and retire the “admin” username.
Disable XML-RPC if you don’t need it, and restrict (don’t remove) the REST API.
Ask your host or developer to confirm the basics: file editor off, correct permissions, a firewall.
Run automatic off-site backups, test a restore, and set up vulnerability and uptime alerts.
Resource mentionedCheck your HTTPS status and confirm your website is showing secured content over HTTPS by visiting: https://www.whynopadlock.com/
Take the next stepVisit fivepennyweb.com to learn how Fivepenny Web Studio helps nonprofits build accessible, secure WordPress websites.
Enjoyed the episode? Please leave a review wherever you listen. It helps other nonprofit leaders find the show.

In part two of our look at WCAG 1.3.1, Info and Relationships, we tackle the places where nonprofit websites struggle most: forms, tables, and meaning that depends on color or layout. You’ll learn how to make sure your donation, volunteer, and event forms work for everyone, why a red error message isn’t enough on its own, and how to make schedules and board lists easy to follow. We walk you through a simple page check you can run yourself, with no coding needed, and shares the most common mistakes to avoid. Written for nonprofit leaders and small teams who manage their own websites.
Have a question or a page you’re wrestling with? Send it at fivepennyweb.com, and please leave feedback on the podcast wherever you listen.

A critical PHP vulnerability hit the news this week, and if you have a WordPress website, it affects you. The good news is that you don’t need to be technical to handle it. You just need to know who is responsible for the fix and what to ask.
In this episode of No Stress Web Success, Lisa explains the PHP vulnerability in plain English: what it allows, why updating WordPress or your plugins won’t fix it, and why the repair has to happen on the server. You’ll learn the difference between the PHP your website uses and the PHP installed on the hosting server, and how shared hosting, isolated hosting (like Pressable and SiteGround), and private servers (like Cloudways and xCloud) change who protects you. We also break down what “patching” really means: installed, restarted, and checked.
Don’t panic, but do ask. Here are five questions to send to your host or web developer:
On my plan, who is responsible for patching PHP: you, me, or my developer?
Has the October 21st PHP security release been applied to my site’s server, and when?
What PHP version am I on, is the whole server covered, and is that version still supported?
If the full fix isn’t in place yet, what protection is active right now, and when will the real fix land?
After patching, will anyone check my site for signs of anything that happened before the fix, and what happens if you find something?
As always, if you have questions about your own site, reach out to us at fivepennyweb.com and leave us a review wherever you listen to your favorite podcasts.