Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 5 REVIEW 3 FIX

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Landmark Structure

9 landmarks

REVIEW

9 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

5 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

Link & Button Quality

10 issue(s) across 294 links and 23 buttons

REVIEW

10 issue(s) across 294 links and 23 buttons

10 button(s) with no accessible text

294 link(s) with descriptive text

294 links

0 empty

0 generic text

0 new tab

10 empty buttons

Element	Text	Issue	Suggested Fix
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

307 links and buttons have descriptive text

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

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

Favicon & Branding

8 icon(s) detected

REVIEW

8 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 18 fail WCAG AA

REVIEW

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

2 pass 18 fail WCAG AA

h1 Your choice regarding cookies on this si…

1.13:1

#000000

#00132A

needs 3.0:1 (large text)

32px · top of page (header area)

h1 University of Oxford

1.16:1

#000000

#01162F

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Mathematical, Physical & Life Sciences D…

1.16:1

#000000

#01162F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Medical Sciences Division

1.16:1

#000000

#01162F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Social Sciences Division

1.16:1

#000000

#01162F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Department for Continuing Education

1.16:1

#000000

#01162F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Gardens, Libraries and Museums

1.16:1

#000000

#01162F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Colleges

1.16:1

#000000

#01162F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Colleges

1.16:1

#000000

#01162F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Divisions & departments

1.16:1

#000000

#01162F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Did you miss our recent Oxford Student C…

1.16:1

#000000

#01162F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The Ashmolean's In Bloom exhibition open…

1.16:1

#000000

#01162F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Fully-funded graduate studentships for e…

1.16:1

#000000

#01162F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 News

1.16:1

#000000

#01162F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Oxford’s women triumph in historic 80t…

1.16:1

#000000

#01162F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Spectacular fossil treasure trove pushes…

1.16:1

#000000

#01162F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 World Happiness Report 2026 shows a comp…

1.16:1

#000000

#01162F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Events

1.16:1

#000000

#01162F

needs 3.0:1 (large text)

24px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Your choice regardin…	1.13:1	3.0:1	#000000	#00132A	Fail
h1 University of Oxford	1.16:1	3.0:1	#000000	#01162F	Fail
h2 Divisions & departme…	7.37:1	3.0:1	#000000	#999999	Pass
h2 Humanities Division	6.93:1	3.0:1	#000000	#959492	Pass
h2 Mathematical, Physic…	1.16:1	3.0:1	#000000	#01162F	Fail
h2 Medical Sciences Div…	1.16:1	3.0:1	#000000	#01162F	Fail
h2 Social Sciences Divi…	1.16:1	3.0:1	#000000	#01162F	Fail
h2 Department for Conti…	1.16:1	3.0:1	#000000	#01162F	Fail
h2 Gardens, Libraries a…	1.16:1	3.0:1	#000000	#01162F	Fail
h2 Colleges	1.16:1	3.0:1	#000000	#01162F	Fail
h2 Colleges	1.16:1	3.0:1	#000000	#01162F	Fail
h2 Divisions & departme…	1.16:1	3.0:1	#000000	#01162F	Fail
h2 Did you miss our rec…	1.16:1	3.0:1	#000000	#01162F	Fail
h2 The Ashmolean's In B…	1.16:1	3.0:1	#000000	#01162F	Fail
h2 Fully-funded graduat…	1.16:1	3.0:1	#000000	#01162F	Fail
h2 News	1.16:1	3.0:1	#000000	#01162F	Fail
h2 Oxford’s women tri…	1.16:1	3.0:1	#000000	#01162F	Fail
h2 Spectacular fossil t…	1.16:1	3.0:1	#000000	#01162F	Fail
h2 World Happiness Repo…	1.16:1	3.0:1	#000000	#01162F	Fail
h2 Events	1.16:1	3.0:1	#000000	#01162F	Fail

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.

Heading Hierarchy

44 headings

PASS

44 headings

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

H1 Your choice regarding cookies on this site
H2 Divisions & departments
H2 Humanities Division
H2 Mathematical, Physical & Life Sciences Division
H2 Medical Sciences Division
H2 Social Sciences Division
H2 Department for Continuing Education
H2 Gardens, Libraries and Museums
H2 Colleges
H2 Colleges
H2 Divisions & departments
H1 University of Oxford duplicate H1
H2 Did you miss our recent Oxford Student Conference?
H2 The Ashmolean's In Bloom exhibition opens for spring
H2 Fully-funded graduate studentships for entry in 2026/27
H2 News
H2 Oxford’s women triumph in historic 80th boat race
H2 Spectacular fossil treasure trove pushes back origins of complex animals
H2 World Happiness Report 2026 shows a complex global picture of social media and happiness
H2 Events
H2 English Faculty/OWC Shakespeare Webinar: Henry VI, Part 1
H2 RSV Revisited: Immune responses in a post-vaccine era
H2 Discover
H2 University support during times of conflict and crisis
H2 Oxford in The Conversation
H2 Eggstraordinary Easter Eggventure Family Trail
H2 The OED Blog
H2 Department of International Development blog
H2 Victorian Visual Wonders
H2 Making space sustainable
H2 The Reuters Institute
H2 The OUP blog
H2 What's it like for women working in F1?
H2 Featured podcast
H2 Oxplore: the Home of Big Questions
H2 Studying at Oxford
H3 Undergraduate admissions
H3 Graduate admissions
H3 Lifelong learning
H3 Current Oxford students
H2 Connect with us
H2 Information About
H2 Information For
H2 Quick Links

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+

Alt Text Quality

All 22 images OK

PASS

All 22 images OK

1 image(s) with alt text over 125 characters

21 image(s) with good alt text

22 images 21 good alt text

Issue	Count
too long	1 image(s)

Form Accessibility

1 of 2 controls have issues

PASS

1 of 2 controls have issues

1 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="submit" name="op" id="edit-submit">

1 control(s) properly labeled

2 controls

1 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#edit-query	text	Search	for/id
#edit-submit	submit	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /sites/files/oxford/advagg_css/css__RIcZxFo3rxANGr7A_V48h3_N6P8l3crvS6Yb2q7wEVc__sb8Ujj6tWWssQfu7D3msxBLfh4PrTezTVySEM7hOySI__h7T-cjtV_dUO9EYp5xzvQZuTpmuCIt2rzPKmYSUARw8.css

Print Stylesheet ✓ Print Optimized

Print stylesheet /sites/files/oxford/advagg_css/css__RIcZxFo3rxANGr7A_V48h3_N6P8l3crvS6Yb2q7wEVc__sb8Ujj6tWWssQfu7D3msxBLfh4PrTezTVySEM7hOySI__h7T-cjtV_dUO9EYp5xzvQZuTpmuCIt2rzPKmYSUARw8.css ✓Inline @media print Not detected ✗

A+

Lighthouse Accessibility Audits

Score 95/100 — 1 failing, 25 passed

PASS

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.field > span.field-item-single > div.ds-1col > button.toggle-icon `div.field > span.field-item-single > div.ds-1col > button.toggle-icon`
div.field > span.field-item-single > div.ds-1col > button.toggle-icon `div.field > span.field-item-single > div.ds-1col > button.toggle-icon`
div.field > span.field-item-single > div.ds-1col > button.toggle-icon `div.field > span.field-item-single > div.ds-1col > button.toggle-icon`

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.

○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

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

●`[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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[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 have a discernible name

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

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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 type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○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

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

○Elements with visible text labels have matching accessible names.

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