update rule metadata (#289)

README.md

@@ -55,6 +55,6 @@ The "Ruling Test" are an integration test suite which launches the analysis of a
 
 ### License
 
-Copyright 2010-2022 SonarSource.
+Copyright 2010-2024 SonarSource.
 
 Licensed under the [GNU Lesser General Public License, Version 3.0](http://www.gnu.org/licenses/lgpl.txt)

sonar-html-plugin/src/main/java/org/sonar/plugins/html/checks/accessibility/NoNoninteractiveElementToInteractiveRoleCheck.java

@@ -21,7 +21,6 @@
 import static org.sonar.plugins.html.api.HtmlConstants.hasKnownHTMLTag;
 import static org.sonar.plugins.html.api.HtmlConstants.isNonInteractiveElement;
 
-import java.util.Locale;
 import org.sonar.check.Rule;
 import org.sonar.plugins.html.checks.AbstractPageCheck;
 import org.sonar.plugins.html.node.TagNode;

sonar-html-plugin/src/main/resources/org/sonar/l10n/web/rules/Web/S1135.html

@@ -1,8 +1,8 @@
 <h2>Why is this an issue?</h2>
 <p>Developers often use <code>TODO</code> tags to mark areas in the code where additional work or improvements are needed but are not implemented
-immediately. However, these <code>TODO</code> tags sometimes get overlooked or forgotten, leading to incomplete or unfinished code. This code smell
-class aims to identify and address such unattended <code>TODO</code> tags to ensure a clean and maintainable codebase. This description will explore
-why this is a problem and how it can be fixed to improve the overall code quality.</p>
+immediately. However, these <code>TODO</code> tags sometimes get overlooked or forgotten, leading to incomplete or unfinished code. This rule aims to
+identify and address unattended <code>TODO</code> tags to ensure a clean and maintainable codebase. This description explores why this is a problem
+and how it can be fixed to improve the overall code quality.</p>
 <h3>What is the potential impact?</h3>
 <p>Unattended <code>TODO</code> tags in code can have significant implications for the development process and the overall codebase.</p>
 <p>Incomplete Functionality: When developers leave <code>TODO</code> tags without implementing the corresponding code, it results in incomplete
@@ -11,8 +11,8 @@ <h3>What is the potential impact?</h3>
 Delayed bug fixes can result in more severe issues and increase the effort required to resolve them later.</p>
 <p>Impact on Collaboration: In team-based development environments, unattended <code>TODO</code> tags can hinder collaboration. Other team members
 might not be aware of the intended changes, leading to conflicts or redundant efforts in the codebase.</p>
-<p>Codebase Bloat: Accumulation of unattended <code>TODO</code> tags over time can clutter the codebase and make it difficult to distinguish between
-work in progress and completed code. This bloat can make it challenging to maintain an organized and efficient codebase.</p>
+<p>Codebase Bloat: The accumulation of unattended <code>TODO</code> tags over time can clutter the codebase and make it difficult to distinguish
+between work in progress and completed code. This bloat can make it challenging to maintain an organized and efficient codebase.</p>
 <p>Addressing this code smell is essential to ensure a maintainable, readable, reliable codebase and promote effective collaboration among
 developers.</p>
 <h3>Noncompliant code example</h3>

sonar-html-plugin/src/main/resources/org/sonar/l10n/web/rules/Web/S6842.html

@@ -17,7 +17,7 @@ <h2>How to fix it</h2>
 <h3>Code examples</h3>
 <h4>Noncompliant code example</h4>
 <pre data-diff-id="1" data-diff-type="noncompliant">
-&lt;li role="button"&gt;Foo&lt;/li&gt;; // Noncompliant; "li" isn't interactive, but "button" is
+&lt;li role="button"&gt;Foo&lt;/li&gt; &lt;!--Noncompliant; "li" isn't interactive, but "button" is--&gt;
 </pre>
 <h4>Compliant solution</h4>
 <pre data-diff-id="1" data-diff-type="compliant">

sonarpedia.json

@@ -3,7 +3,7 @@
  "languages": [
  "HTML"
  ],
- "latest-update": "2024-01-26T08:34:26.980892Z",
+ "latest-update": "2024-02-23T15:02:03.435402Z",
  "options": {
  "no-language-in-filenames": true,
  "preserve-filenames": true