Feature #3229

make DynDNS status accessible to the colorblind

Added by Bill McGonigle over 7 years ago. Updated 5 months ago.

Dynamic DNS
Target version:
Start date:
Due date:
% Done:


Estimated time:
Release Notes:


DynDNS status uses red/green to indicate its status. Especially in a lightweight typeface, this is inaccessible to the 10% of males who are red/green colorblind.

Attached patch adds bold style to the red status and notes the difference in the help text. An up/down indicator would be much better, but this is quick & dirty and works for me.

dyndns-colorblind-accessible.patch (1.51 KB) dyndns-colorblind-accessible.patch Bill McGonigle, 09/24/2013 12:39 PM

Associated revisions

Revision 9447acda (diff)
Added by Viktor Gurov 5 months ago

DynDNS status icons. Implements #3229

Revision a88079e0 (diff)
Added by Jim Pingle 5 months ago

Update/sync DynDNS/RFC2136 status note. Fixes #3229


#1 Updated by Phillip Davis over 7 years ago

It would be easy enough to add status icons for good/bad to Services->Dynamic DNS, and to the Dynamic DNS dashboard widget. The question is which icons:
1) Up and down arrow icons, like the Interfaces widget, or;
2) Running/stopped icons like Services Status widget, or ?

The "Up arrow", "Down arrow" or "Running" icons are not quite the correct thing. The "stopped" icon seems good for when the address is not up-to-date. icon_error.gif looks the thing to use when it is wrong, but I can't see "icon_good.gif". Is there a "tick"/"good" icon somewhere in the pfSense themes already that could be used for the good (green) case?

#3 Updated by Renato Botelho 5 months ago

  • Status changed from New to Feedback
  • Assignee set to Viktor Gurov
  • Target version set to 2.5.0

PR has been merged. Thanks!

#4 Updated by Viktor Gurov 5 months ago

  • % Done changed from 0 to 100

#5 Updated by Danilo Zrenjanin 5 months ago

Tested the patch on 2.4.5-p1.

The status column appears and works correctly.

However, I believe the comment needs to be updated. Please check.

#6 Updated by Jim Pingle 5 months ago

I updated the note, and also copied it over to the RFC 2136 page since it applies there as well.

#7 Updated by Danilo Zrenjanin 5 months ago

  • Status changed from Feedback to Resolved

It looks excellent now. Thank you. Ticket resolved.

Also available in: Atom PDF