Skip to content

Conversation

@mercy-orejo
Copy link

@mercy-orejo mercy-orejo commented Oct 28, 2025

Hi @YvoneAtienoOnyango

Title Image Alt Missing
Task Category Image Alt Missing
Content Task Link/Mail Screenshot
UX task NA
Hotfix #727
Ticket/Task link https://dev.azure.com/Syncfusion-Infrastructure/Syncfusion%20SEO/_workitems/edit/210696
Excel/SharePoint link
Changes made Reason for changes
Image Alt Missing According to SEO image should have image ALT text

Regards,
Mercy A.

@SyncfusionBuild
Copy link
Contributor

Your pull request has been created. Syncfusion support team will validate this commit and publish your changes accordingly.

@SyncfusionBuild
Copy link
Contributor

Your pull request has been created. Syncfusion support team will validate this commit and publish your changes accordingly.

@SyncfusionBuild
Copy link
Contributor

Your pull request has been created. Syncfusion support team will validate this commit and publish your changes accordingly.

Copy link
Collaborator

@ChristoIssac ChristoIssac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The alt text additions are a good idea for accessibility, but several of the strings have grammar and consistency issues and could be made shorter and clearer. I recommend using consistent wording, correct verb agreement, and a standard way to indicate case-sensitivity (for example: "(case-sensitive)"). Also avoid repeating "in Xamarin.Android ComboBox" in every alt text if the page already makes that clear.

Problems I found

Subject/verb agreement: e.g., "Words that contains" should be "Words that contain".
Awkward phrasing: "Starting letter with case sensitive", "Ending word with input text" sound unnatural.
Inconsistent casing and punctuation: some end with a period, some do not.
Repetition: every alt repeats "in Xamarin.Android ComboBox" — alt text should be concise and describe the image; the surrounding text already gives context.
Prefer hyphenation for “case-sensitive”.
Suggested alt text replacements (concise and consistent)

images/startswith.png
Suggested: "Words that start with the input text (StartsWith)"
images/startswithcasesensitive.png
Suggested: "Words that start with the input text (case-sensitive)"
images/contains.png
Suggested: "Words that contain the input text (Contains)"
images/containswithcasesensitive.png
Suggested: "Words that contain the input text (case-sensitive)"
images/equals.png
Suggested: "Words equal to the input text (Equals)"
images/equalswithcasesensitive.png
Suggested: "Words equal to the input text (case-sensitive)"
images/endswith.png
Suggested: "Words that end with the input text (EndsWith)"
images/endswithcasesensitive.png
Suggested: "Words that end with the input text (case-sensitive)"
images/customfilter.png
Suggested: "Custom filter applied to suggestions (example)"
Best-practices for alt text here

Keep it short and descriptive (under ~125 characters).
Describe the image purpose (what a screen reader user needs to know), not the file or that it is a screenshot.
Use consistent phrasing and parenthetical flags like "(case-sensitive)".
Omit the control name if the page already makes it obvious; include it only if needed for clarity.
Do not include trailing periods.

@SyncfusionBuild
Copy link
Contributor

Your pull request has been created. Syncfusion support team will validate this commit and publish your changes accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants