WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Organizational Charts

for

From: Robert Fentress
Date: May 15, 2015 2:27PM

I think aria-flowto would be the ideal solution, if it was better
supported. If the org chart is strictly hierarchical, then a nested lists
approach works, but if you have people in your organization who work across
groups, then you've got problems, don't you?

Here is another resource on aria-flowto:
http://www.3needs.org/en/testing/code/aria-flowto.html

Any way you could create some sort of shim for browsers/screen readers that
don't support this property?

The fact that you can't determine using JS if a particular attribute, role,
or property is supported is a big problem, as I see it. It makes creating
shims or polyfills more difficult and retards progress on adoption due to
the chicken-egg problem. Am I the only one who sees this as an issue? I
know there are privacy concerns, but couldn't screen readers simply
implement a do-not-track kind of feature to address this? What am I
missing?

On Mon, May 11, 2015 at 11:06 AM, Bourne, Sarah (ITD) <
<EMAIL REMOVED> > wrote:

> Coming to this thread late, but wanted to share a heading/nested list and
> CSS approach we took for org charts on Mass.Gov in 2008. We always meant
> to go back and make it prettier, but nobody ever complained, so, well, it
> might still be being used someplace in the budget office. Here's an
> example page. Note that the hyperlinks take you to child org units for more
> details.
>
> http://www.mass.gov/bb/h1/fy2009h1/brec2_09/dpt09/hceqe.htm
>
> Sarah E. Bourne
> Director of IT Accessibility, MassIT
> Commonwealth of Massachusetts
> 1 Ashburton Pl. rm 1601 Boston MA 02108
> 617-626-4502
> <EMAIL REMOVED>
> http://www.mass.gov/MassIT
> > > > >



--
Robert Fentress
Senior Accessibility Solutions Designer
540.231.1255

Technology-enhanced Learning & Online Strategies
Assistive Technologies
1180 Torgersen Hall
620 Drillfield Drive (0434)
Blacksburg, Virginia 24061