Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

17 PASS 3 REVIEW 4 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-y0adhw

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

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

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

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

Mobile-Readable Font Sizes

Action

73% of visible text renders at >= 12 CSS px (12 below threshold)

REVIEW

73% of visible text renders at >= 12 CSS px (12 below threshold)

12 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> 10.6px ("شماره تماس 09128855288"); <span> 10.6px ("ارسال در تهران"); <span> 10.6px ("fff888 یففاثیا"); <p> 10.6px ("بدون عکس"); <p> 10.6px ("بدون عکس").

Favicon & Branding

Action

6 icon(s) detected

REVIEW

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

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

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

h1 fff888 شثفا

1.47:1

#000000

#272B2D

needs 3.0:1 (large text)

32px · above the fold

h2 فروشگاه اینترنتی - صفح…

1.53:1

#000000

#2B2E2F

needs 3.0:1 (large text)

24px · above the fold

h2 دسته‌بندی‌ها

1.37:1

#000000

#202628

needs 3.0:1 (large text)

24px · mid-page

h2 کوکی‌ها

1.66:1

#000000

#333333

needs 3.0:1 (large text)

24px · bottom of viewport

h3 تاج گل سه طبقه

1.26:1

#000000

#181F23

needs 3.0:1 (large text)

19px · mid-page

h3 گرد صورتی

1.17:1

#000000

#10181C

needs 3.0:1 (large text)

19px · mid-page

h3 تاج گل یک طبقه

1.66:1

#000000

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 تاج گل دو طبقه

1.66:1

#000000

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 تاج گل گرد

1.66:1

#000000

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 دسترسی سریع

1.66:1

#000000

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 نمادهای اعتماد

1.66:1

#000000

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 تماس با ما

1.66:1

#000000

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

title فروشگاه اینترنتی گلسا…

1.61:1

#000000

#303132

needs 4.5:1 (normal text)

16px · top of page (header area)

a پرش به محتوای اصلی

1.66:1

#000000

#333333

needs 4.5:1 (normal text)

16px · top of page (header area)

span شماره تماس 09128855288

1.66:1

#000000

#333333

needs 4.5:1 (normal text)

16px · top of page (header area)

span ارسال در تهران

1.66:1

#000000

#323333

needs 4.5:1 (normal text)

16px · top of page (header area)

span گلسا پلاس

1.63:1

#000000

#313232

needs 4.5:1 (normal text)

16px · above the fold

button همه محصولات

1.61:1

#000000

#303132

needs 4.5:1 (normal text)

16px · above the fold

a تماس با ما

1.59:1

#000000

#2F3031

needs 4.5:1 (normal text)

16px · above the fold

a ورود

1.56:1

#000000

#2D2F30

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 fff888 شثفا	1.47:1	3.0:1	#000000	#272B2D	Fail
h2 فروشگاه ای�…	1.53:1	3.0:1	#000000	#2B2E2F	Fail
h2 دسته‌بندی�…	1.37:1	3.0:1	#000000	#202628	Fail
h2 کوکی‌ها	1.66:1	3.0:1	#000000	#333333	Fail
h3 تاج گل سه ط�…	1.26:1	3.0:1	#000000	#181F23	Fail
h3 گرد صورتی	1.17:1	3.0:1	#000000	#10181C	Fail
h3 تاج گل یک ط�…	1.66:1	3.0:1	#000000	#333333	Fail
h3 تاج گل دو ط�…	1.66:1	3.0:1	#000000	#333333	Fail
h3 تاج گل گرد	1.66:1	3.0:1	#000000	#333333	Fail
h3 دسترسی سری�…	1.66:1	3.0:1	#000000	#333333	Fail
h3 نمادهای اع�…	1.66:1	3.0:1	#000000	#333333	Fail
h3 تماس با ما	1.66:1	3.0:1	#000000	#333333	Fail
title فروشگاه ای�…	1.61:1	4.5:1	#000000	#303132	Fail
a پرش به محتو…	1.66:1	4.5:1	#000000	#333333	Fail
span شماره تماس …	1.66:1	4.5:1	#000000	#333333	Fail
span ارسال در ته…	1.66:1	4.5:1	#000000	#323333	Fail
span گلسا پلاس	1.63:1	4.5:1	#000000	#313232	Fail
button همه محصولا�…	1.61:1	4.5:1	#000000	#303132	Fail
a تماس با ما	1.59:1	4.5:1	#000000	#2F3031	Fail
a ورود	1.56:1	4.5:1	#000000	#2D2F30	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.

Landmark Structure

6 landmarks

PASS

6 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

12 headings

PASS

12 headings

Single H1 present

1 hidden heading(s) (aria-hidden)

H2 فروشگاه اینترنتی - صفحه اصلی hidden
H1 fff888 شثفاfff888
H2 دسته‌بندی‌ها
H3 تاج گل سه طبقه
H3 گرد صورتی
H3 تاج گل یک طبقه
H3 تاج گل دو طبقه
H3 تاج گل گرد
H3 دسترسی سریع
H3 نمادهای اعتماد
H3 تماس با ما
H2 کوکی‌ها

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

11 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: 11 all-caps heading(s)

A+

Alt Text Quality

All 7 images OK

PASS

All 7 images OK

7 image(s) with good alt text

7 images 7 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
input	text	فیلد جستجو	aria-label

Link & Button Quality

21 links, 8 buttons — all OK

PASS

21 links, 8 buttons — all OK

9 link(s) open in new tab without warning

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

Got: https://golsaplus.ir/; https://golsaplus.ir/; https://golsaplus.ir/; https://golsaplus.ir/; https://golsaplus.ir/; https://golsaplus.ir/contact; https://golsaplus.ir/about; https://golsaplus.ir/faq; https://golsaplus.ir/terms

12 link(s) with descriptive text

21 links

0 empty

0 generic text

9 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://golsaplus.ir/	روبیکا	new tab	Add '(opens in new tab)' to text
https://golsaplus.ir/	بله	new tab	Add '(opens in new tab)' to text
https://golsaplus.ir/	ایتا	new tab	Add '(opens in new tab)' to text
https://golsaplus.ir/	اینستاگرام	new tab	Add '(opens in new tab)' to text
https://golsaplus.ir/	تلگرام	new tab	Add '(opens in new tab)' to text
https://golsaplus.ir/contact	تماس با ما	new tab	Add '(opens in new tab)' to text
https://golsaplus.ir/about	درباره ما	new tab	Add '(opens in new tab)' to text
https://golsaplus.ir/faq	سوالات متداول	new tab	Add '(opens in new tab)' to text
https://golsaplus.ir/terms	شرایط و قوانین	new tab	Add '(opens in new tab)' to text

20 links and buttons have descriptive text

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

https://golsaplus.ir/; https://golsaplus.ir/; https://golsaplus.ir/; https://golsaplus.ir/; https://golsaplus.ir/; https://golsaplus.ir/contact; https://golsaplus.ir/about; https://golsaplus.ir/faq; https://golsaplus.ir/terms

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

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "fa"

PASS

Lang attribute set to "fa"

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

Got: fa

A+

Tabindex Anti-Patterns

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

PASS

6 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+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: گلسا پلاس - فروشگاه اینترنتی

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name گلسا پلاس - فروشگاه اینترنتی ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name گلسا پلاس - فروشگاه اینترنتی Display Mode standalone Theme Color #0EA5E9 Background Color #ffffff Icons 5 icon(s)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

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

Lighthouse Accessibility Audits

Score 90/100 — 2 failing, 20 passed

PASS

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
شماره تماس 09128855288 `div.flex > div.flex > a > span`
ورود `div.container > div.flex > div.flex > a.inline-flex`
fff888 یففاثیا `div.grid > div.space-y-8 > div > span.whitespace-nowrap`

These are opportunities to improve the legibility of your content.

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`

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-*]` 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

●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

●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>`).

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

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

○Links have a discernible name

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

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