@alansouzati I don't know if aria-roledescription is implemented anywhere yet - but adding it should do no harm (as it will be ignored if not implemented)
[alansouzati] jsconf one is more technical with codepen for reference. CSUN is more high level with the work we are doing in Grommet for accessibility. which is far from done
yeah, we have our own internal CSS/html lib that this will end up being part of. We currently don't use any lib/frameworks, but will for charts as it is too complex to expect our devs to write by hand.
[alansouzati] cool, I don’t expect you to use Grommet, but the JSconf presentation i believe will give you pointers when you decide to go for a charting library. D3 is very famous but I’m not sure how accessible is that
thanks! Yeah, we use all different solutions throughout internal/external. Hoping to standardise with one blessed method. I think it is our data page that uses D3, but it is fairly low level.
If you are looking at charts we did quite a bit of work on chart and graph accessibility in our open source framework too - not that I would expect you to use ours either ....
i'll be honest I don't think we went down the canvas road at all. We moved from flash to SVG. I don't see why the canvas approach couldnt work though - just SVG seems more appropriate for charts and graphs to me.
I guess I'm trying to make my mind up if the data is just a visualised table, or if the data should be exposed/explained differently to a SR. I can imagine a big data table isn't the greatest experience, but I can imagine it is complex to describe a chart by other methods. But charts do show visually patterns that would be hard to spot by just reading a spread sheet type table
Yeah. That is always a quandry. my general rule is, if the data is complex enough that someone might want a table to provide it to them via a link. Then they can do what they want with it (import into excel and manipulate etc)
[karlgroves] Anyone online right now, can you do me a favor?
Run a test over at http://tenon.io/ and let me know if you get an error "Tenon's API could not process the results…"
Working with a user having trouble but I can’t replicate their issue
[mrenty] I get Tenon's API could not process the results: undefined is not an object (evaluating 'this.props.data.resultSummary.issues') please try again.
thanks @jnurthen I considered making them landmarks, but there is likely to be less than 6, and more like 1 or 2. I came to the conclusion that landmarks might be overkill. They are th only thing listed in the main region so I don’t think it will be burdensome to navigate. Plus, they only contain about 5 pieces of discrete information.
the first https://ethicalweb.org book, which covers accessibility, progressive enhancement, and inclusive form design should be out any day now and will be a free download from O'Reilly
@stevefaulkner: to sum it all up, it's not hard to do, just takes some time to setup. I'll try to add some sort of guide to my write up for future use.