YouTube Video fVPNBZXyGH8 🔗 **Source:** [YouTube Video fVPNBZXyGH8](https://www.youtube.com/watch?v=fVPNBZXyGH8) > [!note]+ Document Notes > tags: [accessibility, wordpress, media-player] > author: Accessibility Craft > source: Equalized Digital > reference: https://www.youtube.com/watch?v=fVPNBZXyGH8 > date created: 2024-12-28 10:30 > > # 🏷️ Title: Able Player: The Accessibility-First Media Player with Joe Dolson > <!-- deep-read:sections start --> ## 🧰 Action Inbox - [H1] Test Able Player beta releases — help identify issues before quarterly releases #testing - [H2] Consider GitHub sponsorship for Able Player — no current funding for sustainability #funding - [H3] Explore Able Player integration with Accessibility Checker — flag videos and suggest solutions #integration ## 🧭 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) ### 🔗 References - [Able Player GitHub](https://github.com/ableplayer/ableplayer) - [Joe Dolson's Donation Page](https://joedolson.com/donate) ## 📝 Summary - Joe Dolson discusses Able Player, an accessibility-first JavaScript media player library - Why accessibility-first design matters more than just keyboard-accessible controls - Key challenges in maintaining open source accessibility tools without funding - Common video accessibility mistakes on WordPress websites - Future roadmap focused on modernization rather than new features ## 📖 Main Content Able Player is a comprehensive JavaScript library designed with accessibility as the primary concern, not an afterthought. Unlike typical media players that focus mainly on keyboard accessibility and basic captions, Able Player offers advanced features like synchronized sign language interpretation, generated audio descriptions from VTT files, customizable caption appearance, and a built-in captions editor. Joe Dolson, a WordPress core committer and board member of WP Accessibility Day, recently took over maintenance of this 9,000-line codebase from original creator Terrell Thompson. The transition highlighted challenges in code archaeology when previous development used large, monolithic commits rather than discrete changes. The player supports local files, YouTube, and Vimeo, with WordPress and Drupal integrations available. A key WordPress feature allows Able Player to seamlessly replace native video blocks while maintaining the same editing experience. ## 🗒️ Notes #### ⏱️ [00:00:00](https://www.youtube.com/watch?v=fVPNBZXyGH8?t=0) — [H1] Introduction and Beer Tasting - Key idea: Podcast introduction with King Grackle Stout from Texas Beer Co - Evidence: "Solar-brewed beer with notes of chocolate and coffee" #### ⏱️ [00:08:15](https://www.youtube.com/watch?v=fVPNBZXyGH8?t=495) — [H2] What Makes Able Player Different - Key idea: Accessibility-first design prioritizes media accessibility over other concerns - Evidence: "If I need to make some kind of HTML structural change because I need to improve accessibility issues, accessibility first" #### ⏱️ [00:12:30](https://www.youtube.com/watch?v=fVPNBZXyGH8?t=750) — [H3] Advanced Accessibility Features - Key idea: Goes beyond basic controls to include synchronized sign language and generated audio descriptions - Evidence: "Synchronized sign language, generating audio description from a VTT file, which very few players have even attempted" #### ⏱️ [00:16:45](https://www.youtube.com/watch?v=fVPNBZXyGH8?t=1005) — [H2] Library vs Plugin Architecture - Key idea: Core JavaScript library can be packaged for different platforms - Evidence: "It's basically just a gigantic pile of JavaScript, 9,000 lines of JavaScript" #### ⏱️ [00:22:30](https://www.youtube.com/watch?v=fVPNBZXyGH8?t=1350) — [H1] Taking Over Project Maintenance - Key idea: Transition from Terrell Thompson due to University of Washington ADA compliance demands - Evidence: "He's leading their push to get their Title 2 ADA compliance in place by April 2026" #### ⏱️ [00:28:15](https://www.youtube.com/watch?v=fVPNBZXyGH8?t=1695) — [H3] Code Archaeology Challenges - Key idea: Large monolithic commits make debugging and maintenance difficult - Evidence: "You go look at the commit history and there were 1,200 lines of code changed" #### ⏱️ [00:32:45](https://www.youtube.com/watch?v=fVPNBZXyGH8?t=1965) — [H2] WordPress Integration Features - Key idea: Can seamlessly replace WordPress video blocks while maintaining editing experience - Evidence: "Map Able Player over your WordPress video block and it's fine, it's invisible" #### ⏱️ [00:38:20](https://www.youtube.com/watch?v=fVPNBZXyGH8?t=2300) — [H1] Common Video Accessibility Mistakes - Key idea: Three main issues dominate WordPress video accessibility problems - Evidence: "Not having captions, not having transcripts, using really crappy video players" #### ⏱️ [00:41:15](https://www.youtube.com/watch?v=fVPNBZXyGH8?t=2475) — [H3] Native vs Custom Players - Key idea: Native browser players aren't always the best accessibility choice - Evidence: "Just because it's a native video player doesn't mean it's the best one" #### ⏱️ [00:45:30](https://www.youtube.com/watch?v=fVPNBZXyGH8?t=2730) — [H2] jQuery Dependency Removal Timeline - Key idea: Modernization focuses on removing jQuery dependency by version 6.9 - Evidence: "I want to rip jQuery out, I don't want it to be dependent on jQuery" #### ⏱️ [00:51:20](https://www.youtube.com/watch?v=fVPNBZXyGH8?t=3080) — [H1] Funding and Sustainability Challenges - Key idea: Open source accessibility tools struggle without dedicated funding - Evidence: "I have earned absolutely nothing from it and have no monetization of any kind" #### ⏱️ [00:54:45](https://www.youtube.com/watch?v=fVPNBZXyGH8?t=3285) — [H2] Contribution and Support Options - Key idea: Multiple ways to support the project beyond coding - Evidence: "Testing, code contributions, GitHub sponsorship, PayPal donations" ## 📚 References - [Able Player GitHub Repository](https://github.com/ableplayer/ableplayer) - [Joe Dolson's GitHub Sponsors](https://github.com/sponsors/joedolson) - [WP Accessibility Day Archives](https://wpaccessibilityday.org/) - [Equalized Digital Accessibility Checker](https://equalizedigital.com/accessibility-checker) ## 🗣️ Paraphrase - Able Player prioritizes making video content accessible to all users, not just making player controls keyboard-navigable like most players do - The 9,000-line JavaScript library offers unique features like synchronized sign language and generated audio descriptions that are typically only available in expensive commercial solutions - Maintaining open source accessibility tools is challenging without dedicated funding, especially when trying to modernize legacy codebases on aggressive quarterly release schedules ## 📰 Newsletter **Accessible Media Made Easy: Meet Able Player** Creating truly accessible video content goes far beyond adding captions. Joe Dolson's Able Player library demonstrates what "accessibility-first" design really means - prioritizing features like synchronized sign language interpretation and customizable caption displays that most players ignore. The recent transition of this project highlights both the opportunities and challenges in open source accessibility. While Able Player offers enterprise-level features completely free, sustaining such projects requires community support through testing, contributions, and funding. For WordPress users, the seamless integration with native video blocks means you can enhance accessibility without changing your content creation workflow. As we approach 2026 ADA compliance deadlines, tools like Able Player become increasingly valuable. Resources: [Able Player Demo](https://ableplayer.github.io/ableplayer/), [WordPress Plugin](https://wordpress.org/plugins/able-player/), [GitHub Sponsorship](https://github.com/sponsors/joedolson) ## ✅ Action Items #### WordPress - Core: Evaluate native video player limitations and potential improvements - Accessibility: Review video block accessibility features and documentation gaps - Community: Promote accessible video practices through education and tooling - Plugins: Consider integration opportunities between accessibility tools and media players #### Community - Maintainers: Support open source accessibility projects through testing and funding - Contributors: Help with jQuery removal and modernization efforts in Able Player - Sponsors: Fund accessibility-focused projects that benefit entire ecosystem #### OSPO - Strategic Alignment: Include media accessibility in accessibility compliance programs - Community Engagement: Support maintenance of critical accessibility infrastructure - Developer Support: Provide guidance on accessible media implementation ## 🧪 Hypotheses - Accessibility-first design produces better user experiences for everyone, not just disabled users - Open source accessibility tools require dedicated funding models to remain sustainable long-term - Generated audio descriptions from VTT files can significantly lower barriers to video accessibility - Native browser video players create inconsistent accessibility experiences across platforms ### 📊 Methodology - Compare user task completion rates between native players and Able Player across different assistive technologies - Survey content creators about barriers to implementing video accessibility features - Measure implementation costs between generated and professionally produced audio descriptions ### ❓ Questions - How can the WordPress ecosystem better support critical accessibility infrastructure projects? - What funding models work best for maintaining open source accessibility tools? - How do generated audio descriptions compare to professional ones in user satisfaction studies? ### 🔮 Future Research - Investigate streaming video support implementation challenges and solutions - Explore AI applications for video accessibility that avoid common hallucination problems - Study the effectiveness of different video accessibility education approaches ### 💡 Implications - Practice: Accessible video requires more than captions and keyboard controls - Policy: ADA compliance timelines create urgency for accessible media solutions - Security: Third-party video players may introduce vulnerabilities that need assessment - Education: Content creators need better guidance on comprehensive video accessibility - Funding: Open source accessibility tools need sustainable financial support models ### 🧠 Learning Styles Assessment Reading level estimate: 12th grade (Flesch-Kincaid Grade Level) #### 👀 Visual learners - Present: Beer can imagery, video player screenshots in referenced sites - Improve: Architecture diagrams showing player integration, feature comparison charts #### 🔊 Aural learners - Present: Full podcast audio with detailed technical discussion - Improve: Audio examples of generated vs professional audio descriptions #### 🗣️ Verbal learners - Present: Clear explanations of technical concepts, accessibility terminology - Improve: More analogies comparing different player approaches #### 🧩 Kinesthetic learners - Present: References to hands-on testing at WP Accessibility Day - Improve: Step-by-step setup guides, interactive feature demos #### 🧠 Logical learners - Present: Clear technical architecture discussion, systematic feature comparison - Improve: Decision flowcharts for player selection, performance benchmarks #### 🧑‍🤝‍🧑 Social learners - Present: Community discussion format, collaborative project maintenance - Improve: Contribution guidelines, community feedback mechanisms #### 🧘‍♀️ Solitary learners - Present: Detailed technical documentation references - Improve: Self-assessment tools for video accessibility compliance #### 🌿 Naturalistic learners - Present: Discussion of sustainable open source project maintenance - Improve: Ecosystem thinking about accessibility tool interdependencies ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Podcast format naturally provides audio content - Improve: Enhanced show notes with clear heading hierarchy #### Keyboard navigation - Present: Standard podcast player controls are keyboard accessible - Improve: Timestamp links should be properly focusable #### Contrast and readability - Present: Transcript provides text alternative to audio - Improve: Ensure transcript formatting meets contrast requirements #### Text resizing and reflow - Present: Standard web text that should reflow properly - Improve: Verify transcript text scales appropriately #### Media and captions - Present: Full transcript provided for podcast content - Improve: Consider time-synchronized captions for video version #### Forms and interactions - Present: Basic web interactions for accessing content - Improve: Ensure sponsor/donation links are properly labeled #### Standards reference - Maps to WCAG 2.2 Level AA for multimedia content and navigation ### 🌍 DEIB Assessment #### Cultural breadth - Present: Discussion includes global accessibility compliance (Title 2 ADA) - Improve: Include international accessibility standard perspectives #### Inclusive language - Present: Uses people-first language when discussing disability - Improve: Define technical jargon more consistently #### Neurodiversity support - Present: Well-structured content with clear topic transitions - Improve: Provide content outline/summary at beginning #### Representation - Present: Features accessibility expert as primary speaker - Improve: Include perspectives from disabled media consumers #### Psychological safety - Present: Respectful discussion of accessibility challenges - Improve: Acknowledge different accessibility needs explicitly ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Accessibility-first design principles lead to better outcomes for all users - Inductive strength: Examples from WP Accessibility Day demonstrate real-world usage - Causal reasoning: Funding challenges directly impact open source project sustainability - Analogical strength: Comparison between form validation and media players illustrates native element limitations #### Fallacies - Appeal to authority: Reliance on Joe's expertise is justified by demonstrated knowledge and experience - False dichotomy: Slight tendency to present native vs custom players as binary choice when hybrid approaches exist #### Tone of voice - Overall tone: Collaborative and educational, with technical expertise balanced by practical concerns ### 🛡️ DARVO Analysis - Deny: No denial patterns observed - Attack: No attacks on individuals or groups - Reverse victim/offender: No victim/offender reversals present - Emotional cues and rhetoric: Positive, solution-focused discussion about accessibility challenges ## 🎯 Conclusion Able Player represents a significant advancement in accessible media technology, demonstrating how open source projects can deliver enterprise-level accessibility features. The project's transition to new maintainership highlights both the opportunities and sustainability challenges facing critical accessibility infrastructure. For WordPress users and the broader web community, supporting projects like Able Player through testing, contributions, and funding ensures continued innovation in making digital media truly accessible to all users. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] Accessibility-first design prioritizes user needs over technical convenience > [!quote] [Able Player: The Accessibility-First Media Player with Joe Dolson](https://www.youtube.com/watch?v=fVPNBZXyGH8) by [[Joe Dolson]] via [[Accessibility Craft]]. Published 2024. Accessed 2024-12-28. > "If I need to make some kind of HTML structural change because I need to improve some accessibility issues, I know that's going to have down the road consequences for people who are doing custom CSS and custom styles and whatnot. And tough accessibility first." Demonstrates philosophical commitment to accessibility over backward compatibility concerns. [view highlight](https://www.youtube.com/watch?v=fVPNBZXyGH8#00:08:15) #xref #articleseed ID:rw_001 ### [H2] Open source accessibility tools face sustainability challenges without dedicated funding > [!quote] [ <!-- deep-read:sections end -->