spaceninja + screenreaders   42

WebAIM: Screen Reader User Survey #8 Results
The results of WebAIM's 8th screen reader user survey are now available. There are several interesting and surprising findings: NVDA takes a bite out of JAWS and is now the most common screen reader; Chrome usage increased 3X making it the most used browser; IE usage still at 14.5%; PDF = problems;
fridayfrontend  accessibility  screenreaders  surveys 
2 days ago by spaceninja
You should use a screen reader
If you’ve never used one before, opening up a site you’ve built, turning on a screen reader, and using the tab key on your keyboard to move through the links or interacting with content on the site can be very enlightening.
fridayfrontend  accessibility  cssbasics  screenreaders  voiceover 
15 days ago by spaceninja
An HTML Element Potentially Worth $18M to Indiegogo Campaigns
To recap, if Indiegogo had correctly implemented <label>s on its payment form then last year its campaigns would have had access to more than $18 million dollars. Indiegogo then could have put nearly a million dollars in its pocket. There may be a reason accessibility-related campaigns on Indiegogo consistently fail to make their goals.
fridayfrontend  accessibility  labels  forms  screenreaders 
15 days ago by spaceninja
Update on accessibility improvements we’re making to Chorus
Over the last few months, we’ve been changing that. The product team’s been hard at work improving the accessibility of Chorus and every website powered by it. We’ve been working to ensure our websites are more usable for everyone, regardless of which browsers, devices, and assistive technologies they rely on. To reach our goal, we’ve been making improvements to our design system, and we’ve been creating new resources and training to inform our practices. In this post, we’ll share what we’ve done so far, how your experience of browsing our websites might be improved, and—most importantly—we’ll talk about the work that’s still ahead of us.
fridayfrontend  accessibility  contrast  alt  forms  screenreaders  vox 
9 weeks ago by spaceninja
Truths about digital accessibility
Creating, maintaining, or evaluating accessible technology? Here are some things to keep in mind (note that identity-first language is intentional):
fridayfrontend  cssbasics  accessibility  screenreaders 
10 weeks ago by spaceninja
Understanding Assistive Technology: How Does a Blind Person use the Internet?
Understanding digital accessibility challenges is easy if you know people with disabilities. But what if you’ve never seen a person who is blind use their computer or smartphone? We’re here to help you understand a little bit about what it’s like to use the internet if you have a disability.
fridayfrontend  cssbasics  accessibility  screenreaders  blind 
july 2019 by spaceninja
An Intro To Screen Reader Testing for Sighted Developers
Besides the design, loading time and performance, accessibility determines the user experience of the web apps that you're building profoundly. This quick guide will give you an introduction to the why and how of testing your website's user experience using screen readers.
fridayfrontend  accessibility  screenreaders  testing 
july 2019 by spaceninja
Using VoiceOver to Evaluate Web Accessibility
VoiceOver is a screen reader program that comes on new Mac computers, iPhones, iPads, and iPod touches. This article is designed to help users who are new to VoiceOver learn the basic controls for testing web content, and to serve as a reference for the occasional VoiceOver user.
fridayfrontend  accessibility  voiceover  screenreaders 
june 2019 by spaceninja
Drop caps & design systems: A story about making things 1% better
This experience was a reminder for me that most design systems work is rarely flashy or sudden. Rather, it involves communication, iteration, and slow, careful research. If you can do that mapmaking, and if you’ve got a good team to help you find your way, your design system will be in excellent shape. And so will your drop caps.
fridayfrontend  css  accessibility  voiceover  screenreaders  dropcaps  first-letter 
june 2019 by spaceninja
My Web Accessibility Testing Process
It sounded like people were curious about my web accessibility testing approach! So I’m going to walk you through my thought process, what I test for, how early I check, and how I test. It’s like having my web accessibility testing checklist in your back pocket.
fridayfrontend  accessibility  testing  webaim  wave  contrast  tabindex  screenreaders  voiceover 
june 2019 by spaceninja
The difference between keyboard and screen reader navigation
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.
fridayfrontend  cssbasics  accessibility  keyboard  screenreaders 
june 2019 by spaceninja
Thoughts on screen reader detection
The subject of screen reader detection has been under discussion lately. It isn’t something I’m comfortable with, so I’d like to share the reasons why: I don't want to share personal info with the sites I visit. I don't want to be relegated to a ghetto. I don't want design decisions to be based on the wrong thing. I don't want old mistakes to be repeated. I don't want things to be hard work. I _do_ want much more conversation about screen reader detection.
fridayfrontend  accessibility  screenreaders  detection  privacy 
march 2019 by spaceninja
How A Screen Reader User Accesses The Web
In this Smashing TV webinar recording, join Léonie Watson (a blind screen reader user) as she explores the web, and find out about some unexpected properties of HTML elements that not only have a huge impact on accessibility, but also turn out to be pretty good for performance, too.
fridayfrontend  video  accessibility  screenreaders  aria 
march 2019 by spaceninja
See No Evil: Hidden Content and Accessibility
It’s important to ensure our websites are accessible to everyone, regardless of whether or not they use a screen reader, but with this myriad of options, how do we know when to use what?

