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

11–20 of 93 posts

Re: Tota11y

#11

Post by FroshKiller »

BinaryIdiot wrote: post #10
ohitsdom wrote: post #8

Having an tag below an tag is an accessibility concern? What does incrementally decreasing in heading size have to do with accessibility?

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.

Re: Tota11y

#12

Post by ohitsdom »

vanderZwan wrote: post #9
ohitsdom wrote: post #8

Having an tag below an tag is an accessibility concern? What does incrementally decreasing in heading size have to do with accessibility?

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.

Re: Tota11y

#13

Post by Kartificial »

rcaught wrote: post #3

This is really great. Just two suggestions. While minimised, the tab could display a score like A+ - this could incentivise websites to permanently present it on their pages as a badge of pride (while ensuring visibility to any changes that degrade the score). Secondly, if you link to the project within the maximised tab, you'll likely see greater adoption.

But why would you place this tab on a live site? It's a great tool for developers, but there's no need to place this in production imo.

Re: Tota11y

#14

Post by sparaker »

ohitsdom wrote: post #8

Having an tag below an tag is an accessibility concern? What does incrementally decreasing in heading size have to do with accessibility?

under an has nothing to do with accessibility. Its just some people think it makes sense to have smaller headings after bigger ones and not the way around. I for one think that it sometimes is important to use an h2 after an h4. This has nothing to do with semantics btw.

Re: Tota11y

#15

Post by a3n »

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.

1.2

1.2.1

1.3

1.3.1.1

Re: Tota11y

#16

Post by sparaker »

Kartificial wrote: post #13
rcaught wrote: post #3

This is really great. Just two suggestions. While minimised, the tab could display a score like A+ - this could incentivise websites to permanently present it on their pages as a badge of pride (while ensuring visibility to any changes that degrade the score). Secondly, if you link to the project within the maximised tab, you'll likely see greater adoption.

But why would you place this tab on a live site? It's a great tool for developers, but there's no need to place this in production imo.

Yeah spot on. Accessibility is not something you show an award for. It's expected it will work on its own.

Re: Tota11y

#17

Post by rcaught »

sparaker wrote: post #16
Kartificial wrote: post #13

Earlier quoted context omitted.

But why would you place this tab on a live site? It's a great tool for developers, but there's no need to place this in production imo.

Yeah spot on. Accessibility is not something you show an award for. It's expected it will work on its own.

It wouldn't be an award, it would be a grade. Compliance and accessibility notices on websites have been used extensively over the years.

Re: Tota11y

#18

Post by agentgt »

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).

Re: Tota11y

#19

Post by elliottcarlson »

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.
Post reply on HN