gsmarena.com Accessibility Report

Accessibility audit of gsmarena.com — scanned on Feb 20, 2026

Technology
0 /100
D Poor

6 issues found across 3 categories

3 Critical 2 Major 1 Minor

WCAG Compliance Overview

Perceivable 3 issues
Operable 2 issues
Understandable 0 issues
Robust 1 issues

Issues Found

Images missing alt text

Critical

Images must have alternative text to convey their meaning to screen reader users.

WCAG 1.1.1
18 element(s) affected
  • <img src="https://fdn2.gsmarena.com/vv/bigpic/vivo-v70.jpg">
  • <img src="https://fdn2.gsmarena.com/vv/bigpic/infinix-note60-pro.jpg">
  • <img src="https://fdn2.gsmarena.com/vv/bigpic/google-pixel-10a.jpg">
  • <img src="https://fdn2.gsmarena.com/vv/bigpic/tecno-camon-50-pro-4g.jpg">
  • <img src="https://fdn2.gsmarena.com/vv/bigpic/vivo-v70-elite.jpg">
How to fix

Add descriptive alt attributes to all <img> elements. Use alt="" for decorative images.

Links missing accessible name

Critical

Links must have discernible text so screen reader users understand their purpose.

WCAG 2.4.4
9 element(s) affected
  • <a href="samsung_officially_reveals_the_upgraded_bixby_in_one_ui_85-news-71644.php">
  • <a href="realme_p4_lite_features_price_sale_date-news-71643.php">
  • <a href="vivo_v70_in_for_review-news-71632.php">
  • <a href="newscomm-71649.php">
  • <a href="newscomm-71650.php">
How to fix

Add text content, aria-label, or aria-labelledby to links. Avoid empty <a> tags.

Form inputs missing labels

Critical

Form elements must have associated labels so users know what information to enter.

WCAG 1.3.1
2 element(s) affected
  • <input type="text" name="sSearch">
  • <input type="Hidden" name="sSource">
How to fix

Add <label> elements with matching for attributes, or use aria-label.

Duplicate element IDs

Major

Element IDs must be unique to ensure correct assistive technology behavior.

WCAG 4.1.1
3 element(s) affected
  • id="th3a"
  • id="th3b"
  • id="th3c"
How to fix

Make each id attribute value unique within the page.

Positive tabindex values

Major

Elements with tabindex > 0 disrupt natural tab order and confuse keyboard users.

WCAG 2.4.3
1 element(s) affected
  • <input tabindex="201">
How to fix

Remove positive tabindex values. Use tabindex="0" or tabindex="-1" only.

Invalid autocomplete values

Minor

Form fields with autocomplete must use valid token values.

WCAG 1.3.5
2 element(s) affected
  • <input name="sEmail" autocomplete="false">
  • <input name="sPassword" autocomplete="false">
How to fix

Use standard autocomplete values like 'name', 'email', 'tel', 'address-line1', etc.

Top Priority Fixes

Here are the most impactful changes gsmarena.com should make to improve accessibility:

  1. #1
    Images missing alt text Critical

    Add descriptive alt attributes to all <img> elements. Use alt="" for decorative images.

  2. #2
    Links missing accessible name Critical

    Add text content, aria-label, or aria-labelledby to links. Avoid empty <a> tags.

  3. #3
    Form inputs missing labels Critical

    Add <label> elements with matching for attributes, or use aria-label.

Frequently Asked Questions

Is gsmarena.com accessible?

gsmarena.com scored 36/100 (grade D) on our accessibility audit. This score reflects automated checks against WCAG 2.1 Level AA criteria.

Is gsmarena.com WCAG compliant?

Our scan found 6 accessibility issues on gsmarena.com. Full WCAG compliance requires addressing all critical and major issues identified above.

Is gsmarena.com EAA compliant?

The European Accessibility Act requires websites to meet WCAG 2.1 AA standards. Check the detailed report above to see gsmarena.com's compliance status.

What accessibility issues does gsmarena.com have?

See the full issue list above with severity levels, affected elements, and recommended fixes for gsmarena.com.

Scan Your Own Website

Get a free accessibility report for your website in seconds.

Scan Your Website Free View Pricing