@adobe/spectrum-design-data 3.3.0-beta.2 → 3.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/components/accordion.json +17 -35
- package/components/action-bar.json +7 -0
- package/components/action-button.json +16 -3
- package/components/action-group.json +8 -0
- package/components/alert-dialog.json +14 -3
- package/components/avatar-group.json +11 -15
- package/components/avatar.json +15 -18
- package/components/badge.json +15 -2
- package/components/breadcrumbs.json +7 -0
- package/components/button-group.json +16 -3
- package/components/button.json +16 -3
- package/components/calendar.json +7 -0
- package/components/card.json +13 -0
- package/components/cards.json +4 -4
- package/components/checkbox-group.json +10 -3
- package/components/checkbox.json +10 -3
- package/components/close-button.json +16 -3
- package/components/color-area.json +7 -0
- package/components/color-handle.json +8 -0
- package/components/color-loupe.json +16 -4
- package/components/color-slider.json +7 -0
- package/components/color-wheel.json +7 -0
- package/components/combo-box.json +10 -3
- package/components/contextual-help.json +10 -3
- package/components/date-field.json +7 -0
- package/components/date-picker.json +7 -0
- package/components/divider.json +15 -2
- package/components/drop-zone.json +10 -3
- package/components/field-label.json +7 -3
- package/components/heading.json +7 -0
- package/components/help-text.json +3 -3
- package/components/illustrated-message.json +13 -0
- package/components/link.json +10 -3
- package/components/list-view.json +7 -0
- package/components/menu.json +10 -3
- package/components/meter.json +16 -3
- package/components/number-field.json +7 -0
- package/components/picker.json +10 -3
- package/components/popover.json +16 -3
- package/components/progress-bar.json +16 -3
- package/components/progress-circle.json +16 -3
- package/components/radio-group.json +10 -3
- package/components/search-field.json +10 -3
- package/components/segmented-control.json +10 -3
- package/components/select-box.json +7 -0
- package/components/side-navigation.json +3 -3
- package/components/slider.json +10 -3
- package/components/status-light.json +15 -2
- package/components/swatch-group.json +3 -3
- package/components/swatch.json +3 -3
- package/components/switch.json +14 -3
- package/components/table.json +3 -3
- package/components/tabs.json +16 -3
- package/components/tag-group.json +10 -3
- package/components/tag.json +10 -3
- package/components/text-area.json +10 -3
- package/components/text-field.json +11 -4
- package/components/time-field.json +7 -0
- package/components/toast.json +11 -7
- package/components/tooltip.json +16 -3
- package/components/tree-view.json +10 -3
- package/components/user-card.json +7 -0
- package/fields/structure.json +1 -2
- package/guidelines/ai-resource-guide.json +7 -15
- package/guidelines/app-frame-overview.json +24 -25
- package/guidelines/applying-the-type-system.json +15 -11
- package/guidelines/attention-hierarchy.json +3 -3
- package/guidelines/background-layers.json +20 -16
- package/guidelines/bi-directionality.json +9 -9
- package/guidelines/border-width.json +18 -6
- package/guidelines/brand.json +9 -17
- package/guidelines/cognitive.json +32 -0
- package/guidelines/colors.json +23 -15
- package/guidelines/component-spacing.json +12 -8
- package/guidelines/contact-us.json +1 -41
- package/guidelines/containers.json +21 -28
- package/guidelines/content-area-browsing-context.json +20 -12
- package/guidelines/creating-bluelines-browsing-context.json +9 -29
- package/guidelines/design-tokens.json +47 -19
- package/guidelines/developer-overview.json +8 -0
- package/guidelines/drop-shadow.json +14 -6
- package/guidelines/faqs.json +4 -0
- package/guidelines/fonts.json +6 -2
- package/guidelines/grammar-and-mechanics.json +69 -45
- package/guidelines/grays.json +5 -5
- package/guidelines/header-browsing-context.json +6 -6
- package/guidelines/icon-fundamentals.json +5 -5
- package/guidelines/illustration.json +41 -26
- package/guidelines/in-product-word-list.json +2 -6
- package/guidelines/inclusive-design.json +8 -8
- package/guidelines/inclusive-ux-writing.json +6 -2
- package/guidelines/internationalization.json +31 -15
- package/guidelines/layout-spacing.json +5 -5
- package/guidelines/manifest.json +46 -134
- package/guidelines/motion.json +9 -5
- package/guidelines/object-styles-overview.json +2 -2
- package/guidelines/principles.json +2 -2
- package/guidelines/resources.json +8 -0
- package/guidelines/rounding.json +19 -7
- package/guidelines/side-navigation-browsing-context.json +16 -16
- package/guidelines/spacing-overview.json +44 -11
- package/guidelines/states.json +4 -4
- package/guidelines/support.json +13 -1
- package/guidelines/typography-overview.json +5 -9
- package/guidelines/typography-system.json +39 -35
- package/guidelines/using-icons.json +19 -23
- package/guidelines/voice-and-tone.json +8 -4
- package/guidelines/whats-new.json +4 -15
- package/guidelines/writing-about-people.json +12 -16
- package/guidelines/writing-for-errors.json +41 -21
- package/guidelines/writing-for-onboarding.json +22 -18
- package/guidelines/writing-for-readability.json +17 -5
- package/guidelines/writing-with-visuals.json +19 -11
- package/package.json +2 -2
- package/registry/platform-implementations.json +30 -0
- package/tokens/layout.tokens.json +88 -0
- package/guidelines/content-design-grammar-and-mechanics.json +0 -241
- package/guidelines/content-design-voice-and-tone.json +0 -37
- package/guidelines/content-grammar-and-mechanics.json +0 -252
- package/guidelines/content-language-and-inclusivity-writing-about-people.json +0 -103
- package/guidelines/content-language-and-inclusivity-writing-with-visuals.json +0 -70
- package/guidelines/content-voice-and-tone.json +0 -47
- package/guidelines/language-and-inclusivity-writing-about-people.json +0 -85
- package/guidelines/language-and-inclusivity-writing-with-visuals.json +0 -61
- package/guidelines/layout-and-structure-containers.json +0 -47
- package/guidelines/layout-and-structure-spacing-overview.json +0 -66
- package/guidelines/visual-language-containers.json +0 -36
- package/registry/platform-extensions/web-components-states.json +0 -58
|
@@ -8,15 +8,19 @@
|
|
|
8
8
|
{ "type": "purpose", "content": "Applying the type system" },
|
|
9
9
|
{
|
|
10
10
|
"type": "guideline",
|
|
11
|
-
"content": "
|
|
11
|
+
"content": "The following are some general examples to show how the Spectrum 2 typography system all comes together, and how type styles can be used together to create visual hierarchy."
|
|
12
12
|
},
|
|
13
13
|
{
|
|
14
14
|
"type": "guideline",
|
|
15
|
-
"content": "Card
|
|
15
|
+
"content": "Image: Card example with numbered callouts: 1) \"Card title\" labeled as the Title style, and 2) \"Card description\" labeled as the Body style, over a colorful gradient image. (source: https://spectrum.adobe.com/foundations/typography/media_18dd0601a7059dd3b917ba5cc09fa50cfc5e3786e.png?width=750&format=png&optimize=medium)"
|
|
16
16
|
},
|
|
17
17
|
{
|
|
18
18
|
"type": "guideline",
|
|
19
|
-
"content": "
|
|
19
|
+
"content": "Card.\n\nIn this card example, Title and Body text styles are used together to establish a clear visual hierarchy, helping users quickly identify the primary content while keeping supporting information easy to scan. Title S The card title uses the Title style to establish the primary focus of the card. It provides strong visual emphasis, making it easy for users to quickly identify and scan content across multiple cards. Body XS The supporting description uses the Body style because it provides additional context without competing with the title. Its lighter weight and smaller size reinforce the content hierarchy while maintaining readability. The body text is presented in gray-700 to further distinguish it as secondary information and keep attention on the primary title. Image: Dark \"Featured project\" page section for \"Dreams from Oostende\" with numbered callouts labeling the eyebrow text, heading, body paragraph, byline, and button group. (source: https://spectrum.adobe.com/foundations/typography/media_1e2a2ea1530d45f5b5ab50e4406d52bfc78a2b4e6.png?width=750&format=png&optimize=medium)"
|
|
20
|
+
},
|
|
21
|
+
{
|
|
22
|
+
"type": "guideline",
|
|
23
|
+
"content": "Page section.\n\nSpectrum's type scale creates a clear visual hierarchy that naturally guides the eye through the page. By assigning each type style a distinct role, Spectrum organizes information into predictable patterns that make content easier to scan and understand. Title M Heading XXL Body M Body S Component M, used in a button group Image: Unlabeled image (source: https://spectrum.adobe.com/foundations/typography/media_1cd4d7ef6ccfd52ab7af605bc861bcdd334201f0a.png?width=750&format=png&optimize=medium)"
|
|
20
24
|
},
|
|
21
25
|
{
|
|
22
26
|
"type": "guideline",
|
|
@@ -24,36 +28,36 @@
|
|
|
24
28
|
},
|
|
25
29
|
{
|
|
26
30
|
"type": "guideline",
|
|
27
|
-
"content": "All-caps.\n\nAll-caps styles are not recommended for usage within UI components because it does not support accessibility requirements An all-caps style can still be used sparingly and strategically in use cases where longform content is the primary experience (like a blog post or a marketing website). All-caps text brings a heavier, punctuated feel to letterforms and adds visual impact to single words or short, standalone phrases. Image: Button labeled \"EXPORT VIDEO\" in all-caps text, shown as a don't example. (source: https://
|
|
31
|
+
"content": "All-caps.\n\nAll-caps styles are not recommended for usage within UI components because it does not support accessibility requirements An all-caps style can still be used sparingly and strategically in use cases where longform content is the primary experience (like a blog post or a marketing website). All-caps text brings a heavier, punctuated feel to letterforms and adds visual impact to single words or short, standalone phrases. Image: Button labeled \"EXPORT VIDEO\" in all-caps text, shown as a don't example. (source: https://spectrum.adobe.com/foundations/typography/media_111cb65fe657204f59fbf7ba2758d84ed1330d7c2.png?width=750&format=png&optimize=medium)"
|
|
28
32
|
},
|
|
29
33
|
{
|
|
30
34
|
"type": "guideline",
|
|
31
|
-
"content": "Use Spectrum font sizes.\n\nChoose from Spectrum's defined font sizes. By using unique font sizes, you risk upsetting the hierarchy and balance of typography in your product. Image: Text reading \"Spectrum delivers what's needed, when it's needed.\" labeled with a custom value of 17 px instead of a Spectrum font size token, shown as a don't example. (source: https://
|
|
35
|
+
"content": "Use Spectrum font sizes.\n\nChoose from Spectrum's defined font sizes. By using unique font sizes, you risk upsetting the hierarchy and balance of typography in your product. Image: Text reading \"Spectrum delivers what's needed, when it's needed.\" labeled with a custom value of 17 px instead of a Spectrum font size token, shown as a don't example. (source: https://spectrum.adobe.com/foundations/typography/media_1280ff1daf36ac669b43bcc3e021b8a6774c4cbb6.png?width=750&format=png&optimize=medium) Image: Text reading \"Spectrum delivers what's needed, when it's needed.\" labeled with the token font-size-200, shown as a do example. (source: https://spectrum.adobe.com/foundations/typography/media_17c4dbbf625e3b2e743e6a75e591d7f5991b5cfbc.png?width=750&format=png&optimize=medium)"
|
|
32
36
|
},
|
|
33
37
|
{
|
|
34
38
|
"type": "guideline",
|
|
35
|
-
"content": "Respect capitalization rules.\n\nUse sentence case for all UX content. For more on capitalization guidelines, go to Grammar and mechanics. Image: Form with a \"Create audience\" button, an \"Email address\" field, and a \"Contact preference\" dropdown listing \"Phone call,\" \"Email address,\" and \"Text message\" in sentence case, shown as a do example. (source: https://
|
|
39
|
+
"content": "Respect capitalization rules.\n\nUse sentence case for all UX content. For more on capitalization guidelines, go to Grammar and mechanics. Image: Form with a \"Create audience\" button, an \"Email address\" field, and a \"Contact preference\" dropdown listing \"Phone call,\" \"Email address,\" and \"Text message\" in sentence case, shown as a do example. (source: https://spectrum.adobe.com/foundations/typography/media_1e8d9950994f825a7339aaac2677a0f16286e1762.png?width=750&format=png&optimize=medium)"
|
|
36
40
|
},
|
|
37
41
|
{
|
|
38
42
|
"type": "guideline",
|
|
39
|
-
"content": "Use tabular numbers for numerical data.\n\nNumbers within components should be tabular with lining figures. In tables, numbers should be right aligned to make numerical data easier to read and compare. This is used, for example, in tables, time stamps, and bar loaders. This is supported by Adobe Clean (via the Monospace uppercase option in Figma, the OpenType panel in Illustrator, or the CSS font feature settings). For iOS and Android, use the Spectrum Monospace numbers type styles. Image: Table with a \"Count\" column showing right-aligned tabular numbers 2, 5, 10, 12, and 25, with a bolded total of 324, shown as a do example. (source: https://
|
|
43
|
+
"content": "Use tabular numbers for numerical data.\n\nNumbers within components should be tabular with lining figures. In tables, numbers should be right aligned to make numerical data easier to read and compare. This is used, for example, in tables, time stamps, and bar loaders. This is supported by Adobe Clean (via the Monospace uppercase option in Figma, the OpenType panel in Illustrator, or the CSS font feature settings). For iOS and Android, use the Spectrum Monospace numbers type styles. Image: Table with a \"Count\" column showing right-aligned tabular numbers 2, 5, 10, 12, and 25, with a bolded total of 324, shown as a do example. (source: https://spectrum.adobe.com/foundations/typography/media_17aab398526c4b42c420abce55611379ee1eba044.png?width=750&format=png&optimize=medium)"
|
|
40
44
|
},
|
|
41
45
|
{
|
|
42
46
|
"type": "do-dont",
|
|
43
47
|
"content": "Don't let paragraph widths get too thin",
|
|
44
|
-
"dont": "Paragraphs of text that are too long are difficult to follow, and paragraphs of text that are too thin are difficult to read. Ideally, blocks of text should be roughly 70 characters wide. Be sure to keep them at least between 50 and 120 characters wide. Image: Narrow column of the \"Collaborative\" paragraph broken into many short lines, illustrating a paragraph width that is too thin, shown as a don't example. (source: https://
|
|
48
|
+
"dont": "Paragraphs of text that are too long are difficult to follow, and paragraphs of text that are too thin are difficult to read. Ideally, blocks of text should be roughly 70 characters wide. Be sure to keep them at least between 50 and 120 characters wide. Image: Narrow column of the \"Collaborative\" paragraph broken into many short lines, illustrating a paragraph width that is too thin, shown as a don't example. (source: https://spectrum.adobe.com/foundations/typography/media_13bb8774bddfb85d336faadbf8f1f4936f9020f4e.png?width=750&format=png&optimize=medium)"
|
|
45
49
|
},
|
|
46
50
|
{
|
|
47
51
|
"type": "guideline",
|
|
48
|
-
"content": "Keep content short and to the point.\n\nKeep paragraphs concise. Some users with cognitive disabilities (and even those who don't) can have a very difficult time reading and comprehending large blocks of text. Image: Moderate-width column of the \"Collaborative\" paragraph with comfortably readable line lengths, shown as a do example. (source: https://
|
|
52
|
+
"content": "Keep content short and to the point.\n\nKeep paragraphs concise. Some users with cognitive disabilities (and even those who don't) can have a very difficult time reading and comprehending large blocks of text. Image: Moderate-width column of the \"Collaborative\" paragraph with comfortably readable line lengths, shown as a do example. (source: https://spectrum.adobe.com/foundations/typography/media_15433cd18805249164930961eb963e4bec4bacba9.png?width=750&format=png&optimize=medium)"
|
|
49
53
|
},
|
|
50
54
|
{
|
|
51
55
|
"type": "do-dont",
|
|
52
56
|
"content": "Don't fully-justify text",
|
|
53
|
-
"dont": "Do not use fully-justified blocks of text. This adds trapped white space within paragraphs, which makes it harder to read, especially for those with cognitive disabilities or dyslexia. Right alignment (left rag) is also discouraged for paragraphs of text. Image: The \"Collaborative\" paragraph shown fully justified with uneven word spacing on a pink background, shown as a don't example. (source: https://
|
|
57
|
+
"dont": "Do not use fully-justified blocks of text. This adds trapped white space within paragraphs, which makes it harder to read, especially for those with cognitive disabilities or dyslexia. Right alignment (left rag) is also discouraged for paragraphs of text. Image: The \"Collaborative\" paragraph shown fully justified with uneven word spacing on a pink background, shown as a don't example. (source: https://spectrum.adobe.com/foundations/typography/media_1da6c7af0217c78e26865de32b20a08b32471b743.png?width=750&format=png&optimize=medium)"
|
|
54
58
|
}
|
|
55
59
|
],
|
|
56
|
-
"sourceUrl": "https://
|
|
60
|
+
"sourceUrl": "https://spectrum.adobe.com/foundations/typography/applying-the-type-system",
|
|
57
61
|
"lastUpdated": "2026-08-13",
|
|
58
62
|
"status": "published",
|
|
59
63
|
"tags": [
|
|
@@ -12,14 +12,14 @@
|
|
|
12
12
|
},
|
|
13
13
|
{
|
|
14
14
|
"type": "guideline",
|
|
15
|
-
"content": "High attention elements should be used sparingly and selectively. If too many things are high attention at once, the experience becomes noisy and unfocused. For example, both high-contrast colors and elevation communicate specific meanings and add emphasis within pages and flows — and these are both used very thoughtfully. Image: Three labeled pill buttons on a low-to-high attention scale: a light gray button on the left (low attention), a dark gray/black button in the middle, and a solid blue button on the right (high attention). (source: https://
|
|
15
|
+
"content": "High attention elements should be used sparingly and selectively. If too many things are high attention at once, the experience becomes noisy and unfocused. For example, both high-contrast colors and elevation communicate specific meanings and add emphasis within pages and flows — and these are both used very thoughtfully. Image: Three labeled pill buttons on a low-to-high attention scale: a light gray button on the left (low attention), a dark gray/black button in the middle, and a solid blue button on the right (high attention). (source: https://spectrum.adobe.com/foundations/media_14ae3b9cab583541ca3057219e82b963cb577f719.png?width=750&format=png&optimize=medium) Image: Four empty rounded rectangle cards arranged on a low-to-high attention scale, showing progressively deeper drop shadows from left to right to indicate increasing visual elevation and attention. (source: https://spectrum.adobe.com/foundations/media_145c026b410020965c87b15781c669231233cd7fa.png?width=750&format=png&optimize=medium)"
|
|
16
16
|
},
|
|
17
17
|
{
|
|
18
18
|
"type": "guideline",
|
|
19
|
-
"content": "As a general rule, only one element or group of elements should have high attention on a page. Too many elements drawing high attention makes it difficult to focus. Image: A vertical sidebar with a blue circular add button at top, followed by icons for recent, cloud, and people, with a tooltip labeled 'Recent' pointing to the clock icon, and a panel toggle icon at the bottom. (source: https://
|
|
19
|
+
"content": "As a general rule, only one element or group of elements should have high attention on a page. Too many elements drawing high attention makes it difficult to focus. Image: A vertical sidebar with a blue circular add button at top, followed by icons for recent, cloud, and people, with a tooltip labeled 'Recent' pointing to the clock icon, and a panel toggle icon at the bottom. (source: https://spectrum.adobe.com/foundations/media_1a93a0b0e1b7fb0945b404bf29ffcc9bd5cc43d71.png?width=750&format=png&optimize=medium) Image: A vertical sidebar with a blue circular add button, a highlighted blue 'Recent' clock icon with a matching blue tooltip label, plus cloud and people icons, and a panel toggle icon at the bottom — showing overuse of blue accent color across multiple elements. (source: https://spectrum.adobe.com/foundations/media_19fb239ceeb047bb8e509bb2f502737325765d41e.png?width=750&format=png&optimize=medium) The plus button is the most timely and high impact action to take in this example. Selected state of items in the navigation is competing with the plus button."
|
|
20
20
|
}
|
|
21
21
|
],
|
|
22
|
-
"sourceUrl": "https://
|
|
22
|
+
"sourceUrl": "https://spectrum.adobe.com/foundations/attention-hierarchy",
|
|
23
23
|
"lastUpdated": "2026-08-24",
|
|
24
24
|
"status": "published",
|
|
25
25
|
"tags": [
|
|
@@ -8,7 +8,7 @@
|
|
|
8
8
|
{ "type": "purpose", "content": "Background layers" },
|
|
9
9
|
{
|
|
10
10
|
"type": "guideline",
|
|
11
|
-
"content": "In Spectrum, background layers are used differently depending on the primary context of the page. For pages where the primary purpose is the canvas and related actions for editing, view Editing contexts. For pages where the primary focus is browsing content, such as a Home or Files experience, view Browsing contexts. If you’re not sure whether a page is in an editing or browsing context, contact the Spectrum design team. In addition to the three existing background layer options — background layer 1, background layer 2, and background base — Spectrum includes an elevated option. Elevated background layers create depth and emphasize content floating on top of a canvas. Image: A stack of five overlapping flat panels labeled with callouts from front to back: elevated, layer-2, layer-1, base, and pasteboard, illustrating a background layer hierarchy. (source: https://
|
|
11
|
+
"content": "In Spectrum, background layers are used differently depending on the primary context of the page. For pages where the primary purpose is the canvas and related actions for editing, view Editing contexts. For pages where the primary focus is browsing content, such as a Home or Files experience, view Browsing contexts. If you’re not sure whether a page is in an editing or browsing context, contact the Spectrum design team. In addition to the three existing background layer options — background layer 1, background layer 2, and background base — Spectrum includes an elevated option. Elevated background layers create depth and emphasize content floating on top of a canvas. Image: A stack of five overlapping flat panels labeled with callouts from front to back: elevated, layer-2, layer-1, base, and pasteboard, illustrating a background layer hierarchy. (source: https://spectrum.adobe.com/foundations/color/media_125baf8974fe134e65d43f0f3ae7eeac5a7fd609b.png?width=750&format=png&optimize=medium) Background layer Light theme Dark theme Elevated gray-25 (with drop shadow) gray-75 (with drop shadow) Layer 2 gray-25 gray-75 Layer 1 gray-50 gray-50 Pasteboard gray-100 gray-25"
|
|
12
12
|
},
|
|
13
13
|
{
|
|
14
14
|
"type": "guideline",
|
|
@@ -16,11 +16,11 @@
|
|
|
16
16
|
},
|
|
17
17
|
{
|
|
18
18
|
"type": "guideline",
|
|
19
|
-
"content": "Editing application.\n\nPages in editing contexts draw attention to the canvas, which is the primary focus. Image: A UI mockup showing a light gray toolbar and content area, with a small white vertical panel on the left labeled 'elevated. (source: https://
|
|
19
|
+
"content": "Editing application.\n\nPages in editing contexts draw attention to the canvas, which is the primary focus. Image: A UI mockup showing a light gray toolbar and content area, with a small white vertical panel on the left labeled 'elevated. (source: https://spectrum.adobe.com/foundations/color/media_170fe70f90d11502945ba73f759534964da2df900.png?width=750&format=png&optimize=medium)"
|
|
20
20
|
},
|
|
21
21
|
{
|
|
22
22
|
"type": "guideline",
|
|
23
|
-
"content": "Image: An isometric exploded view of a UI panel showing stacked layers labeled layer-2, elevated, pasteboard, and layer-2 again, illustrating depth and stacking order. (source: https://
|
|
23
|
+
"content": "Image: An isometric exploded view of a UI panel showing stacked layers labeled layer-2, elevated, pasteboard, and layer-2 again, illustrating depth and stacking order. (source: https://spectrum.adobe.com/foundations/color/media_1f8b886169da3f23ccfffdbb27b5c0ea4021846d2.png?width=750&format=png&optimize=medium)"
|
|
24
24
|
},
|
|
25
25
|
{
|
|
26
26
|
"type": "guideline",
|
|
@@ -28,7 +28,7 @@
|
|
|
28
28
|
},
|
|
29
29
|
{
|
|
30
30
|
"type": "guideline",
|
|
31
|
-
"content": "Image: The same UI mockup with a light gray toolbar and content area, with the surrounding background area labeled 'layer-2.' (source: https://
|
|
31
|
+
"content": "Image: The same UI mockup with a light gray toolbar and content area, with the surrounding background area labeled 'layer-2.' (source: https://spectrum.adobe.com/foundations/color/media_10fb4e74c2e2cf1b5db032034b80119c621df637f.png?width=750&format=png&optimize=medium)"
|
|
32
32
|
},
|
|
33
33
|
{
|
|
34
34
|
"type": "guideline",
|
|
@@ -36,7 +36,7 @@
|
|
|
36
36
|
},
|
|
37
37
|
{
|
|
38
38
|
"type": "guideline",
|
|
39
|
-
"content": "Image: The same UI mockup with a light gray toolbar and content area, with the outermost background area labeled 'pasteboard.' (source: https://
|
|
39
|
+
"content": "Image: The same UI mockup with a light gray toolbar and content area, with the outermost background area labeled 'pasteboard.' (source: https://spectrum.adobe.com/foundations/color/media_110c564baa38fffaae914eb5a11d469cd41ccf2a1.png?width=750&format=png&optimize=medium)"
|
|
40
40
|
},
|
|
41
41
|
{
|
|
42
42
|
"type": "guideline",
|
|
@@ -44,15 +44,19 @@
|
|
|
44
44
|
},
|
|
45
45
|
{
|
|
46
46
|
"type": "guideline",
|
|
47
|
-
"content": "
|
|
47
|
+
"content": "This example shows an editing application using background layer 2 for both the artboard and the app frame. An elevated background is used for a floating toolbar, which appears on top of the canvas. Image: An isometric exploded view of a UI panel with a floating button element, showing stacked layers labeled layer-1, elevated, pasteboard, and layer-2 (twice), illustrating depth and stacking order. (source: https://spectrum.adobe.com/foundations/color/media_1c8fba7f2acf4599eb31649e0b3ee41437f88041b.png?width=750&format=png&optimize=medium)"
|
|
48
48
|
},
|
|
49
49
|
{
|
|
50
50
|
"type": "guideline",
|
|
51
|
-
"content": "Image:
|
|
51
|
+
"content": "Image: A UI mockup showing a toolbar, content area, and a floating rounded button, with the button labeled 'elevated.' (source: https://spectrum.adobe.com/foundations/color/media_19136fb540bd10ab5985b00318dd4c6a06d6648db.png?width=750&format=png&optimize=medium)"
|
|
52
52
|
},
|
|
53
53
|
{
|
|
54
54
|
"type": "guideline",
|
|
55
|
-
"content": "Image: The same UI mockup with a toolbar, content area, and floating button, with the
|
|
55
|
+
"content": "Image: The same UI mockup with a toolbar, content area, and floating button, with the light gray sidebar area labeled 'Layer 2.' (source: https://spectrum.adobe.com/foundations/color/media_1167297ee70d5bc333820478afdcf8410d5cd2e22.png?width=750&format=png&optimize=medium)"
|
|
56
|
+
},
|
|
57
|
+
{
|
|
58
|
+
"type": "guideline",
|
|
59
|
+
"content": "Image: The same UI mockup with a toolbar, content area, and floating button, with the white toolbar area labeled 'Layer 1. (source: https://spectrum.adobe.com/foundations/color/media_18abc351c445528d2ace3af106f13f2b6626b2715.png?width=750&format=png&optimize=medium)"
|
|
56
60
|
},
|
|
57
61
|
{
|
|
58
62
|
"type": "guideline",
|
|
@@ -60,7 +64,7 @@
|
|
|
60
64
|
},
|
|
61
65
|
{
|
|
62
66
|
"type": "guideline",
|
|
63
|
-
"content": "Image: The same UI mockup with a toolbar, content area, and floating button, with the outermost background area labeled 'Pasteboard.' (source: https://
|
|
67
|
+
"content": "Image: The same UI mockup with a toolbar, content area, and floating button, with the outermost background area labeled 'Pasteboard.' (source: https://spectrum.adobe.com/foundations/color/media_1fca78125ec28d3d0af8819e33bc53e96dd8dbfd2.png?width=750&format=png&optimize=medium)"
|
|
64
68
|
},
|
|
65
69
|
{
|
|
66
70
|
"type": "guideline",
|
|
@@ -68,30 +72,30 @@
|
|
|
68
72
|
},
|
|
69
73
|
{
|
|
70
74
|
"type": "guideline",
|
|
71
|
-
"content": "
|
|
75
|
+
"content": "Pages in browsing contexts draw attention to the content, which is the primary focus. Examples of pages in browsing contexts include a Home or Files experience. Image: An isometric exploded view of a UI panel with a floating rounded element on top, showing stacked layers labeled base, layer 2, and elevated, illustrating depth and stacking order. (source: https://spectrum.adobe.com/foundations/color/media_1060f435fd95504c233c5d57dc8d8f6570ce93e02.png?width=750&format=png&optimize=medium)"
|
|
72
76
|
},
|
|
73
77
|
{
|
|
74
78
|
"type": "guideline",
|
|
75
|
-
"content": "
|
|
79
|
+
"content": "Elevated (highest attention).\n\nElevated backgrounds create the illusion of depth through the use of a drop shadow, and display content that appears on top of other content. They draw attention and are used sparingly. In browsing contexts, this background layer style is used in components like menus and tooltips."
|
|
76
80
|
},
|
|
77
81
|
{
|
|
78
82
|
"type": "guideline",
|
|
79
|
-
"content": "
|
|
83
|
+
"content": "Image: A UI mockup showing a content area with a floating rounded card in the top-right corner, with the surrounding gray background labeled 'base.' (source: https://spectrum.adobe.com/foundations/color/media_1856cd39f76bc9d38d6f9ddfe57400ceb603e983b.png?width=750&format=png&optimize=medium)"
|
|
80
84
|
},
|
|
81
85
|
{
|
|
82
86
|
"type": "guideline",
|
|
83
|
-
"content": "
|
|
87
|
+
"content": "Layer 2 is used to group related content together and to create separation from the primary content on a page, such as in the background of the app frame."
|
|
84
88
|
},
|
|
85
89
|
{
|
|
86
90
|
"type": "guideline",
|
|
87
|
-
"content": "
|
|
91
|
+
"content": "Image: The same UI mockup with a content area and floating card, with the white content panel labeled 'layer 2.' (source: https://spectrum.adobe.com/foundations/color/media_14cfd47611567b8649816d2022de82b47339f2d42.png?width=750&format=png&optimize=medium)"
|
|
88
92
|
},
|
|
89
93
|
{
|
|
90
94
|
"type": "guideline",
|
|
91
|
-
"content": "
|
|
95
|
+
"content": "Base.\n\nSpectrum 2 uses gray-25 as the base background color to draw attention to the primary content of a page. Using gray-25 allows for higher contrast between the background and content, and it provides a blank canvas for more vibrant colors. For using a drop shadow to draw emphasis to a container that isn’t elevated, view container emphasis. Image: Two side-by-side diagrams, light theme and dark theme, each showing three overlapping square panels labeled elevated, Layer 2, and Base from front to back, illustrating background layer hierarchy in both color modes. (source: https://spectrum.adobe.com/foundations/color/media_135b74d5364580adabc3490eb36efcbd74084d1e8.png?width=750&format=png&optimize=medium) Background layer Light theme Dark theme Elevated gray-25 (with drop shadow) gray-75 (with drop shadow) Layer 2 gray-25 gray-75 Layer 1 gray-50 gray-50 Pasteboard gray-100 gray-25"
|
|
92
96
|
}
|
|
93
97
|
],
|
|
94
|
-
"sourceUrl": "https://
|
|
98
|
+
"sourceUrl": "https://spectrum.adobe.com/foundations/color/background-layers",
|
|
95
99
|
"lastUpdated": "2026-08-13",
|
|
96
100
|
"status": "published",
|
|
97
101
|
"tags": [
|
|
@@ -8,38 +8,38 @@
|
|
|
8
8
|
{ "type": "purpose", "content": "Bi-directionality" },
|
|
9
9
|
{
|
|
10
10
|
"type": "guideline",
|
|
11
|
-
"content": "In digital experiences, languages that are based on Latin script (e.g., English and French), Cyrillic script (e.g., Russian and Bulgarian), Chinese and Japanese* are consistently read and written from left to right. Languages that are based on certain writing systems like Arabic (e.g., Arabic, Persian, and Urdu) and Hebrew (Hebrew and Yiddish), are mostly read and written from right to left. These languages are called “bi-directional,” or are also commonly referred to as “RTL” (“right-to-left”) languages. Digital experiences for these languages should be mirrored to follow the same right-to-left reading pattern. UI mirroring is the process of positioning components in the opposite side of the interface, which creates, as the term suggests, a mirror-like effect. *
|
|
11
|
+
"content": "In digital experiences, languages that are based on Latin script (e.g., English and French), Cyrillic script (e.g., Russian and Bulgarian), Chinese and Japanese* are consistently read and written from left to right. Languages that are based on certain writing systems like Arabic (e.g., Arabic, Persian, and Urdu) and Hebrew (Hebrew and Yiddish), are mostly read and written from right to left. These languages are called “bi-directional,” or are also commonly referred to as “RTL” (“right-to-left”) languages. Digital experiences for these languages should be mirrored to follow the same right-to-left reading pattern. UI mirroring is the process of positioning components in the opposite side of the interface, which creates, as the term suggests, a mirror-like effect. *Chinese and Japanese, especially in printing, books, and publications, maintain their top-to-bottom, right-to-left writing/reading patterns, but are mainly using the left-to-right system in digital experiences."
|
|
12
12
|
},
|
|
13
13
|
{
|
|
14
14
|
"type": "guideline",
|
|
15
|
-
"content": "Mirror individual components.\n\nComponents and their constituting parts are affected by user interface mirroring. Mirroring guidelines for each component are available on their respective pages, when applicable. Image: Key example showing the correct usage of a bi-directional component. (source: https://
|
|
15
|
+
"content": "Mirror individual components.\n\nComponents and their constituting parts are affected by user interface mirroring. Mirroring guidelines for each component are available on their respective pages, when applicable. Image: Key example showing the correct usage of a bi-directional component. (source: https://spectrum.adobe.com/foundations/inclusivity/media_18e5aff774a8531f0cf4fb9dc3f5a154b7f6ef74a.png?width=750&format=png&optimize=medium)"
|
|
16
16
|
},
|
|
17
17
|
{
|
|
18
18
|
"type": "guideline",
|
|
19
|
-
"content": "Don't mirror components that represent time.\n\nComponents that are used to represent the concept of time should not be mirrored (e.g., a video player). Image: Key example showing the incorrect usage of a bi-directional component. (source: https://
|
|
19
|
+
"content": "Don't mirror components that represent time.\n\nComponents that are used to represent the concept of time should not be mirrored (e.g., a video player). Image: Key example showing the incorrect usage of a bi-directional component. (source: https://spectrum.adobe.com/foundations/inclusivity/media_19187d9d281d10a389dfd6809de49d18be985e1fe.png?width=750&format=png&optimize=medium)"
|
|
20
20
|
},
|
|
21
21
|
{
|
|
22
22
|
"type": "guideline",
|
|
23
|
-
"content": "Mirror composite images with directional flow.\n\nComposite images that depict a directional flow or convey a linear narrative require a dedicated bi-directional version since the sense of the narrative, reading from right to left, could appear reversed. Image: Key example of correct usage of bi-directional flow in a linear narrative. (source: https://
|
|
23
|
+
"content": "Mirror composite images with directional flow.\n\nComposite images that depict a directional flow or convey a linear narrative require a dedicated bi-directional version since the sense of the narrative, reading from right to left, could appear reversed. Image: Key example of correct usage of bi-directional flow in a linear narrative. (source: https://spectrum.adobe.com/foundations/inclusivity/media_1a664a66a07b819bd3aff649b113040ff5097d898.png?width=750&format=png&optimize=medium)"
|
|
24
24
|
},
|
|
25
25
|
{
|
|
26
26
|
"type": "guideline",
|
|
27
|
-
"content": "Mirror icons that represent movement.\n\nIcons that depict horizontal movement (e.g., back icon) should be mirrored to follow the flow of the right-to-left interface. Image: Key examples of mirror icons that represent movement. (source: https://
|
|
27
|
+
"content": "Mirror icons that represent movement.\n\nIcons that depict horizontal movement (e.g., back icon) should be mirrored to follow the flow of the right-to-left interface. Image: Key examples of mirror icons that represent movement. (source: https://spectrum.adobe.com/foundations/inclusivity/media_195d5a351b079313e2e11c0dae134d74588e500f7.png?width=750&format=png&optimize=medium)"
|
|
28
28
|
},
|
|
29
29
|
{
|
|
30
30
|
"type": "guideline",
|
|
31
|
-
"content": "Don't mirror icons that represent time.\n\nIcons that refer to the passage of time (e.g., clock icon) should not be mirrored in right-to-left interfaces. Image: Key example of incorrectly mirroring icons that represent time. (source: https://
|
|
31
|
+
"content": "Don't mirror icons that represent time.\n\nIcons that refer to the passage of time (e.g., clock icon) should not be mirrored in right-to-left interfaces. Image: Key example of incorrectly mirroring icons that represent time. (source: https://spectrum.adobe.com/foundations/inclusivity/media_1b374016f329125585285f97e193eebd2acbc4e4a.png?width=750&format=png&optimize=medium)"
|
|
32
32
|
},
|
|
33
33
|
{
|
|
34
34
|
"type": "guideline",
|
|
35
|
-
"content": "Don't mirror checkmarks.\n\nCheckmarks are never mirrored in right-to-left interfaces. Image: Key example of illustrating not to mirror the checkmark component. (source: https://
|
|
35
|
+
"content": "Don't mirror checkmarks.\n\nCheckmarks are never mirrored in right-to-left interfaces. Image: Key example of illustrating not to mirror the checkmark component. (source: https://spectrum.adobe.com/foundations/inclusivity/media_1f3f57010df37d6833fadad8b45af031d78e543a8.png?width=750&format=png&optimize=medium)"
|
|
36
36
|
},
|
|
37
37
|
{
|
|
38
38
|
"type": "guideline",
|
|
39
|
-
"content": "Don't mirror slashes.\n\nSlashes are never mirrored in right-to-left interfaces. Image: Key example illustrating not to mirror slash marks. (source: https://
|
|
39
|
+
"content": "Don't mirror slashes.\n\nSlashes are never mirrored in right-to-left interfaces. Image: Key example illustrating not to mirror slash marks. (source: https://spectrum.adobe.com/foundations/inclusivity/media_1eaa9deb489f9741568d5c8549da5fbb7742191c4.png?width=750&format=png&optimize=medium)"
|
|
40
40
|
}
|
|
41
41
|
],
|
|
42
|
-
"sourceUrl": "https://
|
|
42
|
+
"sourceUrl": "https://spectrum.adobe.com/foundations/inclusivity/bi-directionality",
|
|
43
43
|
"lastUpdated": "2026-09-03",
|
|
44
44
|
"status": "published",
|
|
45
45
|
"tags": [
|
|
@@ -6,6 +6,10 @@
|
|
|
6
6
|
"category": "designing",
|
|
7
7
|
"documentBlocks": [
|
|
8
8
|
{ "type": "purpose", "content": "Border width" },
|
|
9
|
+
{
|
|
10
|
+
"type": "guideline",
|
|
11
|
+
"content": "Image: Faint blue icon of a rounded square containing a small toggle switch and rounded rectangle, illustrating minimal border use where borders aren't needed. (source: https://spectrum.adobe.com/foundations/styles/object-styles/media_17c3007ebae0f53d3422c819976245b9093c4f4f4.png?width=750&format=png&optimize=medium) Image: Three horizontal pink gradient bars of consistent border width, illustrating consistent border styling across elements. (source: https://spectrum.adobe.com/foundations/styles/object-styles/media_1e8f2ff262e3c29774ba33c7130140c6fb22bf3a1.png?width=750&format=png&optimize=medium)"
|
|
12
|
+
},
|
|
9
13
|
{
|
|
10
14
|
"type": "guideline",
|
|
11
15
|
"content": "Borders when necessary only.\n\nBorders are an essential way to create separation, but they can also add visual noise to an interface by filling and disrupting negative space. As a result, they should be used sparingly, only when necessary. For example, a divider might sometimes be needed to separate two distinct action button groups. Or, an object might have a border to demarcate distinct areas, such as separating a panel or card from the rest of the content on a page. Whenever possible, achieve separation through other techniques, like negative space and section titles, instead of using borders."
|
|
@@ -16,7 +20,11 @@
|
|
|
16
20
|
},
|
|
17
21
|
{
|
|
18
22
|
"type": "guideline",
|
|
19
|
-
"content": "
|
|
23
|
+
"content": "Borders are primarily used to define component boundaries and organize content within layouts. Different border width styles communicate different levels of emphasis and separation. Spectrum supports two border widths that are used within in-product UI contexts."
|
|
24
|
+
},
|
|
25
|
+
{
|
|
26
|
+
"type": "guideline",
|
|
27
|
+
"content": "Image: UI examples showing medium border widths: a radio button, checkbox, and toggle switch outline, a focused pill-shaped button with a blue border, an unfocused pill button, and a bordered text input field with label and value. (source: https://spectrum.adobe.com/foundations/styles/object-styles/media_1a088c65b63f7e399bb131a44ff80e74953321fff.png?width=750&format=png&optimize=medium)"
|
|
20
28
|
},
|
|
21
29
|
{
|
|
22
30
|
"type": "guideline",
|
|
@@ -24,7 +32,7 @@
|
|
|
24
32
|
},
|
|
25
33
|
{
|
|
26
34
|
"type": "guideline",
|
|
27
|
-
"content": "Image: A list UI with two collapsible \"Title\" sections separated by thin hairline borders, and a checklist titled \"Fruits\" with thin-bordered rows for Apples, Oranges, and Pears. (source: https://
|
|
35
|
+
"content": "Image: A list UI with two collapsible \"Title\" sections separated by thin hairline borders, and a checklist titled \"Fruits\" with thin-bordered rows for Apples, Oranges, and Pears. (source: https://spectrum.adobe.com/foundations/styles/object-styles/media_1435bfbbdbca2c110617d050031937775d717f036.png?width=750&format=png&optimize=medium)"
|
|
28
36
|
},
|
|
29
37
|
{
|
|
30
38
|
"type": "guideline",
|
|
@@ -32,7 +40,11 @@
|
|
|
32
40
|
},
|
|
33
41
|
{
|
|
34
42
|
"type": "guideline",
|
|
35
|
-
"content": "
|
|
43
|
+
"content": "Border treatments vary depending on their context. The following examples show how to apply borders across common interface patterns to create clear separation while maintaining a consistent appearance."
|
|
44
|
+
},
|
|
45
|
+
{
|
|
46
|
+
"type": "guideline",
|
|
47
|
+
"content": "Image: Adobe GenStudio interface with two magnified callouts comparing a rounded corner border end cap against a squared-off border end cap on a sidebar element. (source: https://spectrum.adobe.com/foundations/styles/object-styles/media_149631f31e7ffca6e95f54f0128c7dadc81cc445b.png?width=750&format=png&optimize=medium)"
|
|
36
48
|
},
|
|
37
49
|
{
|
|
38
50
|
"type": "guideline",
|
|
@@ -40,7 +52,7 @@
|
|
|
40
52
|
},
|
|
41
53
|
{
|
|
42
54
|
"type": "guideline",
|
|
43
|
-
"content": "Image: Close-up of an app toolbar with a bordered rounded container grouping a percentage dropdown, share icon, upload icon, and blue Download button, next to ungrouped icon buttons. (source: https://
|
|
55
|
+
"content": "Image: Close-up of an app toolbar with a bordered rounded container grouping a percentage dropdown, share icon, upload icon, and blue Download button, next to ungrouped icon buttons. (source: https://spectrum.adobe.com/foundations/styles/object-styles/media_1fd7f0c9ddbc8acc442c352f72f2f9f1888c96383.png?width=750&format=png&optimize=medium)"
|
|
44
56
|
},
|
|
45
57
|
{
|
|
46
58
|
"type": "guideline",
|
|
@@ -48,10 +60,10 @@
|
|
|
48
60
|
},
|
|
49
61
|
{
|
|
50
62
|
"type": "guideline",
|
|
51
|
-
"content": "Platform availability.\n\nThese tokens are currently available on web. Guidance for additional platforms will be added in a future release.
|
|
63
|
+
"content": "Platform availability.\n\nThese tokens are currently available on web. Guidance for additional platforms will be added in a future release. Style Token Value Small border-width-100 1 px Medium border-width-200 2 px Large border-width-400 4 px"
|
|
52
64
|
}
|
|
53
65
|
],
|
|
54
|
-
"sourceUrl": "https://
|
|
66
|
+
"sourceUrl": "https://spectrum.adobe.com/foundations/styles/object-styles/border-width",
|
|
55
67
|
"lastUpdated": "2026-08-14",
|
|
56
68
|
"status": "published",
|
|
57
69
|
"tags": ["border width", "divider"]
|
package/guidelines/brand.json
CHANGED
|
@@ -8,54 +8,46 @@
|
|
|
8
8
|
{ "type": "purpose", "content": "Brand" },
|
|
9
9
|
{
|
|
10
10
|
"type": "guideline",
|
|
11
|
-
"content": "
|
|
11
|
+
"content": "There are a number of key assets that are used systematically across interfaces."
|
|
12
12
|
},
|
|
13
13
|
{
|
|
14
14
|
"type": "guideline",
|
|
15
|
-
"content": "Product logos, app icons, and lockups.\n\nA product logo or tile color does not change, even if the background is dark. One-color product logos are for usage as workflow icons. Image: \"Adobe Express branding with colorful 'A' app icon and text lockups shown in horizontal and vertical orientations.\" (source: https://
|
|
16
|
-
},
|
|
17
|
-
{
|
|
18
|
-
"type": "guideline",
|
|
19
|
-
"content": "Loading screens include desktop splash screens, mobile loading screens, and web loaders. Desktop splash screens celebrate artwork from the Adobe community and are updated at least once a year. All desktop products that have a loading time of longer than 2 seconds, or don’t open instantaneously, are required to have a splash screen. This is so a user can understand that there’s a loading process happening. Follow OS-specific conventions for mobile loading screens. View more information about using Android loading screens."
|
|
15
|
+
"content": "Product logos, app icons, and lockups.\n\nA product logo or tile color does not change, even if the background is dark. One-color product logos are for usage as workflow icons. Image: \"Adobe Express branding with colorful 'A' app icon and text lockups shown in horizontal and vertical orientations.\" (source: https://spectrum.adobe.com/foundations/media_1b535db2549466c3c1f81290211e8cb97e3b0277c.png?width=750&format=png&optimize=medium)"
|
|
20
16
|
},
|
|
21
17
|
{
|
|
22
18
|
"type": "guideline",
|
|
23
19
|
"content": "Loading screens include desktop splash screens, mobile loading screens, and web loaders. Desktop splash screens celebrate artwork from the Adobe community and are updated at least once a year. All desktop products that have a loading time of longer than 2 seconds, or don’t open instantaneously, are required to have a splash screen. This is so a user can understand that there’s a loading process happening. Follow OS-specific conventions for mobile loading screens."
|
|
24
20
|
},
|
|
25
|
-
{
|
|
26
|
-
"type": "guideline",
|
|
27
|
-
"content": "File type and folder illustrations.\n\nOn desktop, product folder icons are branded to help users find any product-related settings. For web and mobile, folders use Spectrum colors to fit better in the experience. Primary file types always utilize brand colors, since they’re often file formats proprietary to the product (for example, PSD to Photoshop, or AEP to AE). Secondary filetypes are shared across many products, so they take a neutral palette using Spectrum 1 colors. The Brand team creates desktop versions of these icons in ICNS (for Mac) and ICO (for Windows) files, while web versions are delivered most often as SVGs. Desktop folders and file types can be found on the Brand wiki under individual product delivery pages. View web folders and file types."
|
|
28
|
-
},
|
|
29
21
|
{
|
|
30
22
|
"type": "guideline",
|
|
31
23
|
"content": "File type and folder illustrations.\n\nOn desktop, product folder icons are branded to help users find any product-related settings. For web and mobile, folders use Spectrum colors to fit better in the experience. Primary file types always utilize brand colors, since they’re often file formats proprietary to the product (for example, PSD to Photoshop, or AEP to AE). Secondary filetypes are shared across many products, so they take a neutral palette using Spectrum 1 colors."
|
|
32
24
|
},
|
|
33
25
|
{
|
|
34
26
|
"type": "guideline",
|
|
35
|
-
"content": "
|
|
27
|
+
"content": "Color has historically been an extremely important part of Adobe’s brand. Bringing more color into Spectrum 2 lets product experiences draw a much closer connection to marketing materials and product branding. Spectrum’s 6.0.0 color system didn’t throughly incorporate the Adobe brand colors, even though in-product UI colors are so close to them in both hue and saturation. With the colors for Spectrum 2, we’ve made some shifts to ensure that brand colors are better represented throughout product experiences. Image: Color-coded Adobe app icons with hex codes and names: Ai (Orange), Ps (Cyan), Dn (Celery), Ae (Indigo), Xd (Fuchsia), Id (Magenta). (source: https://spectrum.adobe.com/foundations/media_140ed33e3bdfc0215811463a3914f62aa3b83debd.png?width=750&format=png&optimize=medium) Brand colors used outside of in-product illustrations and splash imagery may differ slightly from the Spectrum 2 colors. Image: Color chart comparing brand colors and spectrum colors for Adobe apps, showing hex codes and color variations side by side. (source: https://spectrum.adobe.com/foundations/media_19e48a995352b0a44ae5ac4478d0b0780916e06e1.png?width=750&format=png&optimize=medium) Along with Adobe’s primary brand color palette (red, black, grey, and white), there’s also an extended color palette that brings a modern and bold personality to the Adobe brand. These colors are the starting point for graphics, diagrams and icons, illustrations, and backgrounds — and there are additional considerations for colors in Creative Cloud, Document Cloud, Experience Cloud, and Adobe Express for Spectrum 2 experiences."
|
|
36
28
|
},
|
|
37
29
|
{
|
|
38
30
|
"type": "guideline",
|
|
39
|
-
"content": "
|
|
31
|
+
"content": "Creative Cloud uses Adobe red and six product-specific colors, each with corresponding light and dark values. Image: Color palette grid with Adobe app icons (Ai, Dn, Ps, Ae, Xd, Id) above corresponding color swatches and hex codes. (source: https://spectrum.adobe.com/foundations/media_1fc8580f8a8ad1855ad6d91b5e412d1323e574af9.png?width=750&format=png&optimize=medium)"
|
|
40
32
|
},
|
|
41
33
|
{
|
|
42
34
|
"type": "guideline",
|
|
43
|
-
"content": "
|
|
35
|
+
"content": "Document Cloud’s colors align to Spectrum. There’s three primary product colors plus Adobe red, as well as six secondary colors. Image: Grid of color swatches with hex codes, featuring Adobe Acrobat icons in red, purple, and teal at the top row. (source: https://spectrum.adobe.com/foundations/media_1e553a0a604bb2734012ea65f4a3545209e9749b7.png?width=750&format=png&optimize=medium)"
|
|
44
36
|
},
|
|
45
37
|
{
|
|
46
38
|
"type": "guideline",
|
|
47
|
-
"content": "
|
|
39
|
+
"content": "Experience Cloud’s colors align to Spectrum. The foundational apps use cool colors, while the functional apps use warm colors. Image: Diagram categorizing \"Foundational\" and \"Functional\" elements with labeled colored squares: Insights, Content, Data, Setup, Marketing, Ads, Commerce. (source: https://spectrum.adobe.com/foundations/media_18af562eadd246ad3934851d77fca39cfca07bed5.png?width=750&format=png&optimize=medium)"
|
|
48
40
|
},
|
|
49
41
|
{
|
|
50
42
|
"type": "guideline",
|
|
51
|
-
"content": "
|
|
43
|
+
"content": "Adobe Express uses three colors. Indigo is used for a fill accent color and for highlighting main metaphors. Spectrum gray is the main stroke color. Image: Three colored squares with hex codes: light purple (#DEDEF9), blue (#5C5CE0), and black (#242424) displayed in a row. (source: https://spectrum.adobe.com/foundations/media_1704be25c74bac41af593635d0107205d2d97aec0.png?width=750&format=png&optimize=medium)"
|
|
52
44
|
},
|
|
53
45
|
{
|
|
54
46
|
"type": "guideline",
|
|
55
|
-
"content": "
|
|
47
|
+
"content": "Gradients are a significant characteristic of Spectrum 2 and a very noticeable part of how the Adobe brand is expressed in UI contexts. They help communicate product differentiation across our brand portfolio, and also allow for individual products to have a wider range of expression. Both of these aspects heavily contribute to the bolder, more colorful visual language of Spectrum 2. Because gradients are very expressive, they’re always placed intentionally and with a strategic meaning. They should not distract from the main content in an experience. They’re only used in specific areas in order to create a system, feature the product brand, and support visual hierarchy. And, their colors are directly tied to product brand color palettes."
|
|
56
48
|
}
|
|
57
49
|
],
|
|
58
|
-
"sourceUrl": "https://
|
|
50
|
+
"sourceUrl": "https://spectrum.adobe.com/foundations/brand",
|
|
59
51
|
"lastUpdated": "2026-09-10",
|
|
60
52
|
"status": "published",
|
|
61
53
|
"tags": [
|
|
@@ -9,6 +9,10 @@
|
|
|
9
9
|
"type": "purpose",
|
|
10
10
|
"content": "Neurodivergence encompasses a wide range of cognitive, behavioral, and developmental differences. It includes medical diagnoses like ADHD, Autism Spectrum Disorder, Dyslexia, Anxiety, Tourette Syndrome, and more. Approximately 1 in 5 humans have neurodivergent diagnoses, although rates are significantly higher in tech workers, marketers, entrepreneurs, creatives, and younger generations. Neurodivergence is not directly related to a level of intelligence or physical ability, but sometimes overlaps with other disabilities. Every neurodivergent person experiences neurodivergence differently. While all people enter and exit disability throughout their lives, and may require special support temporarily, neurodivergent people live with their disabilities and cognitive experiences every day. For them, it’s not about finding a cure but adapting to their challenges to make the most of their abilities. They can’t change who they are or how they think, so it’s our duty to adapt to our products to suit their unique cognitive needs.\n\n### Opportunities from neuroinclusion\n\nNeurotypical users often feel frustrated by overly complex workflows and product inconsistencies. Neurodivergent users also find these things frustrating, but may become so overwhelmed by these challenges that they choose not to use these products at all. This shared frustration across different user types can negatively impact customer retention and potential loss of custom acquisition."
|
|
11
11
|
},
|
|
12
|
+
{
|
|
13
|
+
"type": "guideline",
|
|
14
|
+
"content": "Neurodivergent users process information in a variety of ways. While every lived experience is unique, these are some common traits that can be used to understand challenges and decision-making processes."
|
|
15
|
+
},
|
|
12
16
|
{
|
|
13
17
|
"type": "guideline",
|
|
14
18
|
"content": "Maximizing (not Satisficing).\n\nCompelled to understand and compare all options to find the best opposed to selecting the first option that seems reasonable."
|
|
@@ -41,6 +45,10 @@
|
|
|
41
45
|
"type": "guideline",
|
|
42
46
|
"content": "The importance of novelty & stimulation.\n\nWhile finding patterns and building deep knowledge of special interests is a strength for many neurodivergent people, it can also be difficult for neurodivergent users to maintain focus on task completion. Neurodivergent brains often seek novelty due to differences in how their nervous systems process stimuli and regulate dopamine. For some, like individuals with ADHD, the brain may have lower baseline dopamine levels, making new or exciting experiences more rewarding and necessary to sustain interest and focus. Novelty can help reduce monotony and provide stimulation, which some neurodivergent individuals need to maintain engagement and regulate emotions. This drive for newness isn't universal, but reflects how diverse brains may seek balance, learning, and growth through fresh and varied experiences."
|
|
43
47
|
},
|
|
48
|
+
{
|
|
49
|
+
"type": "guideline",
|
|
50
|
+
"content": "While it is often assumed that more choices create more flexibility and control, the opposite is true - especially for neurodivergent users. Too many options make it difficult for users to compare them and make a satisfactory choice."
|
|
51
|
+
},
|
|
44
52
|
{
|
|
45
53
|
"type": "guideline",
|
|
46
54
|
"content": "Options can create a negative experience.\n\nMore options can make it harder to choose the right one. Deciding between many options requires more time and effort to weigh each one, especially since neurodivergent users often need to consider all details to proceed. This process leads to overwhelm and reduces user confidence."
|
|
@@ -53,6 +61,10 @@
|
|
|
53
61
|
"type": "guideline",
|
|
54
62
|
"content": "Increased impact on neurodivergent users.\n\nWhile all users are affected by choice-paralysis, neurodivergent users have a lower tolerance due to the increased volume of daily decisions (as compared to neurotypical peers) and risk aversion to failure. Neurodivergent users are more likely to quit a workflow if they feel overwhelmed by choices."
|
|
55
63
|
},
|
|
64
|
+
{
|
|
65
|
+
"type": "guideline",
|
|
66
|
+
"content": "Consistent and intentional UI layout can provide neurodivergent users the support they need to complete challenging tasks."
|
|
67
|
+
},
|
|
56
68
|
{
|
|
57
69
|
"type": "guideline",
|
|
58
70
|
"content": "Content volume.\n\nNeurodivergent users need to see the whole picture, but showing too much content can be demotivating. While extensive content may initially look more appealing, it can actually damage users’ motivation when they experience choice paralysis. Instead of trying to satisfy all of the users’ different needs in one space, offer more flexible tools to organize content."
|
|
@@ -65,6 +77,10 @@
|
|
|
65
77
|
"type": "guideline",
|
|
66
78
|
"content": "Consistency is key.\n\nUsers subconsciously learn the layout of apps as they use them. They come to expect side menus, containers, and other elements to appear in the same places. Users even expect this consistency across tools when multiple apps are part of the same workflow. When the layout within and across tools is inconsistent, users get confused and become frustrated. This can impact product adoption and even customer retention."
|
|
67
79
|
},
|
|
80
|
+
{
|
|
81
|
+
"type": "guideline",
|
|
82
|
+
"content": "It can be even more challenging for neurodivergent users to complete tasks within workflows that move across multiple products, product features, or tools. They can easily become stuck when relevant information is missing or hidden, or located in an unexpected place. They’re more likely to quit a workflow if a clear path forward is not obvious."
|
|
83
|
+
},
|
|
68
84
|
{
|
|
69
85
|
"type": "guideline",
|
|
70
86
|
"content": "Containers within a single screen.\n\nContaining editing tools within a single screen is a great way to reduce cognitive load and help neurodivergent users complete tasks. Editing tools should be placed in the same container or adjacent container to reduce transition time and distance. It’s best to avoid extraneous editing containers and switching context to access editing tools."
|
|
@@ -73,6 +89,10 @@
|
|
|
73
89
|
"type": "guideline",
|
|
74
90
|
"content": "Containers across screens.\n\nMany neurodivergent users leverage split screens and window tiling to improve cognition when multiple browsers are required. When there is no feedback between windows, or when a task requires multiple large transitions, task completion becomes difficult."
|
|
75
91
|
},
|
|
92
|
+
{
|
|
93
|
+
"type": "guideline",
|
|
94
|
+
"content": "Complex or ambiguous workflows can cause major challenges for neurodivergent users. Too many options can easily overwhelm, and fear of failure can shatter user confidence. When designing product workflows, it’s important to continuously evaluate and consider supportive measures to help users complete their tasks."
|
|
95
|
+
},
|
|
76
96
|
{
|
|
77
97
|
"type": "guideline",
|
|
78
98
|
"content": "Task breakdown.\n\nBreaking down tasks into steps requires linear thinking, which isn’t natural for neurodivergent brains. They need help identifying the correct steps to take and support to make sure tasks are prioritized in the correct order."
|
|
@@ -85,6 +105,10 @@
|
|
|
85
105
|
"type": "guideline",
|
|
86
106
|
"content": "Transitions.\n\nMoving between steps can become especially difficult for neurodivergent users when they also have to transition between containers (like multiple browser tabs, panels, or products). The space between screens is where neurodivergent users get lost, largely due to gapped working memory. Transitions can make or break an experience for neurodivergent users, so it’s important to identify and minimize transition time, ambiguity, and the number of containers."
|
|
87
107
|
},
|
|
108
|
+
{
|
|
109
|
+
"type": "guideline",
|
|
110
|
+
"content": "Task management is especially important for neurodivergent users to stay focused on the work they should be doing rather than all the work they could be doing. But task management can be challenging because neurodivergent brains struggle to organize, focus on, and break down large tasks."
|
|
111
|
+
},
|
|
88
112
|
{
|
|
89
113
|
"type": "guideline",
|
|
90
114
|
"content": "Task support for increased user confidence.\n\nAgentic AI can help users to identify and complete tasks, and navigate complex workflows. This is especially impactful for neurodivergent users who may become more easily overwhelmed by decision-making and task completion. As AI continues to support neurodivergent users, it can become a reliable tool to maintain motivation and increase task completion, which in turn leads to improved product loyalty.The challenge of task lists While task lists can remove the burden of remembering tasks, and act as a safety net for anxious users, they aren’t sufficient tools for continued task management support. Neurodivergent users need help planning and prioritizing tasks by clearly seeing when the task is due and how long it will take. Transparency is key to maintaining focus on the most important tasks and driving task execution. Even if the task list has sufficient details to be helpful, most task lists exist outside of the users’ workspace. It’s also common for users to have multiple task lists in different tools. Users often need to add a task reminder quickly in the most convenient tool, out of fear that they will forget the task due."
|
|
@@ -97,6 +121,10 @@
|
|
|
97
121
|
"type": "guideline",
|
|
98
122
|
"content": "Content layout and stylistic preferences depend on cognitive processing abilities and needs. Since these needs can vary significantly between neurodivergent users, it’s important to give users tools to customize their spaces. Supportive customization tools can allow users to (un)hide content. User-customized spaces can improve efficiency, reduce cognitive load, and build product confidence, trust, and loyalty."
|
|
99
123
|
},
|
|
124
|
+
{
|
|
125
|
+
"type": "guideline",
|
|
126
|
+
"content": "Neurodivergent users often welcome proactive AI interventions, recognizing their potential to enhance working memory, offer a judgment-free collaborator, and serve as a motivating presence. These tools can bridge gaps in memory, provide support without fear of rejection, and act as a body-double to help maintain focus and motivation."
|
|
127
|
+
},
|
|
100
128
|
{
|
|
101
129
|
"type": "guideline",
|
|
102
130
|
"content": "Supporting different communication needs.\n\nAI can be a valuable tool to support neurodiverse communication needs by customizing language and tone. Reassuring and encouraging AI tone and voice can provide content accessibility across different reading levels. Options for formal or casual tones can support neurodivergent users with RSD and ambiguity sensitivity, and “read aloud” options can support users who have difficulty processing written information."
|
|
@@ -146,6 +174,10 @@
|
|
|
146
174
|
"type": "guideline",
|
|
147
175
|
"content": "Use supportive AI voice and tone.\n\nSome users may become overwhelmed when they perceive rejection or a demand. Words can either encourage or discourage users to take action."
|
|
148
176
|
},
|
|
177
|
+
{
|
|
178
|
+
"type": "guideline",
|
|
179
|
+
"content": "If you’re new to neuroinclusive design, it can be difficult to know what product features can best support neurodiverse users. Here are some ideas to try:"
|
|
180
|
+
},
|
|
149
181
|
{
|
|
150
182
|
"type": "guideline",
|
|
151
183
|
"content": "Workflows.\n\nShow users what other people in similar situations chose Show users which choice they have selected in the past Offer templates as visual examples or to provide quick start options Show users a preview of the outcome of their choice so they can better gauge which choice is best Consider streamlined, in-product experiences that allow users to share decision making responsibilities with coworkers in similar roles Use judgement-free content strategy tactics to support and encourage decision making"
|