Joe Dolson 8:58 pm on July 21, 2014  

Prioritization: Accessibility Tickets for WP 4.0

This is a list of current tickets with the 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) focus in WordPress 4.0. So that we can get the most important issues done earlier, allowing for better iteration and testing, I’m prioritizing the tickets according to severity.

Please don’t read this in any way as a listing of importance: all of these issues are important, but some issues have a greater impact and/or require more testing to make sure they’re done right, and these issues are getting higher priority.

Group 1:

These issues may prevent a user with disabilities from installing or using WordPress

New in 4.0:

  1. #28858 New installation: Language Selector

This should get very high priority, as this feature will be a new user’s first introduction to WordPress, and will set the tone for all further experiences.

Group 2:

These issues may prevent a user with disabilities from using a specific feature in WordPress.

New in 4.0:

  1. #28822 Media Grid: Focus doesn’t change when tabbing through selected items
  2. #28857 Media Grid: Manage focus when toggling between the grid and an edit attachment modal
  3. #28892 CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. – Widgets – Feedback for screen reader users when Moving widgets + other actions
  4. #28888 Customizer – Widgets – Screen Readers Don’t Announce WidgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. Names
  5. #26167 PluginPlugin 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/ or can be cost-based plugin from a third-party activation links need to contain plugin name and the “Plugin” column should be marked as row headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes.

Add Media Experience:

  1. #23560 Keyboard Accessibility of Add Media Panel
  2. #28209 Links inside help tabs (help-tab-content) are not keyboard accessible
  3. #25103 Submit buttons on form fields in the Add Media panel
  4. #23562 Using Speech Recognition Software with the Add Media Panel
  5. #28864 Cannot access edit menu options with keyboard inside Image Editor

The Add Media panel and related experiences are a huge part of the day-to-day interaction with WordPress, so these should also get high priority.

TinyMCE:

  1. #27642 Keyboard Accessibility for TinyMCE image panel
  2. #27553 Make WP editor toggle focusable

Customizer:

  1. #20880 Keyboard navigation in Appearance > Header is broken

Widgets:

  1. #27592 Screen Reader Users Do Not Know Widgets are Expandable
  2. #27593 Widgets: Toggle arrows on focus need an indicator beside color alone

Other:

  1. #27555 Make tag post metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. box more accessible
  2. #26600 Search installed themes input has no submit button
  3. #26550 Some anchor links should be buttons in media microtemplates
  4. #18801 Accessibility Enhancements to Settings APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.

Group 3:

These issue impact front-end user experience, and have enormous impact on the visitors to sites built with WordPress.

  1. #15926 Give header and background images alt tags
  2. #24148 Add aria-labelledby attributes to comment form
  3. #21221 Image title and alt attribute content should be texturized.
  4. #27402 Add aria-describedby to image gallery output
  5. #27645 MediaElement.js player & playlist not keyboard accessible
  6. #16433 Extend function to optionally include commenter name in comment_reply_link
  7. #18650 Make archives and categories widgets dropdown ada compliant

Group 4:

These issues should not generally prevent a user from using a feature, but will make it more difficult to use.

  1. #28976 Add Media Panel: Announce context of close button for screen readers
  2. #28867 Correctly label forms in wp_list_table
  3. #26552 Remove title attributes: default-widgets.php
  4. #26758 Edit Tags form on submission does not stay at the same page and gets redirected
  5. #28873 JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. code for adding bookmarklet Press This is hard to access with keyboard only
  6. #25111 Keyboard focus does not stay within Full Screen Editor modal
  7. #26562 Remove title attributes: class-wp-admin-bar.php
  8. #26504 Semantic elements for non-link links
  9. #27609 change ‘<code>’ to ‘<pre>’ in wp-includes/comment-template.php
  10. #21414 Use the “Keyboard Shortcuts” checkbox in the user profile to turn on/off all custom shortcuts
  11. #26601 Inappropriate content in heading on Themes page
  12. #26551 Remove title attributes: link-template.php
  13. #26560 Remove title attributes: rss.php