You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: archive/html_css/semantic_html.md
+2-4
Original file line number
Diff line number
Diff line change
@@ -75,7 +75,7 @@ Headings are the `<h1>` through `<h6>` elements, and like the name implies, thes
75
75
*`<nav>`
76
76
*`<section>`
77
77
78
-
By properly using landmarks and headings, you provide users of assistive technologies a more operable and understandable page: not only can screen reader users navigate a page via landmarks and headings by using quick navigation keyboard commands (or opening a menu in their screen reader), but these elements also have their roles announced to provide additional context.
78
+
By properly using landmarks and headings, you provide users of assistive technologies a more operable and understandbale page: not only can screen readers navigate a page via landmarks and headings by using quick navigation keyboard commands (or opening a menu in their screen reader), but these elements also have their roles announced to provide additional context.
79
79
80
80
If you were to use only `<div>` elements to act as these landmarks and headings, maybe adding in some CSS to visually style them, then a screen reader user would have to go through the entire page just to get to a specific section, and they may not be able to actually tell what is a heading or a landmark on the page.
81
81
@@ -98,6 +98,4 @@ This section contains helpful links to other content. It isn’t required, so co
98
98
99
99
*[NVAccess](https://www.nvaccess.org/download/) provides a download of the NVDA screen reader, one of the more popular (and free!) screen readers available, though it's only available for the Windows OS (this is the **only** time where we're saying it's okay to use Windows in the scope of this curriculum). If you're using a macOS device, you should have the VoiceOver screen reader available to you by default. While the lessons in this section will provide you with what a screen reader will generally announce, it can be invaluable to start using a screen reader yourself to test out your projects and see how they might be perceived.
100
100
*[Screen Reader Basics: VoiceOver](https://www.youtube.com/watch?v=5R-6WvAihms&list=PLNYkxOF6rcICWx0C9LVWWVqvHlYJyqw7g&index=8) and [Screen Reader Basics: NVDA](https://www.youtube.com/watch?v=Jao3s_CwdRU&list=PLNYkxOF6rcICWx0C9LVWWVqvHlYJyqw7g&index=9) go over some basics for getting started with both brands of screen readers. Both videos are worth watching regardless of which screen reader you choose/is available to you, as they contain some universal information as well.
101
-
*]Screen reader Basics: ChromeVox](https://www.youtube.com/watch?v=fpbIsN31hLM) Is a good place to start learning about the screen reader on ChromeBooks.
102
-
*[Screen reader Basics: Orca](https://www.youtube.com/watch?v=UI76P-KPZec) is where you can learn about the screen reader on Linux desktops.
103
-
*[ARIA Landmarks Example](https://www.w3.org/TR/wai-aria-practices/examples/landmarks/HTML5.html) lists the native HTML elements that define landmark regions as well as what their role is. If you check this resource out, be sure to enable the button toggles at the top of the page to see how the page is sectioned by landmarks and how it uses headings.
101
+
*[ARIA Landmarks Example](https://www.w3.org/TR/wai-aria-practices/examples/landmarks/HTML5.html) lists the native HTML elements that define landmark regions as well as what their role is. If you check this resource out, be sure to enable the button toggles at the top of the page to see how the page is sectioned by landmarks and how it uses headings.
0 commit comments