Let your customers search your products using the brands that you resell on your WooCommerce online store with lists an widgets.
In June 2019, I conducted 5 user testing sessions for accessibility research with Fable Tech Labs, a Toronto-based start-up that’s “making it easier for digital teams to engage people with disabilities in product development.”
Facebook’s brief image outage earlier this week exposed the general public to just how bad accessibility really is in our modern visual-first social Web. While governments and the technology community are investing heavily in AI bias, they care little about accessibility bias.
In which I lament the fact that many frontend Web engineers don’t understand the end product of their work, HTML.
I was always told I had to go to college. I was “gifted” so learning came easy and I enjoyed it. From ages 6 to 18, I went to competitive accelerated schools designed to churn out college students. It was a narrow path I’d been set on, without encouragement to explore beyond.
Icons are an essential part of many user interfaces. The thing is: more often than not, they break clarity. Just replace them by a text label. Or an icon plus label.
Various approaches have been employed over many years to distinguish human users of web sites from robots. The traditional CAPTCHA approach asking users to identify obscured text in an image remains common, but other approaches have emerged. All interactive approaches require users to perform a task believed to be relatively easy for humans but difficult for robots. Unfortunately the very nature of the interactive task inherently excludes many people with disabilities, resulting in a denial of service to these users. Research findings also indicate that many popular CAPTCHA techniques are no longer particularly effective or secure, further complicating the challenge of providing services secured from robotic intrusion yet accessible to people with disabilities. This document examines a number of approaches that allow systems to test for human users and the extent to which these approaches adequately accommodate people with disabilities, including recent noninteractive and tokenized approaches.
3.2.1 On Focus: When any component receives focus, it does not initiate a change of context. (Level A) The intent of this success criterion is to make sure that any unwanted actions are not initiated when focus moves on to an element. For example during tab navigation or shift tab navigation if user focus moves on to a link & a modal is triggered this fails this check point. Here user did not initiate this action; it was initiated when user focus moved on to a particular element.
There’s a new international accessibility standard out – ISO 30071-1 – about embedding accessibility in your organisation and processes.
So why should we, as developers, care…?
Aren’t the WCAG checkpoints for developers, and the new ISO for the product/project managers?
Developers don’t have time to be reading every new bit of writing around accessibility. There’s loads of articles out there – some new, some old, some reliable, some misguided. An international standard should be able to be trusted, but does it give developers any solutions for tricky accessibility challenges that they may face?
At the February 2019 Accessibility Talks online meetup, AmyJune Hineline, Drupal and WordPress Community Ambassador at Kanopi Studios, spoke about inclusive content strategy, what it means, and how to craft content that is accessible to everyone.
Instructions help users to submit forms successfully. However, if the instructions are provided with a placeholder attribute, then the user might not be able to use that instruction effectively.
A call for urgency in finding a solution to the content reordering problem which our new layout methods make far more likely.
People often include screen reader users in the much larger group of keyboard-only users. Whilst this is correct (most screen reader users don’t use a mouse), it also creates a false impression of the way screen reader users navigate content.
Also, I really like the footer text on léonie’s site.
CSS is providing newer and more complex methods of laying out your pages. Given the multiple form factors a responsive site has to support, it makes sense that developers want easy ways to structure the layouts that aren’t all floats, clears and position: absolutes.
Regardless of how you want your layout to appear in a browser, you must keep in mind that a clear HTML structure is [start of stricken text] important to search engines[end stricken text] . Sorry, while the bit about search engines is true, it’s not really what I consider important, but it is more likely to get some people to pay attention.
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).
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.
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”.
Cool front-end developers are always pushing the envelope, jumping out of their seat to use the latest and greatest and shiniest of UI frameworks and libraries. However, there is another kind of front-end developer, the boring front-end developer. Here is an ode to the boring front-end developer, BFED if you will.
WordPress 3.7 was released on October 24, 2013 and introduced an automatic update mechanism to ensure security fixes would be automatically deployed on all WordPress sites, in an effort to prevent recently-patched vulnerabilities from being massively exploited in the wild. This is widely regarded by security experts as a good idea.
However, the WordPress automatic update feature had one glaring Achilles’ heel: If a criminal or nation state were to hack into the WordPress update server, they could trigger a fake automatic update to infect WordPress sites with malware.
This isn’t just a theoretical concern, it could have happened if not for WordFence’s security researchers finding and disclosing an easy attack vector into their infrastructure.
WordPress 5.2 was released on May 7, 2019 and provides the first real layer of defense against a compromised update infrastructures: offline digital signatures.