[supermatt]

Ironically your website doesn't meet the first criterion of the WAI design tips you linked (the nav links): https://www.w3.org/WAI/tips/designing/#provide-sufficient-co...

No doubt I have poor a11y on my own projects - but if you are going to launch into critique of the landing page, at least do it from a position of authority :)

TBH, I am not sure how a charting lib could effectively be accessible to any great extent. Its not covered in the resources you linked, and in my experience with other charting libs this seems to be commonplace. I would be interested if you have any insights or suggestions on that, as I use charts extensively on one of my projects.

[egeozcan]

If we are going to go this way: You previously commented that something doesn't work on Firefox, do all your project superior browser support? That doesn't make sense does it? What does my website which I updated 6 years ago (and created more than a decade ago) have anything to do with the validity of my comment? It just has a contrast issue (let me fix that BTW [edit: done]), a criteria that was set way later than I built that site. Also this is a component library aimed at businesses, not a personal website that I'm commenting about. Please stop trying to poison the well (going as far as hunting a11y issues on my personal site) and argue on merits.

I do it from a position of support, which I had the chance of developing by observing the users of the apps I created, and I made a giant software suit (more than 1000 views) pass an accessibility audit in my current company.

This is not just a charting library, see the examples down the page. Also, see: https://www.highcharts.com/blog/tutorials/best-chart-accessi...

[supermatt]

> If we are going to go this way: You previously commented that something doesn't work on Firefox, do all your project superior browser support?

It was in a thread specifically discussing browser support for the guys project where he stated he only has the ability to test on chrome/firefox on fedora: https://news.ycombinator.com/item?id=35448674

> a criteria that was set way later than I built that site

That criterion has been there since 1999.

> Also, see: https://www.highcharts.com/blog/tutorials/best-chart-accessi...

It is highcharts that I use extensively, and I completely disagree that a11y is a solved problem there. Ironically on the referenced page they make the same mistake as you regarding color shades.

I can do this all day. Stop being so hostile.

[egeozcan]

> That criterion has been there since 1999.

Apparently 2001 (and I stand corrected). But well, I'm learning and improving am I not? I was a worse web developer a decade ago than I am now, and I am proud of that.

> Stop being so hostile.

You are the one who analyzed my personal website and reported a single color contrast issue to dismiss my complaint, why am I hostile? Regardless of that discussion, isn't my point coming across: Do we need to be authority on issues we report?

I tried to help, linked some resources, why is that wrong? I feel rather you being hostile.

> Ironically on the referenced page they make the same mistake as you regarding color shades.

Okay now you get to criticize open source libraries?

Anyway, few years ago I created an SVG based charting library for internal use, and we did (and still have) users with sight impairments, and yes it is hard to make it right. NVDA is a pain to bring under control, at least :) And a colleague of mine said something I really like: You cannot make software completely accessible, even for a perfectly capable person with above-human IQ, no, but you can make it always more accessible. It's great that they are trying!

> I can do this all day

What you are doing is something I sincerely don't understand. Teaching me a lesson? Proving I was over the line? Reading my first comment, I did see it's a bit whiny, and in another branch I tried to apologize. Whatever it is, maybe we are misunderstanding each other and perhaps everything is coming across more and more hostile. I do apologize from you if it came across to you like that too.

[supermatt]

>> That criterion has been there since 1999.

> Apparently 2001

Nope, May 1999: https://www.w3.org/standards/history/WAI-WEBCONTENT

> I do apologize

No problem.

[egeozcan]

> No problem.

So apparently I didn't have to second-guess myself :)

> Nope, May 1999

That's not what you think it is: https://www.w3.org/TR/1999/WAI-WEBCONTENT-19990324/wai-pagea...

The one which the previous version of my site failed to validate is apparently published in 2008: https://www.w3.org/standards/history/WCAG20 and when I wrote those styles back in who knows when [edit: found it, 2014 https://web.archive.org/web/20141219164444/https://egeozcan.... ], I wasn't aware of it. I first said 2001 because I looked at the first draft.

edit: So my 2014 version of the site gets 65, and the current one gets 95 from lighthouse accessibility check with current standards.

[supermatt]

> That's not what you think it is:

Its exactly what I think it is: "Ensure that foreground and background color combinations provide sufficient contrast" (with reference to lighthouse.org for specifics about contrast).

They didn't specifically define that ratio in the doc until WCAG 2, but thats irrelevant really.