InFact Accessibility Statement – Web Survey

Last reviewed May 5, 2026

Accessibility Commitment

At InFact, our goal is to provide Web Survey services that are clear, reliable, and accessible to as many users as possible. Web Survey is used to collect feedback, opinions, and insights from different groups of respondents, and we believe that everyone should be able to participate regardless of ability, device, browser, or assistive technology needs.

Accessibility is an important part of how we develop and maintain Web Survey. Our work is guided by the Web Content Accessibility Guidelines (WCAG) 2.1 and the core accessibility principles of making digital content perceivable, operable, understandable, and robust.

Our Web Survey has been reviewed using a combination of automated and manual accessibility testing, including Chrome Lighthouse, Accessibility Insights for Web, WAVE, axe DevTools, and Uutilsynet’s accessibility checklist. The review covered typical Web Survey pages and elements, including landing pages, authorized survey pages, multistep survey forms, text fields, email and phone fields, comment fields, radio buttons, checkboxes, rating questions, dictionary questions, date pickers, required fields, buttons, visibility rules, and survey templates.

Several important accessibility requirements are already supported in Web Survey:

Form accessibility. Many standard form elements, including form fields and select elements, have associated labels. Buttons have accessible names, and required form elements are handled through the survey structure.

Images and visual content. Image elements include alternative text, and image alternative text is not marked as redundant where tested.

ARIA and assistive technology support. ARIA roles are used only on compatible elements, deprecated ARIA roles are not used, role values are valid, and role attributes include the required ARIA properties where relevant.

Page structure. Tested pages include document titles, and frames or iframes include titles where used. The survey pages also avoid placing aria-hidden=”true” on the document body.

Colour and readability. Tested Web Survey pages showed sufficient foreground and background colour contrast in several key checks.

Keyboard and navigation support. The tested survey pages include navigation structures such as headings, skip links, or landmark regions, helping users navigate more efficiently.

Dashboard-related accessibility. Related Web/Dashboard functionality already supports several important accessibility practices, including valid language settings, valid ARIA attributes, image alternative text, correct page titles, no positive tabindex values, sufficient touch target size and spacing, and structured headings.

Accessibility is an ongoing process, and we are continuing to improve Web Survey in the following areas:

Labels and accessible names. We are improving accessible names for links, icons, images, progress indicators, custom controls, and form elements that require clearer screen reader support.

Language settings. We are improving language handling so that Web Survey pages and page sections are correctly announced by screen readers, including Norwegian, Swedish, and other language content where applicable.

Keyboard accessibility. We are working to improve keyboard access to interactive elements such as date pickers, rating scales, custom checkboxes, edit/delete actions, key-field settings, and dashboard controls.

Zoom and mobile usability. We are reviewing viewport settings and touch target spacing to better support users who rely on zooming, magnification, or easier touch interaction.

Page navigation and structure. We are improving landmarks, headings, semantic lists, data tables, and skip-to-main-content functionality to make Web Survey easier to navigate with keyboards and assistive technologies.

Visual accessibility. We are continuing to review contrast, focus visibility, colour use, greyscale and colour-blind scenarios, and template designs that may rely too heavily on visual styling.

Survey templates. We are improving custom survey templates so that custom styles and scripts do not reduce accessibility for buttons, checkboxes, instructions, logos, submit actions, and repeated content.

Error and issue reporting. We are planning to add a clearer “Report an issue” function for Web Survey and survey landing pages, so users can more easily report accessibility or usability problems.

We will continue to review Web Survey as new functionality is developed, as templates are updated, and as survey-related functionality is improved.

Accessibility assistance

If you experience difficulty using or accessing an InFact Web Survey, or if you have suggestions for how we can improve accessibility, please contact us at post@infact.no or use the available report issue function where provided.