Skip to content
https://sau.int

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
9
REVIEW
5
PASS
10
INFO
0
Checks
24
10 PASS 5 REVIEW 9 FIX
D
Landmark Structure
Action
5 landmarks
FIX
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN (missing!) CONTENTINFO footer

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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

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

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

F
Heading Hierarchy
Action
82 headings, 6 skip(s)
FIX
82 headings, 6 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 SOUTH ASIAN UNIVERSITY
  • H3 A University Established by SAARC Nations
  • H2 SOUTH ASIAN UNIVERSITY
  • H3 A University established by SAARC Nations
  • H3 Latest Announcements
  • H4 Beyond the Degree: Exploring Career Horizons and Emerging Opportunities in Science and Technology | 4 November 2026
  • H4 Winter Certificate Programme on Artificial Intelligence and Law – Brochure
  • H4 Student Research Training Programme at CERN, Switzerland (Application Deadline: 1 November 2026)
  • H3 A vibrant and diverse academic community fostering an enriching campus experience
  • H3 Our campus: a dynamic, inclusive environment for exceptional academic and personal growth
  • H2 From the President's Desk
  • H4 Prof. K. K. Aggarwal skipped
  • H2 Our Faculties
  • H4 Faculty of Management skipped
  • H4 Faculty of International Studies (FIS)
  • H4 SAU Virtual Campus
  • H4 Faculty of Arts and Design
  • H4 Faculty of Mathematical Science
  • H4 Faculty of Enginneering and Technology
  • H4 Faculty of Social Sciences
  • H4 Faculty of Life Sciences & Biotechnology
  • H4 Faculty of Legal Studies
  • H4 Faculty of Economics
  • H2 Our Programmes
  • H4 Executive PhD skipped
  • H4 Computer Science
  • H4 Physics
  • H4 Media, Arts and Design
  • H4 Legal Studies
  • H4 Sociology
  • H4 International Relations
  • H4 Economics
  • H4 Biotechnology
  • H4 Mathematics
  • H4 Executive MBA
  • H4 MS (Climate Change & Sustainability)
  • H4 MBA
  • H4 LLM (Master of Laws)
  • H4 MA Sociology
  • H4 MA International Relations
  • H4 MA Economics
  • H4 Integrated M.Tech. (CSE)
  • H4 M.Tech. (Computer Science)
  • H4 MCA
  • H4 MSc Computer Science
  • H4 MSc Biotechnology
  • H4 MSc Mathematics / Applied Mathematics
  • H4 Integrated BBA-MBA
  • H4 BTech (Mathematics and Computing)
  • H4 Dual Degree BTech – MTech (CSE) (Spl Options)
  • H4 BTech CSE (Spl. in Business Systems & Intelligence)
  • H4 BTech CSE (Spl. in Cybersecurity)
  • H4 BTech CSE (Spl. in Data Science & AI)
  • H4 BTech CSE (Spl. in AI & ML)
  • H4 BTech CSE
  • H4 Fashion Design, Modelling and Styling
  • H4 Vocal Music and Art of Singing
  • H4 Communication Design and Graphics
  • H4 MBA
  • H4 MCA
  • H4 MS – Data Science and AI
  • H4 BCA
  • H4 Integrated BBA-MBA
  • H2 Faculty News
  • H4 Prof. Ritu Gaur and her team of PhD students- Madhu and Aradhana Singh have published their research work on porphyrins skipped
  • H4 Dr. Ananda Mustafiz and his research group, published a research article in the prestigious journal Plant Science
  • H4 Dr Yuba Raj Pokharel and his research team from Cancer Biology Laboratory have published a research article on 5-hydroxyisatin thiosemicarbazones in the Bioorganic Chemistry Journal.
  • H4 Dr Ravi Shankar Akundi was invited to deliver a talk at the 38th Annual Meeting of the Society for Neurochemistry India (SNCI) held at Punjab University, Chandigarh, India.
  • H2 SAU Events
  • H4 Beyond the Degree: Exploring Career Horizons and Emerging Opportunities in Science and Technology | 4 November 2026 skipped
  • H4 South Asian University (SAU) – Academic Collaboration at ISOL 2027
  • H4 4th South Asia Conference presents- Call for Papers
  • H2 SAU in Media
  • H2 Experience SAU
  • H4 Capturing SAU: A Visual Symphony of Growth skipped
  • H4 SAU’s 100-Acre Campus: A Place to Learn, Grow, and Thrive
  • H4 SAU Marathon 2025
  • H4 Lok Munch - South Asian Folk Music & Dance Festival
  • H4 Strengthening Educational Ties Between India & Maldives | SAU Distinguished Lecture
  • H2 Our Testimonials
  • H3 L Ambica Jain
  • H4 MA IR Class of 2019

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

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

D
Alt Text Quality
Action
10 of 96 images have issues
FIX
10 of 96 images have issues
Critical::
10 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
11 decorative image(s) correctly marked
Info::
75 image(s) with good alt text
96 images 75 good alt text 11 decorative 10 missing
IssueCount
missing10 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

D
Tap Target Adequacy
Action
45 tap target(s) too small or too close together
FIX
45 tap target(s) too small or too close together
Warning::
45 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

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
No navigation patterns
FIX
No navigation patterns
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 4 <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
Mobile-Readable Font Sizes
98% of visible text renders at >= 12 CSS px (1 below threshold)
REVIEW
98% of visible text renders at >= 12 CSS px (1 below threshold)
Info::
1 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: <a> 10.0px ("+91 (11) 35656500").
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found – South Asian University ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 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
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA
title South Asian University – SAU
2.47:1
#000000
on
#0E4C92
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 SOUTH ASIAN UNIVERSI…19.58:13.0:1
#000000
#F0F8FF
Pass
h2 SOUTH ASIAN UNIVERSI…19.58:13.0:1
#000000
#F0F8FF
Pass
h2 From the11.75:13.0:1
#003366
#F0F8FF
Pass
h2 Our19.58:13.0:1
#000000
#F0F8FF
Pass
h2 Our19.58:13.0:1
#000000
#F0F8FF
Pass
h2 Faculty19.58:13.0:1
#000000
#F0F8FF
Pass
h2 SAU19.58:13.0:1
#000000
#F0F8FF
Pass
h2 SAU in19.58:13.0:1
#000000
#F0F8FF
Pass
h2 Experience19.58:13.0:1
#000000
#F0F8FF
Pass
h2 Our19.58:13.0:1
#000000
#F0F8FF
Pass
h3 A University Establi…19.58:13.0:1
#000000
#F0F8FF
Pass
h3 A University establi…19.58:13.0:1
#000000
#F0F8FF
Pass
h3 Latest Announcement…11.75:13.0:1
#003366
#F0F8FF
Pass
h3 A vibrant and divers…19.58:13.0:1
#000000
#F0F8FF
Pass
h3 Our campus: a dynami…19.58:13.0:1
#000000
#F0F8FF
Pass
h3 L Ambica Jain19.58:13.0:1
#000000
#F0F8FF
Pass
title South Asian Universi…2.47:14.5:1
#000000
#0E4C92
Fail
a Home21.00:14.5:1
#000000
#FFFFFF
Pass
a Quick Links21.00:14.5:1
#000000
#FFFFFF
Pass
a Fee Payment for Wint…21.00:14.5: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.

C
Lighthouse Accessibility Audits
Action
Score 75/100 — 8 failing, 21 passed
REVIEW
75

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Slide 1 div.col-12 > section.image-and-apply > section#hero-carousel > div.carousel-inner

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Slide 1 div.col-12 > section.image-and-apply > section#hero-carousel > div.carousel-inner

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
President's Desk div.col-12 > div > h2 > span
Read More div.row > div.col-12 > div > a.read-more
Faculties section.faculty-section > div.container > h2.primary-heading > span
Programmes section.programs-section > div.container > h2.primary-heading > span
PhD Programmes div.container > ul.nav > li.active > a
Media section.research-section > div.container > h2.primary-heading > span
Testimonials section.testimonial-section > div.container > h2.primary-heading > span
MA IR Class of 2019 div.testimonial-wrapper > div#testimonial-content > div.testimonial-details > h4.text-2xl

