Accessibility Statement

Modality Co is committed to ensuring that our website, communications, documentation and services are accessible to people with disability. Modality Co is disability-led and run by digital accessibility professionals, and so ensuring our organisation is accessible to engage with is a core value and a measure of our own success.

Conformance

The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disability. It defines three levels of conformance: Level A, Level AA, and Level AAA. The Modality Co website is designed and coded to be conformant with WCAG 2.2 level AA, with several AAA success criteria also meeting conformance.

Feedback

We welcome and encourage anyone to reach out to us if you are experiencing accessibility barriers with our website or services. We will take on your feedback seriously and do everything we can to resolve the issue.

You can contact us via:

Improvements we’ve made

For those interested, this section covers more technical changes we did to improve the accessibility of the website.

Our website is built using WordPress with the Astra Pro theme and Elementor Pro page builder. Our forms use Contact Form 7. We chose these website building tools due to its good accessibility foundation, but there were some issues that we had to write custom code to resolve. These include:

  • Wrapping a <main> element around the main content of each webpage, as Astra only uses a <div>.
  • Removing the aria-label on the primary <nav>, so that screen readers don’t read “Primary Site Navigation Navigation”
  • Adding an aria-label of “Footer” to the footer <nav>, so that screen reader users can tell the difference between the header and footer navigation.
  • Removing the “Footer Widget 2” aria-label that Astra likes to add to one of <aside> landmarks in the footer.
  • Adding aria-current=”page” to links which refer to the currently loaded page.
  • Adding aria-hidden=”true” to decorative <svg> elements.
  • Adding a background behind the header text on the homepage to ensure the text is still readable in case the rocket/rocket trail ends up behind the text on some resolutions/browser magnifications.
  • Fixing Yoast SEO’s breadcrumbs so that they are nested in a <nav> with approriate aria-label and nest the breadcrumbs in a list.
  • Fixing Contact form 7 error messages so they refer to the form field in error.
  • Fixing Contact form 7 error messages so they have a warning icon before the error message.
  • Fixing Contact form 7 forms so that every form doesn’t tell the screen reader it’s a contact form via an aria-label.