Accessibility Testing Lab home
Accessibility Testing LabA hands-on environment for practising accessibility testing

Testing language changes on a community library noticeboard

Review Finnish, Swedish, and English notices while separating language-markup defects from voice and platform limitations.

Difficulty:
beginner
Estimated time:
20 minutes

Objectives

  • Identify the intended human language of each passage before inspecting markup.
  • Test language boundaries and nested content with a screen reader.
  • Inspect declared and inherited language values.
  • Distinguish missing, incorrect, invalid, and overly broad language declarations.
  • Separate markup defects from unavailable voices or unsupported automatic switching.

Instructions

Use the Testing language changes with a screen reader method to review the community library noticeboard. Start the exercise from the Exercise workspace.

  1. Record your screen reader, browser, operating system, installed Finnish and Swedish voices, and automatic-language-switching setting.
  2. Review the visible English, Finnish, and Swedish passages and predict each language boundary.
  3. Read through every notice and its nested links with your screen reader.
  4. Inspect the declared and inherited language values in the markup.
  5. Identify exactly five markup findings and four passing checks.
  6. Record actual pronunciation or voice behavior separately from the markup evidence.
  7. For each finding, record the affected passage, declared or inherited value, expected language, user impact, and remediation direction.

Do not report a markup defect solely because a voice did not switch. Voice availability, automatic switching, and supported behavior vary across screen readers, browsers, operating systems, and user settings.

Exercise workspace

Community library language changes exercise

Start exercise

The exercise opens on a separate page. Return to this page whenever you need a hint, or when you are ready to continue and review the solution.

You can open the exercise in a new tab if you want to keep these instructions and hints available.

Hints
  1. Compare each passage's visible language with the language it inherits from the English document.
  2. Inspect nested links and the exact point where content returns from Finnish or Swedish to English.
  3. Look for one missing declaration, one wrong valid language, one invalid value, one unnecessary nested override, and one declaration whose scope is too broad.
Solution

The noticeboard contains five markup findings. The correctly marked Finnish and Swedish activities, inherited Swedish link, and intentional nested English event name are passing checks. Voice switching still depends on the test environment.

The Finnish family-reading notice inherits English

The Finnish sentence has no language declaration, so it inherits English from the document. Declare lang="fi" on the smallest suitable container for the Finnish passage.

The Swedish digital-help notice is marked as Finnish

The notice declares the valid code fi even though its content is Swedish. Automated validation cannot infer that mismatch. Change the declaration to lang="sv".

The Swedish registration link is overridden as English

The surrounding paragraph correctly declares Swedish, but the Swedish link declares English and can trigger the wrong pronunciation. Remove the unnecessary override so the link inherits sv.

The Finnish writing-workshop scope includes English content

The Finnish language declaration wraps both the Finnish notice and the following English availability sentence. Move lang="fi" to the Finnish passage, or restore English exactly at the genuine boundary.

The local-history notice uses an invalid Swedish language value

The value swedish is not a valid BCP 47 language tag. Replace it with the valid Swedish tag sv.