There are four main scenarios where you may wish to hide content:
1. Hiding content for everyone, regardless of whether they use a screen reader
2. Hiding content for screen readers while showing it to other users
3. Showing additional content for screen readers while hiding it from other users
4. Hiding content at specific screen sizes

Let’s dive deeper into each of those scenarios to learn how to handle them.
fridayfrontend  cssbasics  css  aria  accessibility  hidden  screenreaders 
february 2019 by spaceninja
Designing Layouts for Screen Readers
It’s easy to think about a layout as being a primarily visual concern. The header goes up top, the sidebar is over here, the call to action is in an overlay on top of the content (just kidding). Grids, borders, spacing and color all portray valuable visual data, but if these hints to the structure of a page are only visible, some users may find your content unintelligible.
fridayfrontend  accessibility  screenreaders  layout  design 
december 2018 by spaceninja
Finding the Way: screen reader strategies
Sometimes the thing that makes a website difficult to understand for a screen reader user is the absence of information, and that is a problem that is not identified in automated scans.
fridayfrontend  accessibility  screenreaders 
november 2018 by spaceninja
Conversational Semantics
As Alexa, Cortana, Siri, and even customer support chat bots become the norm, we have to start carefully considering not only how our content looks but how it could sound. We can—and should—use HTML and ARIA to make our content structured, sensible, and most importantly, meaningful.
fridayfrontend  semantics  css  html  accessibility  screenreaders  virtualassistants  siri  alexa  cortana  readermode 
september 2018 by spaceninja
Element Hiding Techniques in CSS
Hiding HTML elements from CSS is not a big deal; we do it instinctively until we learn accessibility and find a fundamental difference.
fridayfrontend  accessibility  cssbasics  hidden  display  visibility  opacity  screenreaders  position  clip-path 
august 2018 by spaceninja
Assistive Technologies I Test With
After a recent talk on Accessibility, I was asked during the Q&A about what Assistive Technologies (AT) I test with while I’m developing. Such a good question! I hadn’t ever thought about what I actually test with and as I rambled on I thought it might help to write it down.
fridayfrontend  accessibility  testing  voiceover  screenreaders  narrator  nvda  vox  zoom  contrast 
july 2018 by spaceninja
A11y isn't Just…
For a great many people when you talk about accessibility, they instantly think about Screen Readers. While Screen Readers are an important tool for those that have an impairment there are many other ways a user can be affected.
cssbasics  accessibility  screenreaders  wcag  section508  fridayfrontend 
march 2018 by spaceninja
Text Splitting Causes Screen Reader Problems
I am a screen reader user, and I am annoyed! I repeatedly encounter the same problem on websites. It’s about text splitting up. Let me share my agony with you!
fridayfrontend  accessibility  aria  voiceover  screenreaders 
march 2018 by spaceninja
Software development 450 words per minute
I use a robotic-sounding voice which speaks at around 450 words per minute. For comparison, English is commonly spoken at around 120-150 words per minute.
accessibility  blind  screenreaders  programming 
february 2018 by spaceninja
Screen Readers and ALL CAPS
When you type something in ALL CAPS, screen readers spell it out like: A-L-L C-A-P-S, it's super annoying if it's not an abbr, so use CSS
screenreaders  accessibility  aria  abbr  abbreviations  capitalization 
february 2018 by spaceninja
A Tale of Two Rooms: Understanding screen reader navigation
"As you move the light around the darkened room you will need to build a mental map or image of what is in the room and how it is laid out. Building this mental map will take significantly longer than visually scanning the room when all the lights were on. As you move the flashlight around, you will need to remember each thing you have seen and how they all relate together. If you forget where something is located, it will take more time to locate it."
fridayfrontend  accessibility  screenreaders  aria 
february 2018 by spaceninja
Why you can't test a screen reader (yet)!
This idea, testing a screen reader, proved much harder than I thought. It's actually a bit of a holy grail in the accessibility space. Something that many have dreamed of, but few—if any—have achieved.
fridayfrontend  accessibility  screenreaders  testing  automation 
january 2018 by spaceninja
RAT: Results from Assistive Technology
RAT (Results from Assistive Technology) is a collection of markup patterns and how they are handled by different assistive technology.
aria  reference  accessibility  html  screenreaders 
january 2018 by spaceninja
Basic screen reader commands for accessibility testing
When you test your website with a screen reader there are a few basic commands you should know. Just remember not to make design decisions based only on your tests. Even with these useful screen reader commands, you won’t experience things in the same way as a person who uses a screen reader all the time.
accessibility  voiceover  screenreaders  keyboard 
june 2017 by spaceninja
Accessibility Is More Than Just Supporting Screenreaders – Seren Davies
All too often we think about accessibility as just meeting the needs of those who rely on screenreaders, but it's far wider than that! Seren will explore how people with cognitive, physical, hearing and sight difficulties experience the web, and how the decisions we make as developers affect their experience.
fridayfrontend  video  accessibility  screenreaders  contrast 
april 2017 by spaceninja
Getting Started with VoiceOver & Accessibility
it might not be worth your time trying to get your computer to sound like Chris Hemsworth, but I’m going to let you make that decision for yourself.
fridayfrontend  accessibility  voiceover  screenreaders 
april 2017 by spaceninja
Accessible UI Components For The Web
"When auditing your application for accessibility, ask yourself: Can you use your UI component with the keyboard only? Can you use your UI component with a screen reader? Can your UI component work without sound? Can it work without color? Can your UI component work with high-contrast mode enabled?"
fridayfrontend  accessibility  screenreaders  keyboard 
november 2016 by spaceninja
Hiding inline SVG icons from screen readers
The problem is related to using inline SVG, i.e. the svg element. SVG files may contain a title element which may or may not get announced by screen readers (depending on SVG embedding technique, browser name and version, and screen reader name and version).
fridayfrontend  svg  aria  accessibility  screenreaders 
september 2016 by spaceninja
HTML For Screen Readers - Labelling Elements
To screen readers, a lot of the visual information that is presented on a webpage is lost. Because of this, we need to specifically provide information to them that may be obvious to a person looking at the page.
fridayfrontend  html  accessibility  labels  screenreaders  aria 
august 2016 by spaceninja
Screenreaders and Labels
"Screenreaders read aria-labelledby, aria-label, <label>, placeholder or title, in that order. Omit them all and your input isn't accessible."
screenreaders  accessibility  labels  aria  fridayfrontend 
june 2016 by spaceninja
Links and accessibility
Good solution to a common accessibility problem
links  accessibility  aria  screenreaders  fridayfrontend 
april 2016 by spaceninja
CSS generated content and screen readers
"So just a brief heads-up that CSS generated content is not invisible to all screen readers. Neither is it announced by all screen readers. In other words, use with care and consider what happens both when it is supported and when it isn’t."
accessibility  css  generated  screenreaders 
march 2013 by spaceninja
Page Source Order & Accessibility
"Recommendations: Place navigation before content to benefit some screen reader users. Include skip links. Use meaningful headings."
screenreaders  standards  sourceorder  skiplinks  navigation  seo  accessibility  html 
october 2011 by spaceninja
Does Expectation Equal Preference?
"I expect websites to be badly coded, badly designed and inaccessible, yet I prefer them not to be."
screenreaders  standards  sourceorder  skiplinks  navigation  seo  accessibility  html 
october 2011 by spaceninja
In Defense of Content-First Source Ordering | JohnAlbin
"So why do users expect navigation links first? Because it’s really, really hard to get content-first HTML source ordering. And the vast majority of sites don’t do it... So since users have gotten used to site navigation first… does that mean we shouldn’t attempt content-first HTML source ordering? Of course not!"
screenreaders  standards  sourceorder  skiplinks  navigation  seo  accessibility  html 
october 2011 by spaceninja
Video of a Blind Web Browser
Aaron Cannon, blind since birth, shows how he (and other blind users) browses the web using screen reader technology.
accessibility  blind  screenreaders  video 
october 2011 by spaceninja
Navigation Markup After Content
Healthy debate in the comments section of this post recommending placing your navigation after your content. General vibe seems to be that the SEO benefits are negligible, leaving accessibility as the primary advantage - but that other study implied that the accessibility benefits are also negligible.
screenreaders  jaws  standards  sourceorder  skiplinks  navigation  seo  accessibility  html 
november 2009 by spaceninja
Presenting your main content first
Old (2002) page recommending moving navigation below content for accessibility and SEO benefits. Perhaps this information is no longer accurate?
screenreaders  jaws  standards  sourceorder  skiplinks  navigation  seo  accessibility  html 
november 2009 by spaceninja
Source Order, Skip links and Structural labels
Research from 2006 showing that screen reader users actually prefer site navigation to be presented before content, along with a skip link, contrary to popular wisdom that front-loading the content is an accessibility boost.
screenreaders  jaws  standards  skiplinks  navigation  accessibility  html 
november 2009 by spaceninja

Copy this bookmark: