What is the responsibility of plugin developers?
summary
Built Contact Form 7 and several plugins that power millions of sites, the core claim is concrete: plugins must be secure, private, and genuinely usable by everyone. Specific practices include WCAG and accessibility-ready compliance, giving form fields proper labels and ARIA-friendly markup so screen readers work, and shipping translation-ready strings plus RTL support for languages. Also document behavior, minimize privileges, and treat security and privacy as functional requirements, not optional extras.
AI-written summary · about
chapters (5)
- 0:00Start
- 8:38Let's Look at Two Aspects.
- 16:49In some languages, text is written Right-to-Left (RTL) and pages may have a different layout.
- 17:01Many plugins add blocks into the admin screen.
- 17:44WordPress function is_rtl() tells if the site language is RTL.
related talks
46mPrivacy, data protection, and open source development
36mHow the WordPress Ecosystem Handles Security and What You Can Learn from It
39mSponsored BoF: Cultivating Quality in Open Source: Modern Strategies for Shared Res...
27mSecuring your WordPress sites
34mSecure WordPress Without Coding Skills
14mIt's a Jungle Out There: The Security State of CMS Platforms
41mExtreme Software Portability as an Art Form
25mSecurity and Accessibility can be friends!