Note that some screen readers support more specific, localized language designation, like en-au for Australian English. There are standard, two-letter language codes that we’ve listed in the Semantic Structure and Navigation course, so you can use those for reference. Now let’s quickly discuss language codes. So that gives you an idea of what a screen reader user might encounter if the language is not correctly designated, both the primary language and language of parts. (speaking French with English pronunciation rules) My friends and I went to a fancy French restaurant and they were impressed when I ordered my meal like a native. So at first, the screen reader correctly pronounces the English words with English pronunciation, but then it comes up to the French words and also pronounces them with English pronunciation rules. In this example, the inline language change specification is missing from the HTML. Here is a page that is written primarily in English, with a French sentence. And again, remember that the code must be a valid standard language code. The lang attribute can be applied to block level elements, such as div, heading 1, paragraph, and so on, and to inline elements, such as span, strong, etc. So the first rule is that: Inline language changes must be identified with a valid lang attribute. I need to correctly communicate this language change to the screen reader. Say that most of my web page is written in English, but there is a paragraph in French. Now let’s address language of parts or inline language changes. The screen reader would just read the contents with the pronunciation rules of the default language. The same would happen if there were no lang value at all. If I came to this page with lang = English, the screen reader would not recognize it and would instead read the English words with Spanish pronunciation. So let’s say that I speak Spanish and English, and my default language on my screen reader is set to Spanish. If, for example, it was written as lang = English, this is invalid and would not be accurately recognized by a screen reader. So here the value is en, which is the valid standard language code for English. Second, the primary language of the page must be identified with a valid value. Inside the page source, I see this attribute, lang equals en, and it’s right on the HTML element, where it should be. So let’s take a look here inside this Deque University course. First, the primary language of the page must be identified accurately on the HTML element. This is the language that all or most of the web page is written in. Let’s take a look at the requirements and best practices for designating the language.įirst, let’s address the primary language of the page. If they come to a website that is in a different language, this can either be a smooth, trouble-free experience, if the language is correctly designated, or it can sound like a jumbled mess that is impossible to understand. When a screen reader user installs and configures their software, they select a default language. Most screen readers can read multiple languages. Hi There and welcome! In this brief video, you’ll learn the key concepts for how and why to designate the primary page language, as well as language changes of parts within the page.Ĭorrect language designation is very important for screen reader users.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |