-
Notifications
You must be signed in to change notification settings - Fork 3
210696-SEO-Spider-Help-Domain-Image-alt-Missing-Xamarin.Android-ComboBox #727
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: hotfix/hotfix-v31.2.2
Are you sure you want to change the base?
Conversation
|
Your pull request has been created. Syncfusion support team will validate this commit and publish your changes accordingly. |
|
Your pull request has been created. Syncfusion support team will validate this commit and publish your changes accordingly. |
|
Your pull request has been created. Syncfusion support team will validate this commit and publish your changes accordingly. |
There was a problem hiding this 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.
|
Your pull request has been created. Syncfusion support team will validate this commit and publish your changes accordingly. |
Hi @YvoneAtienoOnyango
Regards,
Mercy A.