@markuplint/html-spec 5.0.0-alpha.3 → 5.0.0-dev.5

package/index.json

@@ -5202,7 +5202,7 @@
 					},
 					{
 						"name": "group",
-						"description": "A set of user interface objects that is not intended to be included in a page summary or table of contents by assistive technologies.\n\nContrast with region, which is a grouping of user interface objects that will be included in a page summary or table of contents.\n\nAuthors SHOULD use a group to form a logical collection of items in a widget, such as children in a tree widget forming a collection of siblings in a hierarchy. However, when a group is used in the context of a listbox, for example, authors MUST limit its children to option elements. Therefore, proper handling of group by authors and assistive technologies is determined by the context in which it is provided.\n\nAuthors MAY nest group elements. If a section is significant enough to warrant inclusion in the web page's table of contents, the author SHOULD assign it a role of region or a standard landmark role.",
+						"description": "A set of user interface objects and information that is not intended to be included in a page summary or table of contents by assistive technologies.\n\nContrast with region, which is a grouping of user interface objects and information that will be included in a page summary or table of contents.\n\nAuthors SHOULD use a group to form a logical collection of items in a widget, such as children in a tree widget forming a collection of siblings in a hierarchy. However, when a group is used in the context of a listbox, for example, authors MUST limit its children to option elements. Therefore, proper handling of group by authors and assistive technologies is determined by the context in which it is provided.\n\nAuthors MAY nest group elements. If a section is significant enough to warrant inclusion in the web page's table of contents, the author SHOULD assign it a role of region or a standard landmark role.",
 						"generalization": ["section"],
 						"requiredContextRole": [],
 						"requiredOwnedElements": [],
@@ -8707,7 +8707,7 @@
 					},
 					{
 						"name": "radiogroup",
-						"description": "A group of radio buttons.\n\nA radiogroup is a type of select list that can only have a single entry checked at any one time. Authors SHOULD enforce that only one radio button in a group can be checked at the same time. When one item in the group is checked, the previously checked item becomes unchecked (its aria-checked attribute becomes false).\n\nAuthors SHOULD provide an accessible name for a radiogroup, which can be done with the aria-label or aria-labelledby attribute. Authors SHOULD reference a visible label with aria-labelledby if a visible label is present for the radiogroup.",
+						"description": "A group of radio buttons.\n\nA radiogroup is a type of select list that can only have a single entry checked at any one time. Authors SHOULD enforce that only one radio button in a group can be checked at the same time. When one item in the group is checked, the previously checked item becomes unchecked (its aria-checked attribute becomes false).\n\nAuthors SHOULD provide an accessible name for a radiogroup, which can be done with the aria-label or aria-labelledby attribute. Authors SHOULD reference a visible label with aria-labelledby if a visible label is present for the radiogroup.\n\nWhile a radiogroup is primarily meant to group and thus associate related radio buttons, a radiogroup can contain other non-radio button elements. For instance, descriptive text beyond what serves as the radio button's label, or even in some cases, form controls or other information that are enabled, revealed or both when a specific radio button has been chosen (checked).\n\nHowever, including non-radio button content into a radiogroup is not without its potential UX drawbacks. As it is generally expected to use arrow keys to navigate between radio buttons, any non-radio button content could go unnoticed by some users, as arrowing through the radio buttons would mean that any other tabbable elements (e.g., hyperlinks or other form fields) would be skipped. When creating a radiogroup with other arbitrary content, consider if the non-radio content could be just as impactful if it was presented as an immediate sibling after the radiogroup.",
 						"generalization": ["select"],
 						"requiredContextRole": [],
 						"requiredOwnedElements": [],

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@markuplint/html-spec",
-	"version": "5.0.0-alpha.3",
+	"version": "5.0.0-dev.5+e96392f56",
 	"description": "A specification of HTML Living Standard for markuplint",
 	"repository": "git@github.com:markuplint/markuplint.git",
 	"author": "Yusuke Hirao <yusukehirao@me.com>",
@@ -29,12 +29,12 @@
 		"gen:prettier": "npx prettier --write index.json"
 	},
 	"devDependencies": {
-		"@markuplint/spec-generator": "5.0.0-alpha.3",
+		"@markuplint/spec-generator": "5.0.0-dev.5+e96392f56",
 		"@markuplint/test-tools": "5.0.0-alpha.3",
 		"jsonc-parser": "3.3.1"
 	},
 	"dependencies": {
-		"@markuplint/ml-spec": "5.0.0-alpha.3"
+		"@markuplint/ml-spec": "5.0.0-dev.5+e96392f56"
 	},
-	"gitHead": "2fbdf26daa3d021ac628ccc2f59f0eeae6ddd53d"
+	"gitHead": "e96392f56e4bc8165ba59622b41c822703a96372"
 }