Make All WordPress Events Accessible  🔗 **Source:** [Make All WordPress Events Accessible](https://www.youtube.com/watch?v=58qAh9x3Ax8) > [!note]+ Document Notes > tags: [wordpress-accessibility, event-accessibility, wordcamp-organizing, disability-advocacy, live-captioning, venue-accessibility] > author: Joe Simpson Jr. > source: WordPress Accessibility Day 2025 > reference: https://www.youtube.com/watch?v=58qAh9x3Ax8 > date created: 2026-09-08 > > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > > # 🏷️ Title: Make All WordPress Events Accessible > <!-- deep-read:sections start --> ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) - [🔄 Refactor Appendix](#-refactor-appendix--make-all-wordpress-events-accessible) ### 🔗 References - [Video: Make All WordPress Events Accessible (WordPress Accessibility Day 2025)](https://www.youtube.com/watch?v=58qAh9x3Ax8) - [Make WordPress Accessible team](https://make.wordpress.org/accessibility/) - [WordCamp Organizer Handbook](https://make.wordpress.org/community/handbook/wordcamp-organizer-handbook/) - [W3C Web Accessibility Initiative](https://www.w3.org/WAI/) - [WordPress Accessibility Day 2025 feedback form](https://2025.wpaccessibility.day/feedback) ## 📝 Summary - **What happened.** Joe Simpson Jr. — front-end developer, WordCamp organizer, and member of the Make WordPress Accessible and Training teams — gave a talk at WordPress Accessibility Day 2025, moderated by Sherose Badruddin (Digital Accessibility Consultant, University of North Carolina), reframing "Make WordPress Accessible" (the software project) into "Make All WordPress Events Accessible" (the in-person and online gatherings the community runs). - **Why it matters.** Joe opens with a heart-surgery story (two 100% blocked arteries, a 90-day medical leave) that reframed his priorities and led him back into WordPress community organizing; from there he lays out a checklist-driven, experience-tested method for building accessibility into venue selection, wayfinding, live captioning, speaker requirements, and event websites, based on his time organizing WordCamp US in San Diego and National Harbor and three Santa Clarita-area meetups. - **Key stakeholders.** WordCamp/meetup organizers and organizing-team captains, the Make WordPress Accessible team, disabled community members who contributed specific fixes on the record — Michelle Frechette (venue-access account of Town and Country resort), Alex Stein (blind team member, wayfinding format), Ryan Bourne (distance badges, pre-recorded content), Meryl Evans and Rachel Lowenstein (speaker/attendee experience accounts) — and event sponsors who fund captioning vendors. - **Risks and tradeoffs.** Joe names budget as the recurring blocker: live captioning and ASL are the first things cut at low-budget meetups, and he treats Zoom's auto-caption-plus-manual-cleanup as a stopgap, not a solution. Venue accessibility decisions made without a physical, disability-aware tour (his Town and Country resort story) surface as post-event complaints instead of pre-event fixes. - **Bottom line.** Accessibility work at WordPress events is operational, not aspirational: tour venues early with a disabled team member, publish wayfinding in at least three formats, staff a dedicated accessibility team distinct from Attendee Experience, and fund captioning as a line item rather than hoping a sponsor covers it. ## 📖 Main Content Joe Simpson Jr. structures the talk in three movements: a personal narrative establishing why he re-engaged with the WordPress community after a medical crisis, a practitioner's checklist for building accessibility into event planning (venue, wayfinding, speakers, website, live production), and a Q&A that surfaces budget as the real constraint behind every recommendation. The opening narrative (t=171s–t=546s) covers a cardiac event, a 90-day medical leave, and a recovery built around hiking Santa Clarita Valley parks. Joe connects this directly to his original path into WordPress: after his agency's lead developer and CSS lead both left within 30 days of each other, he inherited a news blog built on WordPress and was sent to WordPress VIP's Intensive Developer Sessions in Napa, California, where a room of strangers helped him "spin up a virtual box" — the moment he says taught him what the WordPress community was. That memory, revisited during his leave, is what sent him to his first Meetup, into WordCamp LA volunteering, and eventually into starting three meetups (two in Santa Clarita, plus BlackPress) and organizing the first WordCamp north of LA and south of San Francisco since 2015 — whose third edition included the first WordCamp track dedicated to accessibility. The practitioner section (t=610s–t=1852s) is the operational core: an equity-liaison story from his day job at Metro Los Angeles Transit sets up the framing that "accessibility is a floor, not a ceiling"; a short history lesson (Crip Camp, the Capitol Crawl, the ADA) grounds the advocacy in the disability rights movement; and the bulk of the talk works through his WordCamp US San Diego accessibility checklist (later published to Make) point by point — inclusive organizing teams, early venue tours with a disabled team member, multi-format wayfinding (graphic map, text-only turn-by-turn modeled on the National Braille Institute, video walkthrough), a dedicated accessibility team, distance badges (Ryan Bourne's suggestion), quiet/low-capacity viewing rooms, speaker slide requirements, and event-website basics (accessibility-ready theme, contrast, alt text). The Q&A (t=1968s–end) is where budget constraints surface explicitly: Joe states plainly that lack of budget is the top reason ASL and live captioning aren't standard, and describes the low-budget workaround (Zoom auto-captions, manually cleaned up) versus the funded version (professional vendors like 3Play or White Coat Captioning). Sherose adds that the incoming ADA Title II ruling (effective April, applying to U.S. state entities like higher education and government offices) may create indirect momentum, though it doesn't bind WordCamps directly. **Terms and context.** ADA = Americans with Disabilities Act (1990, discussed via the Capitol Crawl protest and the Crip Camp documentary). ASL = American Sign Language. "Craptions" is Joe's own term for low-quality auto-generated captions. The Make WordPress Accessible team is the official WordPress.org contributor team for accessibility work on WordPress core, distinct from the event-accessibility practices Joe describes, which live in the WordCamp Organizer Handbook. **Uncertainties.** Joe cites "over 30 years" at Metro Los Angeles Transit in one place and "after 33 years" in another — the transcript does not resolve which figure is correct. The exact publication location of Michelle Frechette's Town and Country resort accessibility article is referenced but not linked on screen. The current live status of Joe's venue accessibility checklist inside the Organizer Handbook is asserted by Joe but not independently verified here. ### 🗒️ Notes #### ⏱️ [00:02:51](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=171s) Joe's medical crisis and 90-day leave - Opens with a heart-surgery narrative: two 100% blocked arteries, told his daughter about surgery risk at the kitchen table the night before, decided not to burden her further because she was finishing her art-school portfolio. - Recovery ran through Santa Clarita Valley parks — walking distance grew from 1 foot, to 10 feet, to a full lap, to reaching the summit of Central Park's hill five days before returning to work. #### ⏱️ [00:05:54](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=354s) Reframing: "if today were my last day" - Uses the recovery period to ask whether his daily work matched his values; if the answer was "no" too many days running, he'd make a change. - That reflection is what sent him back to re-engage with WordPress community work rather than only his day job. #### ⏱️ [00:06:17](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=377s) How Joe learned WordPress and found the community - Inherited a news blog after his agency's lead developer and CSS specialist both left within 30 days of each other. - Sent to WordPress VIP's Intensive Developer Sessions in Napa, California; on day one, asked to "spin up a virtual box," and "everybody in arm's distance offered to help" — the moment he says taught him what the WordPress community was. #### ⏱️ [00:07:14](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=434s) From first Meetup to organizing three - Attended his first Meetup, where the WordCamp Los Angeles organizing team needed volunteers; over the next three months attended 20+ meetups across LA's five counties. - Started three meetups (two in Santa Clarita, plus BlackPress with two Automatticians) and organized the first WordCamp north of LA / south of San Francisco since 2015; its third edition was the first WordCamp with a dedicated accessibility track (about 14 speakers). #### ⏱️ [00:08:35](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=515s) Leaving Metro, presenting internationally - Left Metro Los Angeles Transit (managed a blog network of 14+ WordPress sites there) to focus on presenting open-source and WordPress topics to "emerging and underrepresented communities" — cites WordCamp Asia (Taiwan) and WordCamp San José (Costa Rica). - Introduces himself formally: SiteGround ambassador, community leader, member of the Make Accessible and Training teams. #### ⏱️ [00:10:02](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=602s) Reframing "Make WordPress Accessible" into events - States the talk's thesis directly: take the existing "Make WordPress Accessible" framing and extend it to "Make All WordPress Events Accessible." - Notes slides are available in multiple formats (a plain-text follow-along deck plus the visual deck) as a first practical demonstration of the principle. #### ⏱️ [00:10:44](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=644s) "Accessibility is a floor, not a ceiling" - States that everyone eventually grows into some form of disability, so accessible spaces are baseline infrastructure, not a bonus feature. - Shares an 18-month equity-liaison program at Metro where a colleague assumed an equitable-transportation presentation should only address deaf riders; Joe used the range of disability types to broaden the team's scope. #### ⏱️ [00:11:41](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=701s) History: Crip Camp, the Capitol Crawl, and the ADA - Summarizes the Netflix documentary *Crip Camp*: teenagers at an upstate New York camp went on to organize sit-ins and protests, influenced by the 1960s–70s Civil Rights Movement. - Describes the Capitol Crawl — disabled protesters climbing the Capitol steps because no accessible entrance existed — as a landmark event that built momentum toward the ADA's passage. #### ⏱️ [00:13:52](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=832s) The WordCamp US San Diego accessibility checklist - As a WordCamp US San Diego organizing-team captain, compiled a bullet-point list of accessibility practices; a team mentor/lead published it to Make so other WordCamps could reuse it. - Frames this document as the source for most of the rest of the talk's recommendations. #### ⏱️ [00:14:40](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=880s) Building an inclusive organizing team - Recommends inviting organizers, volunteers, and speakers who bring perspectives the existing team lacks, treating outspoken voices as "resources, collaborators, and inspiration" rather than obstacles. - Ties this to reusing pre-existing WordPress community resources (Make, blog posts) rather than starting from scratch each event. #### ⏱️ [00:15:55](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=955s) Scout the venue — the Town and Country resort story - First concrete recommendation: tour the venue before booking, ideally with someone aware of accessibility. - Recounts WordCamp US San Diego's venue, the Town and Country resort — a "'50s modernist" retro property that was "one of the worst conferences" for accessibility, with doorway and elevator problems documented by Michelle Frechette in her own account of the event. #### ⏱️ [00:17:12](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=1032s) Venue checklist: doorways, elevators, stage heights - Lists specific things to check on a venue tour: entrance width, automatic doors, elevators versus stairs/escalators relative to conference rooms/dining/sponsor hall/hotel rooms, and accessible-room availability at the hotel block. - Adds speaker-space specifics: stage heights, ramps, chair layout, aisle widths, and lighting, drawn from his time organizing WordCamp US in National Harbor. #### ⏱️ [00:19:07](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=1147s) Wayfinding: avoid "designed" venue materials - Warns that venue-provided wayfinding is often "designed" in ways that hurt accessibility — cites National Harbor's tiny, light-gray text with color-contrast problems. - Recommends redrawing maps from the venue's own printed brochures and providing basic, simple maps and clear signage at key points along common paths. #### ⏱️ [00:20:59](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=1259s) Text-only wayfinding modeled on the National Braille Institute - Alex Stein, a blind team member that year, had attended a conference at the National Braille Institute whose site gave extensive turn-by-turn text directions; Joe replicated that format for the WordCamp venue. - Produced text-only, turn-by-turn directions (registration desk, room, conference space, dining room, sponsor area) plus a video walkthrough — three separate ways to find the venue, because the venue's own app was inaccessible. #### ⏱️ [00:22:59](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=1379s) 2019 Santa Clarita WordCamp: accessible by design - Shows a 2019 Santa Clarita WordCamp photo of a newer, more accessible facility where two attendees using assistive devices could wheel directly into the room and park out of the way. - Notes captions were provided for session videos at that event. #### ⏱️ [00:23:11](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=1391s) A dedicated accessibility team, distinct from Attendee Experience - Proposes accessibility as its own core WordCamp organizing team, working closely with (but separate from) Attendee Experience, so accessibility gets direct input across all teams. - Frames this as where Ryan Bourne's and other community suggestions entered the WordCamp US planning process. #### ⏱️ [00:23:44](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=1424s) Ryan Bourne's suggestions: distance badges and quiet rooms - After Joe posted his suggestions on Make, Ryan Bourne — who has issues in large crowds — proposed distance badges so attendees can signal their comfort level around other people; WordCamp US implemented them. - Ryan also suggested low-capacity/quiet viewing rooms for neurodivergent attendees, live-captioned presentations, ASL for at least the keynote, and pre-recorded content (e.g., the keynote or closing remarks) for people who'd rather watch from home. #### ⏱️ [00:25:43](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=1543s) Speaker slide and event-website requirements - Speaker rules: verbally describe graphics/images while presenting, caption and alt-text all images, and make slides available online before, during, and after the talk. - Website rules: test posts/pages for accessibility, start from an accessibility-ready theme, avoid low color contrast, and add alt text everywhere — including social media images. #### ⏱️ [00:26:57](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=1617s) Call to contribute to Make WordPress Accessible - Urges attendees to join the Make WordPress Accessible team as testers, pointing to weekly bug scrubs, biweekly team meetings, office hours, the team calendar, and the contributor wizard. - Notes the wizard helps people find the right team, join Slack, set up a WordPress.org profile, and take a basic onboarding course. #### ⏱️ [00:30:21](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=1821s) Closing: Ta-Nehisi Coates quote and call to advocacy - Closes with a Ta-Nehisi Coates quote on bridging gaps without sacrificing others' humanity, and asks attendees to stay steadfast advocates for open, inclusive WordPress event spaces. - Plugs the early-planning WordCamp Santa Clarita Valley and the WordPressSCV local community; shares his contact info (joesimpsonjr@gmail, instagram.com/joesimpsonjr). #### ⏱️ [00:33:11](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=1991s) Q&A: accessible maps in multiple formats - Answering "what are the most accessible maps," Joe repeats the multi-format approach: standard JPEG/PDF graphics, text-only turn-by-turn directions, and a video walkthrough, because no single format covers everyone. - Suggests contacting Joe Dolson or the Make accessibility channels for guidance, and to get wayfinding materials published as early as possible so attendees can decide whether they can attend. #### ⏱️ [00:34:53](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=2093s) Q&A: overlooked online-event needs and ADA Title II - On what's overlooked beyond standard digital accessibility: most meetups/WordCamps lack ASL or captioning because of no budget; Joe's fix would be making both mandatory, funded parts of every event. - Sherose flags the upcoming ADA Title II ruling (effective April, U.S. state entities — higher education, government) as a possible source of external momentum toward culture change, though it doesn't directly bind WordCamps. #### ⏱️ [00:37:58](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=2278s) Q&A: tips for small local meetups and early buy-in - For small events, argues for a baseline of accessible practices regardless of budget and for keeping accessibility "second nature" rather than a special request. - On getting buy-in without organizer authority: join the planning conversation as early as possible — a month or six weeks out is already too late to make real impact — citing his push for a ramp and large captioning screen on every WordCamp US stage. #### ⏱️ [00:41:48](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=2508s) Q&A: practical live captioning for low-budget events - Low-budget approach: use Zoom's built-in captioning/transcript on recorded sessions, then manually clean up the "craptions" before publishing the video. - Sherose adds that her institution (University of North Carolina) negotiates a discounted rate with the vendor 3Play; Joe notes his past events used White Coat Captioning and that on-stage ASL (as at Matt Mullenweg's State of the Word) remains an aspirational, unfunded goal. #### ⏱️ [00:43:36](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=2616s) Q&A: post-event follow-up - Recommends running a recap and gathering attendee surveys as soon as possible after the event, and collecting complaints and wish-list items in a running note for next time. - Tells a story of a WordCamp US attendee who couldn't enjoy the after-party because the music was too loud and wished for a nearby quiet space — an example of the kind of feedback organizers need to solicit and act on. #### ⏱️ [00:47:43](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=2863s) Q&A: best examples of accessible events - Names the most recent WordCamp US, with its dedicated accessibility team (Michelle Frechette, Alex Stein) built from people whose voices were already active — sometimes critically — in the community, as his strongest in-person example. - Sherose names WordPress Accessibility Day itself as the online example. ## 📚 References - [Make WordPress Accessible team](https://make.wordpress.org/accessibility/) — official WordPress.org contributor team Joe urges attendees to join as testers. - [WordCamp Organizer Handbook](https://make.wordpress.org/community/handbook/wordcamp-organizer-handbook/) — where Joe says his venue accessibility checklist lives as a "first steps" resource. - [W3C Web Accessibility Initiative](https://www.w3.org/WAI/) — Joe references WAI's guidance on accessible events and accessible remote meetings by name; exact document URLs are not shown on screen in the recording. - *Crip Camp* (Netflix, 2020) — documentary Joe cites for the disability-rights history behind the ADA. - [WordPress Accessibility Day 2025 feedback form](https://2025.wpaccessibility.day/feedback) — session feedback link given by the moderator. - Michelle Frechette's account of WordCamp US San Diego's venue accessibility problems — referenced by name in the talk; publication location not shown on screen. ## 🗣️ Paraphrase Joe frames his return to deep WordPress community involvement as a direct consequence of a health scare: heart surgery, a 90-day leave, and a recovery built one park lap at a time led him to ask whether his daily work matched what mattered, and the answer sent him back to volunteering, meetup-building, and WordCamp organizing. That personal stakes-setting isn't decoration — it's the reason he treats "Make WordPress Accessible" as a mandate that extends past the software project and into the physical and logistical experience of attending a WordCamp or meetup. The practical core of the talk is a checklist built from lived organizing failures and fixes: a venue chosen without an accessibility-aware tour (Town and Country resort) produced real, documented problems, while venues toured early with attention to doorways, elevators, and stage heights (National Harbor) produced better outcomes. Wayfinding needs at least three formats — because a JPEG map, a text-only turn-by-turn version modeled on the National Braille Institute, and a video walkthrough each reach different attendees — and a dedicated accessibility team, distinct from Attendee Experience, is what turns community suggestions like Ryan Bourne's distance badges into shipped features. Underneath all of it sits one blunt constraint Joe names directly in the Q&A: budget, or the lack of it, is why ASL and live captioning remain optional at most events instead of standard. ## 📰 Newsletter Joe Simpson Jr.'s WordPress Accessibility Day 2025 talk is less a philosophy session and more a field-tested checklist you can hand to your next organizing team. He walks through what actually broke at WordCamp US San Diego's Town and Country resort venue, what got fixed at National Harbor and Santa Clarita, and why "no budget" — not lack of will — is the top reason ASL and live captioning still aren't standard at most WordCamps and meetups. Takeaways worth stealing: tour your venue early with someone who uses an assistive device, publish wayfinding in at least three formats (a text-only turn-by-turn version modeled on the National Braille Institute is the one most organizers skip), and give accessibility its own dedicated organizing-team seat instead of folding it into Attendee Experience. If you organize any WordPress event — flagship or five-person meetup — his checklist lives in the [WordCamp Organizer Handbook](https://make.wordpress.org/community/handbook/wordcamp-organizer-handbook/), and the [Make WordPress Accessible team](https://make.wordpress.org/accessibility/) always needs testers. ## ✅ Action Items #### DevRel - Developer advocacy: Turn Joe's checklist into a repeatable lightning talk or workshop organizers can request at Community Summit or via office hours; track adoption with a post-talk organizer survey. - Education: Build a 45-minute "organizing an accessible WordCamp" workshop using Joe's WordCamp US San Diego checklist as the syllabus spine. - Developer experience: Not applicable to this source — the talk covers event/venue accessibility, not SDKs, docs, or dev tooling. - Developer marketing: Cross-link Joe's venue accessibility checklist from DevRel event-planning collateral so organizers see it before signing a venue contract, not after. - Community management: Standardize the "dedicated accessibility team, distinct from Attendee Experience" structure Joe describes as a default organizing-team role in event templates. - Internal/external/cross-project: Share the "no budget" finding with sponsor-relations leads so captioning becomes a named, priced sponsorship tier rather than a stretch goal. #### OSPO - Policy & Governance: Make venue tours with a disabled team member and multi-format wayfinding required steps in the Organizer Handbook, not optional suggestions. - License Compliance: Not applicable to this source — no licensing content. - Security Management: Not applicable to this source — no security content. - Software Inventory: Not applicable to this source — no software/SBOM content. - Developer Support: Nearest equivalent is Joe's pointer to Joe Dolson and the Make Accessible Slack channel for organizer consultation on venue/wayfinding questions. - Community Engagement: WordCamp US's dedicated 2025 accessibility team (Michelle Frechette, Alex Stein) is a reusable staffing model other flagship events can request from host organizations. - Strategic Alignment: Track "share of WordCamps with a published venue accessibility checklist" as a simple, countable KPI descending from Joe's original San Diego document. #### Community - Maintainers: Not applicable to this source — this talk addresses event organizers, not code maintainers. - Contributors: Route new volunteers to the Make WordPress Accessible team's testers program via the contributor wizard and basic onboarding course Joe names. - Sponsors: Price live captioning (3Play, White Coat Captioning) as a named sponsorship line item rather than an ad hoc add-on, since funded events used a vendor and unfunded ones patched together Zoom auto-captions. - Ecosystem: Circulate Joe's venue checklist and common-path map format across regional WordCamps as a shared, versioned template instead of letting each organizing team rebuild it from scratch. #### WordPress - Core: Not applicable to this source. - Core Performance: Not applicable to this source. - Core AI: Not applicable to this source. - Core Program Team: Joe's rule that joining venue/production planning a month or six weeks out is already too late (t=2373s) is a concrete scheduling dependency for Program Team timelines. - Mobile: Not applicable to this source. - Playground: Not applicable to this source. - Community: Direct home for this content — attach Joe's venue checklist, common-path maps, and speaker-slide requirements as default files in meetup kits and WordCamp playbooks. - Training: Joe is a Training team member; convert this talk into a formal lesson plan ("Organizing an accessible WordCamp") built on his checklist. - Marketing: Apply the "alt text on all images, including social media messaging" rule (t=1604s) as a standing checklist item for WordCamp/meetup social accounts. - Support: Not directly covered — no WordPress.org support-forum content in this talk. - Design: Apply the event-website guidance — accessibility-ready theme, adequate contrast (t=1594s–1602s) — to WordCamp Central and local-event site templates. - Documentation: Keep Joe's Organizer Handbook checklist current and link it from new-organizer onboarding instead of leaving it as a single slide reference. - Photos: Not applicable to this source. - TV: Apply Joe's suggestion to add timestamp points to session recordings (t=1533s–1535s) as a publishing standard for WordCamp.tv/YouTube. - Polyglots: Not applicable to this source directly — no translation content, though his multi-format wayfinding approach extends naturally to multilingual signage at international WordCamps like the ones (Asia, Costa Rica) Joe mentions presenting at. - Accessibility: Direct home team — Joe is a member, and the venue checklist and speaker-slide rules are ready-made agenda items for the team's event-facing work. - Meta: Not applicable to this source. - CLI: Not applicable to this source. - Hosting: Not applicable to this source — this talk covers physical venue accessibility, not server/hosting infrastructure. - Tide: Not applicable to this source. - Openverse: Not applicable to this source. - Themes: Joe's rule to "start with an accessibility-ready theme" (t=1594s) points organizers directly at the Themes team's accessibility-ready tag as the correct filter for WordCamp/meetup sites. - Plugins: Not applicable to this source — no plugin-review content in this talk. #### The WPOCC - Programs: Fund a small stipend for organizers who complete a documented venue accessibility tour and publish their findings, following Joe's precedent of publishing his checklist to Make. - Projects: Sponsor a governance clinic to turn Joe's individual checklist into a maintained, versioned community resource rather than a one-time slide-deck artifact. - Funding experiments: Stand up a matched-grant pool WordCamps can draw against for captioning vendors (3Play, White Coat Captioning) or ASL interpreters, paid on invoice — a direct answer to the "no budget" blocker Joe names. #### FAIR - Not applicable to this source — the talk covers physical/event accessibility and organizing practice, not FAIR's federated package distribution, provenance/signature, or anti-capture mission; no content in this talk maps to FAIR's technical-independence scope. ## 🧪 Hypotheses - Touring a venue with a team member who has a disability, before signing the contract, reduces post-event accessibility complaints compared with venues chosen from photos or a standard site visit (contrast Town and Country resort with National Harbor). - Publishing a written, versioned accessibility checklist (like Joe's, published to Make) increases the rate at which subsequent WordCamps adopt specific accessibility practices, compared with WordCamps that rely on organizer memory alone. - Offering distance badges (Ryan Bourne's suggestion, implemented at WordCamp US) lowers reported discomfort among attendees who are uncomfortable in crowds, measurable via post-event survey. - Text-only, turn-by-turn wayfinding directions (modeled on the National Braille Institute) reduce navigation-related support requests from blind or low-vision attendees compared with graphic-only maps (JPEG/PDF). - A dedicated accessibility team, distinct from Attendee Experience, produces more implemented accessibility changes per event than folding accessibility work into Attendee Experience alone. - Making live captioning a funded budget line, rather than sponsor-contingent, increases the share of small/local meetups that provide captions, since "no budget" is the reason Joe cites most often for skipping it. ### 📊 Methodology - Compare complaint volume and type across WordCamp US venues (Town and Country resort vs. National Harbor vs. Santa Clarita 2019) using post-event survey archives, if retained by WordCamp Central. - Track adoption of Joe's published checklist over time by sampling WordCamp organizer-team wikis or Make posts for its presence, before and after its 2025 publication. - Run a simple A/B-style comparison: events that provide distance badges and quiet rooms vs. those that don't, measured against attendee comfort ratings in post-event surveys. - Interview blind/low-vision attendees at events that used text-only turn-by-turn wayfinding versus events that used graphic maps only, to compare wayfinding success and support requests. - Compile a small cost comparison of captioning vendors (3Play, White Coat Captioning) against Zoom auto-caption-plus-cleanup labor hours, to give organizers a real budget number instead of an estimate. ### ❓ Questions - What is the actual difference in accessibility-related complaints between WordCamp US San Diego (Town and Country resort, called "one of the worst" for accessibility) and WordCamp US National Harbor, where the team pre-toured and gathered doorway-width specs? - Can the WPOCC or WordPress Foundation fund a standing captioning line item across flagship and local WordCamps, given Joe's repeated point that "no budget" is the top blocker? - Does the ADA Title II ruling Sherose flags (effective April, applying to U.S. state entities like higher education and government) create any indirect pressure on WordPress-affiliated institutional users, even though WordCamps themselves aren't covered? - Is Joe's venue accessibility checklist still current inside the WordCamp Organizer Handbook, and who owns keeping it updated? - What would it take to get ASL onto the State of the Word stage, the aspirational example Joe names but says hasn't happened yet? ### 🔮 Future Research - A systematic, cross-WordCamp accessibility audit comparing venues chosen with versus without a disability-aware pre-tour. - A published, ongoing cost benchmark for live-captioning vendors sized for WordCamp and meetup budgets, addressing the budget gap Joe names directly. - A needs assessment for on-stage ASL provision at flagship WordPress events (State of the Word, town halls), which Joe frames as aspirational and currently unfunded. - Longitudinal tracking of whether WordCamps that adopted Joe's checklist show measurably fewer accessibility complaints than those that haven't. ### 💡 Implications - **Practice:** Organizer checklists and venue pre-tours with a disabled team member should become default steps, not optional add-ons, in event planning workflows. - **Policy:** The WordPress Foundation/WPOCC could formalize a funding pathway for captioning and ASL so it stops depending on which sponsor happens to be present that year. - **Education:** The Training team has a ready-made lesson plan in Joe's checklist; turning it into a syllabus item would close a gap Joe flags — that most organizers learn this by trial and error, as he did. - **Funding models:** Treating captioning as a named sponsorship tier (rather than a general sponsorship extra) gives sponsors a concrete, budgeted line to fund, addressing the "no budget" blocker directly. ### 🧠 Learning Styles Assessment - **Reading level estimate:** Flesch-Kincaid Grade Level approximately 6–7, estimated from the transcript's short, conversational sentences, personal narrative structure, and minimal technical jargon outside WordPress/accessibility-specific terms (WordCamp, ADA, ASL). #### 👀 Visual learners - Present: on-screen photos (hiking summit, WordCamp venues, National Harbor doorway specs, wayfinding maps), a linked slide deck. - Improve: add alt-text descriptions of the venue photos in the published slide deck; provide labeled diagrams of the common-path maps Joe describes rather than relying on narration alone. #### 🔊 Aural learners - Present: the talk itself is a spoken narrative with a live Q&A; auto-generated YouTube captions are available. - Improve: publish a clean, human-reviewed transcript (the "craptions" problem Joe names applies to this recording too) and a short audio-only summary for people who want the checklist without the full 50-minute talk. #### 🗣️ Verbal learners - Present: Joe defines terms through concrete examples (distance badges, text-only wayfinding) rather than abstract definitions; uses analogies (jazz collaboration, "accessibility is a floor, not a ceiling"). - Improve: a plain-language glossary of ADA, ASL, and WCAG-adjacent terms would help attendees unfamiliar with disability-advocacy vocabulary follow the history section. #### 🧩 Kinesthetic learners - Present: the venue checklist and speaker-slide requirements are step-by-step and directly actionable by an organizer. - Improve: package the checklist as a fillable planning worksheet (venue tour checklist, wayfinding format checklist, budget line-item checklist) rather than a slide-only reference. #### 🧠 Logical learners - Present: the talk moves in a clear cause-and-effect structure (problem venue → specific fix → outcome) across the San Diego, National Harbor, and Santa Clarita examples. - Improve: a before/after comparison table of the three venues (what broke, what was fixed, what it cost) would make the causal pattern easier to scan than narrated anecdotes. #### 🧑‍🤝‍🧑 Social learners - Present: live Q&A with the moderator, direct crediting of community members (Michelle Frechette, Alex Stein, Ryan Bourne, Meryl Evans, Rachel Lowenstein) whose input shaped the checklist. - Improve: a discussion prompt inviting other organizers to share their own venue-accessibility failures and fixes, similar to what the Q&A does informally. #### 🧘‍♀️ Solitary learners - Present: the linked, downloadable checklist and slide deck let someone review the material at their own pace. - Improve: add a short self-assessment ("does your next event have X, Y, Z?") so organizers can audit their own plans without needing the live talk. #### 🌿 Naturalistic learners - Present: minimal direct sustainability content; the hiking-recovery narrative uses outdoor space as a personal-growth setting. - Improve: not a natural fit for this content — no meaningful way to add ecosystem/environmental framing without forcing it onto event-accessibility material. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: the talk itself has no on-screen document structure to assess; a published transcript would need real heading structure to be screen-reader navigable. - Improve: publish session notes with proper heading hierarchy (WCAG 1.3.1 Info and Relationships) rather than only a slide PDF. #### Keyboard navigation - Present: not assessable from the video itself; applies to the linked slide deck and resource document, not shown in this transcript. - Improve: verify the linked slide deck and resource document are keyboard-operable (WCAG 2.1.1 Keyboard) before publishing them as event resources. #### Contrast and readability - Present: Joe explicitly flags a real-world failure — National Harbor's "designed" wayfinding materials used "tiny light gray-type colors" with color-contrast issues (t=1173s–1183s). - Improve: this is a direct WCAG 1.4.3 Contrast (Minimum) violation in the example Joe cites; his fix (redrawing maps with better contrast) is the correct remediation and should be the default, not a patch. #### Text resizing and reflow - Present: not directly addressed; wayfinding materials described are static graphics (JPEG/PDF) that don't reflow. - Improve: static graphic maps fail WCAG 1.4.10 Reflow at 200% zoom; the text-only turn-by-turn format Joe describes is the accessible alternative and should be the primary format, not a secondary one. #### Media and captions - Present: session videos had captions per Joe's account of Santa Clarita 2019; Joe recommends timestamped YouTube videos and pre-recorded content options. - Improve: Joe's own "craptions" comment flags that auto-captions alone don't meet WCAG 1.2.2 Captions (Prerecorded) without human cleanup; audio description of on-screen visuals (venue photos, maps) is absent and would address WCAG 1.2.5 Audio Description. #### Forms and interactions - Present: the event uses a Zoom Q&A box for live questions and a separate feedback form (2025.wpaccessibility.day/feedback). - Improve: not independently assessable from this transcript; the feedback form's label clarity, error handling, and target size (WCAG 3.3.2 Labels or Instructions, 2.5.8 Target Size) would need direct review of the form itself. #### Standards reference - Gaps mapped: 1.3.1 (transcript heading structure), 2.1.1 (linked resource keyboard operability), 1.4.3 (contrast, directly named by the speaker), 1.4.10 (reflow, static wayfinding graphics), 1.2.2 (caption accuracy), 1.2.5 (audio description), 3.3.2 and 2.5.8 (unverified, feedback form not shown on screen). ### 🌍 DEIB Assessment #### Cultural breadth - Present: Joe cites presenting at WordCamp Asia (Taiwan) and WordCamp San José (Costa Rica), and frames his post-Metro work as reaching "emerging and underrepresented communities around the world." - Improve: the talk itself stays U.S.-centric in its accessibility-law framing (ADA, ADA Title II); a note on how accessibility legal frameworks differ in the countries he's presented in would round this out. #### Inclusive language - Present: Joe mixes person-first ("someone with a disability") and identity-first ("disabled attendees") language without treating either as wrong, and defines concepts through concrete examples rather than jargon. - Improve: a brief glossary distinguishing ADA/ASL/WCAG terms for attendees new to disability-advocacy vocabulary would help non-specialist organizers. #### Neurodiversity support - Present: explicitly addressed — low-capacity/quiet viewing rooms, pre-recorded content, and distance badges are all framed as accommodations for neurodivergent and crowd-sensitive attendees (Ryan Bourne, Rachel Lowenstein). - Improve: the talk describes these as add-ons for a subset of attendees; framing quiet rooms and pre-recorded content as default event infrastructure (not just accommodations) would match Joe's own "floor, not ceiling" framing. #### Representation - Present: strong — Joe names and credits specific disabled community members by name and specific contribution (Michelle Frechette's venue account, Alex Stein's wayfinding model, Ryan Bourne's distance badges, Meryl Evans's and Rachel Lowenstein's speaker/attendee experiences). - Improve: none of these contributors' pronouns are stated in the transcript; avoid assuming pronouns from names alone if this note or derived content ever needs to reference them directly. #### Psychological safety - Present: the opening medical narrative models vulnerability; Joe frames organizer-attendee feedback as collaboration ("it's not an adversarial position... it's a collaboration") and commits to acting on complaints and reassuring people their concerns matter. - Improve: no content gap identified — this is one of the stronger sections of the talk for psychological safety framing. ### ✅ Logical Validity #### Strong reasoning - **Inductive, from repeated cases to a general rule:** Joe draws his venue-touring recommendation from comparing three specific WordCamp venues (Town and Country resort, National Harbor, Santa Clarita 2019) with different outcomes, then generalizes to "tour the venue as early as possible" (t=1032s). The reasoning is strong because it's grounded in named, comparable cases rather than a single anecdote. - **Causal, tied to a named intervention and outcome:** He links Ryan Bourne's specific suggestion (distance badges) to a specific implemented fix and names the mechanism (signaling comfort level around others, t=1451s–1460s), rather than asserting a vague benefit. - **Analogical:** He explicitly models WordCamp wayfinding on an external, tested pattern — the National Braille Institute's turn-by-turn text directions (t=1264s–1280s) — rather than inventing a format from scratch, which is a defensible analogy since both are venue-navigation problems for the same population (blind/low-vision users). #### Fallacies - **Mild hasty generalization from individual accounts to policy recommendation:** several checklist items (distance badges, pre-recorded content, quiet rooms) trace to one named individual's account (Ryan Bourne, t=1424s–1460s) presented as a general best practice without citing broader survey data. **Location:** t=1424s onward. **Why it's weak, not disqualifying:** Joe treats these as collaborative inputs he explicitly credits, not as universal claims, and elsewhere in the talk (t=2616s–2654s) he separately recommends collecting post-event survey data — which would supply the broader evidence this section lacks. **Fix:** pair each anecdote-sourced recommendation with aggregated post-event survey results before treating it as a standing checklist item, closing the loop Joe already describes but doesn't apply retroactively to his own examples. #### Tone of voice - Personal and vulnerable in the opening (medical crisis, family conversation at the kitchen table), shifting to direct and instructional through the checklist sections, and consistently collaborative rather than adversarial — Joe repeatedly frames organizer/attendee feedback as partnership ("I love jazz music... collaborating with people that are talented," t=2483s–2503s) rather than criticism to be managed. ### 🛡️ DARVO Analysis - **Deny:** Not applicable to this source — no accusation is made against Joe or the organizations he describes, so there is nothing being denied. - **Attack:** Not applicable to this source — the talk contains no attacks on an accuser's credibility; feedback (Michelle Frechette's account, Ryan Bourne's suggestions) is credited and incorporated, not disputed. - **Reverse victim/offender:** Not applicable to this source — Joe does not recast himself or event organizers as victims of attendee complaints; he explicitly commits to treating complaints as valid and actionable (t=2748s–2760s). ## 🎯 Conclusion Joe Simpson Jr.'s talk turns "Make WordPress Accessible" from a software-team slogan into an operational checklist for anyone organizing a WordCamp or meetup: tour the venue early with a disabled team member, publish wayfinding in at least three formats (graphic, text-only turn-by-turn, video), give accessibility its own dedicated organizing-team seat, and treat live captioning and ASL as budgeted line items rather than sponsor-dependent extras. The clearest gap the talk surfaces and doesn't fully close is budget: Joe names "no budget" as the top reason ASL and captioning aren't standard, but the fixes he describes (3Play, White Coat Captioning, on-stage ASL) all still depend on which sponsor shows up that year. Practical next step for organizers: pull Joe's checklist from the WordCamp Organizer Handbook, walk the next venue with someone who uses an assistive device before signing a contract, and price captioning into the budget from day one instead of asking for it after the venue is booked. ## 🔄 Refactor Appendix — Make All WordPress Events Accessible ### 📚 Literature Atoms (H3) #### [H1] Accessibility is a floor, not a ceiling > [!quote] ID:t_644 > Accessibility is a floor, not a ceiling. **Context & use**: - [00:10:44](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=644s) — opens the practitioner section of the talk, right after Joe reframes "Make WordPress Accessible" into "Make All WordPress Events Accessible." - Sets the thesis for everything that follows: accessibility is baseline event infrastructure, not an optional upgrade for a subset of attendees. **Tags**: #xref #aphorisms **Highlight**: [view highlight](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=644s) <!-- atomicity: 1 idea ✓ --> #### [H2] Tour the venue early with a disabled organizer > [!quote] ID:t_1032 > tour the venue as early as possible, ideally with someone that has a disability. **Context & use**: - [00:17:12](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=1032s) — follows directly from the Town and Country resort story, where a venue was booked without an accessibility-aware tour and produced documented accessibility failures. - The single most actionable, repeatable step in the talk for anyone booking a physical venue. **Tags**: #xref **Highlight**: [view highlight](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=1032s) <!-- atomicity: 1 idea ✓ --> #### [H3] Model text wayfinding on the National Braille Institute > [!quote] ID:t_1273 > Their site had extensive directions that were turn-by-turn. **Context & use**: - [00:21:07](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=1267s) — describes how blind team member Alex Stein's experience at a National Braille Institute conference became the model for WordCamp US's own text-only wayfinding directions. - Demonstrates borrowing a tested accessibility pattern from outside WordPress rather than inventing one from scratch. **Tags**: #xref **Highlight**: [view highlight](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=1273s) <!-- atomicity: 1 idea ✓ --> #### [H4] No budget is why captioning gets skipped > [!quote] ID:t_2118 > One of the biggest reasons is that there's no budget for it. **Context & use**: - [00:35:18](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=2118s) — Q&A answer on what accessibility needs get overlooked at online events; names budget, not awareness, as the real constraint. - Directly motivates the WPOCC funding-experiment action item above. **Tags**: #xref **Highlight**: [view highlight](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=2118s) <!-- atomicity: 1 idea ✓ --> #### [H5] Distance badges let attendees signal their comfort level > [!quote] ID:t_1451 > he suggested offering distance badges to let attendees know your level of comfort in terms of being around other people. **Context & use**: - [00:24:11](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=1451s) — credits Ryan Bourne's suggestion, implemented at WordCamp US, as a concrete example of turning a single community member's need into a shipped event feature. - A low-cost, low-tech accommodation that any meetup or WordCamp could adopt immediately. **Tags**: #xref **Highlight**: [view highlight](https://www.youtube.com/watch?v=58qAh9x3Ax8&t=1451s) <!-- atomicity: 1 idea ✓ --> ### 🧠 Permanent Candidates (H4) #### [P1] Verify venue access by touring with a disabled person **Claim** (one sentence, Courtney's voice): Never book a community-event venue off photos or an unaccompanied walkthrough — tour it with someone who uses an assistive device before signing the contract. **Evidence pointer**: [[#H2 Tour the venue early with a disabled organizer]] **Scope & conditions**: Applies to any in-person community event with a physical venue (WordCamp, meetup, conference); doesn't apply to fully virtual events, where the equivalent step is testing the platform's accessibility features directly. **Links** (≥1 with annotation): - [[WordCamp Organizer Handbook]] — because extends the checklist Joe published there. - [[Event budget template]] — because applies-in the venue-selection phase of event planning. <!-- atomicity: 1 idea ✓ --> #### [P2] Fund captioning as a budget line, not a stretch goal **Claim** (one sentence, Courtney's voice): Price live captioning and ASL into every event budget by default, instead of hoping a sponsor happens to cover it. **Evidence pointer**: [[#H4 No budget is why captioning gets skipped]] **Scope & conditions**: Holds for any budgeted event, WordCamp or meetup scale; the smallest meetups can substitute cleaned-up Zoom auto-captions as a stopgap, not a permanent excuse. **Links** (≥1 with annotation): - [[WPOCC funding experiments]] — because applies-in the captioning line-item action item above. - [[Event budget template]] — because extends the same template as P1. <!-- atomicity: 1 idea ✓ --> #### [P3] Publish wayfinding in three formats: graphic, text, video **Claim** (one sentence, Courtney's voice): Give attendees a graphic map, a text-only turn-by-turn version, and a video walkthrough, because no single wayfinding format serves every attendee. **Evidence pointer**: [[#H3 Model text wayfinding on the National Braille Institute]] **Scope & conditions**: Applies to any venue-based event; the text-only version is the one graphic maps skip and the one blind or low-vision attendees rely on most. **Links** (≥1 with annotation): - [[WordCamp Organizer Handbook]] — because applies-in the wayfinding section of Joe's published checklist. <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Check whether Joe's venue accessibility checklist is still live and current in the WordCamp Organizer Handbook "first steps" section — https://www.youtube.com/watch?v=58qAh9x3Ax8&t=1728s #xref - [F2] Compare 3Play vs. White Coat Captioning rates for small/local-event budget planning — #articleseed ### → Things 3 (max 2 actions) - [ ] Add a venue-tour-with-a-disabled-organizer step to the next WordCamp/meetup planning checklist — event-planning #things - [ ] Draft a live-captioning/ASL budget line item and get 3Play/White Coat Captioning quotes for the next event on the calendar — event-budget #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/Make All WordPress Events Accessible.md|Make All WordPress Events Accessible by Joe Simpson Jr.]] ## Highlights - there were no elevators, things like that. I try to take this information in, and I try to use it in terms of the events that I organize. Again, tour the venue as early as possible, ideally with someone that has a disability. Get the physical venue for things that may be an issue. Are the entrances open? Are they wide enough? Bathrooms, conference spaces, auditoriums, ([View Highlight](https://read.readwise.io/read/01m21etkpxw904yb5zskv1zkw7)) - Note: Directly usable for WordCamp and meetup organizing: tour the venue early, with a disabled organizer present, and check entrances, widths, bathrooms, and auditoriums before booking rather than after. - Tags: wordcamp-organizing, atom/literature/h1, venue-accessibility