Accessibility

Civcampus uses the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA as its accessibility target.

We have not yet completed a formal audit of the whole site against every WCAG 2.2 criterion, so we do not claim full conformance. This page says what we check today and where we know we fall short.

Today, the checks below apply to the public pages: the pages anyone can read without an account.

• Reflow. Every proposed change to the site is checked automatically to confirm that the main public pages fit a screen 320 pixels wide without sideways scrolling. That is the same as zooming to 400% on a typical laptop screen.
• Automated accessibility scan. Every proposed change is also scanned with axe-core against WCAG 2.2 Level A and AA rules on representative public pages (the homepage, sign-in, How it works, Governance, Accessibility, Safety resources and the student questions page), which also check for one main heading, one main region, headings in order, and the skip link. Automated rules catch only some barriers, which is why the rest of this page matters.
• Contrast. Our colors are measured: body text against its background at 4.5:1 or more, and form field borders and focus indicators at 3:1 or more.
• Visible focus. Every link, button and field shows a solid outline when you reach it with a keyboard.
• Target size. Buttons and form controls are at least 44 by 44 pixels, larger than the 24-pixel minimum Level AA requires.
• Forms. On the sign-in and sign-up forms, every field has a visible label, and errors are stated in words rather than by color alone.
• Motion. If your device asks for reduced motion, animations are turned off.

Every page starts with a “Skip to content” link, so you can move past the navigation with one key. The navigation, menus and forms on the public pages can be used with a keyboard alone.

We have not yet tested systematically with screen readers such as VoiceOver, NVDA or JAWS. Until we have, some parts of the site may be harder to use with one, and we want to hear about it.

• The pages you use after signing in, including reports, campaigns and the moderation tools, have not yet had the review the public pages have had.
• The security check on account pages is provided by Cloudflare. We test the surrounding Civcampus experience, but we do not control every aspect of the third-party widget. If it stops you signing in, email us and we will help.
• Student-uploaded files are not currently reviewed for accessibility, so an attachment may not be accessible even when the surrounding Civcampus page is.

If something on Civcampus does not work for you, tell us what you were trying to do, the page you were on, and the device, browser or assistive technology you use. Email team@jyvo.app, or use the feedback form.

Next, we are bringing the signed-in pages up to the same standard, testing with screen readers, and then commissioning a full audit against WCAG 2.2 Level AA. This page will change as that work lands.