Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

HTML checks - check the language the content is written in #67

Closed
Angelsaur opened this issue Jan 26, 2021 · 2 comments
Closed

HTML checks - check the language the content is written in #67

Angelsaur opened this issue Jan 26, 2021 · 2 comments
Assignees
@jhlink @GeorgiaHCA @JamesSCTJ
Labels
accessibility Improves accessibilty for users with diverse needs Community Inclusion Supports diverse inclusion and builds community documentation Improvements or additions to documentation Milestone 4 MVP accessibility checks
Milestone
4: MVP Accessibil...

Comments

@Angelsaur
Copy link
Collaborator

Summary

A screen reader needs to know what language a page is written in so it uses the correct speech libraries for accent and pronunciation. It only knows this if the language is specified in the page HTML.

Deadline

20/02/2021

What needs to be done?

You’ll need to check the HTML of your sample content pages to see whether your website does this. To inspect the page HTML, use the same method you used when checking whether your content was marked up appropriately.

Once you’ve opened the HTML, scroll to the top of the panel. You should see a <!doctype html> tag. Directly under that you should see an <html lang=” tag. This is where the screen reader finds out the page language.

If the page is written in English, the tag should read <html lang=“en” or <html lang=“en-gb”. If it’s empty, the screen reader cannot tell what language the page is in.

If any of your sample pages contain content written in other languages, you’ll need to check that’s marked up properly too, using the country code for the relevant language.

Who can help?
@Angelsaur Angelsaur added documentation Improvements or additions to documentation accessibility Improves accessibilty for users with diverse needs Community Inclusion Supports diverse inclusion and builds community labels Jan 26, 2021
@Angelsaur Angelsaur added this to the Accessibility milestone Jan 26, 2021
@GeorgiaHCA
Copy link
Collaborator

Thanks @Angelsaur - I tried to include these but when I ran it locally this was displayed as text. Any suggestions how to fix this @jhlink?

@GeorgiaHCA GeorgiaHCA added the Milestone 4 MVP accessibility checks label May 24, 2021
@gedankenstuecke
Copy link
Member

Made issue #369 to create an accessibility checklist that can be used for the MVP and going forward. Closing this along with other accessibility checklist items for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jhlink jhlink

@GeorgiaHCA GeorgiaHCA

@JamesSCTJ JamesSCTJ

Labels
accessibility Improves accessibilty for users with diverse needs Community Inclusion Supports diverse inclusion and builds community documentation Improvements or additions to documentation Milestone 4 MVP accessibility checks
Projects
None yet
Milestone
4: MVP Accessibility Check
Development

No branches or pull requests
5 participants
@gedankenstuecke @jhlink @GeorgiaHCA @JamesSCTJ @Angelsaur