Monthly Archives: April 2013

esmi 1:46 pm on April 26, 2013
Tags: ,   

IRC Meeting: April 24, 2013

We had another lively IRC meeting on Wednesday.

3.6 Post Formats

It was previously decided that both the video and audio post formats could benefit from an ability to add links to captions (for videos) or transcripts (for audio files) and some preliminary investigations were started to look at the possibility of submitting patches. However, as there has been some concern about the release schedule for 3.6 and the possibility that Post Formats might be removed from the release, this has been shelved until we hear further.

Continue reading →

#irc, #meetup

Andrew Nacin 5:53 pm on April 23, 2013
Tags: attributes,   

Post titles in attributes

In pretty much every theme, there is something that looks like this:

<a href="<?php the_permalink(); ?>" title="<?php echo esc_attr( sprintf( __( 'Permalink to %s', 'twentythirteen' ), the_title_attribute( 'echo=0' ) ) ); ?>" rel="bookmark"><?php the_title(); ?></a>

My question: Is “Permalink to (title of post)” a WordPress anachronism that, by being a redundant title attribute, actually harms 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)?

#attributes, #themes-2

Joe Dolson 3:28 am on April 21, 2013
Tags: , , patch   

Just submitted http core trac wordpress org ticket…

Just submitted: https://core.trac.wordpress.org/ticket/24148. Comments welcome.

#a11y, #comment-form, #patch

Joe Dolson 6:28 pm on April 16, 2013  

Updated Theme Review Guidelines

I’ve updated the Theme Review guidelines for Accessibility again. This update takes into a consideration a number of suggestions and questions from Chip Bennett regarding the understanding of issues and how to resolve them.

Among the changes:

  • Images now state that decorative images must be included with CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site..
  • Headings explicitly states that post and 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. titles must be wrapped in headings, to draw the ‘reasonable headings’ guidelines into a context explicitly relevant to WordPress structure as defined by a theme.
  • Link text provides specific techniques for accomplishing the goal.
  • Keyboard navigation provides guidance on testing and specific mention of one of the most common failures for dropdown menus.
  • Contrast references tools for testing.
  • Skip links defines a conforming skip link.
  • Forms defines specific changes that can be made to defaults that would break 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).

Your comments are welcome.

esmi 11:01 am on April 11, 2013  

Support Requests

If you post a comment here looking for support regarding your own site, it will be deleted. If you need support, please post on the wordpress.org support forums.

Thank you.

Graham Armfield 10:31 am on April 4, 2013
Tags: , , , , , ,   

Accessibility IRC Chat – 3rd April 2013

A few of us took part in the IRC chat yesterday (see transcript here). Not surprisingly the main subject was the Add Media Panel 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), and the format of the chat turned into a live screen reader test on the functionality performed by @_Redd and @arush (and myself).

@lessbloat had kindly had a go at implementing my quick and dirty pragmatic ARIA solution – for which we are truly grateful. Once we’d got access to an environment where the changes were in effect we could see that vast improvements had been made to the accessibility.

I’ll save the detail to the blog post about Add Media Panel but to summarise:

  • Keyboard-only users can now tab through the items in the media list and select/deselect using Enter key
  • Screen reader users were getting some useful information but possibly only the newest versions can fully use this functionality.
  • Voice recognition users can at least use the tab commands to move around the list and select them.

The key decision now is whether the functionality is useful and solid enough to include in 3.6. A couple of extra enhancements would make the solution better for screen reader users – once again see previous post.

My vote would be to run with it if we can get the small further enhancements. We can hopefully address the rest of the accessibility issues within 3.7.  But what do you think?

#accessibility, #add-media, #irc, #keyboard, #media-manager, #screen-reader, #testing