Project

General

Profile

Actions

Feature #3229

closed

make DynDNS status accessible to the colorblind

Added by Bill McGonigle over 10 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Viktor Gurov
Category:
Dynamic DNS
Target version:
Start date:
09/24/2013
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:

Description

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.


Files

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

Updated by Phillip Davis over 10 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?

Actions #3

Updated by Renato Botelho over 3 years ago

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

PR has been merged. Thanks!

Actions #4

Updated by Viktor Gurov over 3 years ago

  • % Done changed from 0 to 100
Actions #5

Updated by Danilo Zrenjanin over 3 years 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.

Actions #6

Updated by Jim Pingle over 3 years ago

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

Actions #7

Updated by Danilo Zrenjanin over 3 years ago

  • Status changed from Feedback to Resolved

It looks excellent now. Thank you. Ticket resolved.

Actions

Also available in: Atom PDF