Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Tota11y

khan.github.io

Post reply on HN
Print view View original

21–30 of 93 posts

Re: Tota11y

#21

Post by metaobject »

I'll post this here since people interested in accessibility will be reading this thread.

I have terrible vision. One of my pet peeves is when I go to a website on my phone through safari that doesn't allow me to zoom the text. For those occasions, I came across a JavaScript bookmark that I created on my phone that runs to undo whatever is preventing me from zooming in.

I'm not a web developer (I do desktop/server software development), so I have no idea how or why certain pages implement this policy/style. It just seems a little arbitrary to choose a font size for your site and not allow visitors to zoom-in in case they have trouble reading the text.

Re: Tota11y

#22

Post by edraferi »

agentgt wrote: post #18

I am surprised the tool doesn't do any color blind checking (ie putting red and green next to each other is generally not a good idea).

Does the contrast checking catch that?

Re: Tota11y

#23

Post by edraferi »

elliottcarlson wrote: post #19
agentgt wrote: post #18

I am surprised the tool doesn't do any color blind checking (ie putting red and green next to each other is generally not a good idea).

I wonder how hard it would be to cover all types of color blindness - red and green is only one possible issue with deuteranopia - there are other potential color combinations within that, and two other types of color blindness as well.

Hmm you could integrate some information about the prevalence of different types of color blindness.

"This color combination causes mild problems for 15% of people and severe problems for 5%. Consider X and Y to reduce impact to 3%"

Re: Tota11y

#24

Post by edraferi »

ohitsdom wrote: post #12
vanderZwan wrote: post #9

Earlier quoted context omitted.

Couldn't even be bothered to read the explanation, could you? > "[...] In order to maintain a consistent outline of the page for assistive technologies..."

I read that. I still don't understand how an h4 directly under an h2 impairs accessibility.

Perhaps screen readers can be set to read out the major headings to help people figure out what part of the document they want to read. This would have a level of detail or verbosity control.

First you read h1, find the right header. Then h2 with 2 levels of detail, which hits h2 and h3. You miss the sub-section you wanted because it was marked h4 instead of h3.

It's a broken tree structure... that'll cause problems any time somebody wants to do a logical traversal.

Re: Tota11y

#25

Post by davidbarker »

metaobject wrote: post #21

I'll post this here since people interested in accessibility will be reading this thread. I have terrible vision. One of my pet peeves is when I go to a website on my phone through safari that doesn't allow me to zoom the text. For those occasions, I came across a JavaScript bookmark that I created on my phone that runs to undo whatever is preventing me from zooming in. I'm not a web developer (I do desktop/server so…

I agree — disabling zooming is frustrating. Have you tried the "Reader" option in Safari? It works well for a lot of websites.

Re: Tota11y

#27

Post by Rifu »

metaobject wrote: post #21

I'll post this here since people interested in accessibility will be reading this thread. I have terrible vision. One of my pet peeves is when I go to a website on my phone through safari that doesn't allow me to zoom the text. For those occasions, I came across a JavaScript bookmark that I created on my phone that runs to undo whatever is preventing me from zooming in. I'm not a web developer (I do desktop/server so…

I believe one of the reasons for preventing zoom-in is because it plays havoc with any element that is "fixed" in your browser (ie pretty much every nav bar/fixed header you'll ever encounter).

Re: Tota11y

#28

Post by jameshart »

Rifu wrote: post #27
metaobject wrote: post #21

I'll post this here since people interested in accessibility will be reading this thread. I have terrible vision. One of my pet peeves is when I go to a website on my phone through safari that doesn't allow me to zoom the text. For those occasions, I came across a JavaScript bookmark that I created on my phone that runs to undo whatever is preventing me from zooming in. I'm not a web developer (I do desktop/server so…

I believe one of the reasons for preventing zoom-in is because it plays havoc with any element that is "fixed" in your browser (ie pretty much every nav bar/fixed header you'll ever encounter).

Also screws with ad layout and visibility. For sites that are primarily beholden to ad revenue, that can be a dealbreaker.

Re: Tota11y

#29

Post by acdha »

edraferi wrote: post #22
agentgt wrote: post #18

I am surprised the tool doesn't do any color blind checking (ie putting red and green next to each other is generally not a good idea).

Does the contrast checking catch that?

The problem is that you'd need to run the contrast test after applying the transform for various types of color blindness because they're fairly different and some seemingly high-contrast color combinations end up fairly similar:

http://www.color-blindness.com/2008/10/02/color-blindness-si...

If you want to test this on your own, http://colororacle.org/ acts as a screen overlay so you can load any sort of application, web page, etc. and hit a hot-key to see what it looks like with each of the different types of color blindness.

Re: Tota11y

#30

Post by BinaryIdiot »

FroshKiller wrote: post #11
BinaryIdiot wrote: post #10

Earlier quoted context omitted.

Remember the size is a consequence but it means it's a header of a subsection of an h3 which is then a header of a subsection of an h2. It could throw off the emphasis used in some screen readers or screw with a reading layout. It's honestly probably not a big deal but it is an improper use of syntax and could mess with accessibility software in undesirable ways.

It's a big deal if you care about the semantic structure of a document.

Well true I just meant in a functioning and even accessibility context; it'll probably still work well enough.

As a side note I know almost no one that cares about the semantic structure of an HTML document. It makes me sad. I miss XHTML's rigid structure.

Post reply on HN