Tag Archives: 4.6

Joe Dolson 7:59 pm on April 18, 2016
Tags: 4.6, , wishlist   

Accessibility Wish List for 4.6 and beyond

Following the example from development on the WordPress Editor, 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) team is going to start posting our goals in wish list format. If you have an accessibility goal you’d like to see the team pursue on WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., add it in a comment and let us know!

Current Accessibility Goals

  • Color Contrast: coordinate with the Design team to finish the colors. See #31713, #35659, #35596, #35622. (@afercia)
  • 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.: collaborate with the team working on the Fields API to make sure they’re fabulously accessible. See #18801 for history, Fields API development (@joedolson, @afercia)
  • Uniform Search: Work to address the numerous different search interfaces within the WordPress admin so they offer the same experience through the admin. See #31818. (@cheffheid)
  • Develop libraries for Accessible Tabs & Accessible Modals
  • Accessible Video: improve the user interface and 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. data relationships for captions & subtitles to make accessible video easier to manage. See #31177. (@rianrietveld)
  • Accessible Media Grid
  • Review usage of target=”_blank” in the admin. See #23432. (@trishasalas)
  • Finish headings improvements: remove controls from headings. See #26601. (@trishasalas)
  • start accessibility work on Select2. See issue 3744 on Select2. (@afercia)
  • Finish working on an accessible TagTag Tag is one of the pre-defined taxonomies in WordPress. Users can add tags to their WordPress posts along with categories. However, while a category may cover a broad range of topics, tags are smaller in scope and focused to specific topics. Think of them as keywords used for topics discussed in a particular post. Cloud 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.. See #35566.

#4-6, #goals, #wishlist

Joe Dolson 7:18 pm on March 21, 2016
Tags: 4.6, , meetings   

Team Meeting 3/21/2016

Our team meeting for today focused primarily on goal setting. As we’re nearing the release candidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. stage for WordPress 4.5, it’s time to move our attentions forward to the future again.

Coming out of 4.5, we know that while we’ve made a lot of progress on our top issues for that release, there’s still a fair amount of work to do, so we’ll be trying finish off the top issues from 4.5: color contrast audits and resolutions and the continuing removal of title attributes. Most of these questions require some significant design decisions, so we’ll be working closely with the design team to get these accomplished.

Moving forward into 4.6, we want to start work on making the internal search functions inside WordPress more consistent. We also need to tackle a few thorny problems in the media management UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing..

Looking further forward, we’re going to start developing some libraries to create accessible modal dialogs, accessible tabbed interfaces, and accessible tooltips for eventual inclusion in WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. The goal is for these to be available for theme and plug-in developers to use as well as for use within the core, so that everybody developing in WordPress can easily generate these types of user interfaces easily and accessibly.

Review the meeting at Slack

#4-6, #goals, #meetings