Skip to content
https://tainexus.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
80
GRADE
B
FIX
4
REVIEW
5
PASS
15
INFO
0
Checks
24
15 PASS 5 REVIEW 4 FIX
D
Landmark Structure
Action
19 landmarks
FIX
19 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
9 <nav> landmark(s) found
Warning::
6 of 9 <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 "Üye bağlantıları" MAIN (missing!) ASIDE 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

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.

F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
9 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 9 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Heading Hierarchy
Action
63 headings, 3 skip(s)
REVIEW
63 headings, 3 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.
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: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Görünmeyen Kayıplarınızı Kazanca Çeviriyoruz.
  • H2 Çarkları kazanç için döndürüyoruz.
  • H2 Sözümüzü belgeyle veriyoruz.
  • H2 Neden Stratejik Danışmanlık İhtiyacı?
  • H2 Endüstriyel Strateji ve İş Birliği Ekosistemi
  • H2 Fark Yaratan 9 Özgün Çözüm
  • H2 Fabrika Röntgeni — 48 Saat Operasyonel Körlük Raporu
  • H2 Yapay Zekâ Destekli Danışmanlık — Veri ve İnsan Uzmanlığı
  • H2 Sektör Derinlik Kartları — Niş Uzmanlık
  • H2 Canlı Proje Panosu — Gerçek Zamanlı Şeffaflık
  • H2 Bırakarak Büyütme — Kalıcı Yetenek Transferi
  • H2 Yeşil Operasyonel Mükemmellik — ESG + Verimlilik
  • H2 Proaktif Risk Köprüsü — FMEA + BCP + İSG Entegrasyonu
  • H2 Ekosistem Ortaklığı — Ağ Yöneticisi
  • H2 Doğrulanabilir Sonuç — Şeffaf Ölçüm
  • H2 Tavsiye değil, ölçülmüş sonuç.
  • H2 Hizmet Verilen Sektörler
  • H3 Ağır Sanayi
  • H3 Hafif Sanayi
  • H3 Kimya & Enerji
  • H3 Gıda Sanayi
  • H2 Değer Önerimiz
  • H2 Veriyle Karar Veren,Sahada Sonuç ÜretenÇözüm Ortağınız.
  • H3 Veri Odaklı Yaklaşım
  • H3 Ölçülebilir Katma Değer
  • H3 Saha ve Mühendislik Deneyimi
  • H3 Global Metodoloji
  • H2 Hakkımızda
  • H2 Mühendislik Disipliniyle Stratejik Yönetimi Birleştiriyoruz.
  • H4 Odak Noktamız skipped
  • H4 Temel İlkemiz
  • H2 TAInexus 4D Metodolojisi
  • H3 Stratejik Teşhis & Veri Analizi
  • H3 Çözüm Mimarisi & Tasarım
  • H3 Uygulama & Operasyonel İcraat
  • H3 Ölçümleme & Sürdürülebilirlik
  • H2 İşletmenizin her katmanı için tek çatı altında 11 hizmet alanı.
  • H3 İşletme Danışmanlığı
  • H3 Yönetim Danışmanlığı
  • H3 Yalın Dönüşüm
  • H3 Kalite Sistemleri
  • H3 Mühendislik
  • H3 ERP & Dijital Dönüşüm
  • H3 İş Sağlığı ve Güvenliği
  • H3 Eğitim & Akademi
  • H3 Teşvik & Finansman
  • H2 Aile Şirketlerinde Profesyonel Yönetim ve Kurumsallaşma
  • H4 KURUMSALLAŞMA YOL HARİTASI skipped
  • H2 Farklı sektörlerde tamamlanmış dönüşüm projeleri
  • H2 Akademik Veri Yönetim Sistemi
  • H2 TAInexus hakkında merak edilenler
  • H3 TAInexus Kurumsal Sunumunu İnceleyin
  • H5 KURUMSAL skipped
  • H5 HİZMETLER
  • H5 KAMU PORTALLARI
  • H5 İLETİŞİM
  • H2 Sözümüzü belgeyle veriyoruz.
  • H2 Çarkları kazanç için döndürüyoruz.
  • H2 Fabrikanızın gizli kaybını 48 saatte görün.
  • H3 Kurumsal
  • H3 Hizmetler
  • H3 Kaynaklar
  • H3 İletişim

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

