Logout / accessibility

[Cantor, Scott]

> Not surprised. I would be very curious what they could suggest to make it
> truly more accessible. The iframe elements are missing title attributes is
> probably one thing, but I honestly don't feel that's all that meaningful. The
> iframes are an implementation detail.

Our expert, who is a real expert at this, thinks it's possible, and more to the point he's willing to help me do it, so he puts his money where his mouth is.

Partly we need to use different HTML to represent the result to accomodate the ARIA material [1]. Secondly, I think a fairly exotic reporting trick will be needed to stagger the actual reporting of results through the screen reader, which I'm less optimistic on, but he's convinced will work.

> That's an unfunded mandate for me, personally. I do my best, but that's a far
> cry from a thoughtful effort at compliance with a huge standard. And my
> accessibility folks are telling me 508 is not even the most relevant target
> standard for new Web applications. (I forget the name of whatever they told
> me.)

508 is just the law that says you have to do it, but the technical best practices are always in flux. I think they might mean ARIA actually.

Anyway, it is an unfunded mandate everywhere but accessibility is about the only thing I can honestly say OSU is actually pretty ahead of the curve on at both the IT leadership and actual leadership level, so they take it pretty seriously and I wouldn't even try to deploy it until they sign off.

-- Scott

[1] https://www.w3.org/TR/html-aria/