{"id":733,"date":"2013-09-02T12:39:33","date_gmt":"2013-09-02T12:39:33","guid":{"rendered":"http:\/\/make.wordpress.org\/accessibility\/?p=733"},"modified":"2013-09-02T12:39:33","modified_gmt":"2013-09-02T12:39:33","slug":"irc-meeting-august-28-2013","status":"publish","type":"post","link":"https:\/\/make.wordpress.org\/accessibility\/2013\/09\/02\/irc-meeting-august-28-2013\/","title":{"rendered":"IRC Meeting: August 28, 2013"},"content":{"rendered":"

The main focus of the meeting ( and the group) was still on one of our primary objectives<\/a> \u2014 the development of a global accessibilityAccessibility<\/span> Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both \u201cdirect access\u201d (i.e. unassisted) and \u201cindirect access\u201d meaning compatibility with a person\u2019s assistive technology (for example, computer screen readers). (https:\/\/en.wikipedia.org\/wiki\/Accessibility)<\/span><\/span><\/span> statement for WordPress. After reviewing Drupal\u2019s accessibility statement<\/a> again, it was decided to begin work on drafting our own statement that can then be presented to the wider community for discussion.<\/p>\n

<\/p>\n

We hope to be able to publish this draft in the next week or so.<\/p>\n

The theme accessibility audit was recently tested successfully (by request) on the underscores theme<\/a>. Three group members undertook the audit independently and then compared notes. The results correlation between all three was 100% and a combined report was passed to the underscores development team. On this basis, we now feel that we are ready to proceed with the theme accessibility audits and will be liaising with the Theme Review Team<\/a> to bring the audit online officially.<\/p>\n

@<\/span>davidakennedy<\/a> is still working on patches for accessibility issues \u2014 including colour and contrasts \u2014 for the MP6 plugin<\/a>. This is a high priority as there are plans to roll the pluginPlugin<\/span> A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https:\/\/wordpress.org\/plugins\/<\/a> or can be cost-based plugin from a third-party.<\/span><\/span><\/span> into WordPress 3.8 coreCore<\/span> Core is the set of software required to run WordPress. The Core Development Team builds WordPress.<\/span><\/span><\/span>. Other plugins that may become part of WordPress core in future are listed on Features as Plugins Tracking<\/a>. So we do need to also look at plugins such as Omnisearch<\/a> as soon as possible. If you are auditing this plugin, you may find Omnisearch\u2019s documentation<\/a> useful.<\/p>\n

Finally, after 18 months as team repTeam Rep<\/span> A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts.<\/span><\/span><\/span>, @<\/span>esmi<\/a> asked to stand down and @AccessibleJoe offered to take this role on. His offer was accepted by all those attending the meetupMeetup<\/span> All local\/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https:\/\/www.meetup.com\/<\/a>. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for \u2018WordPress\u2019 on meetup.com will help you find options in your area.<\/span><\/span><\/span> and we are now working on a smooth handover.<\/p>\n

#wordpress-ui log for August 28, 2013<\/a><\/p>\n

#<\/span>meetup<\/a>, #<\/span>team-reps<\/a><\/p>