Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DDark Mode SupportActionNo dark mode signalsFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
BHeading Hierarchy32 headings, 1 skip(s)REVIEW
- H1 Our website uses cookies
- H2 Necessary cookies and anonymous statistical cookies
- H3 Optional marketing cookies
- H1 Independent minds.Collective spirit. duplicate H1
- H3 Search for a course skipped
- H3 Browse courses
- H3 Undergraduate Open Days
- H3 Postgraduate study at York
- H2 Explore our research
- H3 Biological cold case
- H3 Yorkshire life
- H3 Air pollution vulnerability
- H3 The power of play
- H2 News and events
- H3 Global recognition
- H3 Boundaries of Love
- H3 Athena Swan success
- H3 Best foot forward
- H3 Driving health innovation
- H3 Quantum leap
- H3 Study redefines positive mental wellbeing
- H3 Lost village on Yorkshire hill may hold secret to long-term prosperity
- H3 Physiotherapist awarded fellowship to improve brain tumour care
- H3 Cutting emissions is not the only way to save lives from air pollution, according to new study
- H2 Campus and city life
- H3 Student life
- H3 Accommodation
- H3 The city of York
- H2 Support in difficult times
- H2 Information for
- H2 Study with us
- H2 Popular links
A page should have only one H1. Multiple H1s dilute the document outline.
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
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
B404 Error PageHTTP 404, custom pageREVIEW
CWeb ManifestActionValid manifestREVIEW
CColor Contrast (Screenshot)Action20 text elements analyzed, 20 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 Our website uses coo… | 1.20:1 | 3.0:1 | #000000 | #00124E | Fail |
| h1 Independent minds. | 1.38:1 | 3.0:1 | #000000 | #071D67 | Fail |
| h1 Collective spirit. | 1.38:1 | 3.0:1 | #000000 | #071D67 | Fail |
| h2 Necessary cookies an… | 1.38:1 | 3.0:1 | #000000 | #071D67 | Fail |
| h2 Explore our research | 1.38:1 | 3.0:1 | #000000 | #071D67 | Fail |
| h2 News and events | 1.38:1 | 3.0:1 | #000000 | #071D67 | Fail |
| h2 Campus and city life | 1.38:1 | 3.0:1 | #000000 | #071D67 | Fail |
| h2 Support in difficult… | 1.38:1 | 3.0:1 | #000000 | #071D67 | Fail |
| h2 Information for | 1.38:1 | 3.0:1 | #000000 | #071D67 | Fail |
| h2 Study with us | 1.38:1 | 3.0:1 | #000000 | #071D67 | Fail |
| h2 Popular links | 1.38:1 | 3.0:1 | #000000 | #071D67 | Fail |
| h3 Optional marketing c… | 1.38:1 | 3.0:1 | #000000 | #071D67 | Fail |
| h3 Search for a course | 1.38:1 | 3.0:1 | #000000 | #071D67 | Fail |
| h3 Browse courses | 1.38:1 | 3.0:1 | #000000 | #071D67 | Fail |
| title University of York | 1.20:1 | 4.5:1 | #000000 | #00124E | Fail |
| p You can change your … | 1.38:1 | 4.5:1 | #000000 | #071D67 | Fail |
| span For more information… | 1.38:1 | 4.5:1 | #000000 | #071D67 | Fail |
| span how we use cookies o… | 1.38:1 | 4.5:1 | #000000 | #071D67 | Fail |
| span (Opens in a new wind… | 1.38:1 | 4.5:1 | #000000 | #071D67 | Fail |
| span Accept all | 1.38:1 | 4.5:1 | #000000 | #071D67 | 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.
ALandmark Structure8 landmarksPASS
Multiple navigations need aria-label to distinguish them for screen readers.
Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.
Learn more ▾ ▴
When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.
Source: WAI-ARIA Authoring Practices
A+Alt Text QualityAll 18 images OKPASS
A+Form AccessibilityAll 8 controls labeledPASS
| Control | Type | Label | Method |
|---|---|---|---|
| input | checkbox | none | |
| #q-search | text | Search | aria-label |
| #q-search | text | Search | aria-label |
| #level-undergraduate | radio | none | |
| #level-postgraduate-taught | radio | none | |
| #level-postgraduate-research | radio | none | |
| #q | text | Search courses | aria-label |
| #q-search | text | Search | aria-label |
A+Link & Button Quality218 links, 9 buttons — all OKPASS
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| /about/legal-statements/cookies/ | how we use cookies on our webs… | new tab | Add '(opens in new tab)' to text |
Add '(opens in new tab)' to link text or aria-label.
/about/legal-statements/cookies/
Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.
Learn more ▾ ▴
Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.
Source: MDN target / OWASP
AFavicon & Branding7 icon(s) detectedPASS
A+Lighthouse Accessibility AuditsScore 99/100 — 1 failing, 28 passedPASS
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.
Navigation
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Search for a course div.uoy_tabs > div.uoy_tabs_content > div#search-for-a-course > h3.uoy_tab_tabless_heading |
These are opportunities to improve keyboard navigation in your application.