Skip to content
https://nyazd.ir

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
73
GRADE
C
FIX
6
REVIEW
7
PASS
11
INFO
0
Checks
24
11 PASS 7 REVIEW 6 FIX
D
Heading Hierarchy
Action
78 headings, 4 skip(s)
FIX
78 headings, 4 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H6 (missing H2)
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 → H6 (missing H4)
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 نوآوران یزد – مرکز آموزش علمی و کاربردی
  • H6 ◆درباره مرکز skipped
  • H6 ◆ساختار
  • H6 ◆دپارتمان‌ها
  • H6 ◆اطلاعات عمومی
  • H5 مرکز نوآوران یزد، پیشرو در آموزش علمی و کاربردی
  • H6 ◆مقاطع
  • H6 ◆گروه‌های آموزشی
  • H6 ◆امور آموزشی
  • H6 ◆پژوهش
  • H6 ◆دوره‌های آزاد
  • H6 ◆انتشارات علمی
  • H5 ثبت‌نام تا ۳۰ مهر ماه
  • H6 ◆خدمات دانشجویی
  • H6 ◆رفاه دانشجویی
  • H6 ◆فرهنگی و اجتماعی
  • H6 ◆بهداشت و سلامت
  • H6 ◆ورزش
  • H6 ◆مسیرنـــو
  • H5 در کنار دانش‌آموختگان نوآوران
  • H6 ◆خبر و اطلاعیه
  • H6 ◆تقویم فعال
  • H6 ◆چند رسانه ای
  • H5 خبرنامه
  • H5 گالری تصاویر و آرشیو کامل
  • H6 ◆سامانه‌های آموزشی
  • H6 ◆سامانه‌های اداری
  • H6 ◆منابع
  • H6 ◆پشتیبانی
  • H5 کارشناسان ما آماده پاسخگویی هستند
  • H2 فصل تازه‌ آغاز شد
  • H4 سازمان سنجش skipped
  • H4 علمی و کاربردی
  • H4 علمی و کاربردی
  • H4 هم آوا
  • H4 چارگون
  • H4 آموزش مجازی
  • H3 آخرین اخبار و رویدادهای نوآوران
  • H4 اخبار و اطلاعیه‌ها
  • H4 گروه درس اخلاق حرفه‌ای
  • H5 اطلاعیه برنامه کلاسی
  • H5 اطلاعیه برنامه کلاسی
  • H5 سایت سازمان سنجش
  • H4 رویدادهای پیش‌رو
  • H5 راه‌اندازی وب‌سایت نوآوران
  • H6 گرامیداشت هفته انتظامی
  • H3 رشته‌ها و دوره‌های مرکز نوآوران
  • H4 رشته‌های تحصیلی
  • H4 آخرین دوره‌ها
  • H3 پادکست‌های مرکز نوآوران
  • H6 آینده آموزش عالی در ایران و جهان skipped
  • H6 کارآفرینی دانشجویی
  • H6 مسیر تحصیل در خارج از کشور
  • H6 مهارت‌های نرم برای دانشجویان
  • H3 جامعه مرکز آموزش نوآوران
  • H4 اعضای علمی و مدیریتی
  • H5 ابوالفضل قطب الدینی
  • H5 ابوالفضل قطب الدینی
  • H5 ابوالفضل قطب الدینی
  • H4 انجمن‌ها و گروه‌ها
  • H4 انجمن علمی دانشجویی
  • H4 گروه ورزشی
  • H4 انجمن فرهنگی هنری
  • H4 انجمن پژوهش‌های علمی
  • H5 تفاهم‌نامه‌ها
  • H3 گالری تصاویر و ویدیوها
  • H5 برگزاری کلاس حضوری ترم مهرماه ۱۴۰۵ skipped
  • H5 به مناسبت هفته دفاع مقدس و روز سرباز
  • H5 آغاز سال تحصیلی جدید
  • H5 منزل شهید والامقام جواد زارعی
  • H5 شورای هم‌اندیشی رؤسای مراکز آموزش علمی‌کاربردی استان یزد
  • H3 آماده‌اید مسیر آینده خود را روشن کنیم؟
  • H4 مرکز آموزش علمی و کاربردی نوآوران
  • H5 دسترسی سریع
  • H5 پشتیبانی
  • H5 خبرنامه
  • H4 مشاوره نوآوران
  • H2 چه چیزی را می‌خواهید پیدا کنید؟

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

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

D
Mobile-Readable Font Sizes
Action
35% of visible text renders at >= 12 CSS px (60 below threshold)
FIX
35% of visible text renders at >= 12 CSS px (60 below threshold)
Warning::
60 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.5px ("یکشنبه، ۱۹ مهر ۱۴۰۵"); <span> 11.0px ("سایت سازمان سنجش"); <span> 11.5px ("نقشه سایت"); <span> 10.5px ("فارسی"); <span> 10.5px ("EN").
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::
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
2 landmarks
REVIEW
2 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) 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 MAIN CONTENTINFO (missing!)

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
Form Accessibility
6 of 12 controls have issues
REVIEW
6 of 12 controls have issues
Warning::
6 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="tel">; <input type="password">; <input type="tel">; <input type="text">; <input type="email">; <input type="search" name="s" id="nyazdSearchInput">
Info::
6 control(s) properly labeled
12 controls
6 labeled
6 placeholder only
0 unlabeled
ControlTypeLabelMethod
#cnf-nametextنام و نام خانوادگی *for/id
#cnf-phonetelشماره همراه *for/id
#cnf-emailemailایمیل (اختیاری)for/id
#cnf-deptselectواحد مربوطه *for/id
#cnf-subjecttextموضوعfor/id
#cnf-messagetextareaمتن پیام *for/id
inputpassword(رمز عبور)placeholder only
inputtel(۰۹۱۲۳۴۵۶۷۸۹)placeholder only
inputtext(کد ۶ رقمی)placeholder only
inputemail(ایمیل شما...)placeholder only
inputtel(شماره تلفن همراه)placeholder only
#nyazdSearchInputsearch(مثلاً: دوره برنامه‌نویسی، اساتید، اخبار...)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="tel">; <input type="password">; <input type="tel">; <input type="text">; <input type="email">; <input type="search" name="s" id="nyazdSearchInput">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

C
Mobile Keyboard & Autofill
Action
8/12 eligible field(s) missing autocomplete or inputmode
REVIEW
8/12 eligible field(s) missing autocomplete or inputmode
Warning::
4 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: tel, current-password, email.
Got: <input type="tel">, <input type="password">, <input type="tel">, <input type="email">
Warning::
4 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: tel, email, search.
Got: <input type="tel">, <input type="email">, <input type="email" name="email" id="cnf-email">, <input type="search" name="s" id="nyazdSearchInput">
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
h1 نوآوران یزد – مرکز آم…
1.41:1
#000000
on
#192646
needs 3.0:1 (large text)
32px · above the fold
h2 فصل تازه‌ آغاز شد
1.19:1
#000000
on
#0E182F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 چه چیزی را می‌خواهید …
1.19:1
#000000
on
#0E182F
needs 3.0:1 (large text)
24px · bottom of viewport
h3 آخرین اخبار و رویداده…
1.19:1
#000000
on
#0E182F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 رشته‌ها و دوره‌های م…
1.19:1
#000000
on
#0E182F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 پادکست‌های مرکز نوآو…
1.19:1
#000000
on
#0E182F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 جامعه مرکز آموزش نوآو…
1.19:1
#000000
on
#0E182F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 گالری تصاویر و ویدیوه…
1.19:1
#000000
on
#0E182F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 آماده‌اید مسیر
1.19:1
#000000
on
#0E182F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 خود را روشن کنیم؟
1.19:1
#000000
on
#0E182F
needs 3.0:1 (large text)
19px · bottom of viewport
title نوآوران یزد - مرکز آمو…
1.39:1
#000000
on
#182547
needs 4.5:1 (normal text)
16px · top of page (header area)
span ۸۰
1.20:1
#000000
on
#0E1932
needs 4.5:1 (normal text)
16px · top of page (header area)
div در حال بارگذاری
1.21:1
#000000
on
#0F1933
needs 4.5:1 (normal text)
16px · top of page (header area)
span یکشنبه، ۱۹ مهر ۱۴۰۵
1.35:1
#000000
on
#152342
needs 4.5:1 (normal text)
16px · top of page (header area)
span آخرین
1.35:1
#000000
on
#152343
needs 4.5:1 (normal text)
16px · above the fold
span گروه درس اخلاق حرفه‌ا…
1.36:1
#000000
on
#162344
needs 4.5:1 (normal text)
16px · above the fold
span نقشه سایت
1.37:1
#000000
on
#172445
needs 4.5:1 (normal text)
16px · above the fold
span فارسی
1.37:1
#000000
on
#172445
needs 4.5:1 (normal text)
16px · above the fold
span صفحه اصلی
1.43:1
#000000
on
#192748
needs 4.5:1 (normal text)
16px · above the fold
span درباره ما
1.44:1
#000000
on
#1A2849
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 نوآوران یز…1.41:13.0:1
#000000
#192646
Fail
h2 فصل تازه‌ …1.19:13.0:1
#000000
#0E182F
Fail
h2 چه چیزی را …1.19:13.0:1
#000000
#0E182F
Fail
h3 آخرین اخبا…1.19:13.0:1
#000000
#0E182F
Fail
h3 رشته‌ها و …1.19:13.0:1
#000000
#0E182F
Fail
h3 پادکست‌ها…1.19:13.0:1
#000000
#0E182F
Fail
h3 جامعه مرکز …1.19:13.0:1
#000000
#0E182F
Fail
h3 گالری تصاو…1.19:13.0:1
#000000
#0E182F
Fail
h3 آماده‌اید …1.19:13.0:1
#000000
#0E182F
Fail
h3 خود را روشن…1.19:13.0:1
#000000
#0E182F
Fail
title نوآوران یز…1.39:14.5:1
#000000
#182547
Fail
span ۸۰1.20:14.5:1
#000000
#0E1932
Fail
div در حال بارگ…1.21:14.5:1
#000000
#0F1933
Fail
span یکشنبه، ۱۹ …1.35:14.5:1
#000000
#152342
Fail
span آخرین1.35:14.5:1
#000000
#152343
Fail
span گروه درس اخ…1.36:14.5:1
#000000
#162344
Fail
span نقشه سایت1.37:14.5:1
#000000
#172445
Fail
span فارسی1.37:14.5:1
#000000
#172445
Fail
span صفحه اصلی1.43:14.5:1
#000000
#192748
Fail
span درباره ما1.44:14.5:1
#000000
#1A2849
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::
78 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: 78 all-caps heading(s)
A+
Alt Text Quality
All 12 images OK
PASS
All 12 images OK
Info::
12 image(s) with good alt text
12 images 12 good alt text
All images have appropriate alt text.
A+
Form Input Types
12 form control(s) checked, no type mismatches
PASS
12 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A
Form Input Quality
1 input-semantic issue(s) across 12 form control(s)
PASS
1 input-semantic issue(s) across 12 form control(s)
Info::
1 password field(s) missing or with invalid `autocomplete`
Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password">.
A+
Document Language
Lang attribute set to "fa-IR"
PASS
Lang attribute set to "fa-IR"
Info::
<html lang="fa-IR"> is set and valid
Got: fa-IR
A+
Tabindex Anti-Patterns
0 positive, 1 -1-on-focusable
PASS
0 positive, 1 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <input>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
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+
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 92/100 — 2 failing, 20 passed
PASS
92

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.podcast-grid > div.player-card > div.player-controls > button.pc-btn div.podcast-grid > div.player-card > div.player-controls > button.pc-btn
div.podcast-grid > div.player-card > div.player-controls > button.pc-btn div.podcast-grid > div.player-card > div.player-controls > button.pc-btn
div.podcast-grid > div.player-card > div.player-controls > button.pc-btn div.podcast-grid > div.player-card > div.player-controls > button.pc-btn

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
سازمان سنجش div.systems-grid > a.sys-card > div.sys-info > h4
آینده آموزش عالی در ایران و جهان div.playlist > a.playlist-item > div.pl-info > h6
برگزاری کلاس حضوری ترم مهرماه ۱۴۰۵ div#sceneGalleryGrid > a.gal-item > div.gal-content > h5

These are opportunities to improve keyboard navigation in your application.

○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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●`[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
●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
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○`[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
○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
○Form elements have associated labels
○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.
○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.
○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