[Meta] OUI Compliance Audit Tracking

[BSFishy]

This issue is to track the status of auditing each plugin and core service that has custom CSS. Ping @BSFishy if this list needs to be updated :)

Audits so far:

These are the results of audits. They typically have findings from the audits as well as action items to remediate anything found in the audits.

• [Research] [CCI] OUI Usage Audit in advanced_settings plugin #3963
• [Research] [CCI] OUI Usage Audit in console plugin #3966
• [Research] OUI Compliance Audit of dev_tools plugin #4160
• [Research] OUI usage audit in the expressions plugin #4122
• [Research] OUI Usage Audit Example home plugin #3945
• [Research] OUI Compliance audit of the inspector plugin #4084
• [Research] [CCI] OUI Usage Audit in navigation plugin #3962
• [Research] OUI Compliance audit of the saved_objects plugin #4161
• [Research] [CCI] OUI Usage Audit in saved_objects_management plugin #3967
• [Research] [CCI] OUI Usage Audit in share plugin #3965
• [Research] OUI usage audit in the tile_map plugin #4109
• [Research] [CCI] OUI usage audit in the vis_type_table plugin #4162

Core plugins compliance tracking issues:

These are issues to track who is performing each audit. They follow a template linking back to issue #3945 as reference for how to perform the audit and list out relevant files to the audit that may be useful.

• [Research] OUI Compliance audit of the dashboard plugin #4076
• [Research] OUI Compliance audit of the dev_tools plugin #4078
• [Research] OUI Compliance audit of the data plugin #4077
• [Research] OUI Compliance audit of the discover plugin #4079
• [Research] OUI Compliance audit of the embeddable plugin #4080
• [Research] OUI Compliance audit of the expressions plugin #4081
• [Research] OUI Compliance audit of the index_pattern_management plugin #4082
• [Research] OUI Compliance audit of the input_control_vis plugin #4083
• [Research] OUI Compliance audit of the inspector plugin #4084
• [Research] OUI Compliance audit of the management plugin #4085
• [Research] OUI Compliance audit of the maps_legacy plugin #4086
• [Research] OUI Compliance audit of the opensearch_dashboards_legacy plugin #4087
• [Research] OUI Compliance audit of the opensearch_dashboards_overview plugin #4088
• [Research] OUI Compliance audit of the opensearch_dashboards_react plugin #4089
• [Research] OUI Compliance audit of the opensearch_ui_shared plugin #4090
• [Research] OUI Compliance audit of the region_map plugin #4091
• [Research] OUI Compliance audit of the saved_objects plugin #4092
• [Research] OUI Compliance audit of the tile_map plugin #4093
• [Research] OUI Compliance audit of the timeline plugin #4094
• [Research] OUI Compliance audit of the vis_builder plugin #4095
• [Research] OUI Compliance audit of the vis_default_editor plugin #4096
• [Research] OUI Compliance audit of the vis_type_markdown plugin #4097
• [Research] OUI Compliance audit of the vis_type_metric plugin #4098
• [Research] OUI Compliance audit of the vis_type_table plugin #4099
• [Research] OUI Compliance audit of the vis_type_tagcloud plugin #4100
• [Research] OUI Compliance audit of the vis_type_timeline plugin #4101
• [Research] OUI Compliance audit of the vis_type_timeseries plugin #4102
• [Research] OUI Compliance audit of the vis_type_vega plugin #4103
• [Research] OUI Compliance audit of the vis_type_vislib plugin #4104
• [Research] OUI Compliance audit of the visualizations plugin #4105
• [Research] OUI Compliance audit of the visualize plugin #4106

Core service compliance tracking issues:

These are tracking issues for auditing core services. They are similar to the tracking issues for plugins, but focus on services that are core to Dashboards, rather than core Dashboards plugins. Note that these are core services, which may be involved with the implementation and inclusion of OUI styles and themes. Since these are core services, the conclusions of them might actually not involve any additional work.

• [Research] OUI Compliance audit of src/core/public/application #4112
• [Research] OUI Compliance audit of src/core/public/chrome #4113
• [Research] OUI Compliance audit of src/core/public/core_app #4114
• [Research] OUI Compliance audit of src/core/public/overlays #4115
• [Research] OUI Compliance audit of src/core/public/rendering #4116
• [Research] OUI Compliance audit of src/core/public/styles #4117

[kavilla]

Note: OUI Compliance is important but it also might not accurately reflect the entire OpenSearch Dashboard ecosystem.

For example,
opensearch-project/dashboards-observability#484

Plugins are able to modify global styles or update OUI variables that impact the entire ecosystem presented in OpenSearch Dashboards. Visual regressions can occur outside of Core OpenSearch Dashboards.

We should add CI checks that catches potential updates downstreams while building OpenSearch Dashboards (or in here) that enables systems to check if OUI variables/styles were modified.

This also showcases that OUI compliance is the per-cursor to usability cohesion. But external plugins must also be audited for look and feel cohesion.

[joshuarrrr]

Yeah, @kavilla, I'll be adding an additional section for audits in OpenSearch Dashboards plugins that are managed by the OpenSearch project.

[kavilla]

Are we also auditing the dark mode?

For example, opensearch-project/ml-commons-dashboards#206

[joshuarrrr]

@kavilla Did you already open an issue to document and audit dark mode?