Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.changeset/port-use-valid-aria-values-html.md:
- Line 5: Update the changeset text to link to the rule documentation and add a
tiny inline example: edit .changeset/port-use-valid-aria-values-html.md to
include a markdown link to the useValidAriaValues rule docs (e.g.,
"useValidAriaValues" -> [link]) and append a short HTML example showing an
invalid vs. corrected usage (e.g., an element with an invalid aria-* value and
the corrected value) so readers see the impact immediately.

In `@crates/biome_html_analyze/src/lint/a11y/use_valid_aria_values.rs`:
- Around line 108-150: Several diagnostic messages in the AriaValueType match
arms have grammar issues; update the user-facing strings in the match arms for
AriaValueType::Boolean, ::OptionalBoolean, ::Integer, ::Number, ::Tristate and
any similar literal messages used with diagnostic.footer_list or diagnostic.note
so they read correctly (e.g., "The only supported values for the
{attribute_name} property are one of the following:", "The only value supported
is a number without fractional components.", "The only supported value is a
number.", and "The only supported value for the {attribute_name} property is one
of the following:"); locate these messages in the AriaValueType match within
use_valid_aria_values.rs and replace the awkward phrasing ("is", "is number",
missing "is") with the corrected wording while keeping attribute_name
interpolation and existing helper calls (diagnostic.footer_list /
diagnostic.note) intact.
- Around line 84-95: The code currently short-circuits on valueless attributes
because html_attr.value()? returns None; update the logic in
use_valid_aria_values (where attribute_value, value_text and
aria_property.value_type() are used) to treat a missing value as the boolean
"true" (or otherwise normalize valueless aria-* to the equivalent string) before
checking aria_property.value_type().contains(&value_text), and add test fixtures
that include valueless aria attributes (e.g., invalid and valid HTML fixtures
exercising <div aria-hidden> and similar) to cover this case and document the
intended behavior; ensure UseValidAriaValuesState remains populated with
attribute_name and property_type as before.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@crates/biome_html_analyze/src/lint/a11y/use_valid_aria_values.rs`:
- Around line 80-83: The code currently lowercases every attribute name before
checking AriaAttribute::from_str, causing framework-specific props in
.vue/.svelte/.astro files to be misclassified; change the logic to inspect the
source file type and only perform case-folding for plain HTML files: keep the
original extracted name (from extract_html_attribute_name) for template files
(.vue, .svelte, .astro) and use name.to_ascii_lowercase_cow() only when the
current file is an .html file, then pass the appropriate string into
AriaAttribute::from_str so case-sensitive matching is preserved for template
files while .html remains case-insensitive.

---

Nitpick comments:
In `@crates/biome_html_analyze/src/lint/a11y/use_valid_aria_values.rs`:
- Around line 72-77: The comment above the match that extracts html_attr is
misleadingly Vue-specific; update it to state that we only process plain HTML
attributes with static values and that all non-HtmlAttribute variants (e.g., Vue
directives and any other variants of AnyHtmlAttribute) are skipped. Mention the
relevant symbols AnyHtmlAttribute and html_attr (the match that returns None for
non-HtmlAttribute cases) so readers know this applies to every non-HtmlAttribute
branch, not just Vue.

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@crates/biome_html_analyze/src/lint/a11y/use_valid_aria_values.rs`:
- Around line 148-152: The footer message for AriaValueType::Token uses singular
phrasing ("The only supported value for the {attribute_name} property is one
of...") while Boolean/Tristate use plural; update the string in the
AriaValueType::Token diagnostic.footer_list invocation to plural phrasing to
match (e.g., "The only supported values for the {attribute_name} property are
one of the following:") so wording is consistent with Boolean and Tristate
messages.