Design Compliance Rules Clarification

[dmcalester]

The Astro Team are currently reviewing the following EGS Design Compliance Rules

2.1.1 - Components and backgrounds shall conform to the colors specified in the Primary, Secondary, Tertiary, and Quaternary

Astro 7 will include refactored color palette and categories. The terminology of Primary, Secondary, Tertiary and Quaternary will be replaced, but the intent of this rule will remain

2.2.4 - Text within Astro components will use sentence case capitalization unless otherwise stated

This rule is incorporated from the Kobayashi Maru UXWG. Feedback has been this needs to be more permissive. See MIL-STD 1472 Section 5.4.7.11.2

3.4.3 - Required fields shall be marked with an asterisk to the right of the label when the majority of a form is optional.

Updated language: marked as required = Tier 1 >> Should be an indicator of some sort; an asterisk in particular might be a bigger lift

3.4.4 - Optional fields shall be marked with an asterisk to the right of the label when the majority of a form is required.

RFC

4.1.2 - Buttons shall not activate Pop Up Menus

RFC

4.1.3 - Grouped Buttons shall have the same width and even spacing

Planned deprecation

4.1.5 - Button widths shall accommodate the full title without truncating or abbreviating

RFC

4.1.7 - An ellipsis (…) shall follow the Button title when further action is required to complete the command.

RFC

4.1.8 - Outline Button style shall indicate the less preferred option in grouped Buttons

Additional discussion – primary + outline vs. primary + secondary (currently secondary in the web components)

4.2.1 - Checkboxes shall set values, not initiate actions

Soften this language to something along the lines of "In general checkboxes shall be used to set values, not initiate actions"

4.2.2 - Checkboxes shall act independently of others in a group

Do we need to re-evaluate the wording regarding the grouping?

4.4.2 - An ellipsis (…) shall follow a menu item when further action is required to complete the command.

RFC

4.5.2 - The Global Status Bar shall include the application name. Other elements are optional

Should this be guidance at all?
RFC

4.5.4 - Global Status Bar shall use dark theme styling even when the application is light themed

RFC

4.6.3 - Percentage Monitoring Icons shall depict a value between 0 and 100 as both an arc and numeric display

Option A:When using Astro specific icons…
Option B:Should Astro-specific components be removed from guidance?

4.6.5 - Icon labels shall identify the item represented, and shall not change. A Sub-Label may provide dynamic information

Monitoring icons = accurate; Other icons = need to re-evaluate / clarify

4.7.2 - Input Fields shall use the minimum text size defined in the CSS

We don’t have CSS anymore and therefore need to reword this. “don’t override input field text…?”

4.7.4 - Input Fields shall have a corresponding label

Need to clarify / define Log and specificity

4.7.7 - Input Field labels shall not use placeholder text in place of labels

Need to re-evaluate

4.8.2 - Links shall not use underlined text

No longer true for the hover states (KM)

4.8.3 - Linked text shall indicate what will happen when the link is clicked, not "Click Here" or "Link"

Need to clarify the text

4.10.1 - Pagination shall not use underlined text

No longer true for the hover states (KM)

4.10.4 - Pagination shall remove the Next link when there are no more pages after the last numeral displayed.

Consider disable vs remove?

4.11.3 - Related groups of menu items shall be indicated by separator lines

Need to review the guidelines

4.12.3 - A Progress indicator shall be displayed when an operation takes longer than one second to complete.

Need to revisit the wording – has the potential to take longer than 1 second to complete

4.14.1 - Search Fields shall contain placeholder text, defaulting to "Search ... "

revisit the language, especially re: the “…”

4.14.2 - When a Search Field has keyboard focus, the clear button shall be enabled

Need to discuss what happens if off focus but contains content

4.15.5 - Help Text shall be left-aligned under the relevant Segmented Button, regardless of location of the label.

Need to confirm if a bug needs to be fixed regarding this text

4.16.3 - Switch labels shall use sentence case capitalization

Need to confirm if a bug needs to be fixed regarding this text

4.17.3 - Large Tabs shall be used within the Global Status Bar, or top of the content area, for top level navigation

Re-evaluate whether this should be included in compliance or not

4.17.4 - Small Tabs shall be used within the content area, for sub level navigation or view switching

Re-evaluate whether this should be included in compliance or not

4.18.4 - Help Text shall be left-aligned under the relevant Switch, regardless of location of the label

There isn’t help text in dev – should probably have form text

4.20.4 - Only Astro's defined background and text colors shall be used for classification and control markings

Need to have an Astro waiver

4.21.2 - Slider labels shall be aligned to the top left of the Slider's track or vertically centered with the track to the left of the Slider

Need to clarify the wording

4.21.3 - Sliders shall have a visual indicator of the currently selected value

Zoom control slider within a timeline is an additional consideration

4.21.4 - Sliders shall have a corresponding label

Need to clarify the wording

4.26.2 - Application State shall only use the default background color or a color from the Astro Tag palettes

Evaluate if this should still be a rule or if it should be deprecated?
”Not” instead of “shall only use”??