Accessibility report
FIXI Website

Result: Passed

Observations:

Fixi uses the alt and title attributes of native HTML with a text value as alternative for non-text content that is presented to the user.

Result: Not present

Observations:

Fixi does not have audio-only or video-only media so there is no alternative required.

Result: Not present

Observations:

Fixi does not have media with prerecorded audio so there are no captions required.

Result: Not present

Observations:

Fixi does not have time-based media so there is no alternative required.

Result: Not present

Observations:

Fixi does not broadcast live audio content so there are no captions required.

Result: Not present

Observations:

Fixi does not have prerecorded video content so there is no audio description required.

Result: Passed

Observations:

Fixi is created with semantic HTML and makes proper use of ARIA attributes (such as aria-required) and roles to programmatically determine what is presented.

Result: Passed

Observations:

Fixi's content order in the DOM / what is visible on screen is always the correct reading sequence. This order can not randomly be changed by internal CSS, changing the sequence is always structured to its intent.

Result: Passed

Observations:

Fixi does not make users rely on sensory cues (e.g. shape, sound or visual location) to understand or operate content.

Result: Passed

Observations:

Fixi uses a responsive layout and does not lock functionality relative to orientation.

Result: Passed

Observations:

Fixi's input fields that collect personal user information are programmatically identifiable

Result: Passed

Observations:

Fixi uses colors just for decorative purposes, actual information what it means is always combined. For example, shown errors are red but clearly describe that user needs to do a certain action to continue.

Result: Not present

Observations:

Fixi does not play audio automatically so there is no audio control mechanism required.

Result: Passed

Observations:

Fixi's design rules cover that the contrast ratio of content is at least 4.5:1.

Result: Passed

Observations:

Fixi supports resizing text up to 200% without loss of content or functionality.

Result: Not present

Observations:

Fixi does not contain images with text that is crucial to be read. All meaningful text is wrapped by semantic HTML tags. The images containing text are mostly logos which are shown for illustrative purposes only.

Result: Passed

Observations:

Fixi's responsive design satisfies this criterion as it arranges content to be functional in a different layout when a high zoom level is used.

Result: Passed

Observations:

Fixi's design rules cover that the contrast ratio of all content is at least 3:1.

Result: Passed

Observations:

Fixi's content remains readable and its layout functional when overriding the line height or spacing.

Result: Passed

Observations:

Fixi ensures users can access and dismiss content that appears on hover or focus without losing information or functionality.

Result: Passed

Observations:

Fixi is fully functional without using a mouse.

Result: Passed

Observations:

Fixi's elements are able to receive focus using standard keyboard navigation without getting trapped in an element.

Result: Passed

Observations:

Fixi does not have custom single-character shortcuts so is compliant with this criterion.

Result: Passed

Observations:

Fixi does not contain time limits except for the contextual "service targets" of responding to the reporter for the first time and handling an issue. However, these time limits are real-time exceptions so they do not interfere with users having content open.

Result: Passed

Observations:

Fixi does not have unessential moving, blinking or scrolling that lasts more than five seconds. The main list of data, the issues, does auto-update unessentially but the auto-update triggers a section above the list showing the buttons "Refresh" and "Close" which acts as the mechanism for the user to control this content update.

Result: Not present

Observations:

Fixi does not contain any content that flashes more than three times in a second.

Result: Passed

Observations:

Fixi is created with semantic HTML and makes proper use of ARIA roles so bypassing blocks can be done by pressing the key equal to what the focus should be put on next, this navigation is compliant with the widely accepted defaults of screen readers (e.g. H for next header, B for next button, P for next paragraph, etc.).

Result: Passed

Observations:

Fixi's code changes the document's title attribute automatically with a value that describes the topic of a page whenever the user navigates to it.

Result: Passed

Observations:

Fixi can logically be navigated through by using the TAB key, the order preserves meaning and operability.

Result: Passed

Observations:

Fixi shows multiple links, the purpose of a link can be determined by reading the added context before it.

