Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7643599
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 31, 20262026-05-31T09:29:20+00:00 2026-05-31T09:29:20+00:00

I get an warning about [Accessibility]Missing contentDescription attribute on image in eclipse. This warning

  • 0

I get an warning about [Accessibility]Missing contentDescription attribute on image in eclipse. This warning show at line 5 (declare ImageView) in XML code below.

This not make any error when build and run my application. But I really want to know why i get this warning.

This is my XML file:

<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
              android:layout_width="fill_parent"
              android:layout_height="wrap_content">
    <ImageView
        android:id="@+id/contact_entry_image"
        android:src="@drawable/ic_launcher"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        />
    <TextView
        android:id="@+id/contact_entry_text"
        android:text=""
        android:layout_width="fill_parent"
        android:layout_height="wrap_content"
        android:textSize="30sp"
        />

</LinearLayout>

Please help me regarding this and thanks for your reading.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-31T09:29:21+00:00Added an answer on May 31, 2026 at 9:29 am

    Follow this link for solution: Android Lint contentDescription warning

    Resolved this warning by setting attribute android:contentDescription
    for my ImageView

    android:contentDescription="@string/desc"

    Android Lint support in ADT 16 throws this warning to ensure that
    image widgets provide a contentDescription

    This defines text that briefly describes the content of the view. This
    property is used primarily for accessibility. Since some views do not
    have textual representation this attribute can be used for providing
    such.

    Non-textual widgets like ImageViews and ImageButtons should use the
    contentDescription attribute to specify a textual description of the
    widget such that screen readers and other accessibility tools can
    adequately describe the user interface.

    This link for explanation: Accessibility, It’s Impact and Development Resources

    Many Android users have disabilities that require them to interact
    with their Android devices in different ways. These include users who
    have visual, physical or age-related disabilities that prevent them
    from fully seeing or using a touchscreen.

    Android provides accessibility features and services for helping these
    users navigate their devices more easily, including text-to-speech,
    haptic feedback, trackball and D-pad navigation that augments their
    experience. Android application developers can take advantage of these
    services to make their applications more accessible and also build
    their own accessibility services.

    This guide is for making your app accessible: Making Apps More Accessible

    Making sure your application is accessible to all users is relatively
    easy, particularly when you use framework-provided user interface
    components. If you only use these standard components for your
    application, there are just a few steps required to ensure your
    application is accessible:

    1. Label your ImageButton, ImageView, EditText, CheckBox and other user
      interface controls using the android:contentDescription attribute.

    2. Make all of your user interface elements accessible with a directional
      controller, such as a trackball or D-pad.

    3. Test your application by turning on accessibility services like TalkBack
      and Explore by Touch,
      and try using your application using only directional controls.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I cant understand what this warning I get on Xcode is about. Searching for
I get a warning about unchecked casts on the return (T) value; line. Is
For public members I get a warning missing XML comment for publicly visible type
I am wondering about a warning I get in my strings.xml file. The very
I get the warning childNodes is null or not an object' with different line
I get this warning from GCC: warning: cannot pass objects of non-POD type 'class
The exact warning I get is warning C4715: 'hand::show' : not all control paths
I get this: Warning: session_start(): Cannot send session cookie - headers already sent by
I know this is wrong and gcc will give you a warning about it,
I want to have the following method not show a warning about using raw

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.