Skip to content
https://timhopam.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
76
GRADE
C
FIX
6
REVIEW
5
PASS
13
INFO
0
Checks
24
13 PASS 5 REVIEW 6 FIX
D
Landmark Structure
Action
33 landmarks
FIX
33 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
8 <nav> landmark(s) found
Warning::
4 of 8 <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 (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

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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
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::
8 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 8 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="range" id="bpmRange">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="hopam-input">
2 controls
0 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#hopam-inputtext(Nhập tên bài hát... ca sĩ, nhạc sĩ...)placeholder only
#bpmRangerange(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="range" id="bpmRange">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

<input type="text" id="hopam-input">

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

B
Mobile-Readable Font Sizes
93% of visible text renders at >= 12 CSS px (16 below threshold)
REVIEW
93% of visible text renders at >= 12 CSS px (16 below threshold)
Info::
16 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 ("NHẠC SĨ"); <span> 11.0px ("NHẠC SĨ"); <span> 11.0px ("NHẠC SĨ"); <span> 11.0px ("NHẠC SĨ"); <span> 11.0px ("NHẠC SĨ").
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.

B
Lighthouse Accessibility Audits
Score 83/100 — 6 failing, 22 passed
REVIEW
83

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.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Tài khoản Đăng ký Đăng nhập div#header > div.container > div#ham-user-nav > div#ham-guest-menu

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Ballad div#content_box > section.hopam-discover > nav.hopam-rhythm-list > a.hopam-rhythm
01 ol.hopam-top-viewed > li > a.hopam-top-link > span.hopam-rank
02 ol.hopam-top-viewed > li > a.hopam-top-link > span.hopam-rank
03 ol.hopam-top-viewed > li > a.hopam-top-link > span.hopam-rank
04 ol.hopam-top-viewed > li > a.hopam-top-link > span.hopam-rank
⭐ BÀI HÁT DÀNH CHO BẠN div#content_box > section.tha-foryou > div.tha-foryou-head > h3.featured-category-title
HỢP ÂM BÀI HÁT MỚI ĐĂNG div.article > div#content_box > section.hopam-home-section > h3.featured-category-title
Duy Mạnh article.latestPost > header > div.post-info > a
Hoàng Hải article.latestPost > header > div.post-info > a
Phạm Khải Tuấn article.latestPost > header > div.post-info > a
Minh Khang article.latestPost > header > div.post-info > a
Jimmii Nguyễn article.latestPost > header > div.post-info > a
Tuno article.latestPost > header > div.post-info > a
Jimmii Nguyễn article.latestPost > header > div.post-info > a
Nhạc Ngoại article.latestPost > header > div.post-info > a
Jimmii Nguyễn article.latestPost > header > div.post-info > a
Nguyễn Đình Long article.latestPost > header > div.post-info > a
Lý Thiên Tuấn article.latestPost > header > div.post-info > a
Đạt Max article.latestPost > header > div.post-info > a
Long Họ Huỳnh article.latestPost > header > div.post-info > a
Tracy Thảo My article.latestPost > header > div.post-info > a
1.034 div.pagination-wrapper > nav.navigation > div.nav-links > a.page-numbers
Next div.pagination-wrapper > nav.navigation > div.nav-links > a.next
🎸 CA KHÚC NGẪU NHIÊN div.article > div#content_box > section.hopam-home-section > h3.featured-category-title
Hạnh Nguyễn article.latestPost > header > div.post-info > a
Nguyễn Văn Chung article.latestPost > header > div.post-info > a
Hà Thúc Sinh article.latestPost > header > div.post-info > a
Phi Bằng article.latestPost > header > div.post-info > a
Quang Dũng article.latestPost > header > div.post-info > a
thơ Yên Ninh article.latestPost > header > div.post-info > a
Thái Cơ article.latestPost > header > div.post-info > a
Xem tất cả › div#block-26 > section.tha-explore-widget > div.tha-explore-head > a#thaExploreAllLink
Nhạc sĩ section.tha-explore-widget > div.tha-explore-controls-row > div.tha-tabs-nav > button.tha-tab-btn
Ca sĩ section.tha-explore-widget > div.tha-explore-controls-row > div.tha-tabs-nav > button.tha-tab-btn
NHẠC SĨ div.tha-track > div.tha-slide-item > a.tha-artist-item > span.tha-artist-role
NHẠC SĨ div.tha-track > div.tha-slide-item > a.tha-artist-item > span.tha-artist-role
Hơn 110 sáng tác div.tha-track > div.tha-slide-item > a.tha-artist-item > span.tha-artist-count
NHẠC SĨ div.tha-track > div.tha-slide-item > a.tha-artist-item > span.tha-artist-role
Hơn 120 sáng tác div.tha-track > div.tha-slide-item > a.tha-artist-item > span.tha-artist-count
Kết nối cùng cộng đồng yêu nhạc div.th-social > div.th-social-title > div > small
Facebook/timhopam div.th-social > a.th-social-item > span.th-social-text > b
Theo dõi trang div.th-social > a.th-social-item > span.th-social-text > small
YouTube/@timhopamguitar div.th-social > a.th-social-item > span.th-social-text > b
Xem video hướng dẫn div.th-social > a.th-social-item > span.th-social-text > small
Tham gia cộng đồng yêu Guitar div.th-social > a.th-social-item > span.th-social-text > small
Bắt đầu đếm div.metro-box > div.metro-btn-row > button#btnToggle > span#btnLabel

These are opportunities to improve the legibility of your content.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.metro-wrapper > div.metro-box > div.metro-control-slider > input#bpmRange div.metro-wrapper > div.metro-box > div.metro-control-slider > input#bpmRange

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#header > div.container > div#secondary-navigation > a#pull div#header > div.container > div#secondary-navigation > a#pull

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js html.js

These items highlight common accessibility best practices.

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
NGƯỜI MỚI TẬP CHƠI aside#sidebar > div#block-16 > div.sidebar-playlist-grid > a.playlist-item
NHẠC XUÂN HAY NHẤT aside#sidebar > div#block-16 > div.sidebar-playlist-grid > a.playlist-item
TUYỆT PHẨM BOLERO aside#sidebar > div#block-16 > div.sidebar-playlist-grid > a.playlist-item
CA KHÚC HAY VỀ MẸ aside#sidebar > div#block-16 > div.sidebar-playlist-grid > a.playlist-item
TOP 100 NHẠC TRỮ TÌNH aside#sidebar > div#block-16 > div.sidebar-playlist-grid > a.playlist-item
NHẠC ĐÁM CƯỚI aside#sidebar > div#block-16 > div.sidebar-playlist-grid > a.playlist-item
○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
●`[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
●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
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
○`[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
○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
○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
○Identical links have the same purpose.
○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.
A+
Heading Hierarchy
30 headings
PASS
30 headings
Info::
Single H1 present
  • H1 HỢP ÂM GUITAR
  • H2 KHÁM PHÁ
  • H3 Bài xem nhiều nhất
  • H3 ⭐ Bài hát dành cho bạn
  • H3 Hợp âm bài hát mới đăng
  • H2 Nước mắt kẻ đa tình
  • H2 Phi trường phút biệt ly
  • H2 Để cho em ra đi
  • H2 Lãng quên chiều thu
  • H2 Mưa tuyết
  • H2 Chỉ muốn suốt đời bên em
  • H2 Chỉ muốn suốt đời cùng anh
  • H2 Đừng hỏi vì sao tôi nhớ người
  • H2 Khói thuốc đợi chờ
  • H2 Lý cầu tre
  • H2 Long đong
  • H2 Lần đầu cũng là lần cuối
  • H2 Khoác xiêm y
  • H2 Hết sẩy Miền Tây
  • H2 Phân trang bài viết
  • H3 🎸 Ca khúc ngẫu nhiên
  • H2 Mẹ của tôi
  • H2 Nỗi nhớ đóng băng
  • H2 Đừng chết nhé ta ơi
  • H2 Còn mãi tình anh
  • H2 Thương lắm cha ơi!
  • H2 Qua bến đò Quan
  • H3 Nghệ Sĩ Việt
  • H3 Bài Viết Mới
  • H3 Máy đếm nhịp (Metronome)
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
2 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: 2 all-caps heading(s)
A+
Alt Text Quality
All 47 images OK
PASS
All 47 images OK
Info::
47 image(s) with good alt text
47 images 47 good alt text
All images have appropriate alt text.
A+
Form Input Types
2 form control(s) checked, no type mismatches
PASS
2 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 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 "vi"
PASS
Lang attribute set to "vi"
Info::
<html lang="vi"> is set and valid
Got: vi
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+
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
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+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 KHÁM PHÁ20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Phân trang bài vi…20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Bài xem nhiều nh…20.82:13.0:1
#000000
#FEFEFE
Pass
h3 ⭐ Bài hát dành …20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Hợp âm bài hát …20.82:13.0:1
#000000
#FEFEFE
Pass
h3 🎸 Ca khúc ngẫu…20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Nghệ Sĩ Việt20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Bài Viết Mới20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Máy đếm nhịp (…20.82:13.0:1
#000000
#FEFEFE
Pass
title Danh sách hợp âm…21.00:14.5:1
#000000
#FFFFFF
Pass
a HỢP ÂM GUITAR21.00:14.5:1
#000000
#FFFFFF
Pass
a Giới thiệu21.00:14.5:1
#000000
#FFFFFF
Pass
a Thể Loại21.00:14.5:1
#000000
#FFFFFF
Pass
a Nhạc Trẻ21.00:14.5:1
#000000
#FFFFFF
Pass
a Nhạc Đỏ21.00:14.5:1
#000000
#FFFFFF
Pass
a Nhạc Vàng21.00:14.5:1
#000000
#FFFFFF
Pass
a Nhạc Học Trò21.00:14.5:1
#000000
#FFFFFF
Pass
a Nhạc Trữ Tình21.00:14.5:1
#000000
#FFFFFF
Pass
a Nhạc Quê Hương21.00:14.5:1
#000000
#FFFFFF
Pass
a Nhạc Thiếu Nhi21.00:14.5:1
#000000
#FFFFFF
Pass

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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback