I’m helping a screen reader who has been recently introduced to WordPress configure their new site, and noticed that they were becoming frustrated with the clutter of their WordPress administration menu thanks to plugins arbitrarily adding things to their top-level menus and inserting their own top-level menus in between the out-of-the-box ones. I had them install Menu Humility by Mark Jaquith. Despite the plugin not being updated in over a year, it still works exactly as it is intended, and I install it on every new site I build and every site I rebuild. I’ve mentioned this plugin before on this site, but wanted to mention it again because I find it so useful in my quest to minimize the trashfire that can result when plugin and theme authors clutter the dashboard in order to fulfill their own hopes or desires for more downloads or upgrades with no regard for the users actually using WordPress. If you’re running the latest version of WordPress, (and you really should be), upon viewing the plugin in the plugins/add-new screen, you’ll get a notice that says “untested with your version of WordPress.” In this case, ignore that notice, because this still works, thanks to WordPress’s commitment to backwards compatibility. This isn’t so much an accessibility issue as it is a “get off my lawn, stop cluttering my dashboard with your crap, my dashboard isn’t your playground” kind of scenario. Menu Humility isn’t the only plugin that can help with dashboard clutter, but it’s the first step to making it a saner place which induces less rage. Go get it if you haven’t already.
Read HTML Source Order vs CSS Display Order by Adrian Roselli

Last month in my post Source Order Matters I wrote about why we need to consider how the source order of the HTML of a page can affect users when the CSS re-orders the content visually. While I used a recipe as an analogue and cited WCAG conformance rules, I failed to provide specific examples. I prepared one for my talk at Accessibility Camp Toronto, but have since expanded on it with more examples.
I want to make sure that we all understand that the source order versus display order discussion is not unique to CSS Flexbox. It is not unique to CSS Grids. Many developers have been dealing with this (correctly and incorrectly) since CSS floats and absolute positioning were introduced (and even earlier with tabled layouts). As such, I have examples of each in this post (no tabled layouts).

Worth a read and reread by anyone doing anything with CSS. For some reason, Adrian’s feed was not in my RSS reader. This is now fixed.
Dear fellow developers: If you’re one of those developers who makes it impossible to press the tab key to move through a screen, hand in your dev creds now and put down your IDE until you learn to do better. I should not have to get help from a sighted person to add FTP users to a server. This is becoming a serious problem. Learn HTML damn it! Learn HTML as if I am going to find out where you live.
Read The Mac Open Web

These days, as the giant social networks behave more and more reprehensibly, many people are looking back to the “good old days” of the web, when self-published blogs were the primary means of sharing one’s thoughts.
Brian Warren has taken this enthusiasm, and combined it with his nostalgia for another classic resource: the links page.

This one is devoted to all things Mack and iOS that allow you to consume and create content for the open web. I don’t have a Mack, and have not gone through all the iOS apps yet, so you’ll have to test the accessibility of some or all of these apps for yourself. Indieweb developers are very open to accessibility feedback though, and this includes implementing things for the sake of accessibility, so this is sort of the one place where productive conversations about accessibility which don’t involve accessibility folks talking to each other are still possible.
Read Defining PDF Accessibility by WebAIM: Web Accessibility In Mind

When people talk about “accessible” PDF files, they are usually referring to “tagged” PDF files. PDF tags provide a hidden, structured representation of the PDF content that is presented to screen readers. They exist for accessibility purposes only and have no visible effect on the PDF file. There is more to an accessible PDF file than tags, but an untagged PDF would not be considered “accessible”.