@adobe/spectrum-design-data 0.0.0-size-token-taxonomy-20260929225107

package/components/calendar.json

@@ -0,0 +1,196 @@
+{
+  "$schema": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/component.schema.json",
+  "$id": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/components/calendar.json",
+  "specVersion": "1.0.0-draft",
+  "name": "calendar",
+  "displayName": "Calendar",
+  "description": "Calendars display days, weeks, and months, allowing users to select dates or ranges.",
+  "meta": {
+    "category": "inputs",
+    "documentationUrl": "https://spectrum.adobe.com/page/calendar/"
+  },
+  "documentBlocks": [
+    {
+      "type": "purpose",
+      "content": "Calendars display days, weeks, and months, allowing users to select dates or ranges."
+    },
+    {
+      "type": "guideline",
+      "content": "Calendars display the days of a selected month and highlight the current day. They support navigating to past or future months and selecting a specific date."
+    },
+    {
+      "type": "guideline",
+      "content": "An array of days that are displayed in the current calendar view. This includes:"
+    },
+    {
+      "type": "guideline",
+      "content": "The maximum amount of months displayed in the calendar popover is three."
+    },
+    {
+      "type": "guideline",
+      "content": "The minimum amount of months displayed in the calendar popover is one."
+    },
+    {
+      "type": "guideline",
+      "content": "The calendar popover may display an error as error text when a user attempts to provide an input that violates the defined constraints of the date selection. For example, when the user selects dates that fall outside allowable limits, or conflict with contextual restrictions."
+    },
+    {
+      "type": "guideline",
+      "content": "The calendar popover is disabled. For example, a month within a three-month range is disabled."
+    },
+    {
+      "type": "guideline",
+      "content": "The types of selection available for the calendar."
+    },
+    {
+      "type": "guideline",
+      "content": "The current year or month displayed in the calendar popover."
+    },
+    {
+      "type": "guideline",
+      "content": "When a day or several days are unavailable within the calendar popover, each day should display a strikethrough to help the user understand that they cannot select it."
+    },
+    {
+      "type": "guideline",
+      "content": "Disabled days use a distinct gray style to clearly differentiate them from unavailable days. When the calendar prevents selection of past dates, this visual treatment helps users distinguish disabled days from those marked as unavailable."
+    },
+    {
+      "type": "guideline",
+      "content": "In a date selection system, users often need to distinguish between dates that cannot be selected and dates that are simply inactive. Supporting both states improves clarity and prevents errors."
+    },
+    {
+      "type": "guideline",
+      "content": "Here’s an example scenario: A potential guest is browsing a calendar to book a stay at a vacation rental."
+    },
+    {
+      "type": "guideline",
+      "content": "Unavailable dates: Days when the rental is already booked or blocked by the owner. These appear with a strikethrough, indicating they cannot be selected."
+    },
+    {
+      "type": "guideline",
+      "content": "Disabled dates: Past dates that are no longer valid for booking. These appear visually distinct (gray style) to show they are inactive."
+    },
+    {
+      "type": "guideline",
+      "content": "Guests see unavailable dates marked clearly so they don’t attempt to select them. Hosts or admins can view past dates as disabled and also mark future dates as unavailable when needed."
+    },
+    {
+      "type": "guideline",
+      "content": "By supporting both behaviors, the system provides a clear, intuitive experience for different user roles and prevents confusion during date selection."
+    },
+    {
+      "type": "guideline",
+      "content": "The range fill shows which days fall between two selected dates. If the range spans more than the three-month calendar view, it ends on the last visible day but continues as users navigate with the calendar chevrons. A dashed stroke outlines the fill to improve visibility on bright screens and for users with vision impairments."
+    },
+    {
+      "type": "guideline",
+      "content": "The strikethrough styling intentionally accommodates internationalization."
+    },
+    {
+      "type": "guideline",
+      "content": "The calendar popover supports a disabled state but not a read-only state. Dates or months may be temporarily disabled based on context (for example, if a user must complete a task before selecting a date). In these cases, help text can explain why certain dates are unavailable."
+    },
+    {
+      "type": "guideline",
+      "content": "If a date picker is truly read-only, users shouldn’t be able to open the calendar popover at all, since they can’t interact with it."
+    },
+    {
+      "type": "guideline",
+      "content": "The calendar popover can also include time-specific fields, allowing users to specify start and end times."
+    }
+  ],
+  "options": {
+    "currentMonth": {
+      "type": "number",
+      "minimum": 1,
+      "maximum": 12,
+      "description": "The month currently displayed in the calendar (1 = January, 12 = December)."
+    },
+    "currentYear": {
+      "type": "number",
+      "description": "The year currently displayed in the calendar (Gregorian year number)."
+    },
+    "selectionMode": {
+      "type": "string",
+      "default": "single",
+      "description": "Controls whether the calendar allows selecting a single date or a date range.",
+      "values": [{ "value": "single" }, { "value": "range" }]
+    },
+    "isDisabled": { "type": "boolean", "default": false },
+    "isError": { "type": "boolean", "default": false },
+    "minValue": {
+      "type": "string",
+      "description": "The minimum allowed date that a user may select (ISO format string)."
+    },
+    "maxValue": {
+      "type": "string",
+      "description": "The maximum allowed date that a user may select (ISO format string)."
+    },
+    "showTimeZone": {
+      "type": "boolean",
+      "default": false,
+      "description": "Whether to show a time zone indicator in the calendar."
+    },
+    "days": {
+      "type": "array",
+      "description": "An array of days displayed in the current calendar view.",
+      "items": {
+        "type": "object",
+        "properties": {
+          "date": {
+            "type": "string",
+            "description": "The date represented by this day (ISO format string)."
+          },
+          "isDisabled": {
+            "type": "boolean",
+            "default": false,
+            "description": "Whether this day is disabled."
+          },
+          "isSelected": {
+            "type": "boolean",
+            "default": false,
+            "description": "Whether this day is currently selected."
+          },
+          "isRangeStart": {
+            "type": "boolean",
+            "default": false,
+            "description": "Whether this day is the start of a selected range."
+          },
+          "isRangeEnd": {
+            "type": "boolean",
+            "default": false,
+            "description": "Whether this day is the end of a selected range."
+          },
+          "isUnavailable": {
+            "type": "boolean",
+            "default": false,
+            "description": "Whether this day is unavailable for selection. If true, the day appears with a strikethrough."
+          },
+          "isToday": {
+            "type": "boolean",
+            "default": false,
+            "description": "Whether this day represents the current date."
+          },
+          "state": {
+            "type": "string",
+            "enum": ["default", "hover", "keyboard focus"],
+            "default": "default",
+            "description": "The interaction state of the day cell."
+          }
+        },
+        "required": ["date"]
+      }
+    }
+  },
+  "lifecycle": { "introduced": "1.0.0-draft" },
+  "accessibility": {
+    "intents": ["input", "choose"],
+    "focusable": true,
+    "keyboardIntents": ["navigate-items", "activate"],
+    "wcag": [
+      { "criterion": "1.3.1", "level": "A", "title": "Info and Relationships" },
+      { "criterion": "2.1.1", "level": "A", "title": "Keyboard" },
+      { "criterion": "4.1.2", "level": "A", "title": "Name, Role, Value" }
+    ]
+  }
+}

package/components/card-horizontal.json

@@ -0,0 +1,14 @@
+{
+  "$schema": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/component.schema.json",
+  "$id": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/components/card-horizontal.json",
+  "specVersion": "1.0.0-draft",
+  "name": "card-horizontal",
+  "displayName": "Horizontal card",
+  "description": "A card variant laid out horizontally, pairing a preview with content side by side.",
+  "meta": {
+    "category": "containers",
+    "documentationUrl": "https://spectrum.adobe.com/page/card-horizontal/"
+  },
+  "states": [{ "name": "default" }],
+  "lifecycle": { "introduced": "1.0.0-draft" }
+}

package/components/card.json

@@ -0,0 +1,22 @@
+{
+  "$schema": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/component.schema.json",
+  "$id": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/components/card.json",
+  "specVersion": "1.0.0-draft",
+  "name": "card",
+  "displayName": "Card",
+  "description": "A single card surface used to group related content and actions; the base of the cards family (cards.json documents the group).",
+  "meta": {
+    "category": "containers",
+    "documentationUrl": "https://spectrum.adobe.com/page/card/"
+  },
+  "anatomy": [
+    { "name": "selection" },
+    { "name": "well" },
+    {
+      "name": "preview",
+      "description": "Preview area or thumbnail within the card."
+    }
+  ],
+  "states": [{ "name": "default" }],
+  "lifecycle": { "introduced": "1.0.0-draft" }
+}

package/components/cards.json

