Do you code for High Contrast? - (deprecated) Accessibility and Usability forum at WebmasterWorld - WebmasterWorld

Forum Moderators: open

Message Too Old, No Replies

Do you code for High Contrast?

Older folks trying to stay on line....

tangor

6:29 am on Jan 7, 2019 (gmt 0)

WebmasterWorld Senior Member

10+ Year Member

Top Contributors Of The Month

I personally run HIGH CONTRAST (varies OS by OS) and am butting heads with a few sites, and an increasing number, which don't play fair. Browser is set to reject all font/color/size, the OS is limited to a 16 color palette, and (this is different) JS turned OFF...

Do you acknowledge those with visual difficulties, have their down desired font choice/size?

Are you missing business, ... or ignore a segment of the web with actual cash for those who drive up numbers with no conversions?

The above is a rant, dismiss that. The real question is "Does your site render properly in High Contrast: for accessibility purposes?"

Do you test it in your dev systems? (easy to do, question is do you do it?)

The web is a great big vibrant place ... but it started with some who are now aging and that number is increasing day by day. Do you remember them in your coding?

Just wondering. These days I check it out both ways (I am 70) just to make sure. Serve all is my motto. And KISS (Keep It Simple Stup... er... substitute your favorite pronoun)

tangor

2:22 am on Jan 9, 2019 (gmt 0)

WebmasterWorld Senior Member

10+ Year Member

Top Contributors Of The Month

Ran into this last week when trying to renew DNS for one of my sites...

As coded all form fields, some "buttons", and other things were simply not visible! Managed to find a support function and explained the problem and, I will say this, that 36 hours later I received an email to try it again. :)

Needless to say they "fixed" it.

iamlost

5:06 pm on Jan 9, 2019 (gmt 0)

WebmasterWorld Senior Member

10+ Year Member

Top Contributors Of The Month

Well played!

I have done a lot over the years to make my sites friendly to as many as possible. Initially just because I thought it was the right thing to do, then because it expanded my market and now because I'm increasing funding getting older making things 'interesting'.

More and more OS and browsers are building in various capabilities however I still see a significant percentage using one or another of my built in accessibility options.

Not being as accessible as possible is like not being as mobile usable as possible (actually that's just device accessibility!) - it's like leaving lots of cash on the table. Mind you, the fact that I get not just my cut but also what competitors can't be bothered with is ummm not a complaint. :)

tangor

11:44 am on Jan 10, 2019 (gmt 0)

WebmasterWorld Senior Member

10+ Year Member

Top Contributors Of The Month

Not being as accessible as possible is like not being as mobile usable as possible (actually that's just device accessibility!) - it's like leaving lots of cash on the table.

This is true! I'm 70... I suspect there are quite a few my age still surfing the web we made vibrant way back when. When I hit a site that "fails" my high contrast (I also force font choice and size) I MIGHT give the site another chance by using "reader view" and if that doesn't work "No Style" and if that fails will view the source code... which is usually useless since these kinds of sites are js dynamic driven, etc and at that point, unless there is a PRESSING NEED, they lost me.

The case mentioned above was important enough I became the squeaky wheel that needed grease (and talked to their higher up ... who supported high contrast!) and got results. Any other website I can't read I just ditch and go to the next... as the web is full of "next"!

Just commonsense you don't make it impossible for folks of an age who actually have a lifetime of money in the bank to view your site(s).