Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 2 REVIEW 9 FIX

Heading Hierarchy

Action

32 headings, 3 skip(s)

FIX

32 headings, 3 skip(s)

Multiple H1 headings (4 found)

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

Heading level skipped: H3 → H5 (missing H4)

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

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H3 Announcing DergiPark’s New Design Era: More Transparent, More Elegant!
H5 Balıkesir Sağlık Bilimleri Dergisi skipped
H5 Avrasya Dosyası
H5 (empty)
H5 Istanbul Business Research
H5 ARÜ İlahiyat Araştırmaları Dergisi
H5 Journal of Social Sciences of Bulanık Vocational School
H5 Veche
H5 Balıkesir University Law Review
H5 Journal of Global Tourism and Technology Research
H5 Communications Faculty of Sciences University of Ankara Series A1 Mathematics and Statistics
H3 3.072
H3 1.717
H3 810.161
H3 886.917
H1 About
H1 DergiPark is not an index duplicate H1
H1 Announcements duplicate H1
H4 Announcing DergiPark’s New Design Era: More Transparent, More Elegant! skipped
H4 Continuous Publication TR Index Integration Completed
H4 Digital Transformation in Publishing Is Ongoing!
H4 DergiPark is now at your service with a faster and more secure infrastructure!
H4 2024 DergiPark User Survey Result
H4 A Short Break for Journal Applications
H4 Happy 100th Anniversary of the Turkish Republic.
H4 DergiPark mobile application is at your service!
H4 "Follow" feature have been added
H4 If you have more than one accounts
H4 DergiPark "New Article Workflow" Guide
H1 Help duplicate H1
H3 How to send my article to a journal? How to use my own domain? How to publish my issue? If you have more to ask... skipped
H3 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

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 ▾

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

Alt Text Quality

Action

4 of 20 images have issues

FIX

4 of 20 images have issues

4 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image-in-link without alt text

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

16 image(s) with good alt text

20 images 16 good alt text 4 missing

Issue	Count
missing	4 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

Link & Button Quality

Action

14 issue(s) across 99 links and 2 buttons

FIX

14 issue(s) across 99 links and 2 buttons

9 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /en/user/notification; /en/user/notification; #; /en/pub/kiupsikoloji; https://play.google.com/store/apps/details?id=tr.org.dergipark.mobile&pcampai…; https://apps.apple.com/us/app/dergipark-akademik/id6462056500?itsct=apps_box_…; https://facebook.com/dergipark; https://twitter.com/dergipark; https://www.instagram.com/dergipark

4 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: //dergipark.org.tr/en/pub/page/about ("Read More"); //dergipark.org.tr/en/pub/page/dergipark-bir-dizin-degildir ("Read More"); https://dergipark.org.tr/tr/download/file/135 ("Click here"); https://dergipark.org.tr/tr/pub/page/dergi-basvurusu-hakkinda ("Click here")

3 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://confluence.ulakbim.gov.tr/display/DYM; https://www.youtube.com/watch?v=OfAhRfQB-LQ; https://ulakbim.tubitak.gov.tr/en

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button#home-search-btn

83 link(s) with descriptive text

99 links

9 empty

4 generic text

3 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
/en/user/notification	(empty)	empty	Add link text or aria-label
https://confluence.ulakbim.gov.tr/displa…	Help	new tab	Add '(opens in new tab)' to text
/en/user/notification	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
/en/pub/kiupsikoloji	(empty)	empty	Add link text or aria-label
//dergipark.org.tr/en/pub/page/about	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: About
//dergipark.org.tr/en/pub/page/dergipark…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Dergipark Bir Dizin Degildir
https://dergipark.org.tr/tr/download/fil…	Click here	generic text	Replace with descriptive text
Before: Click here Suggested: 135
https://dergipark.org.tr/tr/pub/page/der…	Click here	generic text	Replace with descriptive text
Before: Click here Suggested: Dergi Basvurusu Hakkinda
https://www.youtube.com/watch?v=OfAhRfQB…	https://www.youtube.com/watch?…	new tab	Add '(opens in new tab)' to text
https://ulakbim.tubitak.gov.tr/en	Republic of Türkiye Ministry …	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	(empty)	empty	Add link text or aria-label
https://apps.apple.com/us/app/dergipark-…	(empty)	empty	Add link text or aria-label
https://facebook.com/dergipark	(empty)	empty	Add link text or aria-label
https://twitter.com/dergipark	(empty)	empty	Add link text or aria-label
https://www.instagram.com/dergipark	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label

84 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/en/user/notification; /en/user/notification; #; /en/pub/kiupsikoloji; https://play.google.com/store/apps/details?id=tr.org.dergipark.mobile&pcampai…; https://apps.apple.com/us/app/dergipark-akademik/id6462056500?itsct=apps_box_…; https://facebook.com/dergipark; https://twitter.com/dergipark; https://www.instagram.com/dergipark

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

