Global Technical Guidelines

While designing and coding UI Element, we work on solving user issues by following design and code standards, but also complying to accessibility guidelines: WCAG and Renow luxembourgish accessibility guidelines. We know there is a lot to do yet, but our teams are on it.

Browser Support

We try to cover the majority of modern browsers. We have a lot of old software only compatible with old versions of Internet Explorer, but we launch a program to modernize our workplace (physically and virtually) and we are working on tacling this heritage.

That's why our work when it comes to coding is to be compatible with:

• Opera: 49+
• Internet Explorer: 11+
• Microsoft Edge: 12+
• Chrome: 49+
• Safari: 9+
• Firefox: 45+

Common Mobile Browsers on Mobiles and Tablets are included. Most of the interfaces we build are made for our Agents. As we control the type of device we distribute, we know that they are modern enough to support our developments.

Code Standards

Section being written…

Accessibility

One of our Design Principles we care the most at Foyer makes us build interfaces accessible for everyone. Accessibility here have to be taken as "available, readable and usable by people with disabilities", but by extension we would like to be accessible by everybody, under the principle of Inclusive Design.

Contrasts

For example, one of our job is to make User Interface contrasted enough through a good color palette, avoiding combination of colors that would be not contrasted enough. That's why you will find a table of color combinations (still work in progress) for every colors of our palette, to better know if 2 colors are compatible as foreground/background.

This work is not only done on colors, but also on typography, using the right font weight at the right place to bring a better readability to users.

Screen Readers

Screen Readers are softwares and sometimes hardwares that read the page for you when you are not able to do it on your own. For example, VoiceOver on Mac or iPhone/iPad is installed natively on you device and can be activated to read the content of the screen and help you interact with it.

Most of the time, native HTML 5 elements are compatible and well supported by screen readers. But with modern developments in JavaScript, you have to be careful (as a developer) of what you are building and how you do it. That's why we decided to take care of the accessibility part of the code within the UX Team, with the help of our developers.
As soon as we can, and as soon as necessary, we use semantic HTML elements and we implement the WAI-ARIA standard in our developments.

Accessibility requirements and advices are usually distributed with our technical documentation within the component documentation pages itselves.