@@ -0,0 +1,117 @@
+{
+  "$schema": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/component.schema.json",
+  "$id": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/components/cards.json",
+  "specVersion": "1.0.0-draft",
+  "name": "cards",
+  "displayName": "Cards",
+  "description": "Cards group related content into distinct layouts depending on context.",
+  "meta": {
+    "category": "containers",
+    "documentationUrl": "https://spectrum.adobe.com/page/cards/"
+  },
+  "documentBlocks": [
+    {
+      "type": "purpose",
+      "content": "Cards group related content into distinct layouts depending on context."
+    },
+    {
+      "type": "guideline",
+      "content": "Cards group related content and actions into flexible containers for browsing. They preview key information and reveal more detail on interaction."
+    },
+    {
+      "type": "guideline",
+      "content": "Card preview areas have a maximum image height aspect ratio of 3:4, and a minimum height aspect ratio of of 4:1."
+    },
+    {
+      "type": "guideline",
+      "content": "If the card has a fixed height, such as in a tile grid, long titles will be truncated. Use short titles to avoid this. In layouts with variable height, like a waterfall grid, titles will wrap to fit."
+    },
+    {
+      "type": "guideline",
+      "content": "Cards, by definition, should have some form of interaction such as viewing, editing, purchasing, etc. Some actions are exposed in buttons, and others simply occur by clicking the card."
+    },
+    {
+      "type": "guideline",
+      "content": "If a card only has an ability to be opened or viewed in more detail, do not include a button. Clicking anywhere on the card should perform that action."
+    },
+    {
+      "type": "guideline",
+      "content": "If a card has other interactive elements such as a hidden actions menu or an avatar, but no buttons, the whole card (outside of those elements) should be clickable."
+    },
+    {
+      "type": "guideline",
+      "content": "If there’s only one action (that’s not opening or viewing the card), use a button to communicate that action. If there are two or more available actions, and one of those actions is to open or view the card, use a button to communicate “View” or “Open,” instead of relying on clicking on the card."
+    },
+    {
+      "type": "guideline",
+      "content": "If a standard card has a footer with a button, only the button is clickable. If a card has a preview, clicking the preview will open that card. When a preview is purely decorative, it is not clickable."
+    },
+    {
+      "type": "guideline",
+      "content": "When a group of cards are loading, they follow the ghost loading convention. There are 5 phases for ghost loading:"
+    },
+    {
+      "type": "guideline",
+      "content": "Cards are meant to just show a taste of the available information. Don’t overload cards with more information than necessary."
+    },
+    {
+      "type": "guideline",
+      "content": "Only standard cards can have a footer, and buttons can only appear inside a footer."
+    },
+    {
+      "type": "guideline",
+      "content": "Individual cards are not aligned to individual columns in the page's responsive column grid. Instead, groups of cards are aligned to the column grid in a layout region."
+    },
+    {
+      "type": "guideline",
+      "content": "If the preview is a video clip or other moving item, do not automatically play the clip or motion. Save the movement for either when a user hovers on the card or when they click on a play button."
+    }
+  ],
+  "options": {
+    "variant": {
+      "type": "string",
+      "default": "asset",
+      "description": "Determines which card layout variant is used.",
+      "values": [
+        {
+          "value": "asset"
+        },
+        {
+          "value": "collection"
+        },
+        {
+          "value": "flex"
+        },
+        {
+          "value": "gallery"
+        },
+        {
+          "value": "horizontal"
+        },
+        {
+          "value": "product"
+        }
+      ]
+    }
+  },
+  "lifecycle": {
+    "introduced": "1.0.0-draft"
+  },
+  "accessibility": {
+    "intents": ["select"],
+    "focusable": true,
+    "keyboardIntents": ["activate"],
+    "wcag": [
+      {
+        "criterion": "2.1.1",
+        "level": "A",
+        "title": "Keyboard"
+      },
+      {
+        "criterion": "4.1.2",
+        "level": "A",
+        "title": "Name, Role, Value"
+      }
+    ]
+  }
+}

package/components/checkbox-group.json

