Accessibility

What we aim for

This site is built to meet WCAG 2.2 Level AA. That means it should be usable with a keyboard alone, with a screen reader, at high magnification, and without relying on color to tell you anything.

Where it stands

How it is checked

Every page is rendered and put through axe-core (opens in a new tab), against these rule sets:

wcag2a wcag2aa wcag21a wcag21aa wcag22aa best-practice

That runs automatically whenever the site changes, and a change that would introduce a problem does not get published. Alongside it, a set of tests holds the specific things that have gone wrong here before: form fields that lost their labels, headings that skipped a level, filters that submitted before you had finished choosing.

What this does not tell you

Automated checking finds perhaps a third of what matters, and we would rather say so than imply a clean result means more than it does. It can tell that an image has alternative text; it cannot tell whether that text is useful. It can tell that an error message is correctly attached to its field; it cannot tell whether the message makes sense.

In particular: nobody has yet been through this site with a screen reader. The markup is right as far as a machine can judge. That is not the same as it being pleasant, or even workable, to actually use that way.

Two areas sit outside this: the Django administration interface, which is third-party software, and the hallway signage displays, which are screens rather than web pages.

If something blocks you

Please tell us — a barrier nobody reports is a barrier nobody fixes. It helps to say which page you were on, what you were trying to do, and what you were using (a screen reader, keyboard only, magnification, and so on).

Email desjardinsm@etsu.edu, who maintains this site.

The Department of Computing (opens in a new tab) can also pass a report on.

For university-wide matters, ETSU's accessibility office (opens in a new tab) handles reports about any ETSU service.