Monthly Archives: June 2013

Joe Dolson 4:54 am on June 29, 2013
Tags: , , , media,   

Potentially useful accessibility plug in I learned about…

Potentially useful accessibility plug-in I learned about today at WordCamp Chicago: https://wordpress.org/plugins/media-ally/

#a11y, #alt, #images, #media, #plugins-2

esmi 8:01 pm on June 25, 2013
Tags: , ,   

Next IRC Meetup

Just a quick reminder that the next IRC meetupMeetup 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 meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. will be on Wednesday, 26 June at 19:00 UTC in #wordpress-iu.

Everyone welcome!

If you have never attended an WordPress IRC meetup before, you can find all of the details you will need to join in the Codex’s IRC page.

One topic for discussion is likely to be the development of a proposed 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 for WordPress. To whet your appetite and give you an idea of what we could aim for longer term, have a look at Drupal’s accessibility statement.

#core-2, #development, #meetup

esmi 12:49 pm on June 25, 2013
Tags: , html5,   

Should We Be Dropping the Role Attribute in Twenty Thirteen Yet?

Your feedback is requested on Trac Ticket 24629.

Cited example: Should the Twenty Thirteen drop the use of the role attribute on the HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites.5 nav element on the grounds that the element, by definition, has the role of navigation? Or should role="navigation" be retained in order to support technologies that are not yet HTML5 aware?

My own opinion that the role attribute should be retained for the time being in order to support the widest range of technologies. Dropping it would offer only a marginal benefit in reducing page bloat. Please do weigh in with your opinions on the ticket.

#a11y-audit, #html5, #trac-2