 Hello. Nice to meet you. My name is Takayuki Miyoshi. I'm a plugin developer. I'm from Japan. Today I'd like to talk about the responsibility of plugin developers. Sorry, I'm a little bit nervous. This is my profile page on WordPress. I'm a plugin developer. I'm maybe known as Wozard, a content from 7 plugin, but I'm having a part in the WordPress community in a lot of roles. This page represents my roles, so let's look closer. I'm a translation contributor, a supporting member, a support contributor. This is mainly for the Japanese WordPress community. And I send some badges to Core, Core contributor, and the WordPress TV contributor. And I took several times at the World Camp, most of them in Japan, and a translation editor, and I'm a plugin developer. I'm from Fukuoka, Japan. Fukuoka is a place in Japan. You may not know about Fukuoka. Maybe most of you don't know Fukuoka. You must know the famous character born in Fukuoka. A very famous character in the WordPress community. Can you guess it? Wabu. You know. It's Wabu. Do you know Wabu? Yes. The original Wabu, this one, was created by a Fukuoka based illustrator. And introduced at World Camp Fukuoka 2011. This is the first Wabu cake. Now we see so many Wabu children around the world, including Shingabu. You know Shingabu, right? The first Wabu, the original Wabu, was from Fukuoka. And remember Fukuoka as Wabu Topia. I started plugin development in 2006. So I had 10 years experience in plugin development. Now I have 10 plugins in the WordPress plugin directory. Among them, Contact Form 7 and Bogo are my favorite ones. This is Contact Form 7. It manages contact forms. Do you know this? Thank you. Thank you very much. It is now used on more than 1 million sites. It became one of the most popular WordPress plugins. This is Bogo. It is your site's marteringer. The most strong point is it manages language metadata in a very clean and efficient way. If you are interested in this type of marteringer plugin, I can show you a demonstration of this. Contact Form 7 passed 40 million downloads. And I don't repeat around the WordPress site. Made an article. Wrote an article about it. I'm really excited to see such huge number of sites. I use the plugin I created. All over the world, millions of sites are actually using it. Maybe I am the person who is surprised the most. That is awesome. I feel honored. On the other hand, I have been thinking for a long time about the responsibility. What is the responsibility of plugin developers? WordPress allows plugins to do everything. Provings can do everything. Provings can make WordPress better or worse. Most users use only one plugin. You can make their experience for WordPress good or frustrating. WordPress gives us and private developers great opportunities. What should we do for WordPress? What is the responsibility? This is my answer. The responsibility of plugin developers is to keep WordPress accessible for everyone. Regardless of age, disabilities or language. Why? Because WordPress core is designed to be accessible for everyone. Plugins should follow it. Not let your plugins destroy it. So how can we keep WordPress accessible for everyone with plugins? There can be a lot of aspects. But today, let's focus on these two aspects. Accessibility and localization. First, let's look at the accessibility aspect. If you are plugin accessible, many people think accessibility doesn't matter. It's not related to themselves. I myself used to think like that. But now I know it's wrong. All of us get old. Our site becomes weaker. And it gets harder to read. Low contrast text. Like the middle. And elderly people are not minority in the Internet society. You don't want to ignore them. So ensure that there is enough contrast. Grind people use screen reader software to access web sites. If you are plugin manages web forms, you need to pay special attention to the form's accessibility. Most screen readers don't read the text inside a form. Unless it's correctly mapped up. Using form control elements, like label or agent elements. So for important instructions, use correct library. Otherwise, users don't get what they are supposed to input into their fields. And your plugin form will be completely useless. This match, the WordPress accessibility team announced that all new or updated code releasing to WordPress core must confirm with the WCAG 2.0 guidelines. WCAG stands for Web Content Accessibility Guidelines. This means WordPress core code ensures a specific level of accessibility. Plug-ins should follow it. If you want to learn web accessibility and know how to make your plugins accessible, check the WordPress accessibility handbook. Let's look at the localization aspect. If you are plugin monitoring already, let's think about translation aspect. Translate WordPress org makes collaborative translation possible. Now you can translate WordPress plugins or translate WordPress org site more than 100 languages registered on the site. And volunteer translators work for their local languages. To make Friday the user in your plugin translatable, use special get-to-take-its function like this underscore-underscore function. The first argument is the original English take-its. And the second argument is called domain. In this case, the domain is the plugin's name. So this is for my content. Or you can use these variant functions. Let's look at text direction. Note that in some languages, take-its is written in right-to-left direction. Arabic, Persian, and Hebrew in this group. This is our new post-page admin page shown in English. English is the default language of WordPress. The main menu bar is shown on the left side. This is the same page shown in Arabic. Arabic is right-to-left language. Notice that the main menu bar is shown on the right side. This is in Chinese, the English version. This is the same page shown in Hebrew. Hebrew is right-to-left. So here is the sidebar. And this is Japanese version. Left-to-right. So here is the sidebar. And this is the same page in Persian. Here. So as you see, in some languages, text is written right-to-left, and pages may have different layout. Many plugins are blocked into the admin screen. Do your plugins work correctly in RTL languages? If you set these properties in your plugin's style sheet, you may need to change the left to right in the RTL languages like this. What function is RTL? Tell me if the title is RTL. Like this content, make an additional style sheet for RTL and load it when the title is RTL. So this is the function of RTL. Make a style sheet for RTL. Make a style RTL CSS and include a style if it's RTL. Okay. We looked at two aspects today. Accessibility and raw characterization. But of course, these are not the only things we need to run. There are other things important. For example, privacy or writing document, everything. But unfortunately, I don't have enough time, so let's discuss later. These are not about programing technique. But it doesn't mean it's not important for developers. Actually, it's really important. Again, responsibility of plugin developers is to keep one press accessible for everyone. This is my answer to the question of what is the responsibility of a plugin developer. I keep this in mind when creating a plugin. Thank you very much. Thank you. Anybody have any questions for him? Okay, we have some. Hi. My question is not the case. What do you think is the secret of this access with Kotlin? It's secret. I don't know. I don't know why. Completely no idea. What? Why? Why do you think? I don't know. Thank you very much. Okay. Hi. Considering that Kotlin program has 40 million downloads or installs, right? Do you have a team to help you maintain the plugin? I want a team. But I have no team. Yeah. Just a follow-up. Do you consider hiring a team? Hiring a team. Yeah, someday. Yeah, not now. Yeah. I think developing a wrong is sometimes easy. Easier than managing a team. Managing a team. I think it's a little bit difficult. It's okay. I'm sorry. Just two minutes. Okay. All right. If somebody else has any questions, we will move along. It's 7. It's... I created the contract from 7 10 years ago. So I don't remember the reason. Why? Yeah. Yeah. In 2007. So it might be a different reason. But I'm not sure. I don't remember. Okay. Thank you.