We’ve been extremely busy lately defining a list of accessibility objectives for WordPress as a whole. Top of the list is the drafting of a WordPress AccessibilityAccessibility 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 “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Statement in line with other open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. CMS applications such as Drupal & Joomla. We feel that this would go a long way towards solidifying the current work that is being done and providing a pathway for future development.
Selected themes are now being tested against the theme accessibility audit both as a services to some developers and as a way of ironing out any final issues before formally launching this as new initiative. A small sub-group are currently auditing the _s theme and the results from each auditor will be compared to ensure that we are able to provide a suitably standardised review process.
We are still concerned about the lack of real feedback from disabled users. Despite our best efforts, we recognise that commenting via the Make WordPress Accessible P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. blog may still be too intimidating for many non-technical disabled users. To that end, we are currently investigating the possibility of using short accessible surveys and/or mini-polls to increase end user involvement.