Skip to content
https://gsk.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-nqpxag
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://gsk.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://gsk.com/manifest.json

Manifest contains invalid JSON.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="q">; <input type="search" name="q">
2 controls
0 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
qsearch(Enter a search term...)placeholder only
qsearch(Enter a search term...)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="search" name="q">; <input type="search" name="q">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

B
Favicon & Branding
11 icon(s) detected
REVIEW
11 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 85/100 — 4 failing, 26 passed
REVIEW
85

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Read the article div.hero__head-body > div.hero__head-content > div.hero__head-body-foot > a.button
Read our magazine div.magazine-article-carousel > div.magazine-article-carousel__panel > div.magazine-article-carousel__foot > a.button
Careers at GSK div.culture > div.culture__panel > div.culture__foot > a.button
Global health and health security div.nav > ul > li > button.btn-no-style

These are opportunities to improve the legibility of your content.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
details.cookie_description__container_analytics > summary > label.cookie_banner_checkbox_analytics > input#toggle_cat1 details.cookie_description__container_analytics > summary > label.cookie_banner_checkbox_analytics > input#toggle_cat1
details.cookie_description__container_analytics > summary > label.cookie_banner_checkbox_analytics > input#toggle_cat3 details.cookie_description__container_analytics > summary > label.cookie_banner_checkbox_analytics > input#toggle_cat3

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Change location div.site-header-mobile > div.site-header-mobile__inner > div.site-header-mobile__links > a.site-header-mobile__link

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
We use cookies body.light-theme > div#__tealiumGDPRcpPrefs > div#privacy_prompt > div.privacy_prompt_title_analytics
GSK values your privacy and your trust is important to us. We use cookies to en… div#privacy_prompt > div.privacy_prompt_content_analytics > p > span
Cookie Policy div#privacy_prompt > div.privacy_prompt_content_analytics > p > a.privacy_policy_url_analytics
Always active Strictly Necessary Cookies ❮ Necessary for the website to functi… div#__tealiumGDPRcpPrefs > div#privacy_prompt > div.privacy_prompt_content_analytics > div#show_more_description
Always active Strictly Necessary Cookies ❮ Necessary for the website to functi… div#show_more_description > ul.cookie_description_analytics > li > details.cookie_description__container_analytics
Strictly Necessary Cookies li > details.cookie_description__container_analytics > summary > span.cookie_description__title_analytics
Necessary for the website to function appropriately, such as store session data… ul.cookie_description_analytics > li > details.cookie_description__container_analytics > p.cookie_description_paragraph_analytics
Performance cookies ❮ div#show_more_description > ul.cookie_description_analytics > li > details.cookie_description__container_analytics
Performance cookies li > details.cookie_description__container_analytics > summary > span.cookie_description__title_analytics
Advertising Cookies ❮ div#show_more_description > ul.cookie_description_analytics > li > details.cookie_description__container_analytics
Advertising Cookies li > details.cookie_description__container_analytics > summary > span.cookie_description__title_analytics
CUSTOMIZE div#privacy_prompt > div.privacy_prompt_footer_analytics > div.prompt_button_analytics > button#preferences_prompt_customize
ACCEPT ALL div#privacy_prompt > div.privacy_prompt_footer_analytics > div.prompt_button_analytics > button#preferences_prompt_submit

These are opportunities to improve keyboard navigation in your application.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A+
Landmark Structure
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Global navigation" MAIN CONTENTINFO footer
A+
Heading Hierarchy
22 headings
PASS
22 headings
Info::
Single H1 present
  • H1 Behind the Science magazine
  • H2 Advancing the search for more targeted cancer treatment
  • H2 Who we are
  • H2 Discover how we're getting ahead
  • H3 ‘Digital biological twins and organoids might sound like sci-fi, but they’re real – and we’re using them to fight cancer’
  • H3 ‘Finding the right treatment for my asthma and nasal polyps has transformed my life. I hope my experience can help others achieve the same’
  • H3 ‘Long-acting therapies are no longer the future of HIV treatment – they are the now’
  • H3 ‘Cancer doesn’t have to be a deadly disease – it’s our goal to make it curable’
  • H3 ‘This could be a golden moment’: Is prevention the ‘medicine’ we need to end the HIV epidemic?
  • H3 ‘I feel hopeless and frustrated’: Why patients living with incurable blood cancers need more treatment options
  • H2 Find out what it's like to work with us
  • H3 Make a difference with us
  • H3 Do your best work with us
  • H3 Be yourself with us
  • H2 Positively impacting society and the planet
  • H3 Access
  • H3 Global health and health security
  • H3 Environment
  • H3 Inclusion
  • H3 Ethical standards
  • H3 Product governance
  • H3 INVESTORS
A+
Alt Text Quality
All 16 images OK
PASS
All 16 images OK
Info::
6 decorative image(s) correctly marked
Info::
10 image(s) with good alt text
16 images 10 good alt text 6 decorative
All images have appropriate alt text.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Behind the Science m…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Advancing the search…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Who we are21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Discover how we're g…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Find out what it's l…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Positively impacting…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ‘Digital biologica…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ‘Finding the right…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ‘Long-acting thera…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ‘Cancer doesn’t …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ‘This could be a g…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ‘I feel hopeless a…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Make a difference wi…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Do your best work wi…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Be yourself with us21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Access21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Global health and he…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Environment21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Inclusion21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Ethical standards21.00:13.0:1
#000000
#FFFFFF
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback