In light themes, disabled inputs are clearly distinguishable from regular inputs. This is really useful for determining which inputs to fill, and it helps users understand why an input cannot be focused.
In dark themes there is no such distinction. Disabled inputs look exactly the same as regular inputs:
The same is true in high contrast dark themes:
While I don't know if there's a specific WCAG standard governing disabled input styling, I believe this is still an accessibility concern. A mouse user is able to hover over the input and see that it can't be clicked, but they will still be confused as to why, since the input doesn't look disabled. A keyboard user will be worse off, as they will see the input and expect it to be focusable, yet when navigating the page they will be unable to activate it. A voice control user will also be unable to activate the input and won't be able to see why. This is confusing for all users, but it's especially confusing for users who are using less common input modalities.
In light themes, disabled inputs are clearly distinguishable from regular inputs. This is really useful for determining which inputs to fill, and it helps users understand why an input cannot be focused.
In dark themes there is no such distinction. Disabled inputs look exactly the same as regular inputs:
The same is true in high contrast dark themes:
While I don't know if there's a specific WCAG standard governing disabled input styling, I believe this is still an accessibility concern. A mouse user is able to hover over the input and see that it can't be clicked, but they will still be confused as to why, since the input doesn't look disabled. A keyboard user will be worse off, as they will see the input and expect it to be focusable, yet when navigating the page they will be unable to activate it. A voice control user will also be unable to activate the input and won't be able to see why. This is confusing for all users, but it's especially confusing for users who are using less common input modalities.