Skip to content
https://utkay.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
81
GRADE
B
FIX
5
REVIEW
2
PASS
17
INFO
0
Checks
24
17 PASS 2 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
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'>.
Info::
SVG favicon detected — scales perfectly to any size
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✓ SVG Favicon Present
✗ 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
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #101f2c
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 ModePartial Dark Mode
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Back-to-top link detected
Info::
1 navigation landmark(s) detected
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 1 <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.
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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 | Utkay Nesim Gögebakan ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 Ölçülebilir sonuçlar
1.05:1
#000000
on
#020A12
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sahadan gelen deneyim
1.05:1
#000000
on
#020A12
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Öğrenmeye devam
1.05:1
#000000
on
#020A12
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Bilgiyi paylaşmak
1.05:1
#000000
on
#020A12
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Proje Kalite Şefi
1.05:1
#000000
on
#020A12
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Kıdemli Tedarikçi Kalite Mühendisi
1.05:1
#000000
on
#020A12
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Kalite Uzmanı
1.05:1
#000000
on
#020A12
needs 3.0:1 (large text)
19px · bottom of viewport
h3 WCM Uzmanı
1.05:1
#000000
on
#020A12
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Proje ve üretim kalite
1.05:1
#000000
on
#020A12
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Tedarikçi ve müşteri kalite
1.05:1
#000000
on
#020A12
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Sürekli iyileştirme ve dijital araçla…
1.05:1
#000000
on
#020A12
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Üretim prosesleri ve ürün grupları
1.05:1
#000000
on
#020A12
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Mesleki yetkinlikler
1.05:1
#000000
on
#020A12
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Mekatronik Mühendisliği Yüksek Lisans…
1.05:1
#000000
on
#020A12
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Endüstri Mühendisliği ve Yönetimi Y…
1.05:1
#000000
on
#020A12
needs 3.0:1 (large text)
19px · bottom of viewport
h3 İşletme Yüksek Lisansı
1.05:1
#000000
on
#020A12
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Mekatronik Sistemler Mühendisliği Lisa…
1.05:1
#000000
on
#020A12
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Yabancı diller
1.05:1
#000000
on
#020A12
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Tedarikçi kalite yönetimi ve vSRM kull…
1.05:1
#000000
on
#020A12
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Tedarikçi İlişkileri Yönetimi ve Uyg…
1.05:1
#000000
on
#020A12
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Ölçülebilir sonu…1.05:13.0:1
#000000
#020A12
Fail
h2 Sahadan gelen deneyi…1.05:13.0:1
#000000
#020A12
Fail
h2 Öğrenmeye devam1.05:13.0:1
#000000
#020A12
Fail
h2 Bilgiyi paylaşmak1.05:13.0:1
#000000
#020A12
Fail
h3 Proje Kalite Şefi1.05:13.0:1
#000000
#020A12
Fail
h3 Kıdemli Tedarikçi …1.05:13.0:1
#000000
#020A12
Fail
h3 Kalite Uzmanı1.05:13.0:1
#000000
#020A12
Fail
h3 WCM Uzmanı1.05:13.0:1
#000000
#020A12
Fail
h3 Proje ve üretim kal…1.05:13.0:1
#000000
#020A12
Fail
h3 Tedarikçi ve müşt…1.05:13.0:1
#000000
#020A12
Fail
h3 Sürekli iyileştirm…1.05:13.0:1
#000000
#020A12
Fail
h3 Üretim prosesleri v…1.05:13.0:1
#000000
#020A12
Fail
h3 Mesleki yetkinlikler1.05:13.0:1
#000000
#020A12
Fail
h3 Mekatronik Mühendis…1.05:13.0:1
#000000
#020A12
Fail
h3 Endüstri Mühendisl…1.05:13.0:1
#000000
#020A12
Fail
h3 İşletme Yüksek Li…1.05:13.0:1
#000000
#020A12
Fail
h3 Mekatronik Sistemler…1.05:13.0:1
#000000
#020A12
Fail
h3 Yabancı diller1.05:13.0:1
#000000
#020A12
Fail
h3 Tedarikçi kalite y…1.05:13.0:1
#000000
#020A12
Fail
h3 Tedarikçi İlişkil…1.05:13.0:1
#000000
#020A12
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.

A
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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 "Deneyim" MAIN CONTENTINFO footer

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

A
Heading Hierarchy
35 headings, 1 skip(s)
PASS
35 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Kaliteyi yönetenDeğer katan
  • H2 Mühendislik disipliniBütünsel kalite yaklaşımı
  • H2 Ölçülebilir sonuçlar
  • H4 Rollmech proje sunumu onayı skipped
  • H4 Antolin garanti şikayeti ve maliyeti
  • H4 Çalışılan tedarikçi
  • H4 Devreye alma desteği verilen alt parça
  • H4 Devreye alma desteği verilen OEM parçası
  • H4 Gerçekleştirilen proses denetimi
  • H4 Rollmech proses denetimi
  • H4 Antolin’de takip edilen tedarikçi
  • H4 Antolin’de müşteri şikayeti olmadan üretim
  • H4 Kurulan proje kalite fonksiyonu
  • H2 Sahadan gelen deneyim
  • H3 Proje Kalite Şefi
  • H3 Kıdemli Tedarikçi Kalite Mühendisi
  • H3 Kalite Uzmanı
  • H3 WCM Uzmanı
  • H2 Sistemli düşünceGüçlü uygulama
  • H3 Proje ve üretim kalite
  • H3 Tedarikçi ve müşteri kalite
  • H3 Sürekli iyileştirme ve dijital araçlar
  • H3 Üretim prosesleri ve ürün grupları
  • H3 Mesleki yetkinlikler
  • H2 Öğrenmeye devam
  • H3 Mekatronik Mühendisliği Yüksek Lisansı (Tezli)
  • H3 Endüstri Mühendisliği ve Yönetimi Yüksek Lisansı
  • H3 İşletme Yüksek Lisansı
  • H3 Mekatronik Sistemler Mühendisliği Lisansı
  • H3 Yabancı diller
  • H2 Bilgiyi paylaşmak
  • H3 Tedarikçi kalite yönetimi ve vSRM kullanımı
  • H3 Tedarikçi İlişkileri Yönetimi ve Uygulamaları
  • H2 Bir sonraki adım içiniletişime geçelim
  • H3 Özgeçmişler

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+
Heading Text Quality
All 35 heading(s) have substantive, well-formed text
PASS
All 35 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 2 images OK
PASS
All 2 images OK
Info::
2 image(s) with good alt text
2 images 2 good alt text
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Form Input Types
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Mobile Keyboard & Autofill
No form controls -- mobile keyboard check is N/A
PASS
No form controls -- mobile keyboard check is N/A
Info::
No form controls on this page
A+
Document Language
Lang attribute set to "tr"
PASS
Lang attribute set to "tr"
Info::
<html lang="tr"> is set and valid
Got: tr
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 1 visible text node(s) render at >= 12 CSS pixels
PASS
All 1 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
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::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
A+
Lighthouse Accessibility Audits
Score 96/100 — 1 failing, 9 passed
PASS
96

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.

Best practices

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-hidden="true"]` is not present on the document `<body>`
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`[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
●Links have a discernible name
●Touch targets have sufficient size and spacing.
●Skip links are focusable.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○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
○Elements use only permitted ARIA attributes
○`[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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○The page contains a heading, skip link, or landmark region
○Background and foreground colors have a sufficient contrast ratio
○`<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
○Heading elements appear in a sequentially-descending order
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Image elements have `[alt]` attributes
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback