Skip to content
https://omicsonline.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 FIX
D
Landmark Structure
Action
16 landmarks
FIX
16 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
14 <nav> landmark(s) found
Warning::
14 of 14 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 header 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
Alt Text Quality
Action
10 of 22 images have issues
FIX
10 of 22 images have issues
Critical::
10 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
10 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
12 image(s) with good alt text
22 images 12 good alt text 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

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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::
14 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 14 <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
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Open Access Journals | OMICS International ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 16 fail WCAG AA
REVIEW

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

4 pass 16 fail WCAG AA 4 pass AA only
title Omics online | Omics | Open Access Journ…
2.47:1
#000000
on
#3E4F5A
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a 44 2039664288
3.50:1
#000000
on
#636363
needs 4.5:1 (normal text)
16px · top of page (header area)
a Home
3.50:1
#000000
on
#636363
needs 4.5:1 (normal text)
16px · top of page (header area)
a Register
3.50:1
#000000
on
#636363
needs 4.5:1 (normal text)
16px · top of page (header area)
a Site Map
3.50:1
#000000
on
#636363
needs 4.5:1 (normal text)
16px · above the fold
a Contact Us
3.50:1
#000000
on
#636363
needs 4.5:1 (normal text)
16px · above the fold
a Editors Recommendation
3.50:1
#000000
on
#636363
needs 4.5:1 (normal text)
16px · above the fold
a Language
3.50:1
#000000
on
#636363
needs 4.5:1 (normal text)
16px · above the fold
a Spanish
3.50:1
#000000
on
#636363
needs 4.5:1 (normal text)
16px · above the fold
a Chinese
3.50:1
#000000
on
#636363
needs 4.5:1 (normal text)
16px · above the fold
a Russian
2.59:1
#000000
on
#3D535D
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a German
1.47:1
#000000
on
#022D48
needs 4.5:1 (normal text)
16px · above the fold
a French
1.49:1
#000000
on
#0D2D49
needs 4.5:1 (normal text)
16px · above the fold
a Japanese
1.54:1
#000000
on
#0E304A
needs 4.5:1 (normal text)
16px · mid-page
a Portuguese
1.60:1
#000000
on
#0D334C
needs 4.5:1 (normal text)
16px · mid-page
a Hindi
1.65:1
#000000
on
#0E364C
needs 4.5:1 (normal text)
16px · mid-page

2 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 About Us3.66:13.0:1
#000000
#666666
Pass
h3 Open Access Journals3.66:13.0:1
#000000
#666666
Pass
h3 Scientific Conferenc…3.66:13.0:1
#000000
#666666
Pass
h3 Scientific Alliance3.66:13.0:1
#000000
#666666
Pass
title Omics online | Omics…2.47:14.5:1
#000000
#3E4F5A
Fail
a 44 20396642883.50:14.5:1
#000000
#636363
Fail
a Home3.50:14.5:1
#000000
#636363
Fail
a Register3.50:14.5:1
#000000
#636363
Fail
a Site Map3.50:14.5:1
#000000
#636363
Fail
a Contact Us3.50:14.5:1
#000000
#636363
Fail
a Editors Recommendati…3.50:14.5:1
#000000
#636363
Fail
a Language3.50:14.5:1
#000000
#636363
Fail
a Spanish3.50:14.5:1
#000000
#636363
Fail
a Chinese3.50:14.5:1
#000000
#636363
Fail
a Russian2.59:14.5:1
#000000
#3D535D
Fail
a German1.47:14.5:1
#000000
#022D48
Fail
a French1.49:14.5:1
#000000
#0D2D49
Fail
a Japanese1.54:14.5:1
#000000
#0E304A
Fail
a Portuguese1.60:14.5:1
#000000
#0D334C
Fail
a Hindi1.65:14.5:1
#000000
#0E364C
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.

