Frequently asked questions
Clear, detailed answers about what Interface Resource Europe offers, how our resources are organised, and how to get help when you need it.
Before you read further
Interface Resource Europe is an independent reference site for people who design, build and maintain digital interfaces across European markets. The answers below explain our scope, our editorial approach and the practical details that visitors ask about most often. If your question is not covered here, the contact page lists every channel we use.
Common questions
We publish guides on interface structure, component patterns, accessibility checks and performance budgets. Each guide is written for working designers and developers, with worked examples and notes on where a pattern tends to fail in practice.
Yes. Reading every guide, checklist and reference table is free. We do not place advertising inside articles, and we do not sell reader data. Some downloadable worksheets ask for an email address so that we can send updates when a guideline changes.
Every article carries a review date. Guides on standards, such as accessibility requirements or data protection rules that affect forms, are checked at least twice a year. Smaller pieces on visual patterns are reviewed when browsers or platform guidelines change in a way that affects their advice.
Our main language is English, and we link to primary sources in other European languages where they exist. Regulatory notes focus on rules that apply across the European Union, such as accessibility obligations and cookie consent requirements, and we flag where national rules add further duties.
Yes, and we welcome it. Send the page address, the sentence in question and your suggested correction through the contact form. Corrections to facts are usually published within five working days, and each change is noted at the foot of the article.
How the library is organised
Resources are grouped by the question they answer rather than by the tool that produced them. Navigation, input handling, feedback and data display each have their own section. Within a section you will find a short orientation, a checklist you can apply to your own work, and a set of examples drawn from public European services.
Using the material in your work
- Start with the checklist at the end of each guide before reading the full explanation.
- Treat examples as starting points and test them with the people who will use your product.
- Record the review date of any article you cite in a design document.
- Ask for a second opinion on accessibility decisions from someone who uses assistive technology.
Our guidance describes common practice. It is not legal advice, and it does not replace an audit of your own product.
Where the answers come from
Each answer is based on a published standard, a platform guideline or a documented test we carried out ourselves. When we rely on our own testing, the method and the date are stated in the article so that you can repeat it.
Working with the reference
Many readers use the site alongside a live project. Pages are kept short enough to read between tasks, and each heading states the decision it helps with, so you can move directly to the part that affects your current sprint.
Still have a question that this page does not answer? Our editors read every message.
Contact the editorial team