Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.The red textboxes in Drupal.org cause many-many problems:
- it is difficult to read red text. it is not good for people who have problems with their eyes. it's not compatible with the various disability act directives, I think.
- Konqueror marks as red any mispelled text because it has an automatic spelling engine. As a result, I cannot use my spellchecker easily, because both the coorect and the erroneous text is red!
- there is just no good reason to have text input boxes.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | error_border.png | 6.71 KB | TDobes |
Comments
Comment #1
TDobes commentedSee comments in this issue as well.
FYI: The red borders around textboxes appear when there is an error in the data entered into that box. Apparently, there is a problem with doing so in Konqueror? It sounds like it's worth investigating the cross-browser usability of this feature.
Comment #2
nsk commentedwhat red borders? I never see any red borders, I just see red text which is impossible to read
Comment #3
TDobes commentedIn Mozilla and IE6-Win, error textboxes are rendered as having red borders and red text. This is meant to highlight the area of the page containing the error.
Comment #4
TDobes commentedHere's a quick screenshot of Firefox's rendering.
Comment #5
nsk commentedI see. However, just the red border should be sufficient, the red text isn't required.
Comment #6
elv commentedI guess every core theme should be tested to see if the issue is still there.
In Garland the alert box has red text on a light red background, which is definitely not the best option for visually impaired users. Black on red background would work though.
This is a case where icons could help: with or without color the icon would be visible. For aural browsers the icon's alt text would have the same function.
Comment #7
Anonymous (not verified) commentedThe user experience project is closing so this issue is being moved to the usability component under the Drupal project
Comment #8
lilou commenteddrupal.org has changed since 2005 ...