Within a web development organization, it’s ideal to maintain (and enforce usage of) design patterns and a components library. And they should work together; design patterns create consistency among visual elements across projects and the components library creates consistent implementation of those patterns during development. This is especially important on several levels including accessibility.
Here is an extensive list of recommended code libraries, patterns, and design systems. It’s one list instead of separating by category as many have elements of each. There are also some related articles below. Please leave a comment for any updates, corrections, additions, etc.
So many great articles around digital accessibility lately! Here are some (with author and quote/summary) which I thought were very useful.
Link Targets and 3.2.5 by Adrian Roselli @aadrian.
“Regardless of what accessibility conformance level you target, do not arbitrarily open links in a new window or tab. If you are required to do so anyway, inform users in text.”
Squarespace, Wix, & Weebly: Accessibility Review by @TerrillThompson.
“For accessibility, avoid Weebly. Both Squarespace and Wix are capable of creating accessible sites, but the user has to be looking to do so—it isn’t gonna happen by default.”
<select> your poison by Sarah Higley @codingChaos.
“recreating the native behavior of a <select> element is impossible: its underlying semantics differ across platforms; its keyboard behavior is inconsistent; its mobile presentation and behavior is entirely different from desktop.”
Studies/statistics on current state of web accessibility:
Higher Ed in 4k Project by PopeTech.
“…93.331% of pages had detectable WCAG violations. There were a total of 7,464,465 detectable errors found or 23.8 errors per page.”
Click-Away Pound Survey (2019) by @CAPsurvey.
“In 2016, the survey found that more than 4 million people abandoned a retail website because of the barriers they found, taking with them an estimated spend of £11.75 billion. In 2019, that lost business, the ‘Click-Away Pound’, has grown to £17.1 billion.”
Operating System and Browser Accessibility Display Modes by Eric Bailey @ericwbailey.
“Five such modes are Dark Mode, Increased Contrast Mode, Inverted Colors Mode, Reduced Motion Mode, and High Contrast Mode. Following is an explanation of each of these mode, who can benefit from it, how to enable it on your device or browser (if supported), and how to work with it in code.”
“You may have difficulty finding a fully accessible solution. Do take the time to run some simple tests to get a better feel for the product. The more precise your questions and requirements about accessibility, the more likely you are to be able to determine if a product meets your needs. And the more protected you’ll be should the product fail to meet expectations.”
Pixels vs. Relative Units in CSS: why it’s still a big deal by Kathleen McMahon @resource11.
“Remember, users really do change their settings under the hood, and we should be maintaining users’ control over their own browsing experience. If you use relative CSS units for your typography styles, you can maintain the fidelity of your layouts without negatively impacting the needs of your users.”
How accessible is the HTML video player? by Scott Vinkle @svinkle.
“relying on native video players should be used with caution…I found most to have poor keyboard and screen reader support, which may lead to frustrated users”
The third annual Accessibility Toronto Conference was held recently at TELUS in downtown Toronto, Ontario, Canada. On Twitter, the hash tag is #a11yTO and the account is @a11yTO.
And for the first time, both an Accessibility In Real Life conference (#a11yIRL) and a conference dedicated to accessible gaming (#a11yTOGaming). They were run the day before and after the main conference. All events were a big success!
The week even included a few social events in the evening including an entertaining karaoke party hosted by Shopify and a Tweetup hosted by Slack.
A theme which seemed to emerge from the conferences collectively was: Design *with* people with disabilities, not *for* people with disabilities.
Other notables from the conference were the adjustable desk on stage and a video puppet which reminded attendees when the sessions are about to start!
See below for a list of available presentation resources (from the a11yTO conference), selected tweets, and a few excellent conference reviews. See you there next year?
My “Can’t let it go” for this week, an example in @ShellELittle’s #a11yTOConf talk on dark patterns: some companies literally photoshop a hair onto images to get users to swipe thru carousels (by trying to swipe the hair off the screen). That level of manipulation is astounding.
@NeilMilliken presents an effective connection between sustainability and accessibility: Poor accessibility is a kind of pollution. And, sadly, society is paying the price, not the companies who are creating the "pollution". #a11yTOConf
The U.S. Supreme Court denied to hear Domino’s Pizza appeal of the Ninth Circuit federal appeals court decision which allowed the case to be heard. So the Ninth Circuit decision for Domino’s v. Robles stands, hooray! Digital products which are a public accommodation must be accessible or will be subject to a lawsuit (and probably lose).
The accessibility community is dumbfounded and outraged as to why Domino’s, a national pizza chain in the U.S., would spend so much money and effort into fighting digital equality rather than making their digital services accessible to all, which would greatly increase their potential customer base (and avoid bad publicity!)
Here’s Domino’s statement about the Supreme Court’s decision. Domino’s doesn’t admit that besides convenience, inclusiveness, and equality, ordering online provides other perks that cannot be received in another way, such as discounts, coupons, and rewards points. Although their call for DOJ regulation has some merit, it’s more of an unwarranted excuse. Regulations aren’t completely necessary; if passed, they would likely still be WCAG 2.0 AA, and digital products would still be subject to lawsuits.
Hooray! US Supreme Court will NOT hear the Domino’s Pizza case. This means that the Ninth Circuit court ruling is still good — disabled people have rights under the #ADA to challenge websites and mobile apps that are not accessible. #a11y#Disabilityhttps://t.co/Zwsh4fTjta
Supreme Court won’t hear case for Domino’s Pizza's desire to build web services that aren't accessible. ADA suit against them may continue. Good. What a shameful stance to take, @dominoshttps://t.co/BYN2y25JX4
"This is not about whether a guy can order pizza from a particular pizza restaurant … [i]t's about whether people [who are blind] are going to be able to participate in society in the 21st century." #a11y (via @A11yNews)https://t.co/qbBGLqO8Pv
While I have celebrated with my community regarding the SCOTUS decision of yesterday, I’m also reading some pretty incredible posts by people who disagree on the “Blind people can’t use the Internet so what difference does it make“ premise. Sadly, I’m not at all surprised.