These are opportunities to improve the legibility of your content.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Prof. K. K. Aggarwal div.row > div.col-12 > div > h4
Faculty of Management a > div.card > div.card-caption > h4
Executive PhD div.card > div.card-caption > a > h4
Dr. Ananda Mustafiz and his research group, published a research article in the… div.swiper-slide > div.event-card > div.event-caption > h4
Beyond the Degree: Exploring Career Horizons and Emerging Opportunities in Scie… div.upcoming-events > div.event-list > div.event-item > h4
Capturing SAU: A Visual Symphony of Growth div.swiper-slide > a > div.sau-video-card > h4

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > div.mobile-header-wrapper > div.mobile-logo > img.sau-logo div.container > div.mobile-header-wrapper > div.mobile-logo > img.sau-logo
div.container > div.mobile-header-wrapper > div.mobile-logo > img.saarc-logo div.container > div.mobile-header-wrapper > div.mobile-logo > img.saarc-logo

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
div.wrapper > div.c-height > div.single-search > a.icon-area div.wrapper > div.c-height > div.single-search > a.icon-area
div.swiper-slide > div.announce-card > h4 > a div.swiper-slide > div.announce-card > h4 > a
div.swiper-slide > div.announce-card > h4 > a div.swiper-slide > div.announce-card > h4 > a
div.swiper-container > div#swiper-wrapper-10f3a7cda1ad2c313 > div.swiper-slide > a div.swiper-container > div#swiper-wrapper-10f3a7cda1ad2c313 > div.swiper-slide > a
div.swiper-container > div#swiper-wrapper-10f3a7cda1ad2c313 > div.swiper-slide > a div.swiper-container > div#swiper-wrapper-10f3a7cda1ad2c313 > div.swiper-slide > a
div.swiper-container > div#swiper-wrapper-10f3a7cda1ad2c313 > div.swiper-slide > a div.swiper-container > div#swiper-wrapper-10f3a7cda1ad2c313 > div.swiper-slide > a
div.swiper-container > div#swiper-wrapper-10f3a7cda1ad2c313 > div.swiper-slide > a div.swiper-container > div#swiper-wrapper-10f3a7cda1ad2c313 > div.swiper-slide > a
div.swiper-container > div#swiper-wrapper-10f3a7cda1ad2c313 > div.swiper-slide > a div.swiper-container > div#swiper-wrapper-10f3a7cda1ad2c313 > div.swiper-slide > a
div.swiper-container > div#swiper-wrapper-10f3a7cda1ad2c313 > div.swiper-slide > a div.swiper-container > div#swiper-wrapper-10f3a7cda1ad2c313 > div.swiper-slide > a
div.swiper-container > div#swiper-wrapper-10f3a7cda1ad2c313 > div.swiper-slide > a div.swiper-container > div#swiper-wrapper-10f3a7cda1ad2c313 > div.swiper-slide > a
div.swiper-container > div#swiper-wrapper-10f3a7cda1ad2c313 > div.swiper-slide > a div.swiper-container > div#swiper-wrapper-10f3a7cda1ad2c313 > div.swiper-slide > a
div.swiper-container > div#swiper-wrapper-10f3a7cda1ad2c313 > div.swiper-slide > a div.swiper-container > div#swiper-wrapper-10f3a7cda1ad2c313 > div.swiper-slide > a
div.swiper-container > div#swiper-wrapper-10f3a7cda1ad2c313 > div.swiper-slide > a div.swiper-container > div#swiper-wrapper-10f3a7cda1ad2c313 > div.swiper-slide > a
div.container > div.socials > div.socials__icons > a div.container > div.socials > div.socials__icons > a
div.container > div.socials > div.socials__icons > a div.container > div.socials > div.socials__icons > a
div.container > div.socials > div.socials__icons > a div.container > div.socials > div.socials__icons > a
div.container > div.socials > div.socials__icons > a div.container > div.socials > div.socials__icons > a
footer > div.container > div.socials > a.btn-to-top footer > div.container > div.socials > a.btn-to-top

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go to slide 1 div.col-md-12 > div#faculty-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div.col-md-12 > div#faculty-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div.col-md-12 > div#faculty-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 4 div.col-md-12 > div#faculty-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 5 div.col-md-12 > div#faculty-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 6 div.col-md-12 > div#faculty-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 7 div.col-md-12 > div#faculty-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 8 div.col-md-12 > div#faculty-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 9 div.col-md-12 > div#faculty-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 10 div.col-md-12 > div#faculty-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 1 div#phd > div.swiper-container > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div#phd > div.swiper-container > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div#phd > div.swiper-container > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 4 div#phd > div.swiper-container > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 5 div#phd > div.swiper-container > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 6 div#phd > div.swiper-container > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 7 div#phd > div.swiper-container > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 8 div#phd > div.swiper-container > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 9 div#phd > div.swiper-container > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 10 div#phd > div.swiper-container > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 1 div.col-md-8 > div#event-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div.col-md-8 > div#event-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div.col-md-8 > div#event-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 4 div.col-md-8 > div#event-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 1 div.col-md-12 > div#research-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div.col-md-12 > div#research-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div.col-md-12 > div#research-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 4 div.col-md-12 > div#research-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 5 div.col-md-12 > div#research-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 6 div.col-md-12 > div#research-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 7 div.col-md-12 > div#research-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 8 div.col-md-12 > div#research-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 9 div.col-md-12 > div#research-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 10 div.col-md-12 > div#research-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 11 div.col-md-12 > div#research-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 12 div.col-md-12 > div#research-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 13 div.col-md-12 > div#research-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 14 div.col-md-12 > div#research-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 15 div.col-md-12 > div#research-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 16 div.col-md-12 > div#research-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 1 div.col-md-12 > div#sau-video-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div.col-md-12 > div#sau-video-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div.col-md-12 > div#sau-video-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 4 div.col-md-12 > div#sau-video-slider > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 5 div.col-md-12 > div#sau-video-slider > div.swiper-pagination > span.swiper-pagination-bullet

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

○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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●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
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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
○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.
○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.
A
Heading Text Quality
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Warning::
2 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H4: 182 chars - H4: 172 chars
Got: 2 >120-char heading(s)
Info::
2 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 2 all-caps heading(s)
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="s" id="s">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#stext(Search …)placeholder only

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

<input type="text" name="s" id="s">

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

A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "s" should use type="search" (currently type="text")
Field name "s" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
1 form control(s) checked, no input-semantic issues
PASS
1 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
110 explicit tabindex attribute(s) checked, no anti-patterns
PASS
110 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback