Noah Yasskin

For your next accessibility audit, keep this list close: things will start making sense! 🙌 Let’s look into it 👇 1. Semantic HTML is your friend 2. Keyboard usage is more important than you may think 3. Contrast really shouldn't be a problem we still have in software in 2024 4. Sizing - you shouldn't need a magnifying glass on the web 5. Form-labelling done right is a life-saver 6. Alternative names & text - it's easy, just give more context #accessibility #checklist #audit

8

1 Comment

This is an interesting talk highlighting some of the issues that can occur on a website when an accessibility overlay is used. #accessibility https://lnkd.in/gSyJF5WF

13

This is a really good article about common techniques of browsing the web with only a keyboard. I consider this a prereq for anyone working in the accessibility field. Martin does a beautiful job keeping the concepts simple and straightforward. #Accessibility #Keyboard https://lnkd.in/eQGKbADX

11

I'll expect more from you if you tell me you want to make something accessible and §508 conformant. The 508 digital accessibility standards are mirroring WCAG 2.0 AA. That version of WCAG came out in December 2008. In other words, that standard is 16 years old... So I'm going to push for you to, at a minimum, adhere to the latest version of WCAG. That is, WCAG 2.2. By doing that, you'll still conform to §508, but you'll also make things more accessible for your end users. Also, remember, accessibility standards are the starting line, not the target.

23

4 Comments

A reader of my daily list asked: How do I know which accessibility issues matter most? "I'm stuck. We scanned our website and we have quite a few errors. It's just too much and we don't have that much time for accessibility. Can you explain how I can focus on the accessibility issues that matter most?" First off, we've all been there, and it's okay to feel a bit overwhelmed. Usually, when you're just starting with accessibility, you'll likely run an automated checker on your site as a first step. It will spit out a bunch of errors and warnings. It's likely that number is rather large and frightening. So now you have to sift through them all and figure out where to start. Here are two suggestions for you: 1. Critical issues or Level A come first These issues will prevent users with disabilities from even accessing your content. Some common critical issues I've seen: - Missing form labels - Missing alt text for images - Wonky ARIA roles or values 2. Look at your backlog Your backlog is pure gold. Just look at what you already know. The scan is great, but nothing beats user feedback. Listen to those using your site with assistive tech; they're giving you the playbook. ___ Did you know you can ask me your burning questions about accessibility? Head over to my profile and and visit the Ask me anything page on my website. #Accessibility #AccessibilityAMA #ShipAccessible ---- Thank you for taking time out of your day to read this! ❤️ Did you enjoy this? Join like-minded peeps learning and contributing to authentic conversations on accessibility. 📬 Click "Get the free daily newsletter" on my profile to subscribe. ♻️ Repost if you enjoyed this! It costs nothing and helps me spread the knowledge.

2

1 Comment

🚨 New Podcast Episode Alert! 🎙️ "VPATs & ARCs: What Developers and Designers Need to Know" This week on "Web Accessibility For All", we’re tackling two critical tools in web accessibility: VPATs (Voluntary Product Accessibility Templates) and ARCs (Accessibility Conformance Reports).  Whether you’re building for the public sector or looking to ensure your product’s accessibility, understanding these documents is essential. We dive deep into how they work, who should be involved in creating and maintaining them, and when to use each (or both!).  Don’t miss this insightful episode! 🔊 Listen now and boost your accessibility knowledge. Listen to this episode right now on your favorite platform: YouTube: https://lnkd.in/dTHXTu_y Spotify: https://lnkd.in/dzuQDg2v Don’t forget to subscribe, like, and share to spread the word about accessibility today! #a11y #Accessibility #WebAccessibility #VPAT #ARC #InclusiveDesign #UX #WebDevelopment #AccessibilityMatters #Podcast

1

#CoDesign according to the #NDIA #NDIS Doesn't look like #CoDesign. No mention of #UNCRPD in *OUR* (ie #NDIA's) #CoDesign principles. A little hint: the #UNCRPD is *THE* design determinant. #CoDesign *CAN'T* happen without explicit commitment to #UNCRPD. Explains why the #NDIS Bill breaches #HumanRights The #CoDesign Advisory Group - which "provides strategic advice to the NDIA on the implementation of co-design and engagement processes in the disability community" -  hasn't met in 9 months. As I explained in my recent article, #CoDesign has been weaponised. https://lnkd.in/d8VMKkvZ Take a look. #NothingAboutUsWithoutUs #RoboNDIS #ClassAction #RoyalCommission robondis.org Mark Toomey Tony Ridley, MSc CSyP FSyI SRMCP Karen Kline Samantha Connor Mark Sweeney Nick Avery Graham Taylor Tara Hannon Muriel Cummins Georgia van Toorn Dr George Taleporos (GAICD, PhD) Shirley Humphris Peter Gregory Jordon Steele-John #BillShorten David Pocock Vinod Ralh Paul Flintoft 👇 👇👇 https://lnkd.in/dKq7mdzZ

6

3 Comments

Don't stress about shifting left! It's just "a" way to being accessible. I see two approaches to accessibility. Either you wait until someone else discovers the issues on your production site. Or you integrate accessibility into your software development lifecycle (SDLC), from the early stages. We call the first being reactive and the second proactive (you might have heard the term "shifting left"). Most of the times, organisations start by being reactive. They usually respond to an outside trigger. Either a client demands an Accessibility Conformance Report (ACR), or, in the extreme case, they face a demand letter from a law firm. Or, as will be the case in Europe next year, new legislation goes into effect demanding digital accessibility. By definition, in all these cases, you are reactive. And you'll have been told that's a bad thing. But it's not the end of the world. Our default stance is being reactive. When you receive a customer complain, you are by definition reactive. We don't all have to be proactive all the time. In fact, being reactive is inevitable. You just have to think of the times when you: - didn't know about some ARIA pattern, a new browser feature or some assistive technology - discovered accessibility issues during user testing or feedback sessions - realised a third-party component wasn't accessible until after implementation - addressed accessibility because the standards and guidelines were updated All these things are beyond your control. And your job is to react to them. Unless you become passive, you're doing fine. #Accessibility #A11y #ShipAccessible ---- Thank you for taking time out of your day to read this! 📬 Did you enjoy this? Go to my profile and click "Get my free daily newsletter" to subscribe. ♻️ Repost if you enjoyed this! It costs nothing and helps me spread the knowledge.

7

4 Comments

What the heck is ARIA? A Beginner's Guide to ARIA for Accessibility https://buff.ly/3MfEoNz #ARIA #HTML #WebDev #WebDevelopment #DigitalAccessibility #Accessibility #A11y

15

2 Comments

I think this article does a good job of highlighting the limitations of automated testing. This is because WCAG is complex and requires human interpretation and testing to identify all the different errors. It also highlights how automated testing is good at preventing regression by tracking progress over time. This is why lots of companies and higher education institutions are using automated testing to track the number of errors on a webpage over time. #accessibility https://lnkd.in/g4Ba-S6P

11

🚨 New Podcast Episode Alert! 🎙️ "Accessibility Overlays: the Good, the Bad, and the Ugly" In this week's episode of "Web Accessibility For All", I take a deep dive into accessibility overlays—the promises they make, the challenges they create, and whether they’re the right solution for your site. If you’re a developer, designer, or manager who’s been told that overlays are the easy fix for web accessibility, this episode is for you.  Let's explore both the benefits and the pitfalls of these tools and how to approach accessibility the right way. 🔊 Listen now and get informed! Listen to this episode right now on your favorite platform: YouTube: https://lnkd.in/d2bBinQk Spotify: https://lnkd.in/dj8jCtRU Don’t forget to subscribe, like, and share to spread the word about accessibility today! #a11y #Accessibility #WebAccessibility #AccessibilityOverlays #InclusiveDesign #UX #WebDevelopment #AccessibilityMatters #Podcast

3

Resharing Episode 211 of The World of UX. Ever heard someone say "Stop drinking the Kool-aid?" This metaphoric statement refers to a tragic event in American history where people either blindly or through coercion ingested something self-detrimental. Check out this episode to learn how and why this metaphor applies to UX today. https://spoti.fi/3KkIbs3

3

Resharing this week's episode of The World of UX podcast, where I itemized and reviewed critical revealing traits from a job rejection notice. Check out Episode 215: The Dysfunction, Inequitability, and Incivility of Today's UX Hiring Landscape, Part 2. https://lnkd.in/eBxmfVaQ

5

What happened when I forced teams to track accessibility? Nothing. My plan wasn't very user-friendly. Bad joke, I know! The reality is, if you are to commit to tracking accessibility, everyone needs to be part of the decision about that change as early as possible. Commitment comes from having choice, not from decisions being passed from the top dogs. The key is to make the decision as a team. The team that discovers and selects metrics should be the same one implementing changes and tracking progress against those metrics. If your team doesn't understand and believe in those metrics, there's little chance of success. So how do I help teams select accessibility metrics? I usually start by gathering the team and encouraging open discussions. Structured discussions. Workshops. Not long tiresome meetings. And I have a few guidelines I follow: - I welcome disagreement because it often leads to better outcomes. - We treat each metric as a learning opportunity. - We never assign responsibility for any one metric to an individual. Half the battle is in knowing good metrics, bad metrics and recognising the difference between the two. Good metrics are: - Specific and measurable - Aligned with user needs - Actionable - Tied to business goals - Those that predict future performance Bad metrics are: - Vague or subjective - Difficult to measure consistently - Disconnected from user experience - Not actionable - Those that reflect past performance To tell them apart, you can begin by asking: - Can we consistently measure and track it? - Does it align with our overall accessibility goals? - Can we influence this metric directly through our actions? - Does this metric give us early warnings about potential issues? - Can we use this metric to make proactive decisions? - Does this metric show us where we're headed, or where we've been? - Is this a real-time or near real-time measurement? Having a set of good metrics builds understanding, alignment and commitment across your team. #Accessibility #A11y #ShipAccessible #KPI ---- 📬 Did you enjoy this? Go to my profile and click "Get my free daily newsletter" to subscribe. ♻️ Repost if you enjoyed this! It costs nothing and helps me spread the knowledge.

6

3 Comments

This article explores the structural elements of a paragraph and how it relates to screen reader accessibility. #accessibility https://lnkd.in/gTw4i4QH

10

Is web accessibility making your head spin? Heck! Mine too! And that's okay. It's normal. It's part of the process. And it's a good thing. If you're like me, you're probably feeling overwhelmed because: - Reading the WCAG puts you to sleep because it feels highly technical - You're confused by the list of cryptic accessibility issues coming your way - You don't know the accessibility jargon, like ARIA, ATAG, ICT - You're intimidated by all the laws and don't even know which ones apply to you - You've seen a VPAT and immediately wanted to run away - You think you're too incompetent to shift left Good! Admitting it is the first step towards learning. It's overwhelming and complex, especially when you're just starting out. But forget the jargon, the technical details, the laws and what experts tell you. Accessibility is about you and how you create experiences that work for everyone, regardless of their disabilities. Feeling incompetent is ok! It means you're on your way to getting better. #Accessibility #A11Y #WCAG #ShipAccessible

2

In her IA Conference presentation, Rachel Price argued convincingly that designing responsible AI solutions calls for skills information architects bring to the table. (For more on this topic, check out the latest episode of my podcast.)

21

1 Comment

This article provides guidance on the Web Content Accessibility Guideline (WCAG) standard 2.4.11, which requires items to not be obscured when they receive focus. #accessibility https://lnkd.in/gN8j9vEK

1