diff --git a/results/aria-allowed-attr.json b/results/aria-allowed-attr.json
index a5f0321..4baa8ef 100644
--- a/results/aria-allowed-attr.json
+++ b/results/aria-allowed-attr.json
@@ -32,5 +32,8 @@
   "span_aria-required": "The issue with the code snippet is that the `aria-required` attribute is not allowed for a `span` element. The `aria-required` attribute is only allowed for form elements such as `input`, `select`, and `textarea`.\n\nThe correct version of the code snippet would be to use a form element that supports the `aria-required` attribute, or to use a different ARIA attribute that is appropriate for the `span` element's role. For example, if the `span` element is being used as a label for an input field, the `aria-labelledby` attribute could be used instead.",
   "td_role=\"button\"": "The issue with the code snippet is that `aria-selected` attribute is not allowed for the `button` role. The correct version of the code snippet is:\n\n<td aria-label=\"...\" role=\"button\" style=\"width: 14.2857%; padding-top: 7.14286%; padding-bottom: 7.14286%;\" tabindex=\"-1\"><div></div></td>\n\nNote that `aria-selected` attribute has been removed.",
   "li_role=\"presentation\"": "The issue with the code snippet is that the `aria-controls`, `aria-hidden`, and `aria-selected` attributes are not allowed for the `role=\"presentation\"` element. These attributes are only allowed for certain roles such as `tab`, `treeitem`, and `tabpanel`. \n\nThe correct version of the code snippet would be:\n\n<li role=\"none presentation\"><button role=\"button\" tabindex=\"0\" type=\"button\"></button></li>\n\nIn this version, the `aria-controls`, `aria-hidden`, and `aria-selected` attributes have been removed and the `role` attribute has been updated to `none presentation`, which allows the element to be treated as a presentation role but without the additional ARIA attributes.",
-  "div_aria-checked": "The issue with this code snippet is that the `aria-checked` attribute is not allowed for the `div` element's role. The `aria-checked` attribute is typically used for checkboxes and radio buttons. \n\nThe correct version of the code snippet would be to either change the `div` element's role to a checkbox or radio button, or to remove the `aria-checked` attribute altogether if it is not necessary for the element's functionality."
+  "div_aria-checked": "The issue with this code snippet is that the `aria-checked` attribute is not allowed for the `div` element's role. The `aria-checked` attribute is typically used for checkboxes and radio buttons. \n\nThe correct version of the code snippet would be to either change the `div` element's role to a checkbox or radio button, or to remove the `aria-checked` attribute altogether if it is not necessary for the element's functionality.",
+  "p_role=\"note\"": "The issue with the code snippet is that the `aria-multiselectable` attribute is not allowed for the `note` role. \n\nThe correct version of the code snippet should be: `<p role=\"note\"></p>`",
+  "div_role=\"header\"": "The issue with this code snippet is that the `aria-level` attribute is not allowed for the `header` role. The correct version of the code snippet should be: `<div role=\"heading\" aria-level=\"2\"></div>` where the `role` attribute is changed to `heading` which is the appropriate role for a header element, and the `aria-level` attribute is placed after the `role` attribute.",
+  "div_aria-disabled_aria-expanded": "The issue with the code snippet is that the `aria-disabled` attribute is not allowed for a `div` element. According to the WAI-ARIA specification, the `aria-disabled` attribute is only allowed for form elements, links, and widgets.\n\nThe correct version of the code snippet would be:\n\n<`div` `aria-hidden`=\"false\" `aria-expanded`=\"true\">\n\nThe `aria-hidden` attribute can be used to indicate that an element is not visible or perceivable to all users, which is more appropriate for a `div` element."
 }
diff --git a/results/aria-allowed-role.json b/results/aria-allowed-role.json
index 50936d1..c41be1a 100644
--- a/results/aria-allowed-role.json
+++ b/results/aria-allowed-role.json
@@ -42,5 +42,7 @@
   "button_role=\"tooltip\"": "The issue with the code snippet is that the value of the `role` attribute is inappropriate. The `role` attribute is used to define the semantic meaning of an element for assistive technologies and should only be used with appropriate values. In this case, the value \"tooltip\" is not a valid value for the `role` attribute of a button element.\n\nThe correct version of the code snippet should be: `<button aria-describedby=\"tooltip\">`. Here, we are using the `aria-describedby` attribute to associate the button with a tooltip element on the page. This will ensure that assistive technologies can properly convey the purpose of the button to users.",
   "section_role=\"region\"": "The issue with the code snippet is that the value of the role attribute is not appropriate for the element. The \"region\" role should only be used for elements that define a large perceivable section of content, such as a main content area or a sidebar. For a section element, the appropriate role would be \"region\" only if it defines a significant portion of the page content.\n\nThe correct version of the code snippet would be:\n\n<section role=\"region\" aria-label=\"Insert appropriate label here\"> \n\nBy adding an aria-label attribute, the purpose of the section element is made clear to assistive technology users. This ensures that the content is accessible to all users.",
   "header_role=\"button\"": "The issue with the code snippet is that the `role` attribute has been set to \"button\", which is inappropriate for a `header` element. The correct version of the code snippet should have the `role` attribute set to \"banner\" or \"heading\", depending on the context. For example:\n\n<`header` `aria-controls`=\"content\" `aria-disabled`=\"false\" `aria-expanded`=\"false\" `role`=\"banner\" `tabindex`=\"0\">",
-  "footer_role=\"complementary\"": "The issue with the code snippet is that the value \"complementary\" is not appropriate for the role attribute of a footer element. According to the W3C Accessibility Guidelines, the role attribute of a footer element should be set to \"contentinfo\" to indicate that it contains information about the document such as authorship, copyright, or contact information.\n\nThe correct version of the code snippet should be:\n\n<footer role=\"contentinfo\">"
+  "footer_role=\"complementary\"": "The issue with the code snippet is that the value \"complementary\" is not appropriate for the role attribute of a footer element. According to the W3C Accessibility Guidelines, the role attribute of a footer element should be set to \"contentinfo\" to indicate that it contains information about the document such as authorship, copyright, or contact information.\n\nThe correct version of the code snippet should be:\n\n<footer role=\"contentinfo\">",
+  "label_role=\"option\"": "The issue with this code snippet is that the role attribute should not be set to \"option\" for a label element. The correct role attribute value for a label element is \"label\".\n\nThe corrected code snippet is: <`label` `aria-disabled`=\"false\" `for`=\"selected-1b3ugLwn5bE8g63bj6CLVW\" `role`=\"label\">",
+  "sup_role=\"doc-noteref\"": "The issue with the code snippet is that the value of the role attribute, \"doc-noteref\", is not a valid value for the sup element. According to the W3C specification, the role attribute can only be used on certain elements and with certain values.\n\nThe correct version of the code snippet would be:\n\n<sup aria-label=\"document reference\"><a href=\"...\"></a></sup>\n\nIn this version, we have replaced the role attribute with the aria-label attribute, which provides a text alternative for the element. This makes the element more accessible to users who rely on assistive technology. The value of the aria-label attribute, \"document reference\", describes the purpose of the element in a clear and concise manner."
 }
diff --git a/results/aria-hidden-focus.json b/results/aria-hidden-focus.json
index fc5c724..bdb0a92 100644
--- a/results/aria-hidden-focus.json
+++ b/results/aria-hidden-focus.json
@@ -8,5 +8,6 @@
   "span_aria-expanded_aria-hidden": "The issue in the given code snippet is that the `aria-hidden` attribute is set to \"true\" for a focusable element or an element containing focusable elements. This can cause accessibility issues, as screen readers will not announce the focusable elements within the `aria-hidden` element.\n\nTo fix this issue, you can either remove the `aria-hidden` attribute if the element should be focusable or make the focusable elements within the `aria-hidden` element non-focusable using `tabindex=\"-1\"`.\n\nCorrected code snippet:\n\n```\n<!-- If the element should be focusable -->\n<span aria-expanded=\"false\">\n  <!-- focusable elements inside -->\n</span>\n\n<!-- If the element should not be focusable -->\n<span aria-expanded=\"false\" aria-hidden=\"true\">\n  <!-- non-focusable elements inside -->\n  <button tabindex=\"-1\">Button</button>\n</span>\n```\n\nIn the corrected code snippet, I've provided two options - one where the `aria-hidden` attribute is removed, making the element focusable, and another where the focusable elements within the `aria-hidden` element are made non-focusable using `tabindex=\"-1\"`. Choose the appropriate option based on the desired behavior.",
   "div_aria-expanded_aria-hidden": "The issue in the given code snippet is that the `aria-hidden` attribute is set to \"true\", which means the element should not be accessible by screen readers or keyboard navigation. However, if the element is focusable or contains focusable elements, it would still be accessible by keyboard navigation, causing confusion for users relying on assistive technologies.\n\nHere's the correct version of the code snippet:\n\n```html\n<div aria-expanded=\"false\" aria-hidden=\"true\" tabindex=\"-1\">\n  <!-- Add tabindex=\"-1\" to any focusable elements inside this div, if any -->\n</div>\n```\n\nBy adding `tabindex=\"-1\"` to the element and any focusable elements inside it, you ensure that the element and its focusable children are not accessible by keyboard navigation, making the `aria-hidden` attribute work as intended.",
   "div_aria-hidden_tabindex": "The issue in the given code snippet is that the element with `aria-hidden=\"true\"` is focusable or contains focusable elements due to the `tabindex=\"-1\"` attribute. This can cause confusion for screen reader users and affect the accessibility of the page.\n\nTo fix the issue, you should remove the `tabindex` attribute or ensure that the focusable elements inside the `aria-hidden` element are also hidden from screen readers.\n\nHere's the corrected version of the code snippet:\n\n```html\n<div aria-hidden=\"true\">\n  <!-- Ensure that any focusable elements inside this div are also hidden from screen readers -->\n</div>\n```\n\nIf you still need the element to be focusable but hidden from screen readers, you can use `aria-hidden=\"true\"` on the focusable elements inside the div:\n\n```html\n<div tabindex=\"-1\">\n  <button aria-hidden=\"true\">Hidden Button</button>\n  <!-- Other focusable elements with aria-hidden=\"true\" -->\n</div>\n```",
-  "span_aria-hidden": "The issue with the code snippet is that it contains an aria-hidden element that is focusable or contains focusable elements. This can cause confusion for screen reader users and make it difficult for them to navigate the page. \n\nThe correct version of the code snippet would be: \n\n<span aria-hidden=\"true\" tabindex=\"-1\"> \n\nBy adding tabindex=\"-1\", the element will be hidden from screen readers and keyboard navigation."
+  "span_aria-hidden": "The issue with the code snippet is that it contains an aria-hidden element that is focusable or contains focusable elements. This can cause confusion for screen reader users and make it difficult for them to navigate the page. \n\nThe correct version of the code snippet would be: \n\n<span aria-hidden=\"true\" tabindex=\"-1\"> \n\nBy adding tabindex=\"-1\", the element will be hidden from screen readers and keyboard navigation.",
+  "article_aria-hidden": "The issue with the given code snippet is that it contains the `aria-hidden` attribute with a value of \"true\", which means the element and its contents will be hidden from assistive technologies such as screen readers. However, the element itself is focusable or contains focusable elements, which can cause confusion and frustration for users who rely on assistive technologies.\n\nThe correct version of the code snippet would be to remove the `aria-hidden` attribute altogether, or set its value to \"false\" if the element needs to be hidden visually but still accessible to assistive technologies. For example:\n\n`<article>`"
 }
diff --git a/results/aria-required-parent.json b/results/aria-required-parent.json
index e07fe02..d541b10 100644
--- a/results/aria-required-parent.json
+++ b/results/aria-required-parent.json
@@ -5,5 +5,7 @@
   "a_role=\"menuitemradio\"": "The issue in the given code snippet is that the \"menuitemradio\" role requires a parent element with the \"menu\" or \"menubar\" role. To fix the issue, you can wrap the \"a\" element inside an element with the \"menu\" role. Here is the corrected version of the code snippet:\n\n```\n<div role=\"menu\">\n  <a aria-checked=\"true\" href=\"...\" role=\"menuitemradio\"></a>\n</div>\n```",
   "ytd-mini-guide-entry-renderer_role=\"tab\"": "The issue in the code snippet is that the ARIA role \"tab\" is not contained within its required parent role \"tablist\". To fix this, you need to add a parent element with the role \"tablist\". Here's the correct version of the code snippet:\n\n```\n<div role=\"tablist\">\n  <ytd-mini-guide-entry-renderer aria-label=\"...\" aria-selected=\"true\" role=\"tab\" tabindex=\"0\">\n  </ytd-mini-guide-entry-renderer>\n</div>\n```\n\nIn this corrected version, the \"ytd-mini-guide-entry-renderer\" element with the role \"tab\" is now properly contained within a parent element with the role \"tablist\".",
   "li_role=\"menuitem\"": "The issue in the given code snippet is that the ARIA role \"menuitem\" should be contained within a parent element with the role \"menu\". \n\nHere's the correct version of the code snippet:\n\n```html\n<ul role=\"menu\">\n  <li role=\"menuitem\"></li>\n</ul>\n```\n\nIn this corrected version, we have added a parent element with the \"menu\" role, which properly contains the \"menuitem\" role.",
-  "sl-tree-item_role=\"treeitem\"": "The issue with this code snippet is that the `treeitem` role should be contained by a `group` or `tree` role. The correct version of the code snippet would be:\n\n<`div` `role`=\"group\">\n  <`sl-tree-item` `aria-disabled`=\"false\" `aria-selected`=\"false\" `role`=\"treeitem\" `tabindex`=\"-1\">\n</div> \n\nBy wrapping the `treeitem` role in a `group` role, it ensures that the ARIA tree structure is properly defined and accessible to assistive technologies."
+  "sl-tree-item_role=\"treeitem\"": "The issue with this code snippet is that the `treeitem` role should be contained by a `group` or `tree` role. The correct version of the code snippet would be:\n\n<`div` `role`=\"group\">\n  <`sl-tree-item` `aria-disabled`=\"false\" `aria-selected`=\"false\" `role`=\"treeitem\" `tabindex`=\"-1\">\n</div> \n\nBy wrapping the `treeitem` role in a `group` role, it ensures that the ARIA tree structure is properly defined and accessible to assistive technologies.",
+  "label_role=\"option\"": "The issue with the code snippet is that the `role` attribute \"option\" is not a valid ARIA role for a `label` element. The correct ARIA role for a `label` element is \"label\". Additionally, the `option` role should only be used for elements that are options within a listbox or combobox. \n\nThe corrected code snippet would be: \n\n<label aria-disabled=\"false\" for=\"selected-1b3ugLwn5bE8g63bj6CLVW\" role=\"label\">",
+  "a_role=\"menuitem\"": "The issue with the code snippet is that the `role` attribute \"menuitem\" is not contained within a parent role of \"menu\". The correct version of the code snippet would be: <`li` `role`=\"menuitem\"><`a` `aria-label`=\"...\" `href`=\"...\" `tabindex`=\"0\"><`span`></span></a></li> where the `li` element contains the parent role of \"menu\" and the `a` element contains the child role of \"menuitem\"."
 }
diff --git a/results/aria-roles.json b/results/aria-roles.json
index 92e4ff2..da15090 100644
--- a/results/aria-roles.json
+++ b/results/aria-roles.json
@@ -9,5 +9,6 @@
   "div_role=\"widget\"": "The issue with the code snippet is that the value \"widget\" is not a valid value for the role attribute. The correct value for the role attribute should be one of the following: \"button\", \"checkbox\", \"combobox\", \"grid\", \"listbox\", \"menu\", \"menubar\", \"progressbar\", \"radio\", \"scrollbar\", \"slider\", \"spinbutton\", \"tab\", \"textbox\", \"toolbar\", or \"tree\". \n\nThe corrected code snippet should look like this: <`div` `role`=\"button\">",
   "input_role=\"email\"": "The issue with the code snippet is that the value \"email\" is not a valid value for the role attribute. The correct value for an input element is \"textbox\". The corrected code snippet is: `<input name=\"...\" role=\"textbox\" type=\"email\">`",
   "div_role=\"section\"": "The issue with the code snippet is that the value of the `role` attribute is not valid. The correct value for the `role` attribute should be chosen from a list of predefined roles specified by the WAI-ARIA specification. \n\nThe correct version of the code snippet with a valid `role` attribute would be:\n\n<div role=\"region\">",
-  "h1_role=\"header\"": "The issue with the code snippet is that the value \"header\" is not a valid value for the role attribute. The correct value for the role attribute in this case should be \"heading\". The corrected code snippet is:\n\n<h1 role=\"heading\"></h1>"
+  "h1_role=\"header\"": "The issue with the code snippet is that the value \"header\" is not a valid value for the role attribute. The correct value for the role attribute in this case should be \"heading\". The corrected code snippet is:\n\n<h1 role=\"heading\"></h1>",
+  "div_role=\"header\"": "The `aria-level` attribute is not a valid attribute for the `div` element. \n\nThe correct version of the code snippet would be: `<div role=\"heading\" aria-level=\"2\"></div>`"
 }
diff --git a/results/landmark-unique.json b/results/landmark-unique.json
index 8309a46..5b279b2 100644
--- a/results/landmark-unique.json
+++ b/results/landmark-unique.json
@@ -35,5 +35,9 @@
   "cor-expander_role": "The issue with the code snippet is that the `role` attribute of the `cor-expander` element is not unique or descriptive enough. It should have a more specific role, label or title to aid in accessibility for users with disabilities. \n\nThe corrected version of the code snippet is:\n\n<`cor-expander` `role`=\"button\" `aria-expanded`=\"false\" `aria-controls`=\"expander-content\" `aria-label`=\"Expand the content\">",
   "div_role_style": "The issue with the code snippet is that the `div` element has a `role` attribute of \"banner\", but it does not have a unique label or title. This could cause issues for users who rely on screen readers or other assistive technologies to navigate the page.\n\nA correct version of the code snippet could be:\n\n<div role=\"banner\" aria-label=\"Website banner\" style=\"transform: translate3d(0px, 0px, 0px) scale3d(1, 1, 1) rotateX(0deg) rotateY(0deg) rotateZ(0deg) skew(0deg, 0deg); transform-style: preserve-3d;\"> \n\nIn this version, the `aria-label` attribute provides a unique label for the `div` element, making it more accessible for users with disabilities.",
   "sgds-masthead_role": "The issue with the code snippet is that the `sgds-masthead` landmark does not have a unique label, role, or title. This can make it difficult for users who rely on assistive technologies to navigate the page. \n\nThe correct version of the code snippet should include a unique label, role, and title for the `sgds-masthead` landmark. For example: \n\n<`header` `role`=\"banner\" `aria-label`=\"Main Header\">\n  <`h1`>Page Title</h1>\n  <`nav`>\n    <`ul`>\n      <`li`><`a` href=\"#\">Link 1</a></li>\n      <`li`><`a` href=\"#\">Link 2</a></li>\n      <`li`><`a` href=\"#\">Link 3</a></li>\n    </ul>\n  </nav>\n</header>",
-  "div_role_div_role": "The issue with the code snippet is that the landmarks do not have a unique role or role/label/title, which can make it difficult for assistive technology users to navigate and understand the content.\n\nThe correct version of the code snippet should include a unique and descriptive label for each landmark, such as:\n\n<div role=\"region\" aria-label=\"Main Content\">\n  <div role=\"region\" aria-label=\"Sidebar\"></div>\n</div>"
+  "div_role_div_role": "The issue with the code snippet is that the landmarks do not have a unique role or role/label/title, which can make it difficult for assistive technology users to navigate and understand the content.\n\nThe correct version of the code snippet should include a unique and descriptive label for each landmark, such as:\n\n<div role=\"region\" aria-label=\"Main Content\">\n  <div role=\"region\" aria-label=\"Sidebar\"></div>\n</div>",
+  "span_aria-label_role": "Issue: The `span` element has an `aria-label` and `role` attribute, but the role is not unique and there is no label or title associated with it.\n\nCorrect version: \n\nIf the navigation landmark is intended to be a navigation bar, the correct role would be `navigation` and a label or title should be provided to describe the purpose of the navigation. The updated code snippet would be:\n\n`<nav aria-label=\"Main Navigation\" role=\"navigation\">`",
+  "nav_sgds-masthead": "The issue with the code snippet is that the `nav` element and `sgds-masthead` custom element do not have a unique role or role/label/title attribute, which can make it difficult for users with disabilities to navigate and understand the content. \n\nThe correct version of the code snippet should include appropriate role and/or aria-label attributes, such as: \n\n<nav role=\"navigation\" aria-label=\"Main Navigation\">\n  <sgds-masthead role=\"banner\" aria-label=\"Site Header\"></sgds-masthead>\n</nav> \n\nThis will help to ensure that the elements are properly identified and labeled for assistive technology users.",
+  "section_aria-labelledby": "The issue with the code snippet is that the `section` element does not have a unique role or label/title. This can make it difficult for users with disabilities who rely on assistive technologies to navigate and understand the content on the page.\n\nTo fix the issue, the `section` element should have a unique `role` attribute that accurately describes its purpose, and a corresponding `label` or `title` attribute that provides additional context. For example:\n\n<`section` `role`=\"main\" `aria-label`=\"Main content\">",
+  "section_aria-labelledby_aria-roledescription_style": "The issue with the code snippet is that the `aria-labelledby` attribute is not pointing to a valid element to provide a label for the section. Additionally, the `aria-roledescription` attribute is not necessary as the `role` attribute is not specified. \n\nThe correct version of the code snippet with a unique label and role would be:\n\n<`section` `role`=\"region\" `aria-label`=\"Main Content\" `style`=\"height: 620px;\">"
 }
diff --git a/results/scrollable-region-focusable.json b/results/scrollable-region-focusable.json
index f5f493f..fbc27c8 100644
--- a/results/scrollable-region-focusable.json
+++ b/results/scrollable-region-focusable.json
@@ -15,5 +15,6 @@
   "div_style": "The issue with the code snippet is that it contains scrollable content that is not accessible by keyboard, which violates accessibility guidelines. To make the content accessible, the code should be modified to include the `tabindex` attribute and the `overflow-y` property set to `scroll` or `auto`. Here is the corrected version of the code snippet:\n\n<div style=\"height: calc(100% - 70px); overflow-y: scroll;\" tabindex=\"0\">",
   "table_style": "The issue with the code snippet is that it contains scrollable content that is not accessible by keyboard. This means that users who rely on keyboard navigation, such as those with motor disabilities, will not be able to access the content.\n\nTo fix this, the code snippet should be updated to include the appropriate ARIA attributes for scrollable content. Here is an example of the corrected code snippet:\n\n```\n<table style=\"width:90%\" role=\"table\" aria-label=\"Table with scrollable content\">\n  <tbody>\n    <tr>\n      <td>Content 1</td>\n      <td>Content 2</td>\n      <td>Content 3</td>\n    </tr>\n    <tr>\n      <td>Content 4</td>\n      <td>Content 5</td>\n      <td>Content 6</td>\n    </tr>\n    <!-- more rows -->\n  </tbody>\n</table>\n```\n\nIn this updated code snippet, the `role` attribute is set to \"table\" to indicate that this is a table element. The `aria-label` attribute provides a description of the table for screen reader users. Additionally, the table should be made scrollable using CSS or JavaScript, and the appropriate ARIA attributes should be added to indicate that the content is scrollable.",
   "div_role": "The issue with the code snippet is that it uses the `role` attribute to indicate that the `div` element is a listbox, but it does not provide any keyboard accessibility for users who cannot use a mouse. To fix this, the `div` element should also have the `tabindex` attribute set to 0 and have keyboard event listeners added to allow keyboard users to navigate and select items in the listbox. The correct version of the code snippet is:\n\n<div role=\"listbox\" tabindex=\"0\" onkeydown=\"handleListboxKeyDown(event)\">\n  <div role=\"option\" aria-selected=\"false\">Option 1</div>\n  <div role=\"option\" aria-selected=\"false\">Option 2</div>\n  <div role=\"option\" aria-selected=\"false\">Option 3</div>\n</div>",
-  "body": "The issue with the code snippet is that it does not include any scrollable content that can be accessed by keyboard. To make the content accessible, the code should include proper HTML tags and attributes such as `aria-label`, `role`, and `tabindex`. Here is an example of an accessible code snippet:\n\n<body>\n  <div role=\"region\" aria-label=\"Scrollable Content\" tabindex=\"0\">\n    <p>Content goes here</p>\n  </div>\n</body>"
+  "body": "The issue with the code snippet is that it does not include any scrollable content that can be accessed by keyboard. To make the content accessible, the code should include proper HTML tags and attributes such as `aria-label`, `role`, and `tabindex`. Here is an example of an accessible code snippet:\n\n<body>\n  <div role=\"region\" aria-label=\"Scrollable Content\" tabindex=\"0\">\n    <p>Content goes here</p>\n  </div>\n</body>",
+  "html_lang": "Issue: The scrollable content is not accessible by keyboard, which means users who rely on keyboard navigation will not be able to access the content.\n\nCorrected code snippet:\n\n<`html` `lang`=\"en\">\n  <`div` role=\"region\" aria-label=\"Scrollable Content\">\n    <`div` tabindex=\"0\">\n      <!-- content here -->\n    </`div`>\n  </`div`>\n</`html`>\n\nExplanation: \n\n- The `role=\"region\"` attribute is added to the `div` element to indicate that it contains a section of content that may be of interest to the user.\n- The `aria-label` attribute is added to provide a descriptive label for the region of content.\n- The `tabindex=\"0\"` attribute is added to make the `div` element focusable by keyboard. This allows users to navigate to the element using the tab key and access the scrollable content using arrow keys."
 }
diff --git a/results/select-name.json b/results/select-name.json
index fb0b1f2..cccaec8 100644
--- a/results/select-name.json
+++ b/results/select-name.json
@@ -8,5 +8,6 @@
   "select_aria-describedby_name": "The issue with this code snippet is that it uses the `aria-describedby` attribute to provide a description for the select element instead of using an accessible name. This can cause issues for users who rely on screen readers or other assistive technologies to navigate the web.\n\nThe correct version of the code snippet should include an accessible name for the select element using the `aria-label` or `aria-labelledby` attribute. For example:\n\n<`select` `aria-label`=\"Select an option\" `name`=\"...\"> \n\nor \n\n<`select` `aria-labelledby`=\"label-id\" `name`=\"...\">\n  <`option` `value`=\"...\">...</`option`>\n</`select`>\n<`label` `id`=\"label-id\">Select an option:</`label`>",
   "select_formcontrolname": "The issue with this code snippet is that it is missing an accessible name for the select element, which can make it difficult for users with disabilities to understand its purpose. The correct version of the code snippet should include an accessible name using the `aria-label` or `aria-labelledby` attributes, like this:\n\n<select formcontrolname=\"eligibilityOption\" aria-label=\"Eligibility Options\">\n  ...\n</select>\n\nor\n\n<label for=\"eligibilityOption\">Eligibility Options:</label>\n<select id=\"eligibilityOption\" name=\"eligibilityOption\" formcontrolname=\"eligibilityOption\" aria-labelledby=\"eligibilityOption\">\n  ...\n</select>",
   "select_name_style": "The issue with this code snippet is that it does not have an accessible name for the select element, which can make it difficult for users with disabilities to understand its purpose. To fix this, the engineer should add a label element that associates with the select element and provides a clear description of its purpose. The corrected code snippet would look like this:\n\n<label for=\"select-element\">Select an option:</label>\n<select id=\"select-element\" name=\"select-element\" style=\"width:165px\">\n  <option value=\"option1\">Option 1</option>\n  <option value=\"option2\">Option 2</option>\n  <option value=\"option3\">Option 3</option>\n</select>",
-  "select_formcontrolname_name": "The issue with this code snippet is that the `name` attribute is left incomplete, which means that the select element does not have an accessible name. To fix this issue, the `name` attribute should be completed with a descriptive name for the select element, like so:\n\n<`select` `formcontrolname`=\"foreignCountry\" `name`=\"countrySelection\">"
+  "select_formcontrolname_name": "The issue with this code snippet is that the `name` attribute is left incomplete, which means that the select element does not have an accessible name. To fix this issue, the `name` attribute should be completed with a descriptive name for the select element, like so:\n\n<`select` `formcontrolname`=\"foreignCountry\" `name`=\"countrySelection\">",
+  "select_aria-label": "Issue: The `select` element does not have an accessible name.\n\nCorrected version: `<select aria-label=\"Descriptive label for the purpose of the select element\">`"
 }