CINXE.COM
WordPress › Ways to Organise the Accessibility Initiative « Make WordPress Accessible
<!DOCTYPE html> <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en-US"><head profile="http://gmpg.org/xfn/11"><script type="text/javascript" src="/_static/js/bundle-playback.js?v=HxkREWBo" charset="utf-8"></script> <script type="text/javascript" src="/_static/js/wombat.js?v=txqj7nKC" charset="utf-8"></script> <script>window.RufflePlayer=window.RufflePlayer||{};window.RufflePlayer.config={"autoplay":"on","unmuteOverlay":"hidden"};</script> <script type="text/javascript" src="/_static/js/ruffle/ruffle.js"></script> <script type="text/javascript"> __wm.init("https://web.archive.org/web"); __wm.wombat("http://make.wordpress.org/accessibility/2013/01/08/ways-to-organise-the-accessibility-initiative/","20130126200808","https://web.archive.org/","web","/_static/", "1359230888"); </script> <link rel="stylesheet" type="text/css" href="/_static/css/banner-styles.css?v=S1zqJCYt" /> <link rel="stylesheet" type="text/css" href="/_static/css/iconochive.css?v=3PDvdIFv" /> <!-- End Wayback Rewrite JS Include --> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> <!-- <meta property="fb:page_id" content="6427302910" /> --> <link href="https://plus.google.com/107188080561309681193" rel="publisher"/> <meta name="google-site-verification" content="7VWES_-rcHBcmaQis9mSYamPfNwE03f4vyTj4pfuAw0"/> <title>WordPress › Ways to Organise the Accessibility Initiative « Make WordPress Accessible</title> <link rel="stylesheet" href="https://web.archive.org/web/20130126200808cs_/http://s.wordpress.org/style/wp4.css?27"/> <link media="only screen and (max-device-width: 480px)" href="https://web.archive.org/web/20130126200808cs_/http://s.wordpress.org/style/iphone.css" type="text/css" rel="stylesheet"/> <link rel="shortcut icon" href="https://web.archive.org/web/20130126200808im_/http://s.wordpress.org/favicon.ico?3" type="image/x-icon"/> <link rel="alternate" type="application/rss+xml" title="Make WordPress Accessible" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/feed/"/> <script type="text/javascript"> var gaJsHost = (("https:" == document.location.protocol) ? "https://web.archive.org/web/20130126200808/https://ssl." : "https://web.archive.org/web/20130126200808/http://www."); document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E")); </script> <script type="text/javascript"> var pageTracker = _gat._getTracker("UA-52447-1"); pageTracker._initData(); pageTracker._trackPageview(); function recordOutboundLink(link, category, action) { pageTracker._trackEvent(category, action); setTimeout('document.location = "' + link.href + '"', 100); } </script> <!--[if lte IE 8]> <style type="text/css"> @import url("http://s.wordpress.org/style/ie.css?1"); </style> <![endif]--> <link rel="pingback" href="http://make.wordpress.org/accessibility/xmlrpc.php"/><link rel="stylesheet" href="https://web.archive.org/web/20130126200808cs_/http://make.wordpress.org/accessibility/wp-content/themes/make-p2/style.css?v=2" type="text/css" media="screen"/> <script type="text/javascript"> // <![CDATA[ // P2 Configuration var ajaxUrl = "https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/wp-admin/admin-ajax.php?p2ajax=true"; var updateRate = "30000"; // 30 seconds var nonce = "4e8542ecc6"; var login_url = "https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/wp-login.php?redirect_to=http%3A%2F%2Fmake.wordpress.org%2Faccessibility%2F2013%2F01%2F08%2Fways-to-organise-the-accessibility-initiative%2F"; var templateDir = "https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/wp-content/themes/p2"; var isFirstFrontPage = 0; var isFrontPage = 0; var isSingle = 1; var isPage = 0; var isUserLoggedIn = 0; var prologueTagsuggest = 1; var prologuePostsUpdates = 1; var prologueCommentsUpdates = 1; var getPostsUpdate = 0; var getCommentsUpdate = 0; var inlineEditPosts = 1; var inlineEditComments = 1; var wpUrl = "https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility"; var rssUrl = ""; var pageLoadTime = "2013-01-26 20:08:08"; var original_title = document.title; var commentsOnPost = new Array; var postsOnPage = new Array; var postsOnPageQS = ''; var currPost = -1; var currComment = -1; var commentLoop = false; var lcwidget = false; var hidecomments = false; var commentsLists = ''; var newUnseenUpdates = 0; var mentionData = null; // ]]> </script> <link rel="alternate" type="application/rss+xml" title="Make WordPress Accessible » Feed" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/feed/"/> <link rel="alternate" type="application/rss+xml" title="Make WordPress Accessible » Comments Feed" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/comments/feed/"/> <script type="text/javascript"> //<![CDATA[ var wpLocale = {"month":["January","February","March","April","May","June","July","August","September","October","November","December"],"monthabbrev":["Jan","Feb","Mar","Apr","May","Jun","Jul","Aug","Sep","Oct","Nov","Dec"],"weekday":["Sunday","Monday","Tuesday","Wednesday","Thursday","Friday","Saturday"],"weekdayabbrev":["Sun","Mon","Tue","Wed","Thu","Fri","Sat"]}; //]]> </script> <link rel="alternate" type="application/rss+xml" title="Make WordPress Accessible » Ways to Organise the Accessibility Initiative Comments Feed" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/08/ways-to-organise-the-accessibility-initiative/feed/"/> <link rel="stylesheet" id="admin-bar-css" href="https://web.archive.org/web/20130126200808cs_/http://make.wordpress.org/accessibility/wp-includes/css/admin-bar.min.css?ver=3.6-alpha-23334" type="text/css" media="all"/> <link rel="stylesheet" id="jetpack-widgets-css" href="https://web.archive.org/web/20130126200808cs_/http://make.wordpress.org/accessibility/wp-content/plugins/jetpack/modules/widgets/widgets.css?ver=20121003" type="text/css" media="all"/> <link rel="stylesheet" id="p2-print-style-css" href="https://web.archive.org/web/20130126200808cs_/http://make.wordpress.org/accessibility/wp-content/themes/p2/style-print.css?ver=20120807" type="text/css" media="print"/> <script type="text/javascript" src="https://web.archive.org/web/20130126200808js_/http://make.wordpress.org/accessibility/wp-includes/js/jquery/jquery.js?ver=1.9.0"></script> <script type="text/javascript" src="https://web.archive.org/web/20130126200808js_/http://make.wordpress.org/accessibility/wp-includes/js/jquery/jquery-migrate.js?ver=1.0.0"></script> <script type="text/javascript" src="https://web.archive.org/web/20130126200808js_/http://make.wordpress.org/accessibility/wp-includes/js/jquery/jquery.color.min.js?ver=2.1.0"></script> <script type="text/javascript"> /* <![CDATA[ */ var userSettings = {"url":"\/","uid":"0","time":"1359230888"}; /* ]]> */ </script> <script type="text/javascript" src="https://web.archive.org/web/20130126200808js_/http://make.wordpress.org/accessibility/wp-includes/js/utils.min.js?ver=3.6-alpha-23334"></script> <script type="text/javascript" src="https://web.archive.org/web/20130126200808js_/http://make.wordpress.org/accessibility/wp-includes/js/comment-reply.min.js?ver=3.6-alpha-23334"></script> <script type="text/javascript" src="https://web.archive.org/web/20130126200808js_/http://make.wordpress.org/accessibility/wp-content/themes/p2/js/jquery.scrollTo-min.js?ver=20120402"></script> <script type="text/javascript" src="https://web.archive.org/web/20130126200808js_/http://make.wordpress.org/accessibility/wp-content/themes/p2/js/wp-locale.js?ver=20110415"></script> <script type="text/javascript" src="https://web.archive.org/web/20130126200808js_/http://make.wordpress.org/accessibility/wp-content/themes/p2/js/spin.js?ver=20120704"></script> <script type="text/javascript"> /* <![CDATA[ */ var p2txt = {"tags":"<br \/>Tags:","tagit":"Tag it","citation":"Citation","title":"Post Title","goto_homepage":"Go to homepage","n_new_updates":"%d new update(s)","n_new_comments":"%d new comment(s)","jump_to_top":"Jump to top","not_posted_error":"An error has occurred, your post was not posted","update_posted":"Your update has been posted","loading":"Loading...","cancel":"Cancel","save":"Save","hide_threads":"Hide threads","show_threads":"Show threads","unsaved_changes":"Your comments or posts will be lost if you continue.","date_time_format":"%1$s <em>on<\/em> %2$s","date_format":"F j, Y","time_format":"g:i a","autocomplete_prompt":"After typing @, type a name or username to find a member of this site","no_matches":"No matches.","comment_cancel_ays":"Are you sure you would like to clear this comment? Its contents will be deleted.","oops_not_logged_in":"Oops! Looks like you are not logged in.","please_log_in":"Please log in again","whoops_maybe_offline":"Whoops! Looks like you are not connected to the server. P2 could not connect with WordPress."}; try{convertEntities(p2txt);}catch(e){};; /* ]]> */ </script> <script type="text/javascript" src="https://web.archive.org/web/20130126200808js_/http://make.wordpress.org/accessibility/wp-content/themes/p2/js/p2.js?ver=20121128"></script> <link rel="EditURI" type="application/rsd+xml" title="RSD" href="http://make.wordpress.org/accessibility/xmlrpc.php?rsd"/> <link rel="wlwmanifest" type="application/wlwmanifest+xml" href="http://make.wordpress.org/accessibility/wp-includes/wlwmanifest.xml"/> <link rel="prev" title="Team Rep Voting Results" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2012/12/24/team-rep-voting-results/"/> <link rel="next" title="WordPress 3.6: Revisions" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/08/wordpress-3-6-revisions/"/> <meta name="generator" content="WordPress 3.6-alpha-23334"/> <link rel="canonical" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/08/ways-to-organise-the-accessibility-initiative/"/> <link rel="shortlink" href="https://web.archive.org/web/20130126200808/http://wp.me/p21sSb-28"/> <!-- Jetpack Open Graph Tags --> <meta property="og:type" content="article"/> <meta property="og:title" content="Ways to Organise the Accessibility Initiative"/> <meta property="og:url" content="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/08/ways-to-organise-the-accessibility-initiative/"/> <meta property="og:description" content="Since the news that some WordPress teams are to be merged, I’ve been thinking (a lot) about this group might move forward. First off, I need to say that I do understand why it might be necess..."/> <meta property="og:site_name" content="Make WordPress Accessible"/> <style type="text/css"> .is-js .hide-if-js { display: none; } .p2-task-list ul { margin-left: 0 !important; } .p2-task-list ul ul { margin-left: 20px !important; } .p2-task-list li { list-style: none; } </style> <script type="text/javascript"> jQuery( function( $ ) { $( 'body' ) .addClass( 'is-js' ) .delegate( '.p2-task-list :checkbox', 'click', function() { var $this = $( this ), $li = $this.parents( 'li:first' ), $form = $this.parents( 'form:first' ), data = $li.find( ':input' ).serialize(), colorEl = $li, origColor = $li.css( 'background-color' ), color; while ( colorEl.get(0).tagName && colorEl.css( 'background-color' ).match( /^\s*(rgba\s*\(\s*0+\s*,\s*0+\s*,\s*0+\s*,\s*0+\s*\)|transparent)\s*$/ ) ) { colorEl = colorEl.parent(); } color = colorEl.get(0).tagName ? colorEl.css( 'background-color' ) : '#ffffff'; data += '&ajax=1&' + $form.find( '.submit :input' ).serialize(); $.post( $form.attr( 'action' ), data, function( response ) { if ( '1' === response ) $li.css( 'background-color', '#F6F3D1' ).animate( { backgroundColor: color }, 'slow', function() { $li.css( 'background-color', origColor ); } ); } ); } ); } ); </script> <style type="text/css">.recentcomments a{display:inline !important;padding:0 !important;margin:0 !important;}</style> <style type="text/css" media="print">#wpadminbar { display:none; }</style> <style type="text/css" media="screen"> html { margin-top: 28px !important; } * html body { margin-top: 28px !important; } </style> <style id="p2-header-style" type="text/css"> </style> <meta id="syntaxhighlighteranchor" name="syntaxhighlighter-version" content="3.1.3"/> <script type="text/javascript"> /* <![CDATA[ */ var wpNotesIsJetpackClient = true; /* ]]> */ </script> <script type="text/javascript" src="https://web.archive.org/web/20130126200808js_/http://s.wordpress.org/wp-includes/js/jquery/jquery.js"></script> <script>document.cookie='devicePixelRatio='+((window.devicePixelRatio === undefined) ? 1 : window.devicePixelRatio)+'; path=/';</script> </head> <body id="wordpress-org" class="single single-post postid-132 single-format-standard admin-bar no-customize-support"> <div id="header"> <div class="wrapper"> <h1><a href="https://web.archive.org/web/20130126200808/http://s.wordpress.org/">WordPress.org</a></h1> <form action="https://web.archive.org/web/20130126200808/http://wordpress.org/search/do-search.php" method="get" id="head-search"> <input class="text" name="search" type="text" value="Search WordPress.org" maxlength="150" onfocus="this.value=(this.value=='Search WordPress.org') ? '' : this.value;" onblur="this.value=(this.value=='') ? 'Search WordPress.org' : this.value;"/> <input type="submit" class="button" value="Go"/> </form> <ul> <li><a href="https://web.archive.org/web/20130126200808/http://wordpress.org/showcase/" title="See some of the sites built on WordPress.">Showcase</a></li> <li><a href="https://web.archive.org/web/20130126200808/http://wordpress.org/extend/themes/" title="Find just the right look for your website.">Themes</a></li> <li><a href="https://web.archive.org/web/20130126200808/http://wordpress.org/extend/plugins/" title="Plugins can extend WordPress to do almost anything you can imagine.">Plugins</a></li> <li><a href="https://web.archive.org/web/20130126200808/http://wordpress.org/extend/mobile/" title="Take your website on the go!">Mobile</a></li> <li><a href="https://web.archive.org/web/20130126200808/http://wordpress.org/support/" title="Forums, documentation, help.">Support</a><ul class="nav-submenu"><li><a href="https://web.archive.org/web/20130126200808/http://wordpress.org/support/" title="Support and discussion forums.">Forums</a></li><li><a href="https://web.archive.org/web/20130126200808/http://codex.wordpress.org/Main_Page" title="Documentation, tutorials, best practices.">Docs</a></li></ul></li> <li><a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/" title="Contribute your knowledge." class="current">Get Involved</a><ul class="nav-submenu"><li><a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/core/" title="Write the code.">Core</a></li><li><a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/ui/" title="Improve the interface.">UI</a></li><li><a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/" title="Create a better experience.">Accessibility</a></li><li><a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/plugins/" title="Extend the system.">Plugins</a></li><li><a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/themes/" title="Beautify the web.">Themes</a></li><li><a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/support/" title="Help the users.">Support</a></li><li><a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/polyglots/" title="Translate for the world.">Polyglots</a></li><li><a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/mobile/" title="On the go.">Mobile</a></li></ul></li> <li><a href="https://web.archive.org/web/20130126200808/http://wordpress.org/about/" title="About the WordPress Organization, and where we're going.">About</a></li> <li><a href="https://web.archive.org/web/20130126200808/http://wordpress.org/news/" title="Come here for the latest scoop.">Blog</a></li> <li><a href="https://web.archive.org/web/20130126200808/http://wordpress.org/hosting/" title="Find a home for your blog.">Hosting</a></li> <li id="download"><a href="https://web.archive.org/web/20130126200808/http://wordpress.org/download/" title="Get it. Got it? Good.">Download</a></li> </ul> </div> </div> <div id="headline"> <div class="wrapper"> <h2><a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/">Make WordPress Accessible</a></h2> </div> </div> <div id="header2"> <!-- <div class="sleeve"> <h1><a href="http://make.wordpress.org/accessibility/">Make WordPress Accessible</a></h1> <small>Equal Access For All</small> <a class="secondary" href="http://make.wordpress.org/accessibility/"></a> </div> --> </div> <div id="wrapper"> <div id="sidebar"> <ul> <li id="text-5" class="widget widget_text"><h2 class="widgettitle">About</h2> <div class="textwidget"><p>Welcome to the official blog for the WordPress accessibility group - dedicated to improving accessibility in core WordPress and related projects . To join in the discussions, just log in using your WordPress.org username and password.</p> </div> </li> <li id="search-2" class="widget widget_search"><h2 class="widgettitle">Search This Site</h2> <form role="search" method="get" id="searchform" action="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/"> <div><label class="screen-reader-text" for="s">Search for:</label> <input type="text" value="" name="s" id="s"/> <input type="submit" id="searchsubmit" value="Search"/> </div> </form></li> <li id="pages-3" class="widget widget_pages"><h2 class="widgettitle">Pages</h2> <ul> <li class="page_item page-item-142"><a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/can-you-help/">Can You Help?</a></li> <li class="page_item page-item-62"><a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/theme-accessibility-audit-draft-proposal/">Theme Accessibility Audit: Draft Proposal</a></li> <li class="page_item page-item-162"><a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/useful-tools/">Useful Tools</a></li> <li class="page_item page-item-99"><a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/wp-accessibility-plugin/">WP Accessibility Plugin</a></li> </ul> </li> <li id="blog_subscription-3" class="widget jetpack_subscription_widget"><h2 class="widgettitle"><label for="subscribe-field">Subscribe via Email</label></h2> <a id="subscribe-blog"></a> <form action="" method="post" accept-charset="utf-8" id="subscribe-blog"> <p>Enter your email address to subscribe to this blog and receive notifications of new posts by email.</p><p>Join 137 other subscribers</p> <p><input type="text" name="email" style="width: 95%; padding: 1px 2px" value="Email Address" id="subscribe-field" onclick="if ( this.value == 'Email Address' ) { this.value = ''; }" onblur="if ( this.value == '' ) { this.value = 'Email Address'; }"/></p> <p> <input type="hidden" name="action" value="subscribe"/> <input type="hidden" name="source" value="http://make.wordpress.org/accessibility/2013/01/08/ways-to-organise-the-accessibility-initiative/"/> <input type="hidden" name="sub-type" value="widget"/> <input type="hidden" name="redirect_fragment" value="blog_subscription-3"/> <input type="submit" value="Subscribe" name="jetpack_subscriptions_widget"/> </p> </form> </li> <li id="recent-posts-2" class="widget widget_recent_entries"> <h2 class="widgettitle">Recent Posts</h2> <ul> <li> <a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/25/irc-meetups/" title="IRC Meetups">IRC Meetups</a> </li> <li> <a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/24/dont-let-it-snow-how-autoplays-can/" title="Don’t “Let It Snow ” How Autoplays Can…">Don’t “Let It Snow ” How Autoplays Can…</a> </li> <li> <a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/15/aaron-jorbin-is-suggesting-that-the-new-twenty/" title="Aaron Jorbin is suggesting that the new Twenty…">Aaron Jorbin is suggesting that the new Twenty…</a> </li> <li> <a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/11/user-videos-an-accessibility-angle/" title="User Videos – An Accessibility Angle">User Videos – An Accessibility Angle</a> </li> <li> <a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/10/accessibillty-questions-on-the-support-forums/" title="Accessibillty Questions on the Support Forums">Accessibillty Questions on the Support Forums</a> </li> </ul> </li> <li id="recent-comments-2" class="widget widget_recent_comments"><h2 class="widgettitle">Recent Comments</h2> <ul id="recentcomments"><li class="recentcomments"><a href="https://web.archive.org/web/20130126200808/http://accessiblejoe.com/" rel="external nofollow" class="url">Joseph Karr O'Connor</a> on <a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/25/irc-meetups/#comment-38005">IRC Meetups</a></li><li class="recentcomments"><a href="https://web.archive.org/web/20130126200808/http://codex.wordpress.org/User:Esmi" rel="external nofollow" class="url">esmi</a> on <a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/25/irc-meetups/#comment-37997">IRC Meetups</a></li><li class="recentcomments"><a href="https://web.archive.org/web/20130126200808/http://accessiblejoe.com/" rel="external nofollow" class="url">Joseph Karr O'Connor</a> on <a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/25/irc-meetups/#comment-37994">IRC Meetups</a></li><li class="recentcomments"><a href="https://web.archive.org/web/20130126200808/http://accessiblejoe.com/" rel="external nofollow" class="url">Joseph Karr O'Connor</a> on <a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/25/irc-meetups/#comment-37991">IRC Meetups</a></li><li class="recentcomments"><a href="https://web.archive.org/web/20130126200808/http://helen.wordpress.com/" rel="external nofollow" class="url">Helen Hou-Sandi</a> on <a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/25/irc-meetups/#comment-37987">IRC Meetups</a></li></ul></li> <li id="rss_links-2" class="widget widget_rss_links"><h2 class="widgettitle">Feeds</h2> <ul><li><a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/feed/" title="Subscribe to Posts">RSS - Posts</a></li><li><a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/comments/feed/" title="Subscribe to Comments">RSS - Comments</a></li></ul> </li> <li id="text-6" class="widget widget_text"><h2 class="widgettitle">Accessibility Trac tickets</h2> <div class="textwidget"><ul> <li><a href="https://web.archive.org/web/20130126200808/http://core.trac.wordpress.org/query?status=new&component=Accessibility&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&col=resolution&col=reporter&order=id">New</a></li> <li><a href="https://web.archive.org/web/20130126200808/http://core.trac.wordpress.org/query?status=accepted&status=assigned&component=Accessibility&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&col=resolution&col=reporter&order=id">Accepted/Assigned</a></li> <li><a href="https://web.archive.org/web/20130126200808/http://core.trac.wordpress.org/query?status=reopened&component=Accessibility&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&col=resolution&col=reporter&order=id">Re-opened</a></li> <li><a href="https://web.archive.org/web/20130126200808/http://core.trac.wordpress.org/query?status=closed&component=Accessibility&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&col=resolution&col=reporter&order=id">Closed</a></li> </ul></div> </li> <li id="rss-3" class="widget widget_rss"><h2 class="widgettitle"><a class="rsswidget" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/core/feed/" title="Syndicate this content"><img style="border:0" width="14" height="14" src="https://web.archive.org/web/20130126200808im_/http://make.wordpress.org/accessibility/wp-includes/images/rss.png" alt="RSS"/></a> <a class="rsswidget" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/core" title="WordPress Development Updates">Core Development</a></h2> <ul><li><a class="rsswidget" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/core/2013/01/25/revision-update-125/" title="Yesterday, the revisions team had its second scheduled office hours chat in #wordpress-dev at 1600 UTC. @karmatosed and I were both afk, and our first chat was earlier this week, so it was a short meeting [IRC log]. @nacin popped in to mention that he’ll be working on the API for draft changes to published […]">Revision Update, 1/25</a> <span class="rss-date">January 25, 2013</span></li><li><a class="rsswidget" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/core/2013/01/25/autosave-and-post-locking-update-125/" title="We had our scheduled meeting today in IRC to continue planning the feature for this cycle. @azaozz noted that he’s continuing work on the Heartbeat API #23216, on schedule for initial commit before next week. I am continuing work on an initial pass for the post/page tables to display locks, and properly display edit/bulk edit […]">Autosave and Post Locking Update, 1/25</a> <span class="rss-date">January 25, 2013</span></li><li><a class="rsswidget" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/core/2013/01/25/agenda-for-todays-autosave-and-post-locking-team/" title="Agenda for today’s autosave and post locking team meeting at 21:00 UTC: Assign contributors for each component: Autosave in the browser storage, Post locking, Login expiration warning. Further discussion on workflow for post locking, perhaps look at the plugin by jayminkapish on #18515. Free-form Q&A. […]">Agenda for today’s autosave and post locking team…</a> <span class="rss-date">January 25, 2013</span></li><li><a class="rsswidget" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/core/2013/01/24/editorial-flow-update-124/" title="Kovshenin, Nacin and I chatted today in IRC about scope for editorial flow in 3.6. To help narrow things down, we’re now focusing on two things: 1) “Finishing” the existing API such that you can register new post statuses with expected results (no bugs, etc.). Last week, Nacin and I had a long conversation about […]">Editorial Flow Update, 1/24</a> <span class="rss-date">January 24, 2013</span></li><li><a class="rsswidget" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/core/2013/01/23/for-tomorrows-menu-office-hours-i-only/" title="For tomorrows “Menu” office hours I only have one agenda item: To figure out where we’re headed with menus in 3.6. The way I see it, we have 3 options: 1) Nacin’s concept We could push in the direction of Nacin’s concept. 2) The two screen approach We could go with the two screen approach. […]">For tomorrows Menu office hours I only…</a> <span class="rss-date">January 23, 2013</span></li></ul></li> <li id="rss-4" class="widget widget_rss"><h2 class="widgettitle"><a class="rsswidget" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/ui/feed/" title="Syndicate this content"><img style="border:0" width="14" height="14" src="https://web.archive.org/web/20130126200808im_/http://make.wordpress.org/accessibility/wp-includes/images/rss.png" alt="RSS"/></a> <a class="rsswidget" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/ui" title="A Better User Experience">WordPress UI</a></h2> <ul><li><a class="rsswidget" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/ui/2013/01/21/3-6-core-development-cycle/" title="If you’re looking to contribute to core UI, you’ll want to keep an eye on Make/Core, as we’re shifting our thinking of core UI contributions to being an integral part of various areas of core rather than a separate group/workflow/etc. All of the planned features for 3.6 include UI components and participation in them is […]">3.6 Core Development Cycle</a> <span class="rss-date">January 21, 2013</span></li><li><a class="rsswidget" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/ui/2013/01/21/i-thought-id-run-one-more-user-through/" title="I thought I’d run one more user through testing our current concept of having both a “manage” screen and a “add/edit” screen for menus. For this test I added a quick little JS hack to visually highlight the “Menus in your theme” meta box when a user clicks there from the “add/edit” screen success message. […]">I thought I’d run one more user through…</a> <span class="rss-date">January 21, 2013</span></li><li><a class="rsswidget" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/ui/2013/01/11/here-are-the-results-from-user-7-in/" title="Here are the results from user 7 (in our menus user testing series) & user 8 both with the 23119.17.diff patch applied. User #7 Step 1: Log in No issues. Step 2: Go to menus No issues. Step 3: Add a menu No issues. Step 4: Add pages to menu No issues. Step 5: Reorganize […]">Here are the results from user 7 in…</a> <span class="rss-date">January 11, 2013</span></li><li><a class="rsswidget" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/ui/2013/01/09/two-more-menus-user-tests-focusing-on-this/" title="Two more menus user tests, focusing on this layout concept: User 5 (in the series) & User 6. User #5 Step 1: Log in No issues. Step 2: Go to menus No issues. Step 3: Add a menu No issues. Step 4: Add pages to menu No issues. Step 5: Reorganize pages No issues. Step […]">Two more menus user tests focusing on this…</a> <span class="rss-date">January 9, 2013</span></li><li><a class="rsswidget" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/ui/2013/01/07/last-tuesday-we-tested-two-users-on-some/" title="Last Tuesday we tested two users on some menus scenarios. On friday I posted a couple hypotheses and patches for potential improvements. This morning, I tested two additional users with these patches applied: User 3 (in the series) & User 4. Here’s what I saw: User #3 Step 1: Log in No issues. Step 2: […]">Last Tuesday we tested two users on some…</a> <span class="rss-date">January 7, 2013</span></li></ul></li> <li id="rss-5" class="widget widget_rss"><h2 class="widgettitle"><a class="rsswidget" href="https://web.archive.org/web/20130126200808/http://wordpress.org/support/rss/tags/accessibility" title="Syndicate this content"><img style="border:0" width="14" height="14" src="https://web.archive.org/web/20130126200808im_/http://make.wordpress.org/accessibility/wp-includes/images/rss.png" alt="RSS"/></a> <a class="rsswidget" href="https://web.archive.org/web/20130126200808/http://wordpress.org/tags/accessibility" title="WordPress › Support » Tag: accessibility - Recent Posts">Forum Posts</a></h2> <ul><li><a class="rsswidget" href="https://web.archive.org/web/20130126200808/http://wordpress.org/support/topic/coraline-missing-focus-styles#post-3773090" title="There are no ":focus" styles defined in the Coraline theme, which makes it difficult to navigate the page using only a keyboard and no mouse. (Here's a bit more detail on why this is a problem: "Whenever you use :hover, also use :focus" ) I've fixed it locally by adding corresponding :focus rules for each :hover rule -- is there […]">larcher on "Coraline missing :focus styles"</a> <span class="rss-date">January 25, 2013</span></li><li><a class="rsswidget" href="https://web.archive.org/web/20130126200808/http://wordpress.org/support/topic/barrier-free-wordpress-style-switcher#post-3771516" title="As far as I know, thee isn't a decent stylesheet (as opposed to theme) switcher plugin available as yet. Creating one is on my ToDo list. In the meantime, there are some accessibility plugins listed on http://make.wordpress.org/accessibility/useful-tools/ […]">esmi on "barrier-free wordpress - style-switcher"</a> <span class="rss-date">January 25, 2013</span></li><li><a class="rsswidget" href="https://web.archive.org/web/20130126200808/http://wordpress.org/support/topic/barrier-free-wordpress-style-switcher#post-3771472" title="The only plugin I found so far is WP Accessibility, but that's not the feature I am looking for. […]">bej-soan on "barrier-free wordpress - style-switcher"</a> <span class="rss-date">January 25, 2013</span></li><li><a class="rsswidget" href="https://web.archive.org/web/20130126200808/http://wordpress.org/support/topic/barrier-free-wordpress-style-switcher#post-3771467" title="Hello there i'm currently working on a theme, with focus on barrier free access. I can't find much on this topic while searching, i'm looking if there are any plugins or articles. On a lot of barrier-free Websites theres the ability to deativate the standard style and change to a high-contrast or negative version. For Example here http://lfleg […]">bej-soan on "barrier-free wordpress - style-switcher"</a> <span class="rss-date">January 25, 2013</span></li><li><a class="rsswidget" href="https://web.archive.org/web/20130126200808/http://wordpress.org/support/topic/checkbox-group-missing-fieldset-andor-legend-tags-no-title-attribute#post-3766762" title="Joining the party a little later here but... @klepas: Can I possibly entice you to join us over at http://make.wordpress.org/accessibility/ ? […]">esmi on "[Plugin: Jetpack by WordPress.com] Checkbox group missing fieldset and/or legend tags, & no title attribute"</a> <span class="rss-date">January 24, 2013</span></li></ul></li> </ul> <div class="clear"></div> </div> <!-- // sidebar --> <div class="sleeve_main"> <div id="main"> <div class="controls"> <a href="#" id="togglecomments">Hide threads</a> <span class="sep"> | </span> <a href="#directions" id="directions-keyboard">Keyboard Shortcuts</a> <span class="single-action-links"></span> </div> <ul id="postlist"> <li id="prologue-132" class="post-132 post type-post status-publish format-standard hentry category-core"> <a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/author/esmi/" title="Posts by esmi ( @esmi )" class="post-avatar"> <img alt="" src="https://web.archive.org/web/20130126200808im_/http://0.gravatar.com/avatar/0d9561ad86e233e23263cbbeaeb418cc?s=48&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D48&r=G" class="avatar avatar-48 photo" height="48" width="48"/> </a> <h4> <a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/author/esmi/" title="Posts by esmi ( @esmi )">esmi</a> <span class="meta"> <abbr title="2013-01-08T15:43:22Z">3:43 pm <em>on</em> January 8, 2013</abbr> <span class="actions"> <a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/08/ways-to-organise-the-accessibility-initiative/" class="thepermalink printer-only" title="Permalink">Permalink</a> </span> <span class="tags"> </span> </span> </h4> <div id="content-132" class="postcontent"> <h2>Ways to Organise the Accessibility Initiative</h2><p>Since the news that some WordPress teams are to be merged, I’ve been thinking (a lot) about this group might move forward. First off, I need to say that I do understand why it might be necessary to merge some groups. Too much fragmentation is as bad as an overly centralised system when trying to manage/coordinate work whilst also ensuring a constant trickle of new blood.</p> <p>But I don’t think merging is the answer for this group. Accessibility is too over-arching an area to work well if we try to split it down into separate groups. We’re likely to lose impetus with over-dilution, Plus we will loose the opportunity to attract assistive technology users who could, longer term, become a panel of expert testers. We actively need an ongoing dialogue between technical developers and non-technical users to help wordpress.org develop effective accessible solutions.</p> <p>So I feel that we need to stay as a separate group but with direct links into the other groups – possibly via designated lead developers.</p> <p>If that’s possible, then we’ll also need to work hard to coordinate and communicate the changes that are taking place — both in terms of what we’ve achieved and to highlight work in other groups where we might be able to contribute. To that end, I’m going to see if I can pull in feeds from some of the other groups to see if will help us to highlight areas where we need to get involved.</p> <p>If you’re already involved in discussions in other groups or in Trac, then please let us know what you are doing via a status update here. If you do not have posting privileges here, let me know and I’ll sort that out for you.</p> <p>In the meantime, if anyone has any other ideas of how we can ficus our efforts more effectively, then please chime in.</p> </div> <div class="discussion" style="display: none"> <p> <a href="https://web.archive.org/web/20130126200808/http://wpdaily.co/roundup-4/" rel="external nofollow" class="url">The WordPress Weekend Roundup - WP Daily</a>, <img alt="" src="https://web.archive.org/web/20130126200808im_/http://1.gravatar.com/avatar/378e4cbcfa201c8ff0b8398b9da9d1b3?s=16&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D16&r=G" class="avatar avatar-16 photo" height="16" width="16"/> <a href="https://web.archive.org/web/20130126200808/http://gentlewit.com/" rel="external nofollow" class="url">Cyndy Otty</a>, <img alt="" src="https://web.archive.org/web/20130126200808im_/http://0.gravatar.com/avatar/0d9561ad86e233e23263cbbeaeb418cc?s=16&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D16&r=G" class="avatar avatar-16 photo" height="16" width="16"/> <a href="https://web.archive.org/web/20130126200808/http://codex.wordpress.org/User:Esmi" rel="external nofollow" class="url">esmi</a>, and 4 others are discussing. <a href="#" class="show-comments">Toggle Comments</a> </p> </div> <div class="bottom-of-entry"> </div> <ul id="comments-132" class="commentlist inlinecomments"> <li id="comment-35831" class="comment byuser comment-author-sharonaustin even thread-even depth-1"> <img alt="" src="https://web.archive.org/web/20130126200808im_/http://1.gravatar.com/avatar/f29ca7b5a57981f3f44d2d8c4f971af8?s=32&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D32&r=G" class="avatar avatar-32 photo" height="32" width="32"/> <h4> Nelson <span class="meta"> <abbr title="2013-01-08T15:52:16Z">3:52 pm <em>on</em> January 8, 2013</abbr> <span class="actions"> <a class="thepermalink" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/08/ways-to-organise-the-accessibility-initiative/#comment-35831" title="Permalink">Permalink</a> </span> </span> </h4> <div id="commentcontent-35831" class="commentcontent"><p>esmi, by all means, if there is a way that non-technical people such as myself could help with testing, please let us know. Accessibility is so crucial to making knowledge available to those without the privilege of health and wealth. </p> <p>The one idea I have for “focusing” attention on accessibility issues is unfortunately, to divide them up. It’s amazing to me how “different” the technology must be to address “different” accessibility needs–and I find that expertise in one area (e.g., blindness) does not lead to expertise in other areas (e.g., mobility issues)–so possibly breaking down groups by accessibility needs would help, I think.</p> <p>Also, I am stunned at some of the assistive technology available on iPads. Perhaps, if some attention could be given to making WordPress work on iPad technology, that alone would help many who depend on the technology.</p> <p>I also want to say, THANK YOU for what you do here. It matters.</p> <p>Best regards.</p> </div> </li> <li id="comment-35855" class="comment byuser comment-author-esmi bypostauthor odd alt thread-odd thread-alt depth-1"> <img alt="" src="https://web.archive.org/web/20130126200808im_/http://0.gravatar.com/avatar/0d9561ad86e233e23263cbbeaeb418cc?s=32&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D32&r=G" class="avatar avatar-32 photo" height="32" width="32"/> <h4> <a href="https://web.archive.org/web/20130126200808/http://codex.wordpress.org/User:Esmi" rel="external nofollow" class="url">esmi</a> <span class="meta"> <abbr title="2013-01-08T16:26:16Z">4:26 pm <em>on</em> January 8, 2013</abbr> <span class="actions"> <a class="thepermalink" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/08/ways-to-organise-the-accessibility-initiative/#comment-35855" title="Permalink">Permalink</a> </span> </span> </h4> <div id="commentcontent-35855" class="commentcontent"><p>Dividing issues up into areas based on “need” or technology tends to create as many problems as it solves, in my experience because the needs of one group can run counter to the other (visual impairment versus dyslexia immediately springs to mind). What is really needed are solutions that balance disparate needs without skewing towards any one group — including those without any special need. Those of us with a technical background in accessibility tend to approach any one situation by looking at it through “different eyes” so that we get a broad idea of what barriers exist for different groups and how to correct them without creating new ones in the process.</p> <p>With regards to how you can help — firstly, tell us about any specific problems you are facing. We try to identify problem areas but we undoubtedly miss some. So we need people like yourself to keep us on our toes and point out the problems.</p> <p>Secondly, if you are interested in joining an expert panel of testers, please contact me using esmi [at] quirm [dot] net. And thank you for your comments,</p> </div> </li> <li id="comment-35871" class="comment byuser comment-author-sharonaustin even thread-even depth-1"> <img alt="" src="https://web.archive.org/web/20130126200808im_/http://1.gravatar.com/avatar/f29ca7b5a57981f3f44d2d8c4f971af8?s=32&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D32&r=G" class="avatar avatar-32 photo" height="32" width="32"/> <h4> Nelson <span class="meta"> <abbr title="2013-01-08T16:52:50Z">4:52 pm <em>on</em> January 8, 2013</abbr> <span class="actions"> <a class="thepermalink" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/08/ways-to-organise-the-accessibility-initiative/#comment-35871" title="Permalink">Permalink</a> </span> </span> </h4> <div id="commentcontent-35871" class="commentcontent"><p>esmi, thank you for the rapid response.</p> <p>The problem is that I am trying to set up a website for a wide variety of users. It’s for a public institution, which fortunately, by law, requires accessibility, but means accessibility for all disabilities. </p> <p>The site expertise seems to be with blind users, but from the limited exposure I’ve had with testing, the blind user did not use the features we built into the site for the screen readers. The screen readers seem to rely on technology that is one generation behind–they haven’t caught up to HTML5 standards. This is fine, as I find that HTML5 standards aren’t widely supported by browsers yet and don’t really add anything to accessibility.</p> <p>He surprised us, and largely used simple HTML markup to navigate, which is why I’m so adamant about building site using old HTML markup standards h1, then h2, etc. and keeping it simple in terms of markup, CSS, and navigation. And, from what I understand, basic HTML markup is very friendly to assistive technology; it’s when people get fancy with the markup that assistive technology runs into problems. But the point is that if we keep the HTML clean, I think we’ve got the blind users covered.</p> <p>However, building a site for a public institution can’t just be about blind users. Although we haven’t yet had a user with mobility and/or physical restriction issues, I certainly expect such a user to come to the site. We’ve got a lot of wounded veterans out there who (hopefully) will take advantage of what the institution offers. </p> <p>I hope that helps. I will certainly contact you, and again, thankyou for all you do.</p> </div> </li> <li id="comment-35875" class="comment byuser comment-author-esmi bypostauthor odd alt thread-odd thread-alt depth-1"> <img alt="" src="https://web.archive.org/web/20130126200808im_/http://0.gravatar.com/avatar/0d9561ad86e233e23263cbbeaeb418cc?s=32&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D32&r=G" class="avatar avatar-32 photo" height="32" width="32"/> <h4> <a href="https://web.archive.org/web/20130126200808/http://codex.wordpress.org/User:Esmi" rel="external nofollow" class="url">esmi</a> <span class="meta"> <abbr title="2013-01-08T17:08:15Z">5:08 pm <em>on</em> January 8, 2013</abbr> <span class="actions"> <a class="thepermalink" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/08/ways-to-organise-the-accessibility-initiative/#comment-35875" title="Permalink">Permalink</a> </span> </span> </h4> <div id="commentcontent-35875" class="commentcontent"><p>“if we keep the HTML clean, I think we’ve got the blind users covered.”</p> <p>Yes. If you can go one step further and validate your markup, you’ll cover many of the issues faced by blind users. Also have a look at some of the articles on <a href="https://web.archive.org/web/20130126200808/http://accessites.org/site/category/articles/" rel="nofollow">accessites.org</a>. You should find them helpful in developing a balanced approach to a11y.</p> </div> </li> <li id="comment-35904" class="comment byuser comment-author-azaozz even thread-even depth-1"> <img alt="" src="https://web.archive.org/web/20130126200808im_/http://0.gravatar.com/avatar/4e84843ebff0918d72ade21c6ee7b1e4?s=32&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D32&r=G" class="avatar avatar-32 photo" height="32" width="32"/> <h4> <a href="https://web.archive.org/web/20130126200808/http://profiles.wordpress.org/azaozz/" rel="external nofollow" class="url">Andrew Ozz</a> <span class="meta"> <abbr title="2013-01-08T20:29:32Z">8:29 pm <em>on</em> January 8, 2013</abbr> <span class="actions"> <a class="thepermalink" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/08/ways-to-organise-the-accessibility-initiative/#comment-35904" title="Permalink">Permalink</a> </span> </span> </h4> <div id="commentcontent-35904" class="commentcontent"><blockquote><p>I feel that we need to stay as a separate group but with direct links into the other groups…</p></blockquote> <p>Thinking so too. Accessibility is an integral part of the UI. However “getting it right” requires several different types of testing and feedback that are quite different from the “standard” UI and graphic design work.</p> <p>We shouldn’t be making any changes or creating new UI components without them being tested for accessibility. In that terms having the “expert panel of testers” is most important. The next thing would be to encourage users of assistive technology to report bugs and inconsistencies.</p> </div> </li> <li id="comment-35905" class="comment byuser comment-author-joedolson odd alt thread-odd thread-alt depth-1"> <img alt="" src="https://web.archive.org/web/20130126200808im_/http://0.gravatar.com/avatar/ee77adf6adc6fe90b388f97b0bd912b2?s=32&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D32&r=G" class="avatar avatar-32 photo" height="32" width="32"/> <h4> <a href="https://web.archive.org/web/20130126200808/http://www.joedolson.com/" rel="external nofollow" class="url">Joe Dolson</a> <span class="meta"> <abbr title="2013-01-08T20:43:28Z">8:43 pm <em>on</em> January 8, 2013</abbr> <span class="actions"> <a class="thepermalink" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/08/ways-to-organise-the-accessibility-initiative/#comment-35905" title="Permalink">Permalink</a> </span> </span> </h4> <div id="commentcontent-35905" class="commentcontent"><p>Right now, I’m focused on trying to get the accessibility-ready theme tag up and moving. I’m working on adding the appropriate checks to the theme-check plug-in, so that I can send those over when they’re ready. If anybody would like to help, that would be great.</p> </div> <ul class="children"> <li id="comment-35907" class="comment byuser comment-author-esmi bypostauthor even depth-2"> <img alt="" src="https://web.archive.org/web/20130126200808im_/http://0.gravatar.com/avatar/0d9561ad86e233e23263cbbeaeb418cc?s=32&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D32&r=G" class="avatar avatar-32 photo" height="32" width="32"/> <h4> <a href="https://web.archive.org/web/20130126200808/http://codex.wordpress.org/User:Esmi" rel="external nofollow" class="url">esmi</a> <span class="meta"> <abbr title="2013-01-08T20:53:04Z">8:53 pm <em>on</em> January 8, 2013</abbr> <span class="actions"> <a class="thepermalink" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/08/ways-to-organise-the-accessibility-initiative/#comment-35907" title="Permalink">Permalink</a> </span> </span> </h4> <div id="commentcontent-35907" class="commentcontent"><p>Anything I can do to help, just holler..</p> </div> </li> </ul> </li> <li id="comment-35955" class="comment odd alt thread-even depth-1"> <img alt="" src="https://web.archive.org/web/20130126200808im_/http://1.gravatar.com/avatar/9a0144538f841e53a121a00a1fe4c669?s=32&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D32&r=G" class="avatar avatar-32 photo" height="32" width="32"/> <h4> <a href="https://web.archive.org/web/20130126200808/http://www.coolfields.co.uk/" rel="external nofollow" class="url">Graham Armfield</a> <span class="meta"> <abbr title="2013-01-09T09:26:27Z">9:26 am <em>on</em> January 9, 2013</abbr> <span class="actions"> <a class="thepermalink" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/08/ways-to-organise-the-accessibility-initiative/#comment-35955" title="Permalink">Permalink</a> </span> </span> </h4> <div id="commentcontent-35955" class="commentcontent"><p>On balance I think that accessibility should kept as a separate group. Although accessibility needs to become part of all the other groups too, having a separate group hopefully can allow us to keep a real cohesive focus.</p> <p>The challenge, I feel, is to convince enough of the core developers of WordPress to even think about accessibility when they are building the new bits of functionality into the core or updating existing parts. Look at the experience with Theme Customizer – it was just completely impossible to use without a mouse when developed. That was addressed in 3.5 as a result of a trac ticket, but that’s a poor way of ensuring accessibility of WordPress – retrofitting always is difficult and wastes time.</p> <p>How we get accessibility more mainstream within WordPress?</p> <p>Maybe by getting as much action going on within this forum as possible – including from people with disabilities/impairments who have not currently contributed. Would that help? Would some kind of WP accessibility mission statement help? I’d like to think so.</p> <p>Esmi, please can you give me the ability to post new discussions on this forum. Thanks.</p> <p>Graham</p> </div> <ul class="children"> <li id="comment-35971" class="comment byuser comment-author-esmi bypostauthor even depth-2"> <img alt="" src="https://web.archive.org/web/20130126200808im_/http://0.gravatar.com/avatar/0d9561ad86e233e23263cbbeaeb418cc?s=32&d=http%3A%2F%2F0.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D32&r=G" class="avatar avatar-32 photo" height="32" width="32"/> <h4> <a href="https://web.archive.org/web/20130126200808/http://codex.wordpress.org/User:Esmi" rel="external nofollow" class="url">esmi</a> <span class="meta"> <abbr title="2013-01-09T12:06:53Z">12:06 pm <em>on</em> January 9, 2013</abbr> <span class="actions"> <a class="thepermalink" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/08/ways-to-organise-the-accessibility-initiative/#comment-35971" title="Permalink">Permalink</a> </span> </span> </h4> <div id="commentcontent-35971" class="commentcontent"><blockquote><p>How we get accessibility more mainstream within WordPress?</p></blockquote> <p>We join as many relevant development, UI and core discussions as we can so that, with each change, we push for any accessibility changes needed and guard against new barriers being introduced. Sure – that may turn us into the proverbial bad pennies is some places but, if we prod people enough times, they may start starting thinking about accessibility before being prompted.</p> <blockquote><p>including from people with disabilities/impairments who have not currently contributed. Would that help?</p></blockquote> <p>Absolutely! We need feedback, ideas and comments from users with disabilities/impairments. Not technical points but more along the lines of “I use foo software and I find it really difficult/impossible to use bar on my site”. Give us areas that need improvement and we can take them to the people who make the changes. I’d also love to hear from anyone using assistive technology who would be interested in being part of a testing panel. I’m hoping to set up a contact form especially for this purpose shortly.</p> <blockquote><p> can you give me the ability to post new discussions</p></blockquote> <p>You now have full access. Sorry about that. I didn’t realise you weren’t in the list of users here.</p> </div> <ul class="children"> <li id="comment-35992" class="comment byuser comment-author-ceo odd alt depth-3"> <img alt="" src="https://web.archive.org/web/20130126200808im_/http://1.gravatar.com/avatar/378e4cbcfa201c8ff0b8398b9da9d1b3?s=32&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D32&r=G" class="avatar avatar-32 photo" height="32" width="32"/> <h4> <a href="https://web.archive.org/web/20130126200808/http://gentlewit.com/" rel="external nofollow" class="url">Cyndy Otty</a> <span class="meta"> <abbr title="2013-01-09T14:17:11Z">2:17 pm <em>on</em> January 9, 2013</abbr> <span class="actions"> <a class="thepermalink" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/08/ways-to-organise-the-accessibility-initiative/#comment-35992" title="Permalink">Permalink</a> </span> </span> </h4> <div id="commentcontent-35992" class="commentcontent"><blockquote><p>I’d also love to hear from anyone using assistive technology who would be interested in being part of a testing panel.</p></blockquote> <p>I’m more than happy to help with testing stuff. And this is actually very key because much like everyone has their own computer set up (e.g., operating system, browser, etc.) so too are adaptive tech set ups and they all work differently, have their own issues, etc.</p> </div> </li> </ul> </li> </ul> </li> <li id="comment-36157" class="pingback even thread-odd thread-alt depth-1"> <h4> <a href="https://web.archive.org/web/20130126200808/http://wpdaily.co/roundup-4/" rel="external nofollow" class="url">The WordPress Weekend Roundup - WP Daily</a> <span class="meta"> <abbr title="2013-01-12T17:09:18Z">5:09 pm <em>on</em> January 12, 2013</abbr> <span class="actions"> <a class="thepermalink" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/08/ways-to-organise-the-accessibility-initiative/#comment-36157" title="Permalink">Permalink</a> </span> </span> </h4> <div id="commentcontent-36157" class="commentcontent"><p>[...] Better Organization [...]</p> </div> </li> </ul> </li> </ul> <div class="navigation"> <p class="nav-older"><a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2012/12/24/team-rep-voting-results/" rel="prev">← Team Rep Voting Results</a></p> <p class="nav-newer"><a href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/2013/01/08/wordpress-3-6-revisions/" rel="next">WordPress 3.6: Revisions →</a></p> </div> </div> <!-- main --> </div> <!-- sleeve --> <div class="clear"></div> </div> <!-- // wrapper --> <div id="notify"></div> <div id="help"> <dl class="directions"> <dt>c</dt><dd>compose new post</dd> <dt>j</dt><dd>next post/next comment</dd> <dt>k</dt> <dd>previous post/previous comment</dd> <dt>r</dt> <dd>reply</dd> <dt>e</dt> <dd>edit</dd> <dt>o</dt> <dd>show/hide comments</dd> <dt>t</dt> <dd>go to top</dd> <dt>l</dt> <dd>go to login</dd> <dt>h</dt> <dd>show/hide help</dd> <dt>shift + esc</dt> <dd>cancel</dd> </dl> </div> <div id="footer"> <div class="wrapper"> <p> <a href="https://web.archive.org/web/20130126200808/http://wordpress.org/about/privacy/">Privacy</a> | <a href="https://web.archive.org/web/20130126200808/http://wordpress.org/about/license/">License / GPLv2</a> See also: <a href="https://web.archive.org/web/20130126200808/http://wordpress.com/?ref=wporg-footer" title="Hassle-free WP hosting">Hosted WordPress.com</a> | <a href="https://web.archive.org/web/20130126200808/http://wordpress.tv/" title="Videos, tutorials, WordCamps">WordPress.TV Videos</a> | <a href="https://web.archive.org/web/20130126200808/http://central.wordcamp.org/" title="Find a WordPress event near your home">WordCamp Events</a> | <a href="https://web.archive.org/web/20130126200808/http://buddypress.org/" title="A set of plugins to transform your WordPress into a social network">BuddyPress Social Layer</a> | <a href="https://web.archive.org/web/20130126200808/http://bbpress.org/" title="Fast, slick forums built on WordPress">bbPress Forums</a> | <a href="https://web.archive.org/web/20130126200808/http://jobs.wordpress.net/" title="Find or post WordPress jobs">WP Jobs</a> | <a href="https://web.archive.org/web/20130126200808/http://ma.tt/" title="Co-founder of WordPress, an example of what WordPress can do">Matt</a> </p> <br/> <iframe src="https://web.archive.org/web/20130126200808if_/http://www.facebook.com/plugins/like.php?app_id=121415197926116&href=http%3A%2F%2Fwww.facebook.com%2Fwordpress&send=false&layout=button_count&width=150&show_faces=false&action=like&colorscheme=light&font=lucida+grande&height=21" scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:150px; height:21px;" allowtransparency="true"></iframe> <!-- <div class="g-plusone" data-size="medium" data-href="https://plus.google.com/107188080561309681193"></div> --> <iframe allowtransparency="true" frameborder="0" scrolling="no" src="https://web.archive.org/web/20130126200808if_/http://platform.twitter.com/widgets/follow_button.html?screen_name=WordPress&show_count=false" style="width:150px; height:20px;"></iframe> <h6>Code is Poetry</h6> </div> </div> <script type="text/javascript">_qoptions={qacct:"p-18-mFEk4J448M"};</script> <script type="text/javascript" src="https://web.archive.org/web/20130126200808js_/http://edge.quantserve.com/quant.js"></script> <noscript><img src="https://web.archive.org/web/20130126200808im_/http://pixel.quantserve.com/pixel/p-18-mFEk4J448M.gif" style="display: none;" border="0" height="1" width="1" alt=""/></noscript> <!-- 127 queries. 0.787 seconds. --> <script type="text/javascript" src="https://web.archive.org/web/20130126200808js_/http://s.gravatar.com/js/gprofiles.js"></script> <script type="text/javascript"> (function() { var po = document.createElement('script'); po.type = 'text/javascript'; po.async = true; po.src = 'https://web.archive.org/web/20130126200808/https://apis.google.com/js/plusone.js'; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(po, s); })(); </script> <script type="text/javascript"> (function($){ $(document).ready(function() { $('#footer a').click(function() { if (this.href.indexOf('wordpress.org') == -1 && this.href.indexOf('http') == 0) { recordOutboundLink(this, 'Outbound Links', this.href); return false; } }); }); })(jQuery); </script> </body> </html> <script type="text/javascript"> /* <![CDATA[ */ jQuery( document ).ready( function( $ ) { function hideComments() { $('.commentlist').hide(); $('.discussion').show(); } function showComments() { $('.commentlist').show(); $('.discussion').hide(); } $( "#togglecomments" ).click( function() { if ( $( '.commentlist' ).css( 'display' ) == 'none' ) { showComments(); } else { hideComments(); } return false; }); }); /* ]]> */ </script><link rel="stylesheet" id="notes-admin-bar-rest-css" href="https://web.archive.org/web/20130126200808cs_/http://s0.wp.com/wp-content/mu-plugins/notes/admin-bar-rest.css?ver=2.0.2-201304" type="text/css" media="all"/> <link rel="stylesheet" id="noticons-css" href="https://web.archive.org/web/20130126200808cs_/http://s0.wp.com/i/noticons/noticons.css?ver=2.0.2-201304" type="text/css" media="all"/> <script type="text/javascript" src="https://web.archive.org/web/20130126200808js_/http://make.wordpress.org/accessibility/wp-includes/js/admin-bar.min.js?ver=3.6-alpha-23334"></script> <script type="text/javascript" src="https://web.archive.org/web/20130126200808js_/http://s0.wp.com/wp-content/js/devicepx-jetpack.js?ver=201304"></script> <script type="text/javascript" src="https://web.archive.org/web/20130126200808js_/http://s1.wp.com/wp-content/js/mustache.js?ver=2.0.2-201304"></script> <script type="text/javascript" src="https://web.archive.org/web/20130126200808js_/http://make.wordpress.org/accessibility/wp-includes/js/underscore.min.js?ver=1.4.1"></script> <script type="text/javascript" src="https://web.archive.org/web/20130126200808js_/http://make.wordpress.org/accessibility/wp-includes/js/backbone.min.js?ver=0.9.2"></script> <script type="text/javascript" src="https://web.archive.org/web/20130126200808js_/http://s0.wp.com/wp-content/js/postmessage.js?ver=2.0.2-201304"></script> <script type="text/javascript" src="https://web.archive.org/web/20130126200808js_/http://make.wordpress.org/accessibility/wp-content/plugins/jetpack/_inc/spin.js?ver=1.2.4"></script> <script type="text/javascript" src="https://web.archive.org/web/20130126200808js_/http://make.wordpress.org/accessibility/wp-content/plugins/jetpack/_inc/jquery.spin.js?ver=3.6-alpha-23334"></script> <script type="text/javascript" src="https://web.archive.org/web/20130126200808js_/http://s0.wp.com/wp-content/mu-plugins/notes/notes-rest-common.js?ver=2.0.2-201304"></script> <script type="text/javascript" src="https://web.archive.org/web/20130126200808js_/http://s0.wp.com/wp-content/mu-plugins/notes/admin-bar-rest.js?ver=2.0.2-201304"></script> <script src="https://web.archive.org/web/20130126200808js_/http://stats.wordpress.com/e-201304.js" type="text/javascript"></script> <script type="text/javascript"> st_go({v:'ext',j:'1:2.0.2',blog:'29901991',post:'132'}); var load_cmc = function(){linktracker_init(29901991,132,2);}; if ( typeof addLoadEvent != 'undefined' ) addLoadEvent(load_cmc); else load_cmc(); </script> <div id="wpadminbar" class="nojq nojs" role="navigation"> <a class="screen-reader-shortcut" href="#wp-toolbar" tabindex="1">Skip to toolbar</a> <div class="quicklinks" id="wp-toolbar" role="navigation" aria-label="Top navigation toolbar." tabindex="0"> <ul id="wp-admin-bar-root-default" class="ab-top-menu"> <li id="wp-admin-bar-wp-logo" class="menupop"><a class="ab-item" aria-haspopup="true" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/wp-admin/about.php" title="About WordPress"><span class="ab-icon"></span></a><div class="ab-sub-wrapper"><ul id="wp-admin-bar-wp-logo-external" class="ab-sub-secondary ab-submenu"> <li id="wp-admin-bar-wporg"><a class="ab-item" href="https://web.archive.org/web/20130126200808/http://wordpress.org/">WordPress.org</a> </li> <li id="wp-admin-bar-documentation"><a class="ab-item" href="https://web.archive.org/web/20130126200808/http://codex.wordpress.org/">Documentation</a> </li> <li id="wp-admin-bar-support-forums"><a class="ab-item" href="https://web.archive.org/web/20130126200808/http://wordpress.org/support/">Support Forums</a> </li> <li id="wp-admin-bar-feedback"><a class="ab-item" href="https://web.archive.org/web/20130126200808/http://wordpress.org/support/forum/requests-and-feedback">Feedback</a> </li></ul></div> </li></ul><ul id="wp-admin-bar-top-secondary" class="ab-top-secondary ab-top-menu"> <li id="wp-admin-bar-search" class="admin-bar-search"><div class="ab-item ab-empty-item" tabindex="-1"><form action="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/" method="get" id="adminbarsearch"><input class="adminbar-input" name="s" id="adminbar-search" type="text" value="" maxlength="150"/><input type="submit" class="adminbar-button" value="Search"/></form></div> </li> <li id="wp-admin-bar-log-in"><a class="ab-item" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/wp-login.php">Log In</a> </li> <li id="wp-admin-bar-notes" class="menupop"><div class="ab-item ab-empty-item"><span id="wpnt-notes-unread-count" class="wpnt-loading wpn-read"> <span class="noticon noticon-notification"/></span> </span></div><div id="wpnt-notes-panel" style="display:none"><div class="wpnt-notes-panel-header"><span class="wpnt-notes-header">Notifications</span><span class="wpnt-notes-panel-link"></span></div></div> </li></ul> </div> <a class="screen-reader-shortcut" href="https://web.archive.org/web/20130126200808/http://make.wordpress.org/accessibility/wp-login.php?action=logout&_wpnonce=6b8c1aab52">Log Out</a> </div> </body> </html> <!-- FILE ARCHIVED ON 20:08:08 Jan 26, 2013 AND RETRIEVED FROM THE INTERNET ARCHIVE ON 19:25:01 Nov 25, 2024. JAVASCRIPT APPENDED BY WAYBACK MACHINE, COPYRIGHT INTERNET ARCHIVE. ALL OTHER CONTENT MAY ALSO BE PROTECTED BY COPYRIGHT (17 U.S.C. SECTION 108(a)(3)). --> <!-- playback timings (ms): captures_list: 0.686 exclusion.robots: 0.034 exclusion.robots.policy: 0.02 esindex: 0.013 cdx.remote: 9.749 LoadShardBlock: 417.145 (3) PetaboxLoader3.datanode: 136.9 (4) PetaboxLoader3.resolve: 184.484 (2) load_resource: 169.057 -->