Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 5 REVIEW 5 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

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 Missing

✓ 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

Theme color only

FIX

Theme color only

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: #0e1f28

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

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

3 navigation landmark(s) detected

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 3 <nav> element(s)

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.

Landmark Structure

8 landmarks

REVIEW

8 landmarks

<main> landmark present

3 <nav> landmark(s) found

1 of 3 <nav> elements are unlabeled

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

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

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

Heading Hierarchy

19 headings

REVIEW

19 headings

No H1 heading found

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

H2 Çözümler
H3 Kalite
H3 Projeler
H3 Masaüstü
H3 Eğitim
H3 İK
H3 Web
H3 Otomasyon
H3 Akademik
H3 Özel Çözüm
H2 Yaklaşımımız
H3 Üretim
H3 Eğitim
H3 Danışmanlık
H2 Hakkımızda
H2 Rakamlarla
H2 Mağaza
H2 İletişim
H2 İzel Danışman

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

Mobile Keyboard & Autofill

Action

1/2 eligible field(s) missing autocomplete or inputmode

REVIEW

1/2 eligible field(s) missing autocomplete or inputmode

1 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

Got: <input type="email" name="email" id="mail">

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 Page not found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 17 fail WCAG AA

REVIEW

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

3 pass 17 fail WCAG AA

h2 Yaklaşımımız

1.07:1

#000000

#040B1A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Rakamlarla

1.07:1

#000000

#040B1A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Mağaza

1.07:1

#000000

#040B1A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 İzel Danışman

1.07:1

#000000

#040B1A

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Kalite

1.15:1

#000000

#051818

needs 3.0:1 (large text)

19px · mid-page

h3 Projeler

1.15:1

#000000

#051818

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Masaüstü

1.07:1

#000000

#040B1A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Eğitim

1.07:1

#000000

#040B1A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 İK

1.07:1

#000000

#040B1A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Web

1.07:1

#000000

#040B1A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Otomasyon

1.07:1

#000000

#040B1A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Akademik

1.07:1

#000000

#040B1A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Özel Çözüm

1.07:1

#000000

#040B1A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Üretim

1.07:1

#000000

#040B1A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Eğitim

1.07:1

#000000

#040B1A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Danışmanlık

1.07:1

#000000

#040B1A

needs 3.0:1 (large text)

19px · bottom of viewport

title İzel Akademi — Geleceğe İz Bırakan…

1.14:1

#000000

#041718

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Çözümler	18.26:1	3.0:1	#FFFFFF	#051818	Pass
h2 Yaklaşımımız	1.07:1	3.0:1	#000000	#040B1A	Fail
h2 Hakkımızda	19.66:1	3.0:1	#FFFFFF	#040B1A	Pass
h2 Rakamlarla	1.07:1	3.0:1	#000000	#040B1A	Fail
h2 Mağaza	1.07:1	3.0:1	#000000	#040B1A	Fail
h2 İletişim	19.66:1	3.0:1	#FFFFFF	#040B1A	Pass
h2 İzel Danışman	1.07:1	3.0:1	#000000	#040B1A	Fail
h3 Kalite	1.15:1	3.0:1	#000000	#051818	Fail
h3 Projeler	1.15:1	3.0:1	#000000	#051818	Fail
h3 Masaüstü	1.07:1	3.0:1	#000000	#040B1A	Fail
h3 Eğitim	1.07:1	3.0:1	#000000	#040B1A	Fail
h3 İK	1.07:1	3.0:1	#000000	#040B1A	Fail
h3 Web	1.07:1	3.0:1	#000000	#040B1A	Fail
h3 Otomasyon	1.07:1	3.0:1	#000000	#040B1A	Fail
h3 Akademik	1.07:1	3.0:1	#000000	#040B1A	Fail
h3 Özel Çözüm	1.07:1	3.0:1	#000000	#040B1A	Fail
h3 Üretim	1.07:1	3.0:1	#000000	#040B1A	Fail
h3 Eğitim	1.07:1	3.0:1	#000000	#040B1A	Fail
h3 Danışmanlık	1.07:1	3.0:1	#000000	#040B1A	Fail
title İzel Akademi — Ge…	1.14:1	4.5:1	#000000	#041718	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.

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

1 heading(s) are too short (≤2 characters) to convey meaning

Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H3: "İK"

Got: 1 ≤2-char heading(s)

A+

Alt Text Quality

All 3 images OK

PASS

All 3 images OK

3 image(s) with good alt text

3 images 3 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 6 controls labeled

PASS

All 6 controls labeled

6 control(s) properly labeled

6 controls

6 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
bot-field	input	Boş bırakın:	none
#ad	text	Ad Soyad	for/id
#mail	email	E-posta	for/id
#konu	text	Konu	for/id
#mesaj	textarea	Mesajınız	for/id
#chatInput	textarea	Danışmana sorunuz	for/id

Link & Button Quality

33 links, 25 buttons — all OK

PASS

33 links, 25 buttons — all OK

12 link(s) open in new tab without warning

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

Got: https://www.shopier.com/izelakademi; https://www.shopier.com/izelakademi/48622633; https://www.shopier.com/izelakademi; https://www.shopier.com/izelakademi; https://www.instagram.com/izel_akademi/; https://www.linkedin.com/company/izelakademi/; https://www.facebook.com/izelakademi/; https://www.instagram.com/izel_akademi/; https://www.facebook.com/izelakademi/; https://www.linkedin.com/company/izelakademi/ (+2 more)

21 link(s) with descriptive text

33 links

0 empty

0 generic text

12 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.shopier.com/izelakademi	Mağaza ↗	new tab	Add '(opens in new tab)' to text
https://www.shopier.com/izelakademi/4862…	İncele ↗	new tab	Add '(opens in new tab)' to text
https://www.shopier.com/izelakademi	Shopier Mağazası ↗	new tab	Add '(opens in new tab)' to text
https://www.shopier.com/izelakademi	Shopier Mağazası↗	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/izel_akademi/	Instagram · @izel_akademi↗	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/izelaka…	LinkedIn · İzel Akademi↗	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/izelakademi/	Facebook · izelakademi↗	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/izel_akademi/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/izelakademi/	Facebook	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/izelaka…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.x.com/izelakademi/	X	new tab	Add '(opens in new tab)' to text
https://www.shopier.com/izelakademi	Mağaza	new tab	Add '(opens in new tab)' to text

46 links and buttons have descriptive text

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

https://www.shopier.com/izelakademi; https://www.shopier.com/izelakademi/48622633; https://www.shopier.com/izelakademi; https://www.shopier.com/izelakademi; https://www.instagram.com/izel_akademi/; https://www.linkedin.com/company/izelakademi/; https://www.facebook.com/izelakademi/; https://www.instagram.com/izel_akademi/; https://www.facebook.com/izelakademi/; https://www.linkedin.com/company/izelakademi/ (+2 more)

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

A+

Form Input Types

6 form control(s) checked, no type mismatches

PASS

6 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

6 form control(s) checked, no input-semantic issues

PASS

6 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Document Language

Lang attribute set to "tr"

PASS

Lang attribute set to "tr"

<html lang="tr"> is set and valid

Got: tr

A+

Tabindex Anti-Patterns

7 explicit tabindex attribute(s) checked, no anti-patterns

PASS

7 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

No visible text nodes measured on the page

PASS

No visible text nodes measured on the page

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

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.

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 16 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.

○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

●`[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

●`[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

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

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

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

○Buttons have an accessible name

○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

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

○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

○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

○Touch targets have sufficient size and spacing.

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