A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
Microsoft Lists does not expose a setting for the built-in selected-row colors, but SharePoint Online formatting can use @isSelected to force readable text colors in the affected columns.
Supported workaround: format text according to selection state
For each affected plain-text, number, or Choice column:
- Open the column menu.
- Select Column settings → Format this column.
- Select Advanced mode.
- Apply the following JSON:
{
"$schema": "https://developer.microsoft.com/json-schemas/sp/v2/column-formatting.schema.json",
"elmType": "div",
"style": {
"color": "=if(@isSelected, '#000000', '')",
"font-weight": "=if(@isSelected, '600', '')"
},
"txtContent": "@currentField"
}
@isSelected evaluates to true for selected items, so this applies black, slightly heavier text only while a row is selected. Both color and font-weight are supported formatter styles.^1^
For Date/Time, Number, Currency, Yes/No, or Approval Status columns where the formatted display value must be preserved, use:
{
"$schema": "https://developer.microsoft.com/json-schemas/sp/v2/column-formatting.schema.json",
"elmType": "div",
"style": {
"color": "=if(@isSelected, '#000000', '')",
"font-weight": "=if(@isSelected, '600', '')"
},
"txtContent": "@currentField.displayValue"
}
Test this on one column first. Column formatting replaces that column’s normal renderer, so complex Person, Lookup, hyperlink, and managed-metadata fields may require field-specific JSON.
A whole-row rowFormatter is also supported, but it completely replaces the standard row rendering and requires every displayed field and interaction to be rebuilt. rowFormatter and additionalRowClass are mutually exclusive.^2^ For this case, column formatting is the less disruptive workaround.
There is no documented selector or setting specifically for overriding the native Fluent UI selected-row background and border. Injecting custom CSS or JavaScript to alter those internal styles is not a supported modern SharePoint customization.^3^
Determine whether the site theme contributes
Because the issue remains after removing all formatting and occurs for every user, the list JSON has already been ruled out. The next useful comparison is the site theme:
- On a test site, or during an approved test window, select Settings (gear) → Change the look → Theme.
- Preview or apply a standard Microsoft light theme.
- Open the same list and select a row.
- If contrast becomes normal, have the SharePoint administrator review the custom theme rather than changing individual lists.
SharePoint themes provide the colors used by modern experiences. Theme definitions include neutral, text, disabled-text, background, and inversion values; isInverted controls whether dark or light theme colors are used for text on colored backgrounds.^4^ Microsoft recommends modern themes for modern pages and advises testing custom or classic themes for readability and accessibility.^5^
A theme comparison can identify influence, but the available Microsoft documentation does not establish that this exact gray-text/gray-background/turquoise-border combination is a named Microsoft Lists or Fluent UI defect.
If it also occurs with a standard theme
Treat it as a service-side rendering or accessibility issue:
- Capture the list URL, affected view type, applied site theme, browser/version, screenshot, and exact reproduction steps.
- Note that it affects all users and persists in an unformatted standard view.
- Ask the Microsoft 365 administrator to open a support request through Microsoft 365 admin center → Support → Help & support.
- Include that the built-in selected state produces insufficient text/background contrast and that the Title field behaves differently from other fields.
As a temporary user-level accessibility measure, Windows contrast themes can change selected-text and background colors across Windows and many applications, although this affects more than Microsoft Lists.^6^
References