About iron, birds and flowers
#Soul tech
03.17.2023 Reading time: 10 minutes
BizkaiaTech editorial team
Illustration: Dom Campistron
Digitalisation has become a dominant trend in recent years, as companies around the world have perceived the need to transform their businesses; for example, by transferring their services to the Internet, a webpage, or an application.
TECHNOLOGY FOR ME AND MY GRANDMA
Both private companies and the government are using this resource. But what does the digitalisation of services mean, anyway? When we say “digitalisation”, we mean transferring a reality (usually a service) from one medium to another. And the fact is that this is what must be done, as everyone is doing it. If we make everything digital, there will be no problem, since everyone will have access to everything they need, right?
Wrong. That’s not how it works. This is because, if the transfer of that reality to the digital world isn’t done correctly, there are always people who will get lost along the way. Why is this? Because in the real world, the digitalisation of services is usually not very accessible.
We discussed this topic with José Pajares, director and Accessible Design expert at Accenture Song’s design studio. He’s in charge of creating tools that fit with everyone. In a world of inflexible iron where everything is very pragmatic, technical, and technological, he upholds the role of birds and flowers, the more sensitive and empathetic side. Thus, we wanted him to give us his opinion on this topic.
But… we may be going too fast. Let’s back up a bit… What do we mean when we speak of “accessible design?” In a nutshell, it’s the kind of design that seeks to leave nobody behind. Its goal is for everybody – regardless of their origin, disability, level of schooling, or age, among other things – to be able to do what they need to do, easily and clearly. To put it even more simply, it’s about making sure that your aitona (grandpa) can see how much money he has in the bank without leaving his home, or ensuring that a woman who has just arrived from another country can easily get the paperwork she needs to start her working life here.
Accessible design is the key for society to move forward without leaving anyone behind.
TECHNOLOGY THAT EXCLUDES THOSE WHO IT INCLUDES
While the idea may be great, the reality of accessible design is far from ideal. Nowadays, no one has to go to an office to pick up paperwork, a certificate, or any other document they require, because everything has been digitalised. Transferring everything printed to the Cloud is a great idea for everyone to have access to whatever they need. Even so, a few mistakes were made when carrying out this digitalisation process. Even if everything one requires is there, if browsing those pages is a difficult and tedious process, in general, people at risk of exclusion will suffer even more complications.
Pajares has observed three trends in the digitalisation of services. He calls the first trend the “scanner philosophy”, which denotes how we transfer documents to the Internet just as they’re written on paper, without making any changes to their language or design. The issue with this is that all the problems that the physically written form has are transferred to the Cloud, which generates even more confusion. Pajares believes that sometimes we lack a bit of empathy. And this lack of empathy, this failure to talk to those who are really going to use and deal with the digital solution, causes us to make basic mistakes; basic, but as glaring as designing a solution meant only for PCs when the person who needs to use it only has a mobile phone, and their data plan is limited. These “little mistakes” end up producing frustration and constituting a lack of respect towards people, as they unintentionally ignore those who are negatively affected by them.
The second problem arises from digitalisation itself, since there is a tendency to digitalise everything just because we can, without taking into account the intended use and the needs of those involved. As an example of this, he talks about the “App Factory” phenomenon, referring to the compulsion to turn every webpage into an app. At times these entities, often due to demand and production speed, don’t ask themselves the necessary questions that should be posed when creating an app, such as: Why? What’s the goal? What type of user is it for? Etc. Consequently, we end up with thousands of apps that are not used in the long run.
The last issue that Pajares comments on is the well-known question of saving money. Unfortunately, more importance is often attached to this than simply coming up with a good design that is accessible to everyone. This, generally, consists of slashing costs that organisations consider “unnecessary” at the expense of app users’ consumer experience. Banks are an example of this. Why are they closing so many branches daily? How do we explain to an 80-year-old woman who has always interacted with her bank in the same way for the last 60 years that she now has to change and use an app? She may not even have the tools necessary to do so, like a mobile phone or a laptop computer.
THE DEFINITIVE GUIDE TO PRODUCING ACCESSIBLE DESIGN
Since there’s always a solution to every problem, Pajares points out some ways to make the accessibility process more efficient. Are you interested in finding out how to produce design that leaves no one behind?
First of all, and probably the most important thing, is empathy. Do you remember what we talked about? The thing about the birds and flowers? Although this sounds a bit like a “hippie” philosophy, putting yourself in other people’s shoes completely changes your perspective when devising a design. Let’s face it: without this exercise in empathy, users may feel hurt and insulted. The “I’m older, not an idiot” social movement is a clear example of this. This protest originated in Valencia with the aim of criticising the differences created by the technological divide. Shortly after it began, the movement’s petition had already garnered some 350,000 signatures, revealing design deficiencies.
The movement focused on banks’ prioritisation of money over empathy. This movement’s popularity gave rise to a social debate about accessible design, which has spotlighted another factor: the important role of companies’ reputations.
Pajares’ second piece of advice for achieving accessible design is to be inclusive when creating. This level of inclusion can be achieved in two ways: the first is to have people who are at risk of exclusion on the design team itself. This way, any problems that arise throughout the process can be evaluated internally. The other way to include these groups is to seek external advice. If we ask for guidance from people who have nothing to do with the project, they’ll be able to tell us how much of a problem the design we are working on poses for them. Thus, besides helping us comply with the law, they’ll help us to be better designers…achieving a much better product as a result.
The next step is to study closely the law that we’ve just mentioned. The law of September 2018 (Official State Gazette, Royal Decree 1112/2018), which governs everything that has to do with the design, building, maintenance, and updating of a webpage, is the Spanish adaptation of a European Parliament Directive (Directive UE 2016/2102). Both are a reflection of how pressing this issue of accessibility and inclusion is. It’s a law that changes experiences for the better. Sometimes it’s not only necessary for people to be sure about the topic and to call for accessible design, but certain guidelines are also needed, like those that can be found in the aforementioned Directive:
- Audio and video pieces must be accompanied by subtitles and transcripts.
- All graphic elements should have descriptive texts.
- Webpage and app layouts must be orderly and clear.
- There should be a number of ways to interact with a webpage: voice, mouse, keyboard, etc.
- The text and background colours of a webpage or app must have the proper contrast.
In addition, beginning in 2022, private companies will also be regulated by law, which, until now, only affected governmental bodies, subsidised private companies, and private companies working on public projects.
Pajares’ final recommendation is aimed directly at designers. Many of the suggestions given so far require a decision from top officials to move forward. If the person in charge doesn’t give their approval, the project doesn’t go ahead. Or does it? In design, it’s essential to consider accessibility. Discussions, research, and even testing with users are some of the ways to make a difference.
DESIGNING A MUCH MORE INCLUSIVE WORLD
It’s clear that technology has done a lot for people at risk of exclusion. One only has to look at the progress we’ve made: today, the visually impaired can read newspapers thanks to screen readers, and the hearing impaired are using cochlear implants to be able to hear.
Even so, Pajares believes that much remains to be done. First of all, he speaks of the law, which has to continue to evolve and adapt, just as we all have to evolve and adapt to it. Additionally, he insists that we have to put ourselves in other people’s shoes more often. Although the philosophy of “nobody tells me whether or not to have a glass of wine” that Prime Minister Aznar became known for is widespread in society, we need to reflect and debate more on matters of accessibility. In this way, just like what is happening with women’s rights and gender-based violence, we can raise awareness and, in turn, change things.
The conclusion is that accessible design is a plus for everyone: immigrants, disabled people, seniors, the uneducated, and for you. The truth is that when we design without leaving anyone behind, we design better.
Doing things this way, let’s see if we can get the “bird and flower” revolution to be important enough to make inroads in our “iron” world.
Labels
- #cultura
- #bigscience
- #colaboración
- #democratización
- #educación
Take our advice and check it out
Slide to show more
Cookies
We use proprietary and third-party cookies for technical, analytical and customisation purposes, such as choosing the language in which to display the website. For more information, please consult our cookies policy (Opens modal window).
Cookies policy
The website at https://www.bizkaia.eus (hereinafter, the Website) uses tools to track browsing activity on the website and the IP address of the service recipient for the purpose of improving and guaranteeing the provision of services or technical operation of the website, distinguishing you from other users and analysing your browsing habits.
This Cookies Policy seeks to inform you clearly and precisely about the operation and function of the cookies we use.
What are cookies and why do we use them?
A cookie is a file that is downloaded to your computer when accessing certain websites.
Cookies enable a website to, among other things, store and recover information about the browsing habits of a user or their device and, depending on the information contained and the way in which the same is used by the device, may be used to recognise the user.
Current law allows us to store cookies on your device if they are strictly necessary for operation of this website. However, we need permission for all other cookies.
Types of cookies based on the managing entity
Depending on who manages the computer or domain from where the cookies are sent and who processes the data obtained, a distinction can be made between the following types of cookies:
- Proprietary cookies: these are managed by the Provincial Council of Biscay.
-
Third-party cookies: these are managed by another entity, which processes the data obtained via the cookies.
This website may contain cookies belonging to the Basque Government, used for its own purposes and stored by domains other than those owned by the Bizkaia Provincial Council.
Types of cookies based on their purpose
- Technical cookies: these allow the user to browse a website, platform or application and to use the various options or services available, such as control data traffic and communication, identify the session, access restricted areas, request registration or participation in an event, use security elements while browsing, store content for video or audio playback, or share content via social media networks.
- Customisation cookies: these allow the user to access the service with some general characteristics predefined according to a series of criteria on the user’s device, such as the language, type of browser being used to access the service, regional configuration from where the service is accessed, etc.
- Analysis cookies: these allow the number of users to be counted and the browsing activity to be statistically measured and analysed for the purpose of improving the services made available. They may be proprietary or third-party cookies.
Duration of the cookies
- Session cookies: these collect and store data while the user is visiting a website.
- Persistent cookies: the data are stored on the device in an ongoing fashion and may be accessed and processed during a period defined by the cookie manager, which may range from a few minutes to several years.
Which cookies does this website use?
In each row you can find data relating to Technical cookies
| Name | Purpose | Duration | Owner |
|---|---|---|---|
| JSESSIONID | Session identifier | Session | Bizkaia Provincial Council |
| ASPSESSIONID | Session identifier | Session | Bizkaia Provincial Council |
| TS01 | Session identifier | Session | Bizkaia Provincial Council |
| LFR_SESSION_STATE | Session identifier | Session | Bizkaia Provincial Council |
| COOKIE_SUPPORT | Indicate whether the user has the cookie support activated | 1 year | Bizkaia Provincial Council |
| pc_tecnicas_bizkaia | Choose your preferences for acceptance of the block of technical cookies | 1 year | Bizkaia Provincial Council |
| pc_analitica_bizkaia | Choose your preferences for acceptance of the block of analytical cookies | 1 year | Bizkaia Provincial Council |
| pc_preferencias_bizkaia | Choose your preferences for acceptance/rejection of the block of preferential cookies | 1 year | Bizkaia Provincial Council |
| pc_terceros_bizkaia | Choose your preferences for acceptance/rejection of the block of third-party cookies | 1 year | Bizkaia Provincial Council |
| Kultursistema_session | Keeping the user’s session | 1 year | Kultursistema |
| CPLB | Contains information used by our load-balancing servers | Session | Provincial Council of Biscay |
| XSRF-TOKEN | To prevent CSRF (Cross-Site Request Forgery) attacks | 1 year | Kultursistema |
| _GRECAPTCHA | Protects the website from spam and brute-force attacks | 5 months |
In each row you can find data relating to Analysis cookies
| Name | Purpose | Duration | Owner | |
|---|---|---|---|---|
| dtCookie | Track a visit through multiple requests | Session | Bizkaia Provincial Council | |
| dtLatC | Measure the latency of the server to monitor performance | Session | Bizkaia Provincial Council | |
| dtPC | Necessary to identify the appropriate parameters for beacon transmission; includes session ID for correlation | Session | Bizkaia Provincial Council | |
| dtSa | Intermediate storage for actions spanning pages | Session | Bizkaia Provincial Council | |
| rxVisitor | Visitor ID to correlate sessions | Constantly | Bizkaia Provincial Council | |
| rxvt | Session waiting time | Session | Bizkaia Provincial Council | |
| iyrc-user-id | Distinguish users | 1 year | Bizkaia Provincial Council | |
| _ga, _ga_XXXXXXXXXXX | Analysis | To distinguish users | 2 years | Google Analytics |
| _gat, _gat_XXXXXXXXXXX | Analysis | To limit the percentage of requests | 1 minute | Google Analytics |
| _gid | Analysis | To distinguish users | 1 day | Google Analytics |
In each row you can find data relating to Personalisation cookies
| Name | Purpose | Duration | Owner |
|---|---|---|---|
| Idioma | Select the language preferred by the user | 1 year | Bizkaia Provincial Council |
| cookie-tramites-favs | Save favourite procedures in Prior Appointment | 1 year | Bizkaia Provincial Council |
In each row you can find data relating to Third-party cookies
| Name | Purpose | Duration | Owner |
|---|---|---|---|
| CLID | Identify a user’s first visit | 1 year | Microsoft Clarity |
| APISID | Store user preferences and information during page views with Google maps in them. | 2 years | |
| HSID | Store user preferences and information during page views with Google maps in them. | 2 years | |
| MUID | Store user preferences and information during page views with Google maps in them. | 1 year | Microsoft Clarity |
| NID | Remember their preferences and other information | 6 months | |
| SAPISID | Show personalised advertisements on Google sites | 2 years | |
| SID | Provide advertisement delivery or retargeting, provide fraud prevention. | 2 years | |
| SIDCC | Provide reliable web traffic identification. | 1 year | |
| SM | Used to synchronise the MUID between Microsoft domains. | Session | Microsoft Clarity |
| SSID | Provide advertisement delivery or retargeting, provide fraud prevention. | 2 years | |
| __Secure-1PAPISID | Create a website visitor interest profile to show relevant and personalised Google advertising. | 2 years | |
| __Secure-1PSID | Create a website visitor interest profile to show relevant and personalised Google advertising. | 2 years | |
| __Secure-1PSIDCC | Create a website visitor interest profile to show relevant and personalised advertising through retargeting. | 1 year | |
| __Secure-1PSIDTS | Create a website visitor interest profile to show relevant and personalised advertising through retargeting. | 1 year | |
| __Secure-3PSID | 2 years | ||
| __Secure-3PSIDCC | Create a website visitor interest profile to show relevant and personalised advertising through retargeting. | 1 year | |
| __Secure-3PSIDTS | Create a website visitor interest profile to show relevant and personalised advertising through retargeting. | 1 year | |
| __Secure-ENID | Necessary cookies to use website services and options | 1 year | |
| ar_debug | Refine advertisements. | 1 año | |
| MR | Indicate when MUID is refreshed | 6 months | Microsoft Clarity |
| XSRF-TOKEN | Indicate when MUID is refreshed | 1 hour | Kultursistema |
| _fbp | Store and track website visits | 1 year | |
| kultursistema_session | Keep the user’s session | 1 hour | Kultursistema |
| AEC | Detect spam, fraud, and abuse | 6 months | |
| SOCS | Store user cookies preferences | 13 months | |
| Locale | not available | Basque government | |
| _hegoa_coop_session | Create a session ID for users | Session | Basque government |
How to deactivate or delete cookies?
When first accessing the Website, the user may configure and accept or reject the cookies on this Website. Subsequently, the user may change or withdraw their consent at any time via this Cookies Policy or the settings page.
However, you may exercise your right to freely deactivate them and even delete the cookies on this Website at any time. This is done differently depending on which browser you are using. Here is a quick guide for the most popular browsers.
- Deactivate Cookies in Chrome
- Deactivate Cookies in Explorer
- Deactivate Cookies in Firefox
- Deactivate Cookies in Safari
- Deactivate Cookies in Edge
If you deactivate or delete cookies, certain features of the Website may no longer function correctly.
Changes to the Cookies Policy
The Website reserves the right to change this Cookies Policy under the terms provided for by current legislation. We therefore recommend that you revise this policy each time you access our website to see any changes and read the pertinent information.
Configure cookies
We show you hereinbelow the different categories of cookies that our web page uses. You can personalise your choice by accepting or rejecting these categories through the buttons enabled to that end. For more information, consult our cookies policy (Opens modal window).
-
Technical Always active
These are needed to allow browsing on our website and for basic tasks related to correct website operation.
