What is the Responsibility of Plugin Developers?

Bb7bc21850c77e9eb16b44102f4a539d?s=47 takayukister
September 20, 2016

What is the Responsibility of Plugin Developers?

At WordCamp Singapore and Tokyo 2016. As a WordPress plugin developer, I talked about my opinion on the responsibility of plugin developers.

Bb7bc21850c77e9eb16b44102f4a539d?s=128

takayukister

September 20, 2016
Tweet

Transcript

  1. What is the Responsibility of Plugin Developers? Takayuki Miyoshi

  2. https://profiles.wordpress.org/takayukister/

  3. I am Takayuki Miyoshi, WordPress plugin developer.

  4. I have been involved in the WordPress community in a

    lot of roles.
  5. Translation Contributor Support Team Support Contributor Core Contributor WordPress.tv Contributor

    WordCamp Speaker Community Team Translation Editor Plugin Developer
  6. None
  7. I'm from Fukuoka, Japan

  8. I'm from Fukuoka, Japan Me, too!

  9. The original Wapuu was created by a Fukuoka-based illustrator and

    introduced at WordCamp Fukuoka 2011.
  10. https://wapuu.jp/

  11. https://wapuu.jp/

  12. Wapuutopia Fukuoka =

  13. I have 10 years experience in plugin development. Contact Form

    7 and Bogo are my most favorite plugins.
  14. Contact Form 7 manages contact forms.

  15. Bogo makes your sites multilingual.

  16. https://wptavern.com/contact-form-7-passes-40-million-downloads

  17. Last month Contact Form 7 passed 40,000,000 downloads. WP Tavern

    wrote an article about it.
  18. What is the Responsibility of Plugin Developers?

  19. WordPress allows plugins to do everything. Plugins can make WordPress

    better or worse.
  20. WordPress gives us great opportunities. What should we do for

    WordPress?
  21. What is the Responsibility of Plugin Developers?

  22. The Responsibility of Plugin Developers Is to Keep WordPress Accessible

    for Everyone.
  23. WordPress Core is Designed to Be Accessible for Everyone. Plugins

    Should Follow It.
  24. Let's Look at Two Aspects. Accessibility Localization &

  25. Is Your Plugin Accessible?

  26. Can you read this? Ensure Enough Contrast. Low-contrast text is

    hard to read.
  27. form action="http://example.com/donut" metho p> <input type="radio" name="flavor" id="choc <label for="choc">Chocolate</label><br/>

    <input type="radio" name="flavor" id="crea <label for="cream">Cream Filled</label>< <input type="radio" name="flavor" id="hone <label for="honey">Honey Glazed</label>< <input type="submit" value="Purchase Donut </p> </form> Label Correctly.
  28. form action="htt p> <input type="radio" name="flavor" id="choc <label for="choc">Chocolate</label><br/> <input

    type="radio" name="flavor" id="crea <label for="cream">Cream Filled</label>< <input type="radio" name="flavor" id="hone <label for="honey">Honey Glazed</label>< <input type="submit" value="Purchase Donut </p> </form> If your form isn't correctly labeled, screen reader users have no idea what to input into the fields.
  29. https://make.wordpress.org/accessibility/2016/03/21/wordpress-goes-wcag/

  30. The WordPress Accessibility Team announced that all new or updated

    code released into WordPress core must conform with the WCAG 2.0 guidelines.
  31. WordPress core code ensures a specific level of accessibility. Plugins

    should follow it.
  32. https://make.wordpress.org/accessibility/handbook

  33. WordPress Accessibility Handbook provides essential information for plugin developers.

  34. Is Your Plugin Multilingual-Ready?

  35. Translation

  36. https://translate.wordpress.org/projects/wp-plugins/contact-form-7/stable/ja/default

  37. translate.wordpress.org makes collaborative translation possible.

  38. __( "You are not allowed to upload files of this

    type.", 'contact-form-7' ) Make Text Translatable with __() Function.
  39. __( $text, $domain ) _e( $text, $domain ) _x( $text,

    $context, $domain ) _ex( $text, $context, $domain ) _n( $single, $plural, $number, $d _nx( $single, $plural, $number, $ You can also use variant functions.
  40. Text Direction

  41. https://ar.wordpress.org/

  42. In some languages, text is written Right-to-Left.

  43. Add New Post page in English

  44. Add New Post page in Arabic

  45. Add New Post page in Chinese

  46. Add New Post page in Hebrew

  47. Add New Post page in Japanese

  48. Add New Post page in Persian

  49. In some languages, text is written Right-to-Left (RTL) and pages

    may have a different layout.
  50. Do your plugins work correctly in RTL languages? Many plugins

    add blocks into the admin screen.
  51. If you set these properties in your plugin's stylesheet, you

    may need to change the 'left' to 'right' in RTL languages: • text-align: left • margin-left: • padding-left: • border-left: • left:
  52. If you set these properties in your plugin's stylesheet, you

    may need to change the 'left' to 'right' in RTL languages: • text-align: right • margin-right: • padding-right: • border-right: • right:
  53. WordPress function is_rtl() tells if the site language is RTL.

    if ( is_rtl() ) { wp_enqueue_style( 'style-rtl', '/css/style-rtl.css' ); } Make an additional stylesheet for RTL and load it when the site language is RTL.
  54. We looked at two aspects today but of course these

    are not the only things we need to learn. Accessibility Localization &
  55. These are not about cool programming techniques, but it doesn't

    mean it's not important for developers. ACTUALLY, IT’S REALLY IMPORTANT!
  56. The Responsibility of Plugin Developers Is to Keep WordPress Accessible

    for Everyone. This is what I keep in mind when creating a plugin.