Not to beat a dead horse, but this is important. (Screen Readers)
-
In my experience we web devs don't actually use or at least watch a video of a screen reader. This is bad. Very bad. Because we talk about accessibility, but it's amazing how many people still don't use aria tags, leverage semantic elements, etc. Every web dev should watch this video. It's only 4 mins long. [Screen Reader Demo for Digital Accessibility](https://www.youtube.com/watch?v=dEbl5jvLKGQ) Not trying to sound preachy (but I am :laugh:). The man is spot on. The world revolves around the Internet now. We can't forget about our blind brothers and sisters. Side note, one of the cool features (as it pertains to the skip to content thread below) is the screen reader shown already has the ability to jump to a header. Also notice he skipped over the skip to main content link. :laugh: :laugh: But even outside of that, peeps need to see a screen reader in action at least once. In particular how it allows him to scroll with a focus box over content.
Jeremy Falcon
-
In my experience we web devs don't actually use or at least watch a video of a screen reader. This is bad. Very bad. Because we talk about accessibility, but it's amazing how many people still don't use aria tags, leverage semantic elements, etc. Every web dev should watch this video. It's only 4 mins long. [Screen Reader Demo for Digital Accessibility](https://www.youtube.com/watch?v=dEbl5jvLKGQ) Not trying to sound preachy (but I am :laugh:). The man is spot on. The world revolves around the Internet now. We can't forget about our blind brothers and sisters. Side note, one of the cool features (as it pertains to the skip to content thread below) is the screen reader shown already has the ability to jump to a header. Also notice he skipped over the skip to main content link. :laugh: :laugh: But even outside of that, peeps need to see a screen reader in action at least once. In particular how it allows him to scroll with a focus box over content.
Jeremy Falcon
That's a really interesting video and provides great perspective on the issue. I know that Bootstrap is really good about providing the aria tags as part of their controls, etc. and using Bootstrap helped me to gain some understanding of the importance. This video was really informative and helpful and made me re-think about how important it is. Thanks for sharing. :thumbsup:
-
That's a really interesting video and provides great perspective on the issue. I know that Bootstrap is really good about providing the aria tags as part of their controls, etc. and using Bootstrap helped me to gain some understanding of the importance. This video was really informative and helpful and made me re-think about how important it is. Thanks for sharing. :thumbsup:
raddevus wrote:
This video was really informative and helpful and made me re-think about how important it is.
What I find funny is they can already skip to the main content by virtue of headers. :laugh: And home dude just strait up ignored that link. :laugh: One of the peeves I had watching that video is whoever wrote that web page used spacer divs, images, or something without using an [aria-hidden](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-hidden) tag. Granted, it's a university and not a professional site, but still. You'll see some of those tabs tabbed over blank space for that reason. Spacers are so 20 years ago, but if you're gonna use one because you refuse to learn Flexbox, at least use an aria tag to tell the screen reader what's up.
raddevus wrote:
Thanks for sharing.
Any time buddy.
Jeremy Falcon
-
That's a really interesting video and provides great perspective on the issue. I know that Bootstrap is really good about providing the aria tags as part of their controls, etc. and using Bootstrap helped me to gain some understanding of the importance. This video was really informative and helpful and made me re-think about how important it is. Thanks for sharing. :thumbsup:
To be clear, I'm totally agreeing with you about the skip to main content link you talked about being implemented like garbage. It seems like something that would otherwise be a good idea was borked... and to top if off not even needed.
Jeremy Falcon
-
In my experience we web devs don't actually use or at least watch a video of a screen reader. This is bad. Very bad. Because we talk about accessibility, but it's amazing how many people still don't use aria tags, leverage semantic elements, etc. Every web dev should watch this video. It's only 4 mins long. [Screen Reader Demo for Digital Accessibility](https://www.youtube.com/watch?v=dEbl5jvLKGQ) Not trying to sound preachy (but I am :laugh:). The man is spot on. The world revolves around the Internet now. We can't forget about our blind brothers and sisters. Side note, one of the cool features (as it pertains to the skip to content thread below) is the screen reader shown already has the ability to jump to a header. Also notice he skipped over the skip to main content link. :laugh: :laugh: But even outside of that, peeps need to see a screen reader in action at least once. In particular how it allows him to scroll with a focus box over content.
Jeremy Falcon
As a related topic, had come across this a few years ago https://www.technologyreview.com/2017/04/25/152177/mit-students-invent-simple-device-that-makes-printed-text-accessible-to-the-blind/ Not sure whether this was commercialized.
-
As a related topic, had come across this a few years ago https://www.technologyreview.com/2017/04/25/152177/mit-students-invent-simple-device-that-makes-printed-text-accessible-to-the-blind/ Not sure whether this was commercialized.
Amarnath S wrote:
Not sure whether this was commercialized.
That's cool. Hopefully, someone will.
Jeremy Falcon
-
In my experience we web devs don't actually use or at least watch a video of a screen reader. This is bad. Very bad. Because we talk about accessibility, but it's amazing how many people still don't use aria tags, leverage semantic elements, etc. Every web dev should watch this video. It's only 4 mins long. [Screen Reader Demo for Digital Accessibility](https://www.youtube.com/watch?v=dEbl5jvLKGQ) Not trying to sound preachy (but I am :laugh:). The man is spot on. The world revolves around the Internet now. We can't forget about our blind brothers and sisters. Side note, one of the cool features (as it pertains to the skip to content thread below) is the screen reader shown already has the ability to jump to a header. Also notice he skipped over the skip to main content link. :laugh: :laugh: But even outside of that, peeps need to see a screen reader in action at least once. In particular how it allows him to scroll with a focus box over content.
Jeremy Falcon
Very important. I'll be showing this to my daughter (who does some web development). My work is strictly at the back end, so it's less relevant to me.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
-
In my experience we web devs don't actually use or at least watch a video of a screen reader. This is bad. Very bad. Because we talk about accessibility, but it's amazing how many people still don't use aria tags, leverage semantic elements, etc. Every web dev should watch this video. It's only 4 mins long. [Screen Reader Demo for Digital Accessibility](https://www.youtube.com/watch?v=dEbl5jvLKGQ) Not trying to sound preachy (but I am :laugh:). The man is spot on. The world revolves around the Internet now. We can't forget about our blind brothers and sisters. Side note, one of the cool features (as it pertains to the skip to content thread below) is the screen reader shown already has the ability to jump to a header. Also notice he skipped over the skip to main content link. :laugh: :laugh: But even outside of that, peeps need to see a screen reader in action at least once. In particular how it allows him to scroll with a focus box over content.
Jeremy Falcon
I hate everything about web ui, pretty much. That said, working on accessibility facelift WCAG stuff was one of the more interesting things I've ever had to do with it. It also makes me just ever so slightly less enraged about the whole "let's cram everything into a browser because why not, it'll be awesome, guys, come on!?" Because it does bring a sort of standard even with the DOM itself that lends itself to accessibility stuff like screen readers and input devices. That's pretty important, not just with the internet, but with computing/technology.
-
That's a really interesting video and provides great perspective on the issue. I know that Bootstrap is really good about providing the aria tags as part of their controls, etc. and using Bootstrap helped me to gain some understanding of the importance. This video was really informative and helpful and made me re-think about how important it is. Thanks for sharing. :thumbsup:
A couple of hints to developers: * Get hold of a pair of sunglasses (unless you want to do a cleaning job on your own glasses afterwards :-)), and smear them with vaseline or something similar. Carrying those, go through an entire procedure of booting up your PC, reading and responding to emails, running your application with all its features, and shutting the PC down. * For handling tunnel vision: Make a large cardboard with a small hole, at most 1/8 of the screen width. Hide the screen behind the cardboard, but allow the user to move the boar up and down and to both sides to cover the entire screen, and let users run a boot up, running your application and shutting down. * For color blindness: Reduce the color saturation to zero, creating a greyscale image (most display card drives allow this), and try to use applications - maybe your own! - using colors to convey essential information. (You may of course use web sites converting the colors according to a specific defect, but those are usually rather slow. Converting to gray scale is certainly not as exact, but it will give a rough indication.) * Disconnect the mouse (and other navigation tools such as touchpads or joysticks), and go through the process from boot up, starting your application and using all of its features, and closing down, using the keyboard only. * One nice way of demonstrating how suitable your application is to a blind (or near-blind): Turn the screen to the audience so that you cannot see it, but the audience can. Then demonstrate how you handle boot up, activation of different applications including you own, and shutdown. * Find yourself a pair of mittens, as thick as possible, and try to handle your keyboard with those. * Assuming that it is winter, at least 15C below freezing: Go out for at least half an hour without gloves or mittens, and when you come back, go directly to your keyboard and start operating your application. There is one test that beats them all: Make your test team include people with different kinds of disabilities: Various sigh impairment (tunnel vision, color blindness, retina defects), various motoric defects, and so on. A lot of developers who claim that they have adapted their software to various disabilites would (or at least should) feel ashamed when observing how people with those disabilites cope with their software!
Religious freedom is the freedom to say that two plus two make five.
-
In my experience we web devs don't actually use or at least watch a video of a screen reader. This is bad. Very bad. Because we talk about accessibility, but it's amazing how many people still don't use aria tags, leverage semantic elements, etc. Every web dev should watch this video. It's only 4 mins long. [Screen Reader Demo for Digital Accessibility](https://www.youtube.com/watch?v=dEbl5jvLKGQ) Not trying to sound preachy (but I am :laugh:). The man is spot on. The world revolves around the Internet now. We can't forget about our blind brothers and sisters. Side note, one of the cool features (as it pertains to the skip to content thread below) is the screen reader shown already has the ability to jump to a header. Also notice he skipped over the skip to main content link. :laugh: :laugh: But even outside of that, peeps need to see a screen reader in action at least once. In particular how it allows him to scroll with a focus box over content.
Jeremy Falcon
Hi Jeremy, I am not at all fluent with using my screen reader... I did not read the instructions and just dove in and sort of hacked around to learn... LOL so... It is not easy for me, a blind person to find this text box on this page in order to contribute. I hit the E key to find edit boxes and combo boxes and this is neither... but if I took the time to learn how to use my screen reader I probably would not have any problems... I bet a lot of blind people are like me and do not learn the "right" way to be blind? ... I endorse this post. LOL I have ignored the skip to the main content button here for years. I came here to interact with the screen reader post and the skip takes me to a welcome that I have memorized years ago? A functional skip linky would take me to what I came here for? Or a second link saying: "skip to the meat, please." would be nice? I have been blind for some eleven years now and NVDA screen reader is a vital tool for me. Thank you dear Jeremy for this post and blessings chuck 🔥 💖 🔥