@@ -0,0 +1,128 @@
+{
+  "$schema": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/component.schema.json",
+  "$id": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/components/checkbox-group.json",
+  "specVersion": "1.0.0-draft",
+  "name": "checkbox-group",
+  "displayName": "Checkbox group",
+  "description": "A checkbox group is a grouping of checkboxes that are related to each other.",
+  "meta": {
+    "category": "inputs",
+    "documentationUrl": "https://spectrum.adobe.com/page/checkbox-group/"
+  },
+  "documentBlocks": [
+    {
+      "type": "purpose",
+      "content": "A checkbox group is a grouping of checkboxes that are related to each other."
+    },
+    {
+      "type": "guideline",
+      "content": "When a description is present and an error is triggered, it is replaced with an error message. Once the error is resolved, the help text description reappears."
+    },
+    {
+      "type": "guideline",
+      "content": "A checkbox group in a disabled state shows that a selection exists, but is not available in that circumstance. This can be used to maintain layout continuity and communicate that an action may become available later. The field label, checkboxes, and help text are all displayed in a disabled state when the checkbox group is disabled."
+    },
+    {
+      "type": "guideline",
+      "content": "Checkbox groups can be either horizontal or vertical. By default, checkbox groups are stacked vertically. Use a horizontal checkbox group when vertical space is limited."
+    },
+    {
+      "type": "guideline",
+      "content": "Checkbox groups can be marked as optional or required, depending on the situation. Optional checkbox groups are either denoted with text added to the end of the label — “(optional)” — or have no indication at all."
+    },
+    {
+      "type": "guideline",
+      "content": "For required checkbox groups, there are two necessity indicator options: a “(required)” label or an asterisk. If you use an asterisk, be sure to include help text to explain what the asterisk means."
+    },
+    {
+      "type": "guideline",
+      "content": "The asterisk used in this component is an icon that has specific spacing from the label text — not part of the label text itself."
+    },
+    {
+      "type": "guideline",
+      "content": "Labels can be placed either on top or on the side. Top labels are the default and are recommended because they work better with long copy, localization, and responsive layouts. Side labels are most useful when vertical space is limited."
+    },
+    {
+      "type": "guideline",
+      "content": "Checkbox groups should always have a label. In rare cases where context is sufficient and an accessibility expert has reviewed the design, the label could be undefined. These checkbox groups without a visible label should still include an aria-label in HTML (depending on the context, “aria-label” or “aria-labelledby”)."
+    }
+  ],
+  "options": {
+    "label": {
+      "type": "string"
+    },
+    "labelPosition": {
+      "type": "string",
+      "default": "top",
+      "values": [
+        {
+          "value": "top"
+        },
+        {
+          "value": "side"
+        }
+      ]
+    },
+    "necessityIndicator": {
+      "type": "string",
+      "default": "icon",
+      "values": [
+        {
+          "value": "text"
+        },
+        {
+          "value": "icon"
+        }
+      ]
+    },
+    "isRequired": {
+      "type": "boolean",
+      "default": false
+    },
+    "orientation": {
+      "type": "string",
+      "default": "vertical",
+      "values": [
+        {
+          "value": "horizontal"
+        },
+        {
+          "value": "vertical"
+        }
+      ]
+    },
+    "isError": {
+      "type": "boolean",
+      "default": false
+    },
+    "isDisabled": {
+      "type": "boolean",
+      "default": false
+    },
+    "description": {
+      "type": "string"
+    },
+    "errorMessage": {
+      "type": "string"
+    }
+  },
+  "lifecycle": {
+    "introduced": "1.0.0-draft"
+  },
+  "accessibility": {
+    "intents": ["choose"],
+    "focusable": false,
+    "wcag": [
+      {
+        "criterion": "1.3.1",
+        "level": "A",
+        "title": "Info and Relationships"
+      },
+      {
+        "criterion": "4.1.2",
+        "level": "A",
+        "title": "Name, Role, Value"
+      }
+    ]
+  }
+}

package/components/checkbox.json

