Accessibility Statement

Our goal

We want GoRefer.io to work for people who use a keyboard, a screen reader, voice control, magnification or captions. The standard we work toward is the Web Content Accessibility Guidelines (WCAG) 2.2, level AA.

We do not claim that GoRefer.io meets that standard today. This page says what we check, what we already know is wrong, and how to tell us about a barrier we have not found.

What this covers

• This website, gorefer.io.
• The public pages of the GoRefer application: sign-in and sign-up, webinar registration and sign-up, the links clients use to fill in a tax intake, the landing pages firms publish with our page builder, and the academy, where learners buy and take courses from firms.
• The signed-in application. It gets the code checks below, but not the page scans, so it is the part we know least about.

How we check

Code checks on every change

The code of this website and of the application is checked with the accessibility rules in eslint-plugin-jsx-a11y: missing labels, images with no alternative text, clickable elements a keyboard cannot reach, and similar mistakes. On this website an error stops the build. In the application, an error on a line a change touches fails the checks that run on that change.

Automated page scans

On every change to the application, an automated job opens the public pages listed above in a browser and scans them with axe-core, using all of its default rules, at a desktop width and at 375 pixels wide. A serious or critical finding fails the job. The scan runs in Chromium and in light mode. Text contrast is also checked in dark mode on the sign-in page and a few others.

The scan covers the pages of the academy that a visitor meets before signing in: the front page of a firm's academy store, a course page, a bundle page, a certificate check page, the page a buyer returns to after paying (as a visitor who is not signed in sees it), and learner sign-up. It does not yet cover learner sign-in, the course player where lessons play, or the pages a learner sees once signed in.

The checkboxes where someone agrees to receive text messages get three further checks: they have a label that is read out with them, they are not ticked in advance, and the keyboard alone can tick them.

What these checks do not tell us

Automated tools find only part of the problems. They cannot tell whether alternative text is useful, whether a page makes sense read aloud, or whether a task can be finished with a screen reader or with voice control. This statement describes checks that run on every change. It is not the result of an independent audit.

Known limitations

• The AutoFill video has no captions yet. The video on the home page and on the AutoFill extension page has audio, and it does not have captions. The text beside it describes what it shows.
• Small controls. WCAG 2.2 asks for controls at least 24 by 24 pixels (success criterion 2.5.8). Our scans do not check this yet, and some controls, such as a few checkboxes, are smaller.
• Academy courses. Firms write and upload their own courses. A lesson video may not have captions unless the firm uploads them, and videos embedded from YouTube, Vimeo or Loom use those services' captions. Certificate PDFs carry a document title and language, but tagging them for screen readers is only partial; the same details are on the certificate's verify page, in plain HTML.
• What firms publish. A landing page, webinar page or intake link carries the firm's own words, images and colors. We check the templates, not what each firm writes, so a firm's choice of colors or missing image descriptions can cause problems we do not see.
• The signed-in application. Its screens are not scanned page by page. Some have problems we have not found.
• Other companies' parts. A bot check on some forms, and the payment pages of our payment processor, are not ours to change.

Tell us about a barrier

If something on GoRefer.io does not work for you, write to support@gorefer.io. Tell us the address of the page, what you were trying to do, and the browser or assistive technology you use. If you need information from us in another format, say so in the same message.

You can also reach us from our contact page or the support page.

GoRefer.io LLC, Dallas, Texas