B
Lighthouse Accessibility Audits
Score 88/100 — 4 failing, 25 passed
REVIEW
88

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
Language div.container > div.row > div.nav-item > a#multi_lang
Open Access Journals div.col-12 > div.card > div.card-body > h3.text-warning
Read More div.col-12 > div.card > div.card-body > a.btn
Scientific Conferences div.col-12 > div.card > div.card-body > h3.text-warning
Read More div.col-12 > div.card > div.card-body > a.btn
Scientific Alliance div.col-12 > div.card > div.card-body > h3.text-warning
Read More div.col-12 > div.card > div.card-body > a.btn
Article Processing Charges div.row > div.col-12 > nav.nav > a.nav-item
Journal Impact Factor div.row > div.col-12 > nav.nav > a.nav-item
Peer Review Process div.row > div.col-12 > nav.nav > a.nav-item
Journals by Subject div.row > div.col-12 > div.card > h6.card-header
Clinical & Medical Journals div.row > div.col-12 > div.card > h6.card-header
Conferences By Continents div.row > div.col-12 > div.card > h6.card-header
Continents div.col-12 > div.card > h6.card-header > strong
Medical & Clinical Conferences div.row > div.col-12 > div.card > h6.card-header
Medical & Clinical div.col-12 > div.card > h6.card-header > strong
Conferences by Subject div.row > div.col-12 > div.card > h6.card-header
Subject div.col-12 > div.card > h6.card-header > strong
Latest Research Reports div.row > div.col-12 > div.card > h6.card-header
Journal of Materials Science and Nanomaterials div.media-body > div.row > div.col-12 > a.badge
Journal of Materials Science and Nanomaterials div.media-body > div.row > div.col-12 > a.badge
Journal of Materials Science and Nanomaterials div.media-body > div.row > div.col-12 > a.badge
Journal of Materials Science and Nanomaterials div.media-body > div.row > div.col-12 > a.badge
Journal of Materials Science and Nanomaterials div.media-body > div.row > div.col-12 > a.badge
Journal of Materials Science and Nanomaterials div.media-body > div.row > div.col-12 > a.badge
Journal of Materials Science and Nanomaterials div.media-body > div.row > div.col-12 > a.badge
Quick links div.row > div.col-12 > div.card > h6.card-header
New Initiatives div.row > div.col-12 > div.card > h6.card-header
Learn more div.fc-dialog-content > div.fc-dialog-scrollable-content > button.fc-faq-header > span.fc-faq-label
List of partners. div.fc-dialog-scrollable-content > div.fc-footer > p > a.fc-vendors-list-dialog

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
Journals by Subject div.row > div.col-12 > div.card > h6.card-header

These are opportunities to improve keyboard navigation in your application.

Names and labels

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
  body > nav.navbar > div.container-fluid > a.navbar-brand

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
Business & Management div.col-md-6 > ul.list-inline > li > a
Chemical Engineering div.col-md-6 > ul.list-inline > li > a
Clinical Sciences div.col-md-6 > ul.list-inline > li > a
Computer Science div.col-md-6 > ul.list-inline > li > a
Food & Nutrition div.col-md-6 > ul.list-inline > li > a
General Science div.col-md-6 > ul.list-inline > li > a
Medical Sciences div.col-md-6 > ul.list-inline > li > a
Nanotechnology div.col-md-6 > ul.list-inline > li > a
Nursing & Health Care div.col-md-6 > ul.list-inline > li > a
Pharmaceutical Sciences div.col-md-6 > ul.list-inline > li > a
Haematology div.col-md-6 > ul.list-inline > li > a
Healthcare div.col-md-6 > ul.list-inline > li > a
Immunology div.col-md-6 > ul.list-inline > li > a
Neurology div.col-md-6 > ul.list-inline > li > a
Nursing div.col-md-6 > ul.list-inline > li > a
Nutrition div.col-md-6 > ul.list-inline > li > a
Oncology div.col-md-6 > ul.list-inline > li > a
Ophthalmology div.col-md-6 > ul.list-inline > li > a
Orthopaedics div.col-md-6 > ul.list-inline > li > a
Pathology div.col-md-6 > ul.list-inline > li > a
Pediatrics div.col-md-6 > ul.list-inline > li > a
Psychiatry div.col-md-6 > ul.list-inline > li > a
Pulmonology div.col-md-6 > ul.list-inline > li > a
Surgery div.col-md-6 > ul.list-inline > li > a
Toxicology div.col-md-6 > ul.list-inline > li > a
Previous div.card > div.card-footer > nav.nav > button.slick-prev
Next div.card > div.card-footer > nav.nav > button.slick-next

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
●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
●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
●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
●No element has a `[tabindex]` value greater than 0
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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 buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○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.
○Image elements do not have `[alt]` attributes that are redundant text.
○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 Hierarchy
23 headings, 1 skip(s)
PASS
23 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H6 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Open Access Journals
  • H3 Scientific Conferences
  • H3 Scientific Alliance
  • H1 About Us
  • H6 Journals by Subject skipped
  • H6 Clinical & Medical Journals
  • H6 Conferences By Continents
  • H6 USA & Americas
  • H6 Asia-Pacific & Middle East
  • H6 Europe
  • H6 Medical & Clinical Conferences
  • H6 Conferences by Subject
  • H6 Latest Research Reports
  • H6 Tunable Emission Properties of Carbon Quantum Dots for Bioimaging and Photonic Applications
  • H6 Surface Plasmon Resonance-Based Biosensors Using Metal Nanostructures for Ultra-Sensitive Detection
  • H6 Plasmonic Nanostructures for Enhanced Photocatalysis: A Route Toward Efficient Hydrogen Production
  • H6 Next-Generation Solar Harvesting: Synthesis and Efficiency Optimization of Lead-Free Quantum Dots
  • H6 Mechanical and Thermal Behavior of Functionalized Carbon Nanotubes in Polymer Nanocomposites
  • H6 Collaborative Innovation in Nanotechnology: Impact of Global Nanomaterials Consortia on Research Acceleration
  • H6 Boron Nitride Nanotubes for High-Temperature Electronics: Synthesis and Application Review
  • H6 Quick links
  • H6 New Initiatives
  • H4 Testimonials

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

A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback