Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

19 PASS 2 REVIEW 3 FIX

Mobile Keyboard & Autofill

Action

2/2 eligible field(s) missing autocomplete or inputmode

FIX

2/2 eligible field(s) missing autocomplete or inputmode

1 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: country-name.

Got: <select name="country">

1 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: search.

Got: <input type="search" name="q" id="q">

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Mobile-Readable Font Sizes

Action

85% of visible text renders at >= 12 CSS px (23 below threshold)

REVIEW

85% of visible text renders at >= 12 CSS px (23 below threshold)

23 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 11.0px ("/ 1 November 2026"); <bdi> 11.0px ("NexGen Energy Ltd."); <span> 11.0px ("/ 1 November 2026"); <bdi> 11.0px ("American Lithium Corp"); <span> 11.0px ("/ 1 November 2026").

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found | Wellficent ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

A+

Landmark Structure

10 landmarks

PASS

10 landmarks

<main> landmark present

4 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

15 headings

PASS

15 headings

Single H1 present

H1 Cameco and Orano Commission Expanded Tailings Management System at McClean Lake Mill
H2 NexGen Energy Identifies New High-Grade Uranium Mineralization Along SW2 Exploration Corridor
H2 American Lithium Updates Preliminary Economic Assessment for Macusani Uranium Project in Peru
H2 TotalEnergies and Sonangol Advance Engineering for Cameia and Golfinho Deepwater Kwanza Basin Hub
H2 Global energy and well intelligence
H3 NexGen Energy Intersects High-Grade Uranium Mineralization in Arrow Deposit Step-Out Program
H3 Deep Yellow Finalizes Project Debt Facilities and Early Works for Tumas Uranium Mine in Namibia
H3 Pilbara Minerals Achieves First Ore Processing Through P1000 Expansion Circuit at Pilgangoora
H3 Uranium Energy Corp Accelerates In-Situ Recovery Operations at Christensen Ranch in Wyoming
H3 Elk Valley Resources Expands Active Water Treatment and Carbon Reduction at Fording River
H3 Chevron Advances Ballymore Deepwater Subsea Tieback Commissioning in the Gulf of Mexico
H3 Woodside Energy Advances Scarborough Energy Project and Pluto Train 2 Construction in Western Australia
H3 NexGen Energy Advances Rook I Project Toward Final Federal Uranium Licensing in Saskatchewan
H2 Beyond the wellhead, context.
H2 Privacy choices

A+

Heading Text Quality

All 15 heading(s) have substantive, well-formed text

PASS

All 15 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 7 images OK

PASS

All 7 images OK

7 decorative image(s) correctly marked

7 images 7 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 10 controls labeled

PASS

All 10 controls labeled

10 control(s) properly labeled

10 controls

10 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#q	search	Search stories	none
type	select	Content type	none
country	select	Country	none
subdivision	select	Area	none
topic	select	Topic	none
dataKind	select	Data type	none
basis	select	Evidence basis	none
sourceFrom	date	Source from	none
sourceTo	date	Source through	none
#news-sort	select	Sort	none

A+

Link & Button Quality

70 links, 5 buttons — all OK

PASS

70 links, 5 buttons — all OK

70 link(s) with descriptive text

70 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

75 links and buttons have descriptive text

A+

Form Input Types

10 form control(s) checked, no type mismatches

PASS

10 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

10 form control(s) checked, no input-semantic issues

PASS

10 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

2 explicit tabindex attribute(s) checked, no anti-patterns

PASS

2 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

Favicon & Branding

8 icon(s) detected

PASS

8 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Wellficent

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Wellficent ✓192×192 icon ✓512×512 icon ✓Start URL /en/ ✓Display Mode standalone ✓

Name Wellficent Display Mode standalone Theme Color #0f2a33 Background Color #f7f5ef Icons 4 icon(s)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Dark Mode Support

Full dark mode support

PASS

Full dark mode support

color-scheme meta tag present

The site declares support for light and dark color schemes via <meta name='color-scheme'>.

Got: light dark

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta light dark ✓Dark theme-color #0f2a33 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A+

Mobile UX Depth

3 mobile-depth signal(s) detected

PASS

3 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)

The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

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)

Element	Ratio	Required	FG	BG	Result
h2 Global energy and we…	17.94:1	3.0:1	#000000	#EFEDE7	Pass
h2 Beyond the wellhead,…	17.94:1	3.0:1	#000000	#EFEDE7	Pass
h2 Privacy choices	17.94:1	3.0:1	#000000	#EFEDE7	Pass
title Global energy and we…	19.09:1	4.5:1	#000000	#F6F4EE	Pass
a Skip to content	19.09:1	4.5:1	#000000	#F6F4EE	Pass
span FROM WELLHEAD TO MAR…	19.09:1	4.5:1	#000000	#F6F4EE	Pass
a Our standards	19.09:1	4.5:1	#000000	#F6F4EE	Pass
a wellficent	19.09:1	4.5:1	#000000	#F6F4EE	Pass
div Global energy, wells…	19.09:1	4.5:1	#000000	#F6F4EE	Pass
div News, data and analy…	18.76:1	4.5:1	#000000	#F4F2EC	Pass
span ⌄	18.10:1	4.5:1	#000000	#F0EEE8	Pass
span العربية	17.46:1	4.5:1	#000000	#ECEAE4	Pass
span Arabic	16.98:1	4.5:1	#000000	#E9E7E1	Pass
span English	16.83:1	4.5:1	#000000	#E8E6E0	Pass
span Español	16.83:1	4.5:1	#000000	#E8E6E0	Pass
span Spanish	16.83:1	4.5:1	#000000	#E8E6E0	Pass
span Français	16.83:1	4.5:1	#000000	#E8E6E0	Pass
span French	16.83:1	4.5:1	#000000	#E8E6E0	Pass
span Português	16.83:1	4.5:1	#000000	#E8E6E0	Pass
span Portuguese	16.83:1	4.5:1	#000000	#E8E6E0	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.

A+

Lighthouse Accessibility Audits

Score 100/100 — 1 failing, 26 passed

PASS

100

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Wells `body > header.wrap > nav.service-nav > a.service-link`
Refining `body > header.wrap > nav.service-nav > a.service-link`

○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

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●Select elements have associated label elements.

●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

●Background and foreground colors have a sufficient contrast ratio

●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.

●Links have a discernible name

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[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.

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○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.

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○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.

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