Skip to content
https://mediatek.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
43
GRADE
F
FIX
8
REVIEW
1
PASS
4
INFO
0
Checks
13
4 PASS 1 REVIEW 8 FIX
F
Heading Hierarchy
Action
127 headings, 11 skip(s)
FIX
127 headings, 11 skip(s)
Warning::
Multiple H1 headings (11 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
2 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H3 GENERATIVE AI
  • H1 Leading the next wave of edge AI
  • H3 MediaTek. skipped
  • H1 Quarterly Investor Conference duplicate H1
  • H3 IoT skipped
  • H1 MediaTek Genio Pro duplicate H1
  • H3 FLAGSHIP skipped
  • H1 MediaTek Dimensity 9500s duplicate H1
  • H3 MediaTek. skipped
  • H1 This chip changes everything. duplicate H1
  • H3 Chromebooks skipped
  • H1 MediaTekKompanio Ultra duplicate H1
  • H3 PREMIUM skipped
  • H1 MediaTek Dimensity 8500 duplicate H1
  • H3 Inside Tek skipped
  • H1 Innovation. Influence. duplicate H1
  • H3 GENERATIVE AI skipped
  • H1 Leading the next wave of edge AI duplicate H1
  • H3 MediaTek. skipped
  • H1 Quarterly Investor Conference duplicate H1
  • H5 MediaTek skipped
  • H4 Quarterly Investor Conference
  • H5 IoT
  • H4 MediaTek Genio Pro
  • H5 FLAGSHIP
  • H4 MediaTek Dimensity9500s
  • H5 MediaTek
  • H4 This chip changes everything
  • H5 Chromebooks
  • H4 MediaTekKompanio Ultra
  • H5 PREMIUM
  • H4 MediaTek Dimensity8500
  • H5 Inside Tek
  • H4 Strategic Perspectives & Insights
  • H5 GENERATIVE AI
  • H4 MediaTek NPUs empower innovative devices
  • H2 Welcome to MediaTek.
  • H2 It all starts here...with a chip.
  • H2 This chip changes everything.
  • H3 Custom Data Center
  • H4 Cutting edge. Custom made.
  • H3 PRODUCTS
  • H4 (empty)
  • H3 Smartphones
  • H4 Entry to flagship, we’ve got you covered.
  • H3 Smart Home
  • H4 This chip entertains, connects and protects.
  • H3 Networking and Connectivity
  • H4 Connecting you to what matters.
  • H3 Internet of Things
  • H4 From vision to reality.
  • H3 Tablets and Chromebook
  • H4 Powerful all-day productivity in style.
  • H3 MediaTek Dimensity Auto
  • H4 Enabling smart vehicle innovation.
  • H3 Custom Data Center
  • H4 Cutting edge. Custom made.
  • H3 PRODUCTS
  • H4 (empty)
  • H3 White Papers
  • H4 Deep dive.
  • H3 5G
  • H4 Not all 5G is created equal.
  • H3 Display
  • H4 Creating brilliant immersive experiences.
  • H3 Wi-Fi
  • H4 When we say always connected, we mean it.
  • H3 Camera
  • H4 Say cheese.
  • H3 Artificial Intelligence
  • H4 Leading the Edge-AI Technology Revolution
  • H3 HyperEngine Gaming
  • H4 Because every millisecond matters.
  • H3 White Papers
  • H4 Deep dive.
  • H3 5G
  • H4 Not all 5G is created equal.
  • H4 CORPORATE NEWS
  • H1 Brilliant technology for everyday life. duplicate H1
  • H3 One MediaTek: Evolving Our Brand for the AI Edge to Cloud Future skipped
  • H3 MediaTek named Top 100 Global Innovator by LexisNexis for 5th Consecutive Year
  • H3 MediaTek Receives ISSCC Anantha P. Chandrakasan Distinguished Technical Paper Award
  • H3 MediaTek Tops Growth in Interbrand’s Top Taiwan Brands 2025
  • H3 MediaTek Recognized in Two Prestigious Employer Awards
  • H3 Case Study: MediaTek Accelerates AI Development With an AI Factory
  • H3 ESA, MediaTek, Eutelsat, Airbus, Sharp, ITRI, and R&S Announce World’s First Rel-19 5G-Advanced NR-NTN Connection over OneWeb LEO Satellites
  • H3 MediaTek Develops Chip Utilizing TSMC’s 2nm Process
  • H3 MediaTek's NVLink Fusion Partnership: Pioneering AI Innovation with Custom ASIC
  • H4 BUSINESS & INDUSTRY NEWS
  • H2 Where innovation begins
  • H3 How MediaTek and NVIDIA are Making AI More Accessible
  • H3 NPUs, NeuroPilot and LiteRT Ready to Power Millions of AI Devices
  • H3 Transforming the Food & Beverage Industry with MediaTek Genio
  • H3 2025's Best MediaTek-powered Devices
  • H3 MediaTek First to Adopt Google’s Project Treble for Automotive Industry
  • H4 PRODUCT & TECHNOLOGY NEWS
  • H2 It all starts with a chip
  • H3 MediaTek Genio Pro 5100 Flagship-class AI & Computing Performance for IoT
  • H3 How MediaTek is Powering the Future of On-Device AI
  • H3 All-Day Power: MediaTek’s Battery Life Advantage Across Every Segment
  • H3 MediaTek Dimensity 9500s and Dimensity 8500
  • H3 Setting the Benchmark for High-Performance Computing Leadership
  • H3 MediaTek Filogic 8000 Family Pioneers the Wi-Fi 8 Ecosystem
  • H3 What Can Wi-Fi Can Do For AI?
  • H3 MediaTek Kompanio 540
  • H3 Accelerating Automotive Experiences
  • H3 World's First 15k-zone RGB mini-LED Local Dimming TV Chip
  • H4 CUSTOMERS AND PARTNERS
  • H2 Powered by MediaTek
  • H3 Case Study: Developing the Speedport 7 Broadband Gateway
  • H3 Grinn GenioBoard Powered by MediaTek Genio 700
  • H3 MediaTek and DENSO Collaborate on Automotive SoCs for Advanced Driver-Assistance Systems
  • H3 MediaTek and NTE Advance Mobile Gaming Performance
  • H3 OPPO Find X9 powered by MediaTek Dimensity 9500
  • H3 vivo X300 Series powered by MediaTek Dimensity 9500
  • H3 Samsung Galaxy Tab S11 Series powered by MediaTek Dimensity
  • H4 More on MediaTek
  • H2 Incredible starts here
  • H3 Devices powered by MediaTek
  • H3 MediaTek Podcast Central
  • H3 What's Next in Tech
  • H3 MediaTek’s Expert Insights
  • H3 Devices powered by MediaTek
  • H3 MediaTek Podcast Central
  • H3 What's Next in Tech
  • H3 MediaTek’s Expert Insights
  • H3 Join our newsletter

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

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

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
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-tzhawh
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.

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://mediatek.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://mediatek.com/manifest.json

Manifest contains invalid JSON.

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::
5 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 5 <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.
C
Lighthouse Accessibility Audits
Action
Score 71/100 — 9 failing, 23 passed
REVIEW
71

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 div.home_page_banner > div.main_home_page_slider > ul.slick-dots > li#slick-slide00
1 div.cards_slider_items > div#widget_1713777392960 > ul.slick-dots > li#slick-slide40
1 div.cards_slider_prod > div#module_17189824563813 > ul.slick-dots > li#slick-slide50
1 div.cards_slider_prod > div#module_17568825929363 > ul.slick-dots > li#slick-slide60
1 div.cards_slider_prod > div#module_17189834323413 > ul.slick-dots > li#slick-slide70
1 div.blog_cards_wrapper > div.blog_cards > ul.slick-dots > li#slick-slide30

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 2 3 4 5 6 7 8 div.home_page_wrapper > div.home_page_banner > div.main_home_page_slider > ul.slick-dots
1 2 3 4 5 6 7 8 9 div#hs_cos_wrapper_widget_1713777392960 > div.cards_slider_items > div#widget_1713777392960 > ul.slick-dots
1 2 3 4 5 div#hs_cos_wrapper_module_17189824563813 > div.cards_slider_prod > div#module_17189824563813 > ul.slick-dots
1 2 3 4 5 6 7 8 9 10 div#hs_cos_wrapper_module_17568825929363 > div.cards_slider_prod > div#module_17568825929363 > ul.slick-dots
1 2 3 4 5 6 7 div#hs_cos_wrapper_module_17189834323413 > div.cards_slider_prod > div#module_17189834323413 > ul.slick-dots
1 2 3 4 div.page-center > div.blog_cards_wrapper > div.blog_cards > ul.slick-dots

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 div.home_page_banner > div.main_home_page_slider > ul.slick-dots > li#slick-slide00
1 div.cards_slider_items > div#widget_1713777392960 > ul.slick-dots > li#slick-slide40
1 div.cards_slider_prod > div#module_17189824563813 > ul.slick-dots > li#slick-slide50
1 div.cards_slider_prod > div#module_17568825929363 > ul.slick-dots > li#slick-slide60
1 div.cards_slider_prod > div#module_17189834323413 > ul.slick-dots > li#slick-slide70
1 div.blog_cards_wrapper > div.blog_cards > ul.slick-dots > li#slick-slide30

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
GENERATIVE AI Leading the next wave of edge AI Faster, smarter generative AI c… div.home_page_banner > div.main_home_page_slider > div.slick-list > div.slick-track
MediaTek Dimensity Auto Enabling smart vehicle innovation. Scalable, highly in… div.main_tab_slid_wrap > div.main_tab_slider > div.slick-list > div.slick-track
HyperEngine Gaming Because every millisecond matters. Experience faster frame … div.main_tab_slid_wrap > div.main_tab_slider > div.slick-list > div.slick-track
CORPORATE MediaTek Develops Chip Utilizing TSMC’s 2nm Process ASIC MediaTek'… div.cards_slider_items > div#widget_1713777392960 > div.slick-list > div.slick-track
AWARDS 2025's Best MediaTek-powered Devices From smartphones to smart home de… div.cards_slider_prod > div#module_17189824563813 > div.slick-list > div.slick-track
AUTOMOTIVE Accelerating Automotive Experiences At IAA Mobility 2025, MediaTek… div.cards_slider_prod > div#module_17568825929363 > div.slick-list > div.slick-track
SMARTPHONES vivo X300 Series powered by MediaTek Dimensity 9500 DIMENSITY Sa… div.cards_slider_prod > div#module_17189834323413 > div.slick-list > div.slick-track
Devices powered by MediaTek Discover products and brands powered by MediaTek. … div.blog_cards_wrapper > div.blog_cards > div.slick-list > div.slick-track

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
Welcome to MediaTek. div.hm_tp_cont_wrap > div.page-center > div.hm_tp_main > h2
AI a > div.card_content > p.item_cat > span.AI
AI, IOT a > div.card_content > p.item_cat > span.AI,
AI, IOT a > div.card_content > p.item_cat > span.AI,
AI a > div.card_content > p.item_cat > span.AI
form#hsForm_afd29ec0-e531-4714-97fc-99bddc45f567_5730 > div.hs_submit > div.actions > input.hs-button form#hsForm_afd29ec0-e531-4714-97fc-99bddc45f567_5730 > div.hs_submit > div.actions > input.hs-button
Cookie Statement div#hs_menu_wrapper_menu2_ > ul > li.hs-menu-item > a
Terms of Use div#hs_menu_wrapper_menu2_ > ul > li.hs-menu-item > a
Privacy Policy div#hs_menu_wrapper_menu2_ > ul > li.hs-menu-item > a
Copyright © 2026 MediaTek. All rights reserved div.copyright_mobile > div#hs_cos_wrapper_rich_text > span#hs_cos_wrapper_rich_text_ > p

These are opportunities to improve the legibility of your content.

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
One MediaTek: Evolving Our Brand for the AI Edge to Cloud Future div.card_content > div.title_wrapper > div.card_title > h3

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.banner-container > div.home-slide_content > div.slid_btn > a div.banner-container > div.home-slide_content > div.slid_btn > a
div.hm_tp_main > div.hm_tp_cont > p > a div.hm_tp_main > div.hm_tp_cont > p > a
div.main_tab_slide_inner > div.slide-left > div.button_wrap > a div.main_tab_slide_inner > div.slide-left > div.button_wrap > a
div.blog-item-inner > div.blog_btm_cont > div.blog-btn > a div.blog-item-inner > div.blog_btm_cont > div.blog-btn > a
li.hs-form-booleancheckbox > label.hs-form-booleancheckbox-display > span > a li.hs-form-booleancheckbox > label.hs-form-booleancheckbox-display > span > a
div.footer_social_links > ul.social_share > div.facebook_share > a div.footer_social_links > ul.social_share > div.facebook_share > a
div.footer_social_links > ul.social_share > div.linkedin_share > a div.footer_social_links > ul.social_share > div.linkedin_share > a
div.footer_social_links > ul.social_share > div.instagram_share > a div.footer_social_links > ul.social_share > div.instagram_share > a
div.footer_social_links > ul.social_share > div.youtube_share > a div.footer_social_links > ul.social_share > div.youtube_share > a
div.footer_social_links > ul.social_share > div.threads_share > a div.footer_social_links > ul.social_share > div.threads_share > a

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.social_links > div#hs_cos_wrapper_footer_social_links > div.footer_social_links > ul.social_share div.social_links > div#hs_cos_wrapper_footer_social_links > div.footer_social_links > ul.social_share

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 div#widget_1713777392960 > ul.slick-dots > li#slick-slide40 > button
1 div.blog_cards > ul.slick-dots > li#slick-slide30 > button

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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●Form elements have associated labels
●`[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
●ARIA toggle fields have accessible names
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●Uses ARIA roles only on compatible elements
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○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 type="image">` elements have `[alt]` text
○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.
○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>`.
○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.
A
Landmark Structure
8 landmarks
PASS
8 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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 "Navigation Menu" MAIN CONTENTINFO footer

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+
Alt Text Quality
All 70 images OK
PASS
All 70 images OK
Info::
10 decorative image(s) correctly marked
Info::
60 image(s) with good alt text
70 images 60 good alt text 10 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 5 controls have issues
PASS
1 of 5 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="submit">
Info::
4 control(s) properly labeled
5 controls
4 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
termtextSearcharia-label
#firstname-afd29ec0-e531-4714-97fc-99bddc45f567_5730textEnter your name*for/id
#email-afd29ec0-e531-4714-97fc-99bddc45f567_5730emailEnter your E-mail Address*for/id
#i_agree_with_the_mediatek_privacy_policy-afd29ec0-e531-4714-97fc-99bddc45f567_5730checkboxnone
inputsubmit(none)none

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

<input type="submit">

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

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
h1 Leading the next wav…9.74:13.0:1
#000000
#FF9800
Pass
h1 Quarterly Investor C…9.74:13.0:1
#000000
#FF9800
Pass
h1 MediaTek9.74:13.0:1
#000000
#FF9800
Pass
h1 Genio Pro9.74:13.0:1
#000000
#FF9800
Pass
h1 MediaTek Dimensity9.74:13.0:1
#000000
#FF9800
Pass
h1 9500s9.74:13.0:1
#000000
#FF9800
Pass
h1 This chip changes ev…9.74:13.0:1
#000000
#FF9800
Pass
h1 MediaTek9.74:13.0:1
#000000
#FF9800
Pass
h1 Kompanio Ultra9.74:13.0:1
#000000
#FF9800
Pass
h1 MediaTek Dimensity9.74:13.0:1
#000000
#FF9800
Pass
h1 85009.74:13.0:1
#000000
#FF9800
Pass
h1 Innovation. Influenc…9.74:13.0:1
#000000
#FF9800
Pass
h1 Leading the next wav…9.74:13.0:1
#000000
#FF9800
Pass
h1 Quarterly Investor C…9.74:13.0:1
#000000
#FF9800
Pass
h1 Brilliant technology…9.74:13.0:1
#000000
#FF9800
Pass
h2 Welcome to MediaTek.9.74:13.0:1
#000000
#FF9800
Pass
h2 It all starts here..…9.74:13.0:1
#000000
#FF9800
Pass
h2 This chip changes ev…9.74:13.0:1
#000000
#FF9800
Pass
h2 Where innovation beg…9.74:13.0:1
#000000
#FF9800
Pass
h2 It all starts with a…9.74:13.0:1
#000000
#FF9800
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