//dergipark.org.tr/en/pub/page/about ("Read More"); //dergipark.org.tr/en/pub/page/dergipark-bir-dizin-degildir ("Read More"); https://dergipark.org.tr/tr/download/file/135 ("Click here"); https://dergipark.org.tr/tr/pub/page/dergi-basvurusu-hakkinda ("Click here")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

https://confluence.ulakbim.gov.tr/display/DYM; https://www.youtube.com/watch?v=OfAhRfQB-LQ; https://ulakbim.tubitak.gov.tr/en

Why this matters

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

Icon-only buttons need an aria-label so screen readers can announce them.

button#home-search-btn

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

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.

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Lighthouse Accessibility Audits

Action

Score 62/100 — 10 failing, 15 passed

FIX

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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search button `div.kt-portlet__body > div.form-group > div.input-group > span.input-group-append`
Journal status Active `div.col-lg-12 > div.card-columns > div.card > div.journal-classification`
Journal status Active `div.col-lg-12 > div.card-columns > div.card > div.journal-classification`
Journal status Active `div.col-lg-12 > div.card-columns > div.card > div.journal-classification`
Journal status Active `div.col-lg-12 > div.card-columns > div.card > div.journal-classification`
Journal status Active `div.col-lg-12 > div.card-columns > div.card > div.journal-classification`
Journal status Active `div.col-lg-12 > div.card-columns > div.card > div.journal-classification`
Journal status Active `div.col-lg-12 > div.card-columns > div.card > div.journal-classification`
Journal status Active `div.col-lg-12 > div.card-columns > div.card > div.journal-classification`
Journal status Active `div.col-lg-12 > div.card-columns > div.card > div.journal-classification`
Journal status Active `div.col-lg-12 > div.card-columns > div.card > div.journal-classification`

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.

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.form-group > div.input-group > span.input-group-append > button#home-search-btn `div.form-group > div.input-group > span.input-group-append > button#home-search-btn`

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.kt-footer__content_nav > div.google-play-badge > a > img `div.kt-footer__content_nav > div.google-play-badge > a > img`
div.kt-footer__content_nav > div > a > img `div.kt-footer__content_nav > div > a > img`

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.card > div.card-body > h5.card-title > a `div.card > div.card-body > h5.card-title > a`
div.kt-footer__section > div.kt-footer__content_nav > div.google-play-badge > a `div.kt-footer__section > div.kt-footer__content_nav > div.google-play-badge > a`
div.kt-footer__section > div.kt-footer__content_nav > div > a `div.kt-footer__section > div.kt-footer__content_nav > div > a`
div.kt-footer__social > ul.kt-footer__social-nav > li > a `div.kt-footer__social > ul.kt-footer__social-nav > li > a`
div.kt-footer__social > ul.kt-footer__social-nav > li > a `div.kt-footer__social > ul.kt-footer__social-nav > li > a`
div.kt-footer__social > ul.kt-footer__social-nav > li > a `div.kt-footer__social > ul.kt-footer__social-nav > li > a`

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.

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
e-ISSN: 2147-2238 `div.card-body > span.badge-wrap > span.badge > span`
e-ISSN: `span.badge-wrap > span.badge > span > strong`
ISSN: 2146-9601 `div.card-body > span.badge-wrap > span.badge > span`
ISSN: `span.badge-wrap > span.badge > span > strong`
15th Year `div.card-columns > div.card > div.year-badge > span`
ISSN: 1302-5678 `div.card-body > span.badge-wrap > span.badge > span`
ISSN: `span.badge-wrap > span.badge > span > strong`
33rd Year `div.card-columns > div.card > div.year-badge > span`
e-ISSN: 3023-6304 `div.card-body > span.badge-wrap > span.badge > span`
e-ISSN: `span.badge-wrap > span.badge > span > strong`
4th Year `div.card-columns > div.card > div.year-badge > span`
e-ISSN: 2630-5488 `div.card-body > span.badge-wrap > span.badge > span`
e-ISSN: `span.badge-wrap > span.badge > span > strong`
ISSN: 2630-5488 `div.card-body > span.badge-wrap > span.badge > span`
ISSN: `span.badge-wrap > span.badge > span > strong`
1972-2025 `div.card-columns > div.card > div.year-badge > span`
e-ISSN: 3023-8285 `div.card-body > span.badge-wrap > span.badge > span`
e-ISSN: `span.badge-wrap > span.badge > span > strong`
3rd Year `div.card-columns > div.card > div.year-badge > span`
e-ISSN: 3023-5987 `div.card-body > span.badge-wrap > span.badge > span`
e-ISSN: `span.badge-wrap > span.badge > span > strong`
4th Year `div.card-columns > div.card > div.year-badge > span`
e-ISSN: 2979-9562 `div.card-body > span.badge-wrap > span.badge > span`
e-ISSN: `span.badge-wrap > span.badge > span > strong`
5th Year `div.card-columns > div.card > div.year-badge > span`
e-ISSN: 3061-9858 `div.card-body > span.badge-wrap > span.badge > span`
e-ISSN: `span.badge-wrap > span.badge > span > strong`
3rd Year `div.card-columns > div.card > div.year-badge > span`
e-ISSN: 2717-6924 `div.card-body > span.badge-wrap > span.badge > span`
e-ISSN: `span.badge-wrap > span.badge > span > strong`
ISSN: 2717-6924 `div.card-body > span.badge-wrap > span.badge > span`
ISSN: `span.badge-wrap > span.badge > span > strong`
7th Year `div.card-columns > div.card > div.year-badge > span`
e-ISSN: 2618-6470 `div.card-body > span.badge-wrap > span.badge > span`
e-ISSN: `span.badge-wrap > span.badge > span > strong`
ISSN: 1303-5991 `div.card-body > span.badge-wrap > span.badge > span`
ISSN: `span.badge-wrap > span.badge > span > strong`
79th Year `div.card-columns > div.card > div.year-badge > span`
Journal `div.col-lg-6 > div.kt-iconbox > b > a.kt-link`
Publisher `div.col-lg-6 > div.kt-iconbox > a.kt-link > b`
Publisher Application `div.kt-iconbox > div > b > a.kt-link`
Article `div.col-lg-6 > div.kt-iconbox > a.kt-link > b`
Submit a Manuscript `div.kt-iconbox > div > b > a#article-submit`
Researcher `div.col-lg-6 > div.kt-iconbox > a.kt-link > b`
Register `div.kt-iconbox > div > b > a.kt-link`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Click here `div.kt-blog-list__content > label > p > a`
Click here `div.kt-blog-list__content > label > p > a`
Having more than one account `div.kt-blog-list__content > label > p > a`
guide here `div.kt-blog-list__content > label > p > a`

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
Announcing DergiPark’s New Design Era: More Transparent, More Elegant! `div.col-xl-5 > div.kt-blog-list__body > div.kt-blog-list__content > h4`
How to send my article to a journal? How to use my own domain? How to publish… `div.col-xl-5 > div.kt-blog-list__body > a.kt-blog-list__link > h3`

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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.wf-poppins-n4-active `html.wf-poppins-n4-active`

These items highlight common accessibility best practices.

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
Help How to send my article to a journal? How to use my own domain? How to p… `div.row > div.col-xl-5 > div.kt-blog-list__body > a.kt-blog-list__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>`

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Form elements have associated labels

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●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

●Touch targets have sufficient size and spacing.

●All heading elements contain content.

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○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

○`[role]`s have all required `[aria-*]` attributes

○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

○`[role]` values are valid

○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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

○Uses ARIA roles only on compatible elements

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

Landmark Structure

Action

2 landmarks

REVIEW

2 landmarks

No <main> landmark found

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

1 <nav> landmark(s) found

No banner (header) landmark

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

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

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

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Dergipark | 404 - Sayfa Bulunamadı ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="text" name="q" id="search_term">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
#search_term	text	(Search on DergiPark)	placeholder only

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

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+

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
h1 About	19.98:1	3.0:1	#000000	#F9F9FC	Pass
h1 DergiPark is not an …	19.98:1	3.0:1	#000000	#F9F9FC	Pass
h1 Announcements	19.98:1	3.0:1	#000000	#F9F9FC	Pass
h1 Help	19.98:1	3.0:1	#000000	#F9F9FC	Pass
h3 Announcing DergiPark…	19.98:1	3.0:1	#000000	#F9F9FC	Pass
h3 Quick Links	19.98:1	3.0:1	#000000	#F9F9FC	Pass
title Home » DergiPark	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Loading [a11y]/acces…	17.59:1	4.5:1	#000000	#EBEBE9	Pass
a About	14.86:1	4.5:1	#000000	#DAD9D4	Pass
a About	14.86:1	4.5:1	#000000	#DAD9D4	Pass
a Trends	19.98:1	4.5:1	#000000	#F9F9FC	Pass
a DOI Service	19.98:1	4.5:1	#000000	#F9F9FC	Pass
a Subjects	19.98:1	4.5:1	#000000	#F9F9FC	Pass
a Journals	19.98:1	4.5:1	#000000	#F9F9FC	Pass
a Publishers	19.98:1	4.5:1	#000000	#F9F9FC	Pass
a All	19.98:1	4.5:1	#000000	#F9F9FC	Pass
a University	19.98:1	4.5:1	#000000	#F9F9FC	Pass
a Government	19.98:1	4.5:1	#000000	#F9F9FC	Pass
a Association	19.98:1	4.5:1	#000000	#F9F9FC	Pass
a Foundation	19.98:1	4.5:1	#000000	#F9F9FC	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.

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