{"id":21332,"date":"2025-08-01T10:39:43","date_gmt":"2025-08-01T14:39:43","guid":{"rendered":"https:\/\/carleton.ca\/webaccessibility\/?page_id=21332"},"modified":"2025-08-01T10:57:39","modified_gmt":"2025-08-01T14:57:39","slug":"no-need-to-employ-visual-cues-in-text-aside-from-sub-headings","status":"publish","type":"page","link":"https:\/\/carleton.ca\/webaccessibility\/no-need-to-employ-visual-cues-in-text-aside-from-sub-headings\/","title":{"rendered":"No need to employ visual cues in text aside from sub-headings"},"content":{"rendered":"\n
\n
\n\n
\n
\n
\n

\n No need to employ visual cues in text aside from sub-headings\n <\/h1>\n \n \n <\/header>\n\n <\/div>\n\n <\/div>\n\n <\/div>\n<\/section>\n\n\n\n

Accessibility<\/h2>\n\n\n\n

We do not need to provide visual cues in texts to break up a page (for example by using a string of underscores or dashes). Best practice is just to use sub-headings.<\/p>\n\n\n\n

Reason<\/h2>\n\n\n\n

Sometimes, content creators will use a horizontal line to delineate one part of a page from another. Screen readers do not understand this as a cue to say “we’ve switched to another topic or point”. Therefore, when a horizontal line is used, it doesn’t have the effect the content creator intended. Visually, it can also cause a problem. <\/p>\n\n\n\n

Best practice<\/h2>\n\n\n\n

The best practice with organizing the content on a page is to use a proper content hierarchy. You can take a moment to learn about content hierarchy<\/a> and see an example of a well-constructed hierarchy<\/a>. But in brief, it means to use sub-headings as a way to organize content in a way that is meaningful. <\/p>\n\n\n\n

This means that content accessed visually makes sense. Look at this example:<\/p>\n\n\n\n

My topic of interest<\/h3>\n\n\n\n

I am interested in accessibilty for a couple of reasons.<\/p>\n\n\n\n

Accessibility is the right thing to do<\/h4>\n\n\n\n

Morally it is just plain good to help people.<\/p>\n\n\n\n

Accessibility is a sound business decision<\/h4>\n\n\n\n

If your content is accessible to people with disabilities, it is automatically also beneficial to everyone. This means more people will come to your university.<\/p>\n\n\n\n

<\/p>\n\n\n\n

In that example, the sub-headings are a visual cue, and an audible cue to those with a screen reader, telling us how the info is organized hierarchically.<\/p>\n\n\n\n

Example of poor practice<\/h2>\n\n\n\n

Using a visual horizontal divider is an automatic visual cue and so when it is misplaced it gives us false signals as to the nature of the info. Look at this example again, this time with a horizontal line in place:<\/p>\n\n\n\n

My topic of interest<\/h3>\n\n\n\n

I am interested in accessibilty for a couple of reasons.<\/p>\n\n\n\n

Accessibility is the right thing to do<\/h4>\n\n\n\n

Morally it is just plain good to help people.<\/p>\n\n\n\n

Accessibility is a sound business decision<\/h4>\n\n\n\n

If your content is accessible to people with disabilities, it is automatically also beneficial to everyone. <\/p>\n\n\n\n

__________________________________________________<\/p>\n\n\n\n

This means more people will come to your university.<\/p>\n\n\n\n

Because of that horizontal line I now believe the last sentence is unrelated to to the segment above it. This is because people sometimes use horizontal lines in the way our English teaachers told us not to use commas: When you take a pause in writing, or when you are uncertan as to what to write next.<\/p>\n\n\n\n

Additionally, that ___________________________ above was created using multiple instances of an underscore. When i screen reader encounters this it might say “Underscore underscore underscore underscore underscore underscore underscore etc.” (Tedious!) or it might just say it once (Confusing!)<\/p>\n\n\n\n

Additional benefits<\/h2>\n\n\n\n