Result: Passed

Observations:

Fixi's pages can be reached by either going to a link directly or by using the navigation menu or tabs. For the pages that are used daily, like the issue details page, emails and push notifications are also send to the relative user which makes navigation possible with one button click.

Result: Passed

Observations:

Fixi's pages are correctly split into sections, each with its unique heading describing the section. Furthermore, form fields are combined with a label describing what the field is for.

Result: Passed

Observations:

Fixi's focusable elements always show an outline whenever focus is set on an element.

Result: Passed

Observations:

This criterion builds on 2.4.7, the outline shown on elements when focus is set on it is thick enough and is compliant with the contrast ratio.

Result: Passed

Observations:

Fixi avoids gestures that require multiple fingers for essential functionality, although sometimes exceptions are made, e.g. zoom behavior on the map. If that is the case, Fixi makes sure that there is an alternative for the same functionality, e.g. a button that operates the same way.

Result: Passed

Observations:

Fixi always shows a confirmation popup for critical actions to prevent accidental irreversible actions that can be triggered with just a single pointer.

Result: Passed

Observations:

Fixi's elements technically use the same name as what is presented visually.

Result: Passed

Observations:

Fixi does not contain functionality that can be operated by device motion so there is no alternative or option to disable this required.

Result: Passed

Observations:

Fixi supports drag and drop for uploading attachments from an external source, for this the dragging is essential. To not force the user to drag there is also an "Upload" button as alternative.

Result: Passed

Observations:

Fixi's target element for dropping an attachment is well over the required minimum size of 24 by 24 pixels. Currently the target is 390 by 170 pixels.

Result: Passed

Observations:

Fixi supports a total of 6 languages and the set language can be selected by the user itself.

Result: Passed

Observations:

Fixi does not contain static passages, phrases or words of a specific language. The website always strives to translate all displayed content correctly so there would not be exceptions to programatically cover.

Result: Passed

Observations:

Fixi might change styling or show and hide relative content but does not execute other functionality when putting focus on an element.

Result: Passed

Observations:

Same observations as described in criterion 3.2.1.

Result: Passed

Observations:

Fixi's order of navigation options can not be changed automatically as side effect of an action. The navigation options are purely based on the users role and permissions and therefore a change of visible options can only be initiated by the user itself.

Result: Passed

Observations:

Fixi is built on consistent design rules and makes use of a frontend framework whereby the concept of reusable components is important. Extra effort is also put into reusing icons and labels for relative functionalities. This results into a consistent identification of components.

Result: Passed

Observations:

Fixi supports one "human contact mechanism": the option to fill in a form with feedback. This form can be opened through a static button in the header and hence is not repeated on multiple web pages.

Result: Passed

Observations:

Fixi identifies items whereby an input error is detected by giving it a red color accent. In addition the error is described to the user in text, frequently placed under the input.

Result: Passed

Observations:

Fixi shows simple labels and sometimes full instructions for content that requires user input.

Result: Passed

Observations:

Fixi shows the error suggestions wherever applicable so the user would not get stuck somewhere without knowing why.

Result: Not present

Observations:

Fixi does not contain web pages that cause legal commitments or financial transactions for the user.

Result: Passed

Observations:

Fixi helps users to efficiently handle repeating processes so the software will also not request the user to fill in previously entered information, unless this is essential. For example, when resetting a password.

Result: Passed

Observations:

Fixi's native account type requires the user to remember their password, which is a cognitive function test that user owned password managers could assist with. Fixi also supports different kind of authentication like SSO or OAuth with Apple, Facebook or Google as alternatives.

Result: Passed

Observations:

Fixi's code mostly contains native HTML and uses ARIA labels and roles for its custom components to inform assistive technologies what kind of purpose the elements have.

Result: Passed

Observations:

Fixi uses the ARIA attribute role with value "status" and the ARIA attribute live with value "polite" to present status messages to assistive technologies automatically without user focus being required for this.