Skip to content
https://hasanaga.com.tr

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
82
GRADE
B
FIX
4
REVIEW
6
PASS
14
INFO
0
Checks
24
14 PASS 6 REVIEW 4 FIX
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::
2 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 2 <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.
B
Landmark Structure
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <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 CONTENTINFO footer

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

B
Iframe Accessibility
2/3 iframe(s) missing title; 0 placeholder(s)
REVIEW
2/3 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://www.google.com/recaptcha/api2/aframe")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://googleads.g.doubleclick.net/pagead/html/r20261116/r20190131/zrt_lookup.…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
C
Mobile-Readable Font Sizes
Action
85% of visible text renders at >= 12 CSS px (5 below threshold)
REVIEW
85% of visible text renders at >= 12 CSS px (5 below threshold)
Warning::
5 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: <span> 11.0px ("Bursa • Nilüfer"); <div> 11.0px ("Bursa • Nilüfer"); <span> 11.0px ("GÜNCEL"); <span> 11.0px ("FOTOĞRAFLAR"); <span> 11.0px ("İNTERAKTİF").
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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found - Hasanağa ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 10 fail WCAG AA
REVIEW

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

10 pass 10 fail WCAG AA 1 pass AA only
a Ana Sayfa
2.39:1
#000000
on
#3A4D5B
needs 4.5:1 (normal text)
16px · top of page (header area)
span Rehber ▾
1.98:1
#000000
on
#3B3F44
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Hasanağa Hakkında
2.07:1
#000000
on
#3C4342
needs 4.5:1 (normal text)
16px · above the fold
a Doğa & Baraj
1.92:1
#000000
on
#383E3D
needs 4.5:1 (normal text)
16px · above the fold
a Haberler
3.06:1
#000000
on
#585B5B
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Köy Albümü
3.99:1
#000000
on
#6F6B6A
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Günün fotoğrafının nerede çekildiÄ…
3.57:1
#000000
on
#676461
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Türkçe Kelime Oyunu
2.29:1
#000000
on
#49474D
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Günün 5 harfli kelimesini tahmin edin …
1.57:1
#000000
on
#2D302B
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
a İletişim
2.05:1
#000000
on
#404234
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient

7 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 Yaşadığımız Yer…20.24:13.0:1
#000000
#FAFBFA
Pass
h2 Hasanağa’ya Dair …20.24:13.0:1
#000000
#FAFBFA
Pass
h3 Haberler ve Duyurula…20.24:13.0:1
#000000
#FAFBFA
Pass
h3 Köy Albümü20.24:13.0:1
#000000
#FAFBFA
Pass
h3 Hasanağa Konum Tahm…20.24:13.0:1
#000000
#FAFBFA
Pass
title Ana Sayfa - Hasanağ…21.00:14.5:1
#000000
#FFFFFF
Pass
div Hasanağa21.00:14.5:1
#000000
#FFFFFF
Pass
span Bursa • Nilüfer11.60:14.5:1
#000000
#BCC1C8
Pass
a Ana Sayfa2.39:14.5:1
#000000
#3A4D5B
Fail
span Rehber ▾1.98:14.5:1
#000000
#3B3F44
Fail
a Hasanağa Hakkında2.07:14.5:1
#000000
#3C4342
Fail
a Doğa & Baraj1.92:14.5:1
#000000
#383E3D
Fail
a Haberler3.06:14.5:1
#000000
#585B5B
Fail
a Köy Albümü3.99:14.5:1
#000000
#6F6B6A
Fail
span Oyunlar ▾7.06:14.5:1
#000000
#999685
Pass
span Hasanağa Konum Tahm…6.73:14.5:1
#000000
#93928C
Pass
span Günün fotoğrafın…3.57:14.5:1
#000000
#676461
Fail
span Türkçe Kelime Oyun…2.29:14.5:1
#000000
#49474D
Fail
span Günün 5 harfli kel…1.57:14.5:1
#000000
#2D302B
Fail
a İletişim2.05:14.5:1
#000000
#404234
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 Hierarchy
5 headings
PASS
5 headings
Info::
Single H1 present
  • H1 Yaşadığımız Yer, Ortak Hikâyemiz.
  • H2 Hasanağa’ya Dair Her Şey
  • H3 Haberler ve Duyurular
  • H3 Köy Albümü
  • H3 Hasanağa Konum Tahmini
A+
Heading Text Quality
All 5 heading(s) have substantive, well-formed text
PASS
All 5 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
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
1 explicit tabindex attribute(s) checked, no anti-patterns
PASS
1 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
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+
Mobile UX Depth
2 mobile-depth signal(s) detected
PASS
2 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.
Info::
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 91/100 — 1 failing, 10 passed
PASS
91

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
BÖLÜM VE BAŞLIKLAR main > section.section-wrap > div.section-head > span.section-eyebrow
Haberleri İncele → section.section-wrap > div.cards-grid > article.feature-card > a.card-link
Fotoğrafları İncele → section.section-wrap > div.cards-grid > article.feature-card > a.card-link
Oyuna Git → section.section-wrap > div.cards-grid > article.feature-card > a.card-link

These are opportunities to improve the legibility of your content.

○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>`
●Buttons have an accessible name
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
○`[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-hidden="true"]` elements do not contain focusable descendents
○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
○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.
○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.
○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>`.
○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