@@ -0,0 +1,171 @@
+{
+  "$schema": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/component.schema.json",
+  "$id": "https://opensource.adobe.com/spectrum-design-data/schemas/v0/components/checkbox.json",
+  "specVersion": "1.0.0-draft",
+  "name": "checkbox",
+  "displayName": "Checkbox",
+  "description": "Checkboxes allow users to select multiple items from a list of individual items, or to mark one individual item as selected.",
+  "meta": {
+    "category": "inputs",
+    "documentationUrl": "https://spectrum.adobe.com/page/checkbox/"
+  },
+  "documentBlocks": [
+    {
+      "type": "purpose",
+      "content": "Checkboxes allow users to select multiple items from a list of individual items, or to mark one individual item as selected."
+    },
+    {
+      "type": "guideline",
+      "content": "Checkboxes support selecting one or more items from a list. Each item can be selected independently or in combination with others."
+    },
+    {
+      "type": "guideline",
+      "content": "Checkboxes can be marked as having an error to show that a selection needs to be made in order to move forward, or that a selection that was made is invalid. For example, in a form that requires a user to acknowledge legal terms before proceeding, the checkbox would show an unchecked error to communicate that it needs to be selected."
+    },
+    {
+      "type": "guideline",
+      "content": "A checkbox in a disabled state shows that a selection exists, but is not available in that circumstance. This can be used to maintain layout continuity and communicate that an action may become available later."
+    },
+    {
+      "type": "guideline",
+      "content": "By default, checkboxes are not emphasized (gray). This version is optimal for when the checkbox is not the core part of an interface, such as in application panels, where all visual components are monochrome in order to direct focus to the content."
+    },
+    {
+      "type": "guideline",
+      "content": "The emphasized (blue) version provides a visual prominence that is optimal for forms, settings, lists or grids of assets, and other situations where a checkbox need to be noticed."
+    },
+    {
+      "type": "guideline",
+      "content": "Checkboxes come in four different sizes: small, medium, large, and extra-large. The medium size is the default and most frequently used option. Use the other sizes sparingly; they should be used to create a hierarchy of importance within the page."
+    },
+    {
+      "type": "guideline",
+      "content": "Checkboxes can be in an indeterminate state when they represent both selected and not selected values."
+    },
+    {
+      "type": "guideline",
+      "content": "Checkboxes can be selected or not selected."
+    },
+    {
+      "type": "guideline",
+      "content": "Checkboxes should always have a label. When the label is not defined, a checkbox becomes standalone. Standalone checkboxes are only used when their connection to other components is clear and they give sufficient context — for example, in application panels."
+    },
+    {
+      "type": "guideline",
+      "content": "A checkbox can be navigated using a keyboard. The keyboard focus state takes the checkbox’s visual hover state and adds a blue ring to the checkbox in focus."
+    },
+    {
+      "type": "guideline",
+      "content": "When the label is too long for the horizontal space available, it wraps to form another line."
+    },
+    {
+      "type": "guideline",
+      "content": "Emphasized checkboxes are optimal for forms, settings, etc. where the checkboxes need to be noticed, or to bring attention to selected items such as cards or table rows. Not emphasized checkboxes are optimal for application panels where all the visual components are monochrome in order to direct focus to the canvas."
+    },
+    {
+      "type": "guideline",
+      "content": "Standalone checkboxes should be used in situations where the context is clear without an associated text label. An example of this would be when a checkbox is connected to other controls inside of a panel."
+    },
+    {
+      "type": "guideline",
+      "content": "Checkboxes and radio buttons are not interchangeable. A set of checkboxes should be used to select as many options as desired (or none). A set of radio buttons should be used to select only a single option from a list of mutually exclusive options."
+    },
+    {
+      "type": "guideline",
+      "content": "Use checkboxes to show selection, such as choosing multiple table rows. Use switches to show activation, like turning a setting on or off. Unlike switches, checkboxes can display an error state."
+    },
+    {
+      "type": "guideline",
+      "content": "Sets of checkboxes should always have a clear label that describes what the list of options represents and guides users what to do. This is important for accessibility, since a screen reader will read the label before each option."
+    },
+    {
+      "type": "guideline",
+      "content": "When a checkbox represents multiple values that are not identical, the checkbox should appear in the indeterminate state. Any subsequent click or tap should select the checkbox, and update all values to be selected. Another click or tap after that should deselect the checkbox, and update all values to be not selected."
+    }
+  ],
+  "options": {
+    "label": {
+      "type": "string",
+      "description": "When the label is not defined, the checkbox appears as a standalone checkbox."
+    },
+    "isSelected": {
+      "type": "boolean",
+      "default": false
+    },
+    "isIndeterminate": {
+      "type": "boolean",
+      "default": false,
+      "description": "When a checkbox is indeterminate, it overrides the selection state."
+    },
+    "size": {
+      "type": "string",
+      "default": "m",
+      "values": [
+        {
+          "value": "s"
+        },
+        {
+          "value": "m"
+        },
+        {
+          "value": "l"
+        },
+        {
+          "value": "xl"
+        }
+      ]
+    },
+    "isEmphasized": {
+      "type": "boolean",
+      "default": false
+    },
+    "isDisabled": {
+      "type": "boolean",
+      "default": false
+    },
+    "isError": {
+      "type": "boolean",
+      "default": false
+    }
+  },
+  "states": [
+    {
+      "name": "hover",
+      "trigger": "interaction"
+    },
+    {
+      "name": "down",
+      "trigger": "interaction"
+    },
+    {
+      "name": "keyboard-focus",
+      "trigger": "interaction"
+    }
+  ],
+  "lifecycle": {
+    "introduced": "1.0.0-draft"
+  },
+  "accessibility": {
+    "role": "checkbox",
+    "intents": ["choose"],
+    "focusable": true,
+    "keyboardIntents": ["activate"],
+    "wcag": [
+      {
+        "criterion": "1.3.1",
+        "level": "A",
+        "title": "Info and Relationships"
+      },
+      {
+        "criterion": "2.1.1",
+        "level": "A",
+        "title": "Keyboard"
+      },
+      {
+        "criterion": "4.1.2",
+        "level": "A",
+        "title": "Name, Role, Value"
+      }
+    ]
+  }
+}