@herb-tools/linter 0.5.0 → 0.6.1

package/dist/types/types.d.ts

@@ -19,11 +19,27 @@ export declare abstract class ParserRule {
     static type: "parser";
     abstract name: string;
     abstract check(result: ParseResult, context?: Partial<LintContext>): LintOffense[];
+    /**
+     * Optional method to determine if this rule should run.
+     * If not implemented, rule is always enabled.
+     * @param result - The parse result to analyze
+     * @param context - Optional context for linting
+     * @returns true if rule should run, false to skip
+     */
+    isEnabled?(result: ParseResult, context?: Partial<LintContext>): boolean;
 }
 export declare abstract class LexerRule {
     static type: "lexer";
     abstract name: string;
     abstract check(lexResult: LexResult, context?: Partial<LintContext>): LintOffense[];
+    /**
+     * Optional method to determine if this rule should run.
+     * If not implemented, rule is always enabled.
+     * @param lexResult - The lex result to analyze
+     * @param context - Optional context for linting
+     * @returns true if rule should run, false to skip
+     */
+    isEnabled?(lexResult: LexResult, context?: Partial<LintContext>): boolean;
 }
 export interface LexerRuleConstructor {
     type: "lexer";
@@ -44,6 +60,14 @@ export declare abstract class SourceRule {
     static type: "source";
     abstract name: string;
     abstract check(source: string, context?: Partial<LintContext>): LintOffense[];
+    /**
+     * Optional method to determine if this rule should run.
+     * If not implemented, rule is always enabled.
+     * @param source - The source code to analyze
+     * @param context - Optional context for linting
+     * @returns true if rule should run, false to skip
+     */
+    isEnabled?(source: string, context?: Partial<LintContext>): boolean;
 }
 export interface SourceRuleConstructor {
     type: "source";

package/docs/rules/README.md

@@ -6,22 +6,32 @@ This page contains documentation for all Herb Linter rules.
 
 - [`erb-no-empty-tags`](./erb-no-empty-tags.md) - Disallow empty ERB tags
 - [`erb-no-output-control-flow`](./erb-no-output-control-flow.md) - Prevents outputting control flow blocks
+- [`erb-no-silent-tag-in-attribute-name`](./erb-no-silent-tag-in-attribute-name.md) - Disallow ERB silent tags in HTML attribute names
 - [`erb-prefer-image-tag-helper`](./erb-prefer-image-tag-helper.md) - Prefer `image_tag` helper over `<img>` with ERB expressions
-- [`erb-require-whitespace-inside-tags`](./erb-require-whitespace-inside-tags.md) - Requires whitespace around erb tags
+- [`erb-require-whitespace-inside-tags`](./erb-require-whitespace-inside-tags.md) - Requires whitespace around ERB tags
 - [`erb-requires-trailing-newline`](./erb-requires-trailing-newline.md) - Enforces that all HTML+ERB template files end with exactly one trailing newline character.
 - [`html-anchor-require-href`](./html-anchor-require-href.md) - Requires an href attribute on anchor tags
 - [`html-aria-attribute-must-be-valid`](./html-aria-attribute-must-be-valid.md) - Disallow invalid or unknown `aria-*` attributes.
+- [`html-aria-label-is-well-formatted`](./html-aria-label-is-well-formatted.md) - `aria-label` must be well-formatted
 - [`html-aria-level-must-be-valid`](./html-aria-level-must-be-valid.md) - `aria-level` must be between 1 and 6
 - [`html-aria-role-heading-requires-level`](./html-aria-role-heading-requires-level.md) - Requires `aria-level` when supplying a `role`
 - [`html-aria-role-must-be-valid`](./html-aria-role-must-be-valid.md) - The `role` attribute must have a valid WAI-ARIA Role.
 - [`html-attribute-double-quotes`](./html-attribute-double-quotes.md) - Enforces double quotes for attribute values
+- [`html-attribute-equals-spacing`](./html-attribute-equals-spacing.md) - No whitespace around `=` in HTML attributes
 - [`html-attribute-values-require-quotes`](./html-attribute-values-require-quotes.md) - Requires quotes around attribute values
+- [`html-avoid-both-disabled-and-aria-disabled`](./html-avoid-both-disabled-and-aria-disabled.md) - Avoid using both `disabled` and `aria-disabled` attributes
 - [`html-boolean-attributes-no-value`](./html-boolean-attributes-no-value.md) - Prevents values on boolean attributes
-- [`html-img-require-alt`](./html-img-require-alt.md) - Requires alt attributes on img tags
+- [`html-iframe-has-title`](./html-iframe-has-title.md) - `iframe` elements must have a `title` attribute
+- [`html-img-require-alt`](./html-img-require-alt.md) - Requires `alt` attributes on `<img>` tags
+- [`html-navigation-has-label`](./html-navigation-has-label.md) - Navigation landmarks must have accessible labels
+- [`html-no-aria-hidden-on-focusable`](./html-no-aria-hidden-on-focusable.md) - Focusable elements should not have `aria-hidden="true"`
 - [`html-no-block-inside-inline`](./html-no-block-inside-inline.md) - Prevents block-level elements inside inline elements
 - [`html-no-duplicate-attributes`](./html-no-duplicate-attributes.md) - Prevents duplicate attributes on HTML elements
 - [`html-no-duplicate-ids`](./html-no-duplicate-ids.md) - Prevents duplicate IDs within a document
 - [`html-no-nested-links`](./html-no-nested-links.md) - Prevents nested anchor tags
+- [`html-no-positive-tab-index`](./html-no-positive-tab-index.md) - Avoid positive `tabindex` values
+- [`html-no-self-closing`](./html-no-self-closing.md.md) - Disallow self closing tags
+- [`html-no-title-attribute`](./html-no-title-attribute.md) - Avoid using the `title` attribute
 - [`html-tag-name-lowercase`](./html-tag-name-lowercase.md) - Enforces lowercase tag names in HTML
 - [`parser-no-errors`](./parser-no-errors.md) - Disallow parser errors in HTML+ERB documents
 - [`svg-tag-name-capitalization`](./svg-tag-name-capitalization.md) - Enforces proper camelCase capitalization for SVG elements

package/docs/rules/erb-no-silent-tag-in-attribute-name.md

@@ -0,0 +1,34 @@
+# Linter Rule: Disallow ERB silent tags in HTML attribute names
+
+**Rule:** `erb-no-silent-tag-in-attribute-name`
+
+## Description
+
+Disallow the use of ERB silent tags (`<% ... %>`) inside HTML attribute names. These tags introduce Ruby logic that does not output anything, and placing them in attribute names leads to malformed HTML or completely unpredictable rendering.
+
+## Rationale
+
+HTML attribute names, ideally, must be valid, statically defined strings. Placing ERB silent tags (`<% ... %>`) that don't output anything inside attribute names might result in invalid HTML and is confusing. These cases are rarely intentional and almost always indicate a mistake or misuse of ERB templating.
+
+## Examples
+
+### ✅ Good
+
+```erb
+<div data-<%= key %>-target="value"></div>
+<div <%= data_attributes_for(user) %>></div>
+```
+
+### 🚫 Bad
+
+```erb
+<div data-<% key %>-id="value"></div>
+
+<div data-<%# key %>-id="thing"></div>
+
+<div data-<%- key -%>-id="thing"></div>
+```
+
+## References
+
+\-

package/docs/rules/html-aria-label-is-well-formatted.md

@@ -0,0 +1,49 @@
+# Linter Rule: `aria-label` must be well-formatted
+
+**Rule:** `html-aria-label-is-well-formatted`
+
+## Description
+
+Ensure that the value of the `aria-label` attribute is formatted like natural, visual text. The text should use sentence case (capitalize the first letter), avoid line breaks, and not look like an ID or code identifier.
+
+## Rationale
+
+The `aria-label` attribute provides an accessible name for elements that will be read aloud by screen readers. The text should be formatted like natural language that users would expect to hear, not like technical identifiers. Using proper sentence case and avoiding formatting that looks like code (snake_case, kebab-case, camelCase) ensures a better user experience for assistive technology users.
+
+## Examples
+
+### ✅ Good
+
+```erb
+<button aria-label="Close dialog">X</button>
+<input aria-label="Search products" type="search">
+<button aria-label="Page 2 of 10">2</button>
+```
+
+### 🚫 Bad
+
+```erb
+<!-- Starts with lowercase -->
+<button aria-label="close dialog">X</button>
+
+<!-- Contains line breaks -->
+<button aria-label="Close
+dialog">X</button>
+
+<!-- Looks like an ID (snake_case) -->
+<button aria-label="close_dialog">X</button>
+
+<!-- Looks like an ID (kebab-case) -->
+<button aria-label="close-dialog">X</button>
+
+<!-- Looks like an ID (camelCase) -->
+<button aria-label="closeDialog">X</button>
+
+<!-- HTML entity line breaks -->
+<button aria-label="Close&#10;dialog">X</button>
+```
+
+## References
+
+- [ARIA: `aria-label` attribute](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Reference/Attributes/aria-label)
+- [erblint-github: GitHub::Accessibility::AriaLabelIsWellFormatted](https://github.com/github/erblint-github/blob/main/docs/rules/accessibility/aria-label-is-well-formatted.md)

package/docs/rules/html-attribute-equals-spacing.md

@@ -0,0 +1,35 @@
+# Linter Rule: No whitespace around `=` in HTML attributes
+
+**Rule:** `html-attribute-equals-spacing`
+
+## Description
+
+Disallow whitespace before or after the equals sign (`=`) for attribute values in HTML. Attributes must follow the canonical format (`name="value"`) with no spaces between the attribute name, the equals sign, or the opening quote.
+
+## Rationale
+
+Extra whitespace around the `=` in HTML attribute assignments is unnecessary, inconsistent, and not idiomatic. While browsers are usually forgiving, it can lead to confusing diffs, poor formatting, or inconsistent parsing in tools.
+
+## Examples
+
+### ✅ Good
+
+```erb
+<div class="container"></div>
+<img src="/logo.png" alt="Logo">
+<input type="text" value="<%= @value %>">
+```
+
+### 🚫 Bad
+
+```erb
+<div class ="container"></div>
+
+<img src= "/logo.png" alt="Logo">
+
+<input  type  =  "text">
+```
+
+## References
+
+\-

package/docs/rules/html-avoid-both-disabled-and-aria-disabled.md

@@ -0,0 +1,48 @@
+# Linter Rule: Avoid using both `disabled` and `aria-disabled` attributes
+
+**Rule:** `html-avoid-both-disabled-and-aria-disabled`
+
+## Description
+
+Prevent using both the native `disabled` attribute and the `aria-disabled` attribute on the same HTML element. Elements should use either the native `disabled` attribute or `aria-disabled`, but not both.
+
+## Rationale
+
+Using both `disabled` and `aria-disabled` on the same element creates redundancy and potential confusion for assistive technologies. The native `disabled` attribute provides both visual and functional disabling, while `aria-disabled` only provides semantic information without preventing interaction. Having both can lead to inconsistent behavior and unclear expectations for users.
+
+Elements that support the native `disabled` attribute include: `button`, `fieldset`, `input`, `optgroup`, `option`, `select`, and `textarea`.
+
+## Examples
+
+### ✅ Good
+
+```erb
+<!-- Use only the native disabled attribute -->
+<button disabled>Submit</button>
+<input type="text" disabled>
+
+<!-- Use only aria-disabled for custom elements -->
+<div role="button" aria-disabled="true">Custom Button</div>
+
+<!-- Use only aria-disabled -->
+<button aria-disabled="true">Submit</button>
+```
+
+### 🚫 Bad
+
+```erb
+<!-- Both disabled and aria-disabled -->
+<button disabled aria-disabled="true">Submit</button>
+
+<input type="text" disabled aria-disabled="true">
+
+<select disabled aria-disabled="true">
+  <option>Option 1</option>
+</select>
+```
+
+## References
+
+- [HTML: `disabled` attribute](https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/disabled)
+- [ARIA: `aria-disabled` attribute](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Reference/Attributes/aria-disabled)
+- [erblint-github: GitHub::Accessibility::AvoidBothDisabledAndAriaDisabled](https://github.com/github/erblint-github/blob/main/docs/rules/accessibility/avoid-both-disabled-and-aria-disabled.md)

package/docs/rules/html-iframe-has-title.md

@@ -0,0 +1,43 @@
+# Linter Rule: `iframe` elements must have a `title` attribute
+
+**Rule:** `html-iframe-has-title`
+
+## Description
+
+Ensure that all `iframe` elements have a meaningful `title` attribute that describes the content of the frame. The title should not be empty or contain only whitespace.
+
+## Rationale
+
+The `title` attribute on `iframe` elements provides essential context for screen reader users about what content the frame contains. Without this information, users of assistive technology cannot understand the purpose or content of the embedded frame, creating significant accessibility barriers.
+
+::: tip Note
+`<iframe>`'s with `aria-hidden="true"` are exempt from this requirement as they are hidden from assistive technologies.
+:::
+
+## Examples
+
+### ✅ Good
+
+```erb
+<iframe src="https://youtube.com/embed/123" title="Product demonstration video"></iframe>
+<iframe src="https://example.com" title="Example website content"></iframe>
+
+<!-- Hidden from screen readers -->
+<iframe aria-hidden="true"></iframe>
+```
+
+### 🚫 Bad
+
+```erb
+<iframe src="https://example.com"></iframe>
+
+<iframe src="https://example.com" title=""></iframe>
+
+<iframe src="https://example.com" title="   "></iframe>
+```
+
+## References
+
+- [HTML: `iframe` element](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe)
+- [HTML: `title` attribute](https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/title)
+- [erblint-github: GitHub::Accessibility::IframeHasTitle](https://github.com/github/erblint-github/blob/main/docs/rules/accessibility/iframe-has-title.md)

package/docs/rules/html-navigation-has-label.md

@@ -0,0 +1,61 @@
+# Linter Rule: Navigation landmarks must have accessible labels
+
+**Rule:** `html-navigation-has-label`
+
+## Description
+
+Ensure that navigation landmarks have a unique accessible name via `aria-label` or `aria-labelledby` attributes. This applies to both `<nav>` elements and elements with `role="navigation"`.
+
+## Rationale
+
+Navigation landmarks help users of assistive technology quickly understand and navigate to different sections of a website. When multiple navigation landmarks exist on a page, each needs a unique accessible name so users can distinguish between them (e.g., "Main navigation", "Footer links", "Breadcrumb navigation").
+
+## Examples
+
+### ✅ Good
+
+```erb
+<nav aria-label="Main navigation">
+  <ul>
+    <li><a href="/">Home</a></li>
+    <li><a href="/about">About</a></li>
+  </ul>
+</nav>
+
+<nav aria-labelledby="breadcrumb-title">
+  <h2 id="breadcrumb-title">Breadcrumb</h2>
+  <ol>
+    <li><a href="/">Home</a></li>
+    <li>Current Page</li>
+  </ol>
+</nav>
+
+<div role="navigation" aria-label="Footer links">
+  <a href="/privacy">Privacy</a>
+  <a href="/terms">Terms</a>
+</div>
+```
+
+### 🚫 Bad
+
+```erb
+<nav>
+  <ul>
+    <li><a href="/">Home</a></li>
+    <li><a href="/about">About</a></li>
+  </ul>
+</nav>
+
+<div role="navigation">
+  <a href="/privacy">Privacy</a>
+  <a href="/terms">Terms</a>
+</div>
+```
+
+## References
+
+- [ARIA: `navigation` role](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Reference/Roles/navigation_role)
+- [HTML: `nav` element](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/nav)
+- [ARIA: `aria-label` attribute](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Reference/Attributes/aria-label)
+- [ARIA: `aria-labelledby` attribute](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Reference/Attributes/aria-labelledby)
+- [erblint-github: GitHub::Accessibility::NavigationHasLabel](https://github.com/github/erblint-github/blob/main/docs/rules/accessibility/navigation-has-label.md)

package/docs/rules/html-no-aria-hidden-on-focusable.md

@@ -0,0 +1,54 @@
+# Linter Rule: Focusable elements should not have `aria-hidden="true"`
+
+**Rule:** `html-no-aria-hidden-on-focusable`
+
+## Description
+
+Prevent using `aria-hidden="true"` on elements that can receive keyboard focus. When an element is focusable but hidden from screen readers, it creates a confusing experience where keyboard users can tab to "invisible" elements.
+
+## Rationale
+
+Elements with `aria-hidden="true"` are completely hidden from assistive technologies, but they remain visible and interactive for mouse and keyboard users. If a focusable element is hidden from screen readers, keyboard-only users (especially those using screen readers) will encounter focused elements that provide no accessible information, creating a broken user experience.
+
+## Examples
+
+### ✅ Good
+
+```erb
+<button>Submit</button>
+<a href="/link">Link</a>
+<input type="text">
+<textarea></textarea>
+
+<div aria-hidden="true">Decorative content</div>
+<span aria-hidden="true">🎉</span>
+
+<button tabindex="-1" aria-hidden="true">Hidden button</button>
+```
+
+### 🚫 Bad
+
+```erb
+<button aria-hidden="true">Submit</button>
+
+<a href="/link" aria-hidden="true">Link</a>
+
+<input type="text" aria-hidden="true">
+
+<textarea aria-hidden="true"></textarea>
+
+<select aria-hidden="true">
+  <option>Option</option>
+</select>
+
+<div tabindex="0" aria-hidden="true">Focusable div</div>
+
+<a href="/link" aria-hidden="true">Hidden link</a>
+```
+
+## References
+
+- [ARIA: `aria-hidden` attribute](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Reference/Attributes/aria-hidden)
+- [HTML: `tabindex` attribute](https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/tabindex)
+- [WebAIM: Keyboard Accessibility](https://webaim.org/techniques/keyboard/)
+- [erblint-github: GitHub::Accessibility::NoAriaHiddenOnFocusable](https://github.com/github/erblint-github/blob/main/docs/rules/accessibility/no-aria-hidden-on-focusable.md)

package/docs/rules/html-no-positive-tab-index.md

@@ -0,0 +1,55 @@
+# Linter Rule: Avoid positive `tabindex` values
+
+**Rule:** `html-no-positive-tab-index`
+
+## Description
+
+Prevent using positive values for the `tabindex` attribute. Only `tabindex="0"` (to make elements focusable) and `tabindex="-1"` (to remove from tab order) should be used.
+
+## Rationale
+
+Positive `tabindex` values create a custom tab order that can be confusing and unpredictable for keyboard users. They override the natural document flow and can cause elements to be focused in an unexpected sequence. This breaks the logical reading order and creates usability issues, especially for screen reader users who rely on a predictable navigation pattern.
+
+The recommended approach is to structure your HTML in the correct tab order and use `tabindex="0"` only when you need to make non-interactive elements focusable, or `tabindex="-1"` to remove elements from the tab sequence while keeping them programmatically focusable.
+
+## Examples
+
+### ✅ Good
+
+```erb
+<!-- Natural tab order (no tabindex needed) -->
+<button>First</button>
+<button>Second</button>
+<button>Third</button>
+
+<!-- Make non-interactive element focusable -->
+<div tabindex="0" role="button">Custom button</div>
+
+<!-- Remove from tab order but keep programmatically focusable -->
+<button tabindex="-1">Skip this in tab order</button>
+
+<!-- Zero tabindex to ensure focusability -->
+<span tabindex="0" role="button">Focusable span</span>
+```
+
+### 🚫 Bad
+
+```erb
+<button tabindex="3">Third in tab order</button>
+
+<button tabindex="1">First in tab order</button>
+
+<button tabindex="2">Second in tab order</button>
+
+
+<input tabindex="5" type="text">
+
+<button tabindex="10">Submit</button>
+```
+
+## References
+
+- [HTML: `tabindex` attribute](https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/tabindex)
+- [WebAIM: Keyboard Accessibility](https://webaim.org/techniques/keyboard/tabindex)
+- [WCAG: Focus Order](https://www.w3.org/WAI/WCAG21/Understanding/focus-order.html)
+- [erblint-github: GitHub::Accessibility::NoPositiveTabIndex](https://github.com/github/erblint-github/blob/main/docs/rules/accessibility/no-positive-tab-index.md)

package/docs/rules/html-no-self-closing.md

@@ -0,0 +1,65 @@
+# Linter Rule: Disallow self-closing tag syntax for void elements
+
+**Rule:** `html-no-self-closing`
+
+## Description
+
+Disallow self-closing syntax (`<tag />`) in HTML for all elements.
+
+In HTML5, the trailing slash in a start tag is obsolete and has no effect.
+Non-void elements require explicit end tags, and void elements are
+self-contained without the slash.
+
+## Rationale
+
+Self-closing syntax is an XHTML artifact. In HTML:
+
+- On **non-void** elements, it’s a parse error and produces invalid markup
+  (`<div />` is invalid).
+- On **void elements**, the slash is ignored and unnecessary (`<input />` is
+  equivalent to `<input>`).
+
+Removing the slash ensures HTML5-compliant, cleaner markup and avoids mixing
+XHTML and HTML styles.
+
+## Examples
+
+### ✅ Good
+
+```html
+<span></span>
+<div></div>
+<section></section>
+<custom-element></custom-element>
+
+<img src="/logo.png" alt="Logo">
+<input type="text">
+<br>
+<hr>
+```
+
+### 🚫 Bad
+
+```html
+<span />
+
+<div />
+
+<section />
+
+<custom-element />
+
+<img src="/logo.png" alt="Logo" />
+
+<input type="text" />
+
+<br />
+
+<hr />
+```
+
+## References
+
+- [HTML Living Standard: Void Elements](https://html.spec.whatwg.org/multipage/syntax.html#void-elements)
+- [MDN: Void element](https://developer.mozilla.org/en-US/docs/Glossary/Void_element)
+- [erb_lint: SelfClosingTag](https://github.com/Shopify/erb_lint#selfclosingtag)

package/docs/rules/html-no-title-attribute.md

@@ -0,0 +1,69 @@
+# Linter Rule: Avoid using the `title` attribute
+
+**Rule:** `html-no-title-attribute`
+
+## Description
+
+Discourage the use of the `title` attribute on most HTML elements, as it provides poor accessibility and user experience. The `title` attribute is only accessible via mouse hover and is not reliably exposed to screen readers or keyboard users.
+
+## Rationale
+
+The `title` attribute has several accessibility problems:
+- It's only visible on mouse hover, making it inaccessible to keyboard and touch users
+- Screen readers don't consistently announce title attributes
+- Mobile devices don't show title tooltips
+- The visual presentation is inconsistent across browsers and operating systems
+
+Instead of relying on `title`, use visible text, `aria-label`, `aria-describedby`, or other accessible alternatives.
+
+::: warning Exceptions
+This rule allows `title` on `<iframe>` and `<link>` elements where it serves specific accessibility purposes.
+:::
+
+## Examples
+
+### ✅ Good
+
+```erb
+<!-- Use visible text instead of title -->
+<button>Save document</button>
+<span class="help-text">Click to save your changes</span>
+
+<!-- Use aria-label for accessible names -->
+<button aria-label="Close dialog">×</button>
+
+<!-- Use aria-describedby for additional context -->
+<input type="password" aria-describedby="pwd-help">
+<div id="pwd-help">Password must be at least 8 characters</div>
+
+<!-- Exceptions: title allowed on iframe and links -->
+<iframe src="https://example.com" title="Example website content"></iframe>
+<link href="default.css" rel="stylesheet" title="Default Style">
+```
+
+### 🚫 Bad
+
+```erb
+<!-- Don't use title for essential information -->
+<button title="Save your changes">Save</button>
+
+<div title="This is important information">Content</div>
+
+<span title="Required field">*</span>
+
+<!-- Don't use title on form elements -->
+<input type="text" title="Enter your name">
+
+<select title="Choose your country">
+  <option>US</option>
+  <option>CA</option>
+</select>
+```
+
+## References
+
+- [HTML: `title` attribute](https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/title)
+- [WebAIM: Accessible Forms](https://webaim.org/techniques/forms/)
+- [ARIA: `aria-label` attribute](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Reference/Attributes/aria-label)
+- [ARIA: `aria-describedby` attribute](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Reference/Attributes/aria-describedby)
+- [erblint-github: GitHub::Accessibility::NoTitleAttribute](https://github.com/github/erblint-github/blob/main/docs/rules/accessibility/no-title-attribute.md)

package/docs/rules/html-tag-name-lowercase.md

@@ -12,15 +12,28 @@ HTML is case-insensitive for tag names, but lowercase is the widely accepted con
 
 Writing tags in uppercase or mixed case can lead to inconsistent code and unnecessary diffs during reviews and merges.
 
-## Examples
+### Notes
+
+::: tip XML Documents
+This rule is automatically disabled for XML documents and XML+ERB templates. XML allows uppercase tag names and follows different naming conventions than HTML.
+
+The rule will be disabled when:
+- The document contains an XML declaration (`<?xml version="1.0" ?>`)
+- The file extension is `.xml` or `.xml.erb`
+:::
 
+::: tip SVG Elements
+This rule does not apply to child elements within `<svg>` tags, as SVG element names are case-sensitive and may require specific capitalization (e.g., `linearGradient`, `clipPath`). However, the rule still applies to the `<svg>` element itself.
+:::
+
+## Examples
 
 ### ✅ Good
 
 ```erb
 <div class="container"></div>
 
-<input type="text" name="username" />
+<input type="text" name="username">
 
 <span>Label</span>
 
@@ -32,7 +45,7 @@ Writing tags in uppercase or mixed case can lead to inconsistent code and unnece
 ```erb
 <DIV class="container"></DIV>
 
-<Input type="text" name="username" />
+<Input type="text" name="username">
 
 <Span>Label</Span>
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@herb-tools/linter",
-  "version": "0.5.0",
+  "version": "0.6.1",
   "description": "HTML+ERB linter for validating HTML structure and enforcing best practices",
   "license": "MIT",
   "homepage": "https://herb-tools.dev",
@@ -33,9 +33,10 @@
     }
   },
   "dependencies": {
-    "@herb-tools/core": "0.5.0",
-    "@herb-tools/highlighter": "0.5.0",
-    "@herb-tools/node-wasm": "0.5.0",
+    "@herb-tools/core": "0.6.1",
+    "@herb-tools/highlighter": "0.6.1",
+    "@herb-tools/node-wasm": "0.6.1",
+    "@herb-tools/printer": "0.6.1",
     "glob": "^11.0.3"
   },
   "files": [