# People with Disabilities Published articles for People with Disabilities. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Designing Claude for ears, not eyes: An accessibility skill for blind and low-vision users DevFeed: [Designing Claude for ears, not eyes: An accessibility skill for blind and low-vision users]() Original publisher: [Read original article]() Author: Nubank Editorial Published: 2026-09-16T14:09:16Z Content type: article Language: en Sources: [Nubank]() Topics: [Accessibility](), [Claude](), [User interface design](), [screen](), [Users](), [Development]() Tags: [accessibility](), [accessible](), [claude](), [culture-values](), [data-science-machine-learning](), [development-environment](), [engineering](), [inclusive](), [life-at-nu](), [people-with-disabilities](), [text](), [users](), [vision]() ### AI overview Nubank describes BLIND-CLAUDE.md, an instruction set that adapts Claude responses for people who primarily use screen readers or read-aloud functionality. The approach treats auditory comprehension as an engineering constraint and changes behavioral instructions without modifying Claude or adding a native accessibility feature. ### Source excerpt How a cognitively diverse IT team at Nubank, they coded screen reader-friendly rules into Claude's instructions, treating auditory comprehension as an engineering constraint The post Designing Claude for ears, not eyes: An accessibility skill for blind and low-vision users appeared first on Building Nubank. ## Designing Claude for ears, not eyes: An accessibility skill for blind and low-vision users DevFeed: [Designing Claude for ears, not eyes: An accessibility skill for blind and low-vision users]() Original publisher: [Read original article]() Author: Nubank Editorial Published: 2026-09-16T14:09:16Z Content type: opinion Language: en Sources: [Nubank]() Topics: [Accessibility](), [Claude](), [Users](), [screen]() Tags: [accessibility](), [claude](), [configuration](), [culture-values](), [data-science-machine-learning](), [development-environment](), [life-at-nu](), [people-with-disabilities](), [vision]() ### AI overview Nubank describes BLIND-CLAUDE.md, an instruction set that adapts Claude responses for developers who primarily use screen readers or read-aloud tools. The approach addresses conventions such as Markdown tables, diffs, diagrams, long logs, and spatial references by adding behavioral instructions without modifying Claude or introducing a native accessibility feature. ### Source excerpt How a cognitively diverse IT team at Nubank, they coded screen reader-friendly rules into Claude's instructions, treating auditory comprehension as an engineering constraint The post Designing Claude for ears, not eyes: An accessibility skill for blind and low-vision users appeared first on Building Nubank. ## How Interrupting Your Users Can Create Accessibility Concerns DevFeed: [How Interrupting Your Users Can Create Accessibility Concerns]() Original publisher: [Read original article]() Author: Chris Published: 2025-12-22T12:30:00Z Content type: article Language: en Sources: [Blog-Main]() Topics: [Web Accessibility (a11y)](), [Web Content Accessibility Guidelines](), [digital accessibility](), [Website](), [Users](), [notifications]() Tags: [accessibility](), [accessibility-guidelines](), [accessibility-ux](), [automatic](), [digital-accessibility](), [display](), [people-with-disabilities](), [send](), [stop](), [time](), [timeout](), [web-accessibility](), [web-content-accessibility-guidelines](), [web-developers](), [websites]() ### AI overview The article explains how dynamic website behavior, including unexpected notifications, automatic refreshes, and other interruptions, can create accessibility barriers for screen reader users and people with attention disorders. It discusses WCAG Success Criterion 2.2.4, which says interruptions can be postponed or suppressed except in emergencies, while noting that this Level AAA criterion is not generally required for conformance goals. ### Source excerpt If you're building a dynamic website, there are plenty of valid reasons to interrupt your users. You might need to tell someone if their session is about to timeout, for example, or you might want your content to refresh periodically in order to show more up-to-date information. ## Basic Web Accessibility Tests: Turn Your Monitor to Grayscale DevFeed: [Basic Web Accessibility Tests: Turn Your Monitor to Grayscale]() Original publisher: [Read original article]() Author: Vince Published: 2025-09-05T16:15:00Z Content type: tutorial Language: en Sources: [Blog-Main]() Topics: [Accessibility](), [Web Accessibility (a11y)](), [Web Content Accessibility Guidelines](), [color](), [digital accessibility](), [Testing]() Tags: [accessibility](), [accessibility-guidelines](), [accessibility-ux](), [color](), [digital-accessibility](), [people-with-disabilities](), [testing](), [tests](), [wcag](), [web](), [web-accessibility](), [web-content-accessibility-guidelines]() ### AI overview This article explains how viewing a website in grayscale can help reveal accessibility problems caused by using color as the only way to convey information. It places the exercise within a broader strategy combining automated and manual testing for WCAG Level AA conformance and gives examples involving links, form fields, charts, and status indicators. ### Source excerpt To truly test content for accessibility, you need an extensive strategy that combines automated testing with manual tests. You should have a goal in mind -- for most websites, that's Level AA conformance with the Web Content Accessibility Guidelines (WCAG). ## Cognitive Load and Web Accessibility: Quick Tips for Clearer Content DevFeed: [Cognitive Load and Web Accessibility: Quick Tips for Clearer Content]() Original publisher: [Read original article]() Author: Marissa Published: 2025-07-24T19:45:00Z Content type: tutorial Language: en Sources: [Blog-Main]() Topics: [Accessibility](), [Web Accessibility (a11y)](), [Web Content Accessibility Guidelines](), [Website](), [Users](), [User interface design]() Tags: [accessibility](), [accessibility-guidelines](), [accessibility-ux](), [autism](), [charts](), [cognitive-load](), [form](), [layout](), [navigation](), [people-with-disabilities](), [quick-tips](), [tips](), [wcag](), [web-accessibility](), [web-content-accessibility-guidelines]() ### AI overview This article explains how cognitive load affects web accessibility, particularly for people with cognitive and learning disabilities. It recommends simplifying complex content, using consistent layouts and navigation, and following the Understandable principle of WCAG. ### Source excerpt The Web Content Accessibility Guidelines (WCAG) is designed to improve experiences for all users with disabilities. That includes people who have cognitive disabilities and learning disabilities -- but those users are often left out of the discussion. ## Thoughts From Reading Demystifying Disability by Emily Ladau DevFeed: [Thoughts From Reading Demystifying Disability by Emily Ladau]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2023-01-03T08:57:46.868000Z Content type: opinion Language: en Sources: [Eevis Blog]() Topics: [Accessibility]() Tags: [accessibility](), [book](), [identity](), [people-with-disabilities](), [thought]() ### AI overview A personal reflection on Demystifying Disability by Emily Ladau, focusing on disability, ableism, accessibility, disability etiquette, and the distinction between person-first and identity-first language. The author also connects the book's discussion to their experience of identity changes after a concussion. ### Source excerpt I finished reading Demystifying Disability by Emily Ladau last week. It's a fantastic book discussing disability, ableism, accessibility, disability etiquette, and many more things. I highly recommend buying and reading or listening to it! I have so many thoughts from reading the book, and I want to share some of them with you. And I know many more will come, as I often process new things over the course of a longer time. Person-First Language vs. Identity-First Language So, for those unfamiliar with the terms, person-first language (PFL) means using phrases where the person comes first. So, for example, people with disabilities. On the other hand, identity-first language (IFL) recognizes that disability is part of the person's identity, such as Autistic people. Emily Ladau writes about her experiences with these approaches: Truth to be told, I went kind of overboard with my IFL evangelism at first. I could not understand why anyone would prefer PFL and pushed against it whenever I had the chance. I could say I was the opposite. At some point, it was difficult for me to understand why someone would like to go with the identity-first approach. Okay, I knew the reasons, but I could say I did not truly understand it. But now I do, and even better because of reading Demystifying Disability. The book also got me thinking about why I've been feeling this way. For those of you who don't know, I had a concussion a few years back. I'm still recovering from it, and I know that things won't go back to what they were before that hit. I was 26 when that happened, so I had a pretty strong sense of who I was before that. One thing was that I had an extraordinary memory. I could recall details so well that people around me found it strange sometimes. And that was a big part of my identity. After the concussion, I realized I have problems with my memory, and I've had to come a long way to actually accept that this is my life now and I'm not the same person as I used to be back then.