Blind and Visually Impaired Community
↑
7
↓
Screen Reader help! (self.Blind)
submitted by dianainnashville
Hi, y'all--
I work at an educational institution in Nashville, and I'm working on creating some accessible material for our teachers. I'm running into an issue, and I would love some feedback from those of you who utilize screen readers to access school material like syllabi and assignment guides. Here's my question: is it easier for you to navigate a document when the title of the document is designated as a <title> with all of the following sections designated as <h1>? Or is it easier for you to navigate a document with the title of the document is designated as a <h1> with all of the following sections designated as <h2>? Or does it even make a difference?
Thanks so much!
I work at an educational institution in Nashville, and I'm working on creating some accessible material for our teachers. I'm running into an issue, and I would love some feedback from those of you who utilize screen readers to access school material like syllabi and assignment guides. Here's my question: is it easier for you to navigate a document when the title of the document is designated as a <title> with all of the following sections designated as <h1>? Or is it easier for you to navigate a document with the title of the document is designated as a <h1> with all of the following sections designated as <h2>? Or does it even make a difference?
Thanks so much!
MRXGray 4 points 3y ago
Yeah. I prefer Web pages with H1 for the title, H2 for parent sub headers, and H3 for child sub headers.
But for deeply nested content, it gets a bit irritating when it reaches H6 and beyond.
Especially when the content could've been formatted with shallower nests.
And I'm a Python dev, so I'm used to deeply nested code. LOL! :D
**P.S.** I'm completely blind and prefer to use JAWS For Windows.
But for deeply nested content, it gets a bit irritating when it reaches H6 and beyond.
Especially when the content could've been formatted with shallower nests.
And I'm a Python dev, so I'm used to deeply nested code. LOL! :D
**P.S.** I'm completely blind and prefer to use JAWS For Windows.
dianainnashville [OP] 2 points 3y ago
This was my understanding for Web pages, so I'm glad I'm on track there. What about for microsoft word documents? Still H1 for title? or title for title? Thanks for your feedback here! I appreciate it!
MRXGray 1 points 3y ago
The same with MS Word documents — H1 for titles, and H2 / H3 / H4s for nested sub headers.
But this doesn't provide us screenreader users with quick navigation benefits, unlike in Web pages.
Though the primary value is, at least for me, a more straightforward way to visualize content outline and data organization ...
But this doesn't provide us screenreader users with quick navigation benefits, unlike in Web pages.
Though the primary value is, at least for me, a more straightforward way to visualize content outline and data organization ...
Ltmusashi 5 points 3y ago
In Word to use quick navigation:
NVDA: NVDA key+space bar
Narrator: Caps lock+space bar
Jaws: Jaws key+z
I use word for my notes. My notes are organized with headings and tables. couldn't do it without quicknav.
NVDA: NVDA key+space bar
Narrator: Caps lock+space bar
Jaws: Jaws key+z
I use word for my notes. My notes are organized with headings and tables. couldn't do it without quicknav.
MRXGray 5 points 3y ago
Oh, I stand corrected! Thanks for this **—** So I tested it out. And yes **—** I learned something new today!! :)
Superfreq2 3 points 3y ago
The standard is to make an H1 title, followed by H1 section titles and H2 subsection headers.
So kinda both things you said LOL
But good of you to ask!
So kinda both things you said LOL
But good of you to ask!
dianainnashville [OP] 1 points 3y ago
This is a variation that I haven't run into yet! Way to throw a wrench into things! Ha. Thanks for your feedback.
CloudyBeep 1 points 3y ago
The only times I would consider using <title> in Word documents are:
• For books, because it would be weird to have main chapter headings at level 2.
• For material with numbered sections and subsections, because it would be weird to have section 1.1 at level 3.
• For collations of several articles or small documents.
• For books, because it would be weird to have main chapter headings at level 2.
• For material with numbered sections and subsections, because it would be weird to have section 1.1 at level 3.
• For collations of several articles or small documents.
This nonprofit website is run by volunteers.
Please contribute if you can. Thank you!
Our mission is to provide everyone with access to large-
scale community websites for the good of humanity.
Without ads, without tracking, without greed.
scale community websites for the good of humanity.
Without ads, without tracking, without greed.
©2023 HumbleCat Inc • HumbleCat is a 501(c)3 nonprofit based in Michigan, USA.