WCAG audit — Amgen Belgium

WCAG 2.2 Accessibility Audit

Name: Promedia
Address: Chaussée de Nivelles, 16, Braine-l'Alleud, 1420, BE
Telephone: +32475510663

Site: https://www.osteoporosenews.be
Audit date: 28 May 2026
Standard: WCAG 2.0 / 2.1 / 2.2

❌ Significant issues

major barriers across the experience.

3
Critical
8
Major
0
Minor
0
Advisory

Findings overview

Priority	Criterion	Level	Issue
🔴	1.1.1 Non-text Content	A	Across 8 pages of osteoporosenews.be — including the homepage, symptom, diagnosis, treatment, and patient testimonial pages — 91 instances of the .down_arrow <img> element are m…
🔴	4.1.2	A	Across 8 pages of osteoporosenews.be — including the homepage, treatment pages, diagnosis information, and patient testimonials — 245 instances of unsupported ARIA attributes we…
🔴	4.1.2	A	The search input field #header-search carries no programmatic label across 75 instances, spanning at least 8 pages of osteoporosenews.be — including core condition pages coverin…
🟠	1.3.1 Info and Relationships	A	Across 8 pages of osteoporosenews.be — including the condition explainer, symptom overview, treatment page, and patient-facing tips sections — 24 instances of <ol> elements cont…
🟠	1.3.1 Info and Relationships	A	Across 8 pages of osteoporosenews.be — including critical content pages on symptoms, treatments, nutrition, and the fracture-risk self-test — 117 <li> elements (starting with th…
🟠	1.4.3 Contrast (Minimum)	AA	Across 8 pages of osteoporosenews.be — including the homepage, the symptomen, diagnose, and behandelingen pages — 605 instances of low-contrast text were detected
🟠	1.4.6 Contrast (Enhanced)	AAA	Across 8 pages of osteoporosenews.be — including condition pages on symptoms, diagnosis, and treatments — 720 instances of blue text (#0063c3 on #ffffff) fail the WCAG AAA enhan…
🟠	2.4.2	A	Two pages on osteoporosenews.be are missing a non-empty <title> element: the Dutch "Wie zijn we" page (https://www.osteoporosenews.be/dutch/wie-zijn-we) and the French "Ostéopor…
🟠	2.4.4	A	Across 8 audited pages of osteoporosenews.be, 601 instances of links with no discernible text were detected, spanning at least 21 distinct element types — starting with .header_…
🟠	3.1.1	A	Two pages on osteoporosenews.be — the search results page and the French-language advice page (/french/conseils) — have an <html> element with no lang attribute, leaving the doc…
🟠	4.1.2	A	On the ostéoporose page (https://www.osteoporosenews.be/french/ostéoporose), 3 elements marked aria-hidden="true" — including #navigation-panel-0 and 2 further instances — still…

Detailed findings

4.1.2 aria-allowed-attr · A

Evidence: Across 8 pages of osteoporosenews.be — including the homepage, treatment pages, diagnosis information, and patient testimonials — 245 instances of unsupported ARIA attributes were detected on interactive elements. The primary affected element is #navigation-trigger-0 (plus 6 additional element types), each carrying ARIA attributes that are not permitted for their assigned role.
User impact: Screen-reader users relying on JAWS, NVDA, or VoiceOver receive contradictory or broken role announcements when navigating these elements, causing the assistive technology to misrepresent or ignore critical controls. On pages covering osteoporosis treatments and diagnosis (e.g., /behandelingen, /diagnose), patients managing bone-health conditions may be unable to correctly identify or operate navigation and interactive components, cutting them off from clinical information they need to act on.
Fix: Audit each of the 7 affected element types — starting with #navigation-trigger-0 — and remove or replace any ARIA attributes that the element's current role does not support; where needed, change the role itself to one that legitimately allows the intended attribute. Every ARIA attribute must be validated against the role's permitted attribute list defined in the ARIA specification (WCAG 4.1.2, Level A).

1.1.1 image-alt · A

Evidence: Across 8 pages of osteoporosenews.be — including the homepage, symptom, diagnosis, treatment, and patient testimonial pages — 91 instances of the .down_arrow <img> element are missing any alt attribute.
User impact: Screen-reader users (NVDA, JAWS, VoiceOver) navigating this osteoporosis patient site will hear the raw filename or a meaningless string read aloud each time they encounter one of these 91 arrows. On pages such as /behandelingen (treatments) and /diagnose, where these arrows likely guide patients through critical clinical content — treatment options, diagnostic steps, dosage context — the loss of that navigational cue breaks the reading flow precisely where comprehension matters most.
Fix: If the .down_arrow images are purely decorative scroll or section indicators, add alt="" to each so screen readers skip them silently. If any instance conveys direction or action (e.g., "scroll to next section" or "expand"), add a concise descriptive alt such as alt="Volgende sectie" — and audit the treatment and diagnosis pages first, given the clinical weight of their content.

4.1.2 label · A

Evidence: The search input field #header-search carries no programmatic label across 75 instances, spanning at least 8 pages of osteoporosenews.be — including core condition pages covering diagnosis, symptoms, and treatments.
User impact: Screen-reader users (NVDA, JAWS, VoiceOver) land on the search field and hear only "edit text" or a raw field name with no indication of its purpose, forcing patients managing osteoporosis to guess how to navigate the site and find medication or treatment information they need.
Fix: Add a visible <label> element linked to #header-search via a matching for/id pair, or at minimum an aria-label="Zoeken" attribute directly on the input — this satisfies WCAG 4.1.2 Level A and must be applied globally since the unlabelled field recurs across all 75 instances in the shared header template.

4.1.2 aria-hidden-focus · A

Evidence: On the ostéoporose page (https://www.osteoporosenews.be/french/ostéoporose), 3 elements marked aria-hidden="true" — including #navigation-panel-0 and 2 further instances — still contain focusable controls that keyboard and assistive-technology users can reach via Tab.
User impact: Screen-reader users on JAWS, NVDA, or VoiceOver will Tab into these hidden panels and hear nothing — the content is suppressed by aria-hidden — yet focus lands there, leaving users disoriented with no spoken feedback. On a patient-facing osteoporosis site, this is particularly harmful if those panels contain navigation links, treatment information, or dosage guidance that patients managing a chronic condition need to act on.
Fix: For each of the 3 affected elements (starting with #navigation-panel-0), either remove aria-hidden="true" so the content is fully exposed to assistive technology, or — if the panels are genuinely decorative or off-screen — also set tabindex="-1" on every focusable child (links, buttons, inputs) so keyboard focus cannot enter them while they are hidden.

1.4.3 color-contrast · AA

Evidence: Across 8 pages of osteoporosenews.be — including the homepage, the symptomen, diagnose, and behandelingen pages — 605 instances of low-contrast text were detected. The primary failing pair is the salmon-orange heading colour (#f29980) rendered on a white background (#ffffff), producing a contrast ratio of only 2.17:1 against the required 4.5:1. The selector .textimg--left > .layout-column:nth-child(2) > .sm-title is the leading offender, with 12 additional element types also failing.
User impact: Low-vision users — including older patients managing osteoporosis who rely on screen magnification or have reduced contrast sensitivity — cannot reliably read section headings styled in this colour. Critically, this affects content such as treatment options (behandelingen) and diagnostic information (diagnose), where misreading or skipping a heading can cause a patient to miss clinically relevant information about their bone health.
Fix: Darken the salmon-orange heading colour #f29980 to a shade that achieves at least 4.5:1 contrast against the white (#ffffff) background — for example, a deeper terracotta around #b94f2e meets this threshold. Apply the corrected colour token globally to .sm-title and all 12 additional failing element types so that no heading across the site falls below the WCAG AA minimum.

1.4.6 color-contrast-enhanced · AAA

Evidence: Across 8 pages of osteoporosenews.be — including condition pages on symptoms, diagnosis, and treatments — 720 instances of blue text (#0063c3 on #ffffff) fail the WCAG AAA enhanced contrast threshold, starting with the cookie consent link #CybotCookiebotDialogBodyEdgeMoreDetailsLink and 13 further element types. The measured ratio of 5.87:1, while passing AA, falls short of the 7:1 level required by WCAG 1.4.6.
User impact: Low-vision users — including older patients managing osteoporosis who frequently rely on screen magnification or have reduced contrast sensitivity — will find blue interactive text and informational links harder to read at this ratio, particularly on medically critical pages covering treatments and diagnosis. At AAA level this matters most for a health-education site whose core audience skews toward an age group where contrast sensitivity loss is common.
Fix: Darken the blue foreground from #0063c3 to a shade that achieves at least 7:1 against the white #ffffff background — for example #0050a0 or deeper — across all 14 affected element types. Apply the change globally via the site's design token or CSS variable so that the cookie banner, body links, and treatment-page CTAs are all corrected in a single update rather than element by element.

2.4.2 document-title · A

Evidence: Two pages on osteoporosenews.be are missing a non-empty <title> element: the Dutch "Wie zijn we" page (https://www.osteoporosenews.be/dutch/wie-zijn-we) and the French "Ostéoporose" condition page (https://www.osteoporosenews.be/french/ost%C3%A9oporose). Both html documents fail WCAG 2.4.2 Level A because no meaningful page title has been defined.
User impact: Screen-reader users (JAWS, NVDA, VoiceOver) rely on the <title> element as the very first thing announced when a page loads, and browser-tab labels depend on it for orientation. On the French osteoporosis condition page in particular, patients and HCPs researching the disease cannot immediately confirm they have landed on the right resource — a meaningful concern when users are navigating multiple tabs to compare treatment or diagnostic information.
Fix: Add a concise, descriptive <title> to each affected page — for example, <title>Wie zijn we – OsteoporoseNews</title> for the Dutch about page and <title>Ostéoporose – OsteoporoseNews</title> for the French condition page. Titles should follow the pattern "Page topic – Site name" so that both screen-reader announcements and browser tabs give users an unambiguous location cue the moment the page loads.

3.1.1 html-has-lang · A

Evidence: Two pages on osteoporosenews.be — the search results page and the French-language advice page (/french/conseils) — have an <html> element with no lang attribute, leaving the document language entirely undeclared.
User impact: Screen readers (JAWS, NVDA, VoiceOver) rely on the lang attribute to select the correct text-to-speech voice and pronunciation engine; without it, a French-language page about osteoporosis advice and medication guidance may be read aloud in the wrong language, garbling medical terminology and dosage instructions for blind or low-vision patients who depend on audio output.
Fix: Add a lang attribute to the <html> element on both affected pages: lang="nl" for Dutch-language content and lang="fr" for /french/conseils. This single-attribute fix brings both pages into conformance with WCAG 2.2 criterion 3.1.1 (Level A).

2.4.4 link-name · A

Evidence: Across 8 audited pages of osteoporosenews.be, 601 instances of links with no discernible text were detected, spanning at least 21 distinct element types — starting with .header_logo--primary. These links contain no visible label, no aria-label, and no meaningful alt text on any nested image, leaving them completely anonymous to assistive technologies.
User impact: Screen-reader users (JAWS, NVDA, VoiceOver) navigating this Belgian osteoporosis patient site hear only "link" — with no destination or purpose — 601 times across pages covering diagnosis, treatment options, and patient testimonials. A patient managing osteoporosis who relies on a screen reader cannot tell whether a link leads to a treatment overview, a dosage guide, or an external sponsor, making independent navigation of critical health content effectively impossible.
Fix: For every affected link, add a descriptive accessible name: use an aria-label on icon or logo links (e.g., aria-label="Osteoporose News — homepage" on .header_logo--primary), and add meaningful alt text to any linked images so that the link purpose is unambiguous. Pay particular attention to links on the /behandelingen (treatments) and /diagnose pages, where unlabelled links could cause patients to miss key medical information.

1.3.1 list · A

Evidence: Across 8 pages of osteoporosenews.be — including the condition explainer, symptom overview, treatment page, and patient-facing tips sections — 24 instances of <ol> elements contain direct child elements other than <li>, <script>, or <template>. This malformed list structure violates the semantic contract that assistive technologies rely on to interpret ordered sequences.
User impact: Screen-reader users (JAWS, NVDA, VoiceOver) depend on correct <ol>/<li> nesting to hear list announcements such as "list of 5 items" and to navigate step by step. On pages like /behandelingen (treatments) and /test-risico (risk self-test), patients managing osteoporosis may miss that numbered steps — for example, a treatment protocol or fracture-risk checklist — form an ordered sequence, leading to misinterpretation of medically relevant information.
Fix: Audit every <ol> across the 8 affected pages and move any rogue direct children (such as <div> or <p> wrappers) inside proper <li> elements, so the only direct children of each <ol> are <li>, <script>, or <template>. This restores WCAG 1.3.1 (Level A) conformance and allows screen readers to correctly announce the list count and item order on clinically sensitive pages like treatments and the risk-assessment tool.

1.3.1 listitem · A

Evidence: Across 8 pages of osteoporosenews.be — including critical content pages on symptoms, treatments, nutrition, and the fracture-risk self-test — 117 <li> elements (starting with the selector i:nth-child(1) > .ost_link and at least 6 further element patterns) are rendered outside of any parent <ul> or <ol> container, making them structurally orphaned list items.
User impact: Screen-reader users (JAWS, NVDA, VoiceOver) rely on proper list semantics to understand grouped information — for example, a list of osteoporosis symptoms or treatment options is announced as "list of 5 items," letting patients navigate item-by-item and grasp the scope at a glance. Without the <ul>/<ol> wrapper, this structure is invisible to assistive technology: patients managing osteoporosis who use screen readers will hear a stream of disconnected text with no indication that the items form a related set, increasing cognitive load when trying to interpret dosage guidance, treatment options, or side-effect information.
Fix: Wrap every orphaned <li> element — all 117 instances across the 8 affected pages — inside a semantically correct <ul> (for unordered content such as symptom lists or tips) or <ol> (for sequential steps). Pay particular attention to the treatments and risk-test pages, where list structure directly supports patient decision-making and regulatory content integrity.