I'd also like to point out to fellow web developers: it is LAW to make technology accessible *if* you are working for the US Gov't. It's called Section 508. If you are applying for a web development job that serves the gov't, you better know what section 508 is. It's pretty easy to learn the basic idea, just grab a book about it.
Spot on. I totally agree with you that in some sites, text that should have been headings are simply bolded, and this gives screen reader users quite a challenging time. I'd also like to add that the right order of headings should be followed. Heading 1 should be followed by 2, 2 followed by 3 and so on.
Thanks a ton, this video helped a ton and helps me feel good that I used a lot of header tags on my site in what I think logic places. I realized how helpful they can be to you, and so I think I will keep even more priority to them since that's how you navigate.
Thank you for putting this video up. There's been a lot of debate on what headings should be used in a document and this video definitely helped a lot because the most important use of headings would be for screenreaders.
As a 'sighted' web designer, I've found it's helpful to scan over my designs using Lynx, an old text-based browser. It has some similar features/limitations to screen reader software, and can help you catch many of the more blatant accessibility issues. Highly recommended for all designers and front-end developers.
Thanks so much ! I've been trying to explain some of these concepts to people for a long time. It is such a shame alot of the web is made by cowboys (or cowgirls) and sighted users are normally so disinterested in making things properly because all they SEE is pretty graphics :(
This was a great eye opener for me. I have been a designer and developer for years now but I have never actually looked this in-depth into screen readers.
Can I ask a personal question, do you not find the voice reads very fast?
Very informative video Eric. Since Jaws is extremely expensive ($900) and not available for the Mac, very few sighted developers have access to it for testing. So it's great to see a live demo of how it works in practice. There's been an ongoing debate about whether or not to make your site name an h1 tag or not. I think this clearly shows that you shouldn't.
(You can download a demo version of both Jaws and WindowsEyes. They only run for 40 minutes at a time, but the demo doesn't end after a certain number of days.)
I'm not ignoring the other question about what other sites do a good or bad job with headings, it's just that YouTube doesn't seem to permit URLs in comments. Still, I'll give it a shot. One that uses them relatively well is a big competetor with Amazon and their name has a B and an & and an N. The other that uses them poorly is spelled "bee you why dot calm". Hopefully that's clear enough.
Thanks all for the feedback. The screenreader used to make this video is Jaws for Windows version 9.0 (the latest version currently) available from Freedom Scientific.
Wow. This is really an eye opener for me. I have always known headings are important for both off-screen readers and web browsers. But your video really shows it clearly.
Thanks for recording this. What screen reader do you use by the way? I want to check for future sites that I will be making.
Thank you for putting this together. Are there other sites out there that you would expect to use the heading tag well that don't? Or, can you point out other sites that effectively use this tag?
awesome video, thanks for insight on the importance of html headers.
bucky765 5 months ago
Thank you! The more access web developers have to this information, the better we will be at developing better web pages and applications. :-)
Middys1 8 months ago
I'd also like to point out to fellow web developers: it is LAW to make technology accessible *if* you are working for the US Gov't. It's called Section 508. If you are applying for a web development job that serves the gov't, you better know what section 508 is. It's pretty easy to learn the basic idea, just grab a book about it.
smlefo 1 year ago
Thank you for a very insightful video.
AazaDana 1 year ago
Spot on. I totally agree with you that in some sites, text that should have been headings are simply bolded, and this gives screen reader users quite a challenging time. I'd also like to add that the right order of headings should be followed. Heading 1 should be followed by 2, 2 followed by 3 and so on.
EvenGroundsInc 1 year ago
Interesting little video.
Many thanks for sharing this.
atrainhxdotcom 1 year ago
Thank you for sharing this video. I teach Internet technology and this video definitely helps my student on why web accessibility is so important.
iskandarmsarkawi 2 years ago
Thanks. Very useful.
There's also a free/ open source screen reader for Windows - NVDA.
NickFreear 2 years ago
Thanks a ton, this video helped a ton and helps me feel good that I used a lot of header tags on my site in what I think logic places. I realized how helpful they can be to you, and so I think I will keep even more priority to them since that's how you navigate.
@athenenumphe: I'll check out FANGS seems useful!
MyUnv 2 years ago
Thank you for putting this video up. There's been a lot of debate on what headings should be used in a document and this video definitely helped a lot because the most important use of headings would be for screenreaders.
monfreex 2 years ago
As a sighted person, I really like using the Firefox Add-on Fangs to see how a screen reader would read a web page.
athenenumphe 2 years ago 5
As a 'sighted' web designer, I've found it's helpful to scan over my designs using Lynx, an old text-based browser. It has some similar features/limitations to screen reader software, and can help you catch many of the more blatant accessibility issues. Highly recommended for all designers and front-end developers.
slinger23 2 years ago 5
Thanks so much ! I've been trying to explain some of these concepts to people for a long time. It is such a shame alot of the web is made by cowboys (or cowgirls) and sighted users are normally so disinterested in making things properly because all they SEE is pretty graphics :(
SoggyGibblets 2 years ago
This was a good insight into why developing using standards is important. Thanks for sharing.
LavaIce99 2 years ago
This was a great eye opener for me. I have been a designer and developer for years now but I have never actually looked this in-depth into screen readers.
Can I ask a personal question, do you not find the voice reads very fast?
antmadferit 3 years ago
You can set the speech rate and advanced screen reader users tend to have theirs set fast as they become more and more accustomed to it.
schalkn 3 years ago
Wow, and I thought I was making the voice very slow for this video. I generally run it at at least twice that rate.
gringochapin 2 years ago
Great Video, thanks for it.
ryanisnan 3 years ago
my tutorial for how to make an html header here watch?v=qCBEogeyFQc&fmt=18
chamillion02 3 years ago
woops, marked tactics2' comment accidental as spam - sorry. Can't replay anymore.
I'm interested in it, too.
What do you think about the use of H1. Should it be the sites title (where are you) or the contents title (what is it about)?
ruempel 3 years ago
Very informative video Eric. Since Jaws is extremely expensive ($900) and not available for the Mac, very few sighted developers have access to it for testing. So it's great to see a live demo of how it works in practice. There's been an ongoing debate about whether or not to make your site name an h1 tag or not. I think this clearly shows that you shouldn't.
tactics2 3 years ago
Great video! Thank you.
(You can download a demo version of both Jaws and WindowsEyes. They only run for 40 minutes at a time, but the demo doesn't end after a certain number of days.)
strottrot 3 years ago
most helpfull, thanks for bringing this to our attention.
youtubby01 3 years ago
I'm not ignoring the other question about what other sites do a good or bad job with headings, it's just that YouTube doesn't seem to permit URLs in comments. Still, I'll give it a shot. One that uses them relatively well is a big competetor with Amazon and their name has a B and an & and an N. The other that uses them poorly is spelled "bee you why dot calm". Hopefully that's clear enough.
gringochapin 3 years ago
Thanks all for the feedback. The screenreader used to make this video is Jaws for Windows version 9.0 (the latest version currently) available from Freedom Scientific.
gringochapin 3 years ago
Thanks so much for this, I'm going to my blog right now to make sure its all set out properly :-)
mshort1985 3 years ago
More please! This was great!
surfwax95 3 years ago 2
Wow. This is really an eye opener for me. I have always known headings are important for both off-screen readers and web browsers. But your video really shows it clearly.
Thanks for recording this. What screen reader do you use by the way? I want to check for future sites that I will be making.
Brilliant video!
pathetix 3 years ago
The screen reader software is Jaws.
blackshtef 3 years ago
Brilliant video, thanks so much for taking the time to make and post this.
katebp 3 years ago
Great job Eric! Keep them coming!
mmcritter 3 years ago
I hope someone at Youtube sees this.
hackworth 3 years ago
Thank you for putting this together. Are there other sites out there that you would expect to use the heading tag well that don't? Or, can you point out other sites that effectively use this tag?
josephmako 3 years ago