145 provide creedengo dashboard gadgets through a confluence plugin#186
145 provide creedengo dashboard gadgets through a confluence plugin#186DavTheryCap wants to merge 3 commits into
Conversation
# Conflicts: # package.json # pnpm-lock.yaml
version avec 3 macro + dashboard
|
![accesslint[bot]](https://avatars.githubusercontent.com/in/1502?s=60&v=4){kind=small}
| * filtered by a specific metric tag (e.g. CPU or RAM). | ||
| * | ||
| * <p>Each arc segment is proportional to the number of issues at that severity:</p> | ||
| * <ul> |
There was a problem hiding this comment.
WCAG 1.3.1: <ul> contains direct text content. Wrap in <li>.
<ul> and <ol> must only contain <li>, <script>, or <template> as direct children.
Details
Screen readers announce list structure ('list with 5 items') based on proper markup. Placing non-<li> elements directly inside <ul> or <ol> breaks this structure. Wrap content in <li> elements, or if you need wrapper divs for styling, restructure your CSS to style the <li> elements directly.
| if (displayHeader) { | ||
| output.append("<h1>").append(MacroHelper.getText("priorityrules.header", MacroHelper.escapeHtml(projectKey))).append("</h1>"); | ||
| } | ||
| output.append("<h3>Top ").append(topRules.size()).append(" règles critiques</h3>"); |
There was a problem hiding this comment.
Best Practice: Heading level 3 skipped from level 1.
Heading levels should increase by one; skipping levels (e.g. h2 to h4) makes navigation harder.
Details
Previous heading: <h1>").append(MacroHelper.getText("priorityrules.header", MacroHelper.escapeHtml(projectKey))).append("</h1>
Screen reader users navigate by headings to understand page structure. Skipping levels (h2 to h4) suggests missing content and creates confusion. Start with h1 for the page title, then use h2 for main sections, h3 for subsections, etc. You can go back up (h3 to h2) when starting a new section.
| * project size (lines of code).</p> | ||
| * | ||
| * <h3>Score rules</h3> | ||
| * <ul> |
There was a problem hiding this comment.
WCAG 1.3.1: <ul> contains direct text content. Wrap in <li>.
<ul> and <ol> must only contain <li>, <script>, or <template> as direct children.
Details
Screen readers announce list structure ('list with 5 items') based on proper markup. Placing non-<li> elements directly inside <ul> or <ol> breaks this structure. Wrap content in <li> elements, or if you need wrapper divs for styling, restructure your CSS to style the <li> elements directly.
| * Constants used across SonarQube API calls. | ||
| * | ||
| * <p>Sustainability tags used to filter issues or rules:</p> | ||
| * <ul> |
There was a problem hiding this comment.
WCAG 1.3.1: <ul> contains direct text content. Wrap in <li>.
<ul> and <ol> must only contain <li>, <script>, or <template> as direct children.
Details
Screen readers announce list structure ('list with 5 items') based on proper markup. Placing non-<li> elements directly inside <ul> or <ol> breaks this structure. Wrap content in <li> elements, or if you need wrapper divs for styling, restructure your CSS to style the <li> elements directly.
1 participant
First version of confluence plugin.