B
Mobile-Readable Font Sizes
93% of visible text renders at >= 12 CSS px (27 below threshold)
REVIEW
93% of visible text renders at >= 12 CSS px (27 below threshold)
Info::
27 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: <button> 10.0px ("❙❙"); <span> 11.0px ("Bize Yazın"); <span> 10.5px ("Grup Şirketler"); <span> 11.0px ("Ekosistem"); <span> 11.0px ("Üye Girişi").
C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 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::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
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 Çarkları
1.26:1
#000000
on
#111E37
needs 3.0:1 (large text)
24px · bottom of viewport
h2 döndürüyoruz.
1.26:1
#000000
on
#111E37
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sözümüzü belgeyle veriyoruz.
1.26:1
#000000
on
#111E37
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Neden Stratejik Danışmanlık İhtiyac…
1.26:1
#000000
on
#111E37
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Endüstriyel Strateji ve İş Birliği E…
1.26:1
#000000
on
#111E37
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Fark Yaratan 9 Özgün Çözüm
1.06:1
#0A192F
on
#111E37
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Fabrika Röntgeni — 48 Saat Operasyone…
1.26:1
#000000
on
#111E37
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Yapay Zekâ Destekli Danışmanlık — …
1.26:1
#000000
on
#111E37
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sektör Derinlik Kartları — Niş Uzma…
1.26:1
#000000
on
#111E37
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Canlı Proje Panosu — Gerçek Zamanlı…
1.26:1
#000000
on
#111E37
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Bırakarak Büyütme — Kalıcı Yetene…
1.26:1
#000000
on
#111E37
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Yeşil Operasyonel Mükemmellik — ESG …
1.26:1
#000000
on
#111E37
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Proaktif Risk Köprüsü — FMEA + BCP …
1.26:1
#000000
on
#111E37
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ekosistem Ortaklığı — Ağ Yönetici…
1.26:1
#000000
on
#111E37
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Doğrulanabilir Sonuç — Şeffaf Ölç…
1.26:1
#000000
on
#111E37
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Tavsiye değil, ölçülmüş sonuç.
1.26:1
#000000
on
#111E37
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Hizmet Verilen Sektörler
1.26:1
#000000
on
#111E37
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Değer Önerimiz
1.26:1
#000000
on
#111E37
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Veriyle Karar Veren,
1.06:1
#0A192F
on
#111E37
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Çözüm Ortağınız.
1.06:1
#0A192F
on
#111E37
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Çarkları1.26:13.0:1
#000000
#111E37
Fail
h2 döndürüyoruz.1.26:13.0:1
#000000
#111E37
Fail
h2 Sözümüzü belgeyl…1.26:13.0:1
#000000
#111E37
Fail
h2 Neden Stratejik Dan…1.26:13.0:1
#000000
#111E37
Fail
h2 Endüstriyel Stratej…1.26:13.0:1
#000000
#111E37
Fail
h2 Fark Yaratan 9 Özg…1.06:13.0:1
#0A192F
#111E37
Fail
h2 Fabrika Röntgeni …1.26:13.0:1
#000000
#111E37
Fail
h2 Yapay Zekâ Destekli…1.26:13.0:1
#000000
#111E37
Fail
h2 Sektör Derinlik Kar…1.26:13.0:1
#000000
#111E37
Fail
h2 Canlı Proje Panosu …1.26:13.0:1
#000000
#111E37
Fail
h2 Bırakarak Büyütme…1.26:13.0:1
#000000
#111E37
Fail
h2 Yeşil Operasyonel M…1.26:13.0:1
#000000
#111E37
Fail
h2 Proaktif Risk Köpr…1.26:13.0:1
#000000
#111E37
Fail
h2 Ekosistem Ortaklığ…1.26:13.0:1
#000000
#111E37
Fail
h2 Doğrulanabilir Sonu…1.26:13.0:1
#000000
#111E37
Fail
h2 Tavsiye değil, öl…1.26:13.0:1
#000000
#111E37
Fail
h2 Hizmet Verilen Sekt…1.26:13.0:1
#000000
#111E37
Fail
h2 Değer Önerimiz1.26:13.0:1
#000000
#111E37
Fail
h2 Veriyle Karar Veren,1.06:13.0:1
#0A192F
#111E37
Fail
h2 Çözüm Ortağını…1.06:13.0:1
#0A192F
#111E37
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+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
5 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: 5 all-caps heading(s)
A+
Alt Text Quality
All 22 images OK
PASS
All 22 images OK
Info::
22 image(s) with good alt text
22 images 22 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 5 controls labeled
PASS
All 5 controls labeled
Info::
5 control(s) properly labeled
5 controls
5 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#cmplz-functional-optincheckboxFonksiyonelfor/id
#cmplz-preferences-optincheckboxTercihlerfor/id
#cmplz-statistics-optincheckboxİstatistikfor/id
#cmplz-marketing-optincheckboxPazarlamafor/id
textareatextareaMesajınızaria-label
A+
Form Input Types
5 form control(s) checked, no type mismatches
PASS
5 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
5 form control(s) checked, no input-semantic issues
PASS
5 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 "tr"
PASS
Lang attribute set to "tr"
Info::
<html lang="tr"> is set and valid
Got: tr
A+
Tabindex Anti-Patterns
12 explicit tabindex attribute(s) checked, no anti-patterns
PASS
12 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
All 3 iframe(s) have descriptive titles
PASS
All 3 iframe(s) have descriptive titles
Info::
All 3 iframe(s) have title attributes
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+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: https://tainexus.com/wp-content/cache/autoptimize/css/autoptimize_6956e3e6cb6890bf8f0be25a6e8ca17d.css
Print Stylesheet ✓ Print Optimized
Print stylesheet https://tainexus.com/wp-content/cache/autoptimize/css/autoptimize_6956e3e6cb6890bf8f0be25a6e8ca17d.css ✓Inline @media print Not 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.
A+
Lighthouse Accessibility Audits
Score 100/100 — 1 failing, 29 passed
PASS
100

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.

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
TR div#sp-gpz3mz7eo9ii > div.txp-util > div.gt_switcher_wrapper > button.tx-dil-btn
○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
●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
●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
●Background and foreground colors have a sufficient contrast ratio
●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
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○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.
○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.
○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