Of course, this affects website owners worldwide, as any site that serves even one EU citizen is obligated to comply. So, whether you’re based in Paris, France, or Paris, Texas – GDPR applies to you.

The internet has been in a mad scramble as companies send out masses of email notices and are changing privacy policies at near lightspeed. But if you haven’t gotten around to dealing with the issue just yet – it’s okay. We have your back!

Below are eight helpful resources you can use to bring yourself up to speed and get your site into compliance.

*And, as the standard legal disclaimer goes, please know that these resources won’t, by themselves, ensure compliance. It takes some work on your part and advice from a legal professional to make things more official.

The GDPR Compliance Checklist

This interactive checklist will help ensure that you are on the right path to compliance.

While it doesn’t cover every possibility, it is quite handy to have a list in front of you if only to help you gain some peace of mind in a very complex situation.

Awesome GDPR

Developer Erwan Richard has curated this list of tools and resources that you can use to become compliant. Included are alternatives to Google Analytics, Maps and even social sharing buttons that don’t track user data.

Complianz GDPR/CCPA Cookie Consent

WordPress 4.9.6 came stocked with some new privacy tools that have GDPR in mind.

Complianz will scan your WordPress website and generate a cookie consent and policy based on what it finds. The plugin can be configured to display a cookie notice for your specific region, but you can also use a blanket notice for all users. It also blocks common third-party cookies and iframes. And that’s just scratching the surface of what this privacy suite can do.

Anonymizer

Working with a database that is full of personal user information in a development environment? Anonymizer is a tool that will replace that info with randomly generated content.

Obviously, it’s not meant for production environments – but provides an extra layer of security when you’re in the development phase.

GDPR Module for Drupal

If you’re running a Drupal site and looking to become GDPR compliant, this module can be a great help.

It lets users see what data your website collects, while also providing administrators with handy tools to manage data and user consent.

Cookies EU Banner

Cookies EU Banner is a very lightweight JavaScript library for gaining user consent to be tracked by services such as Google Analytics.

All it takes is a little bit of code at the top of your page to get started. The library even has the option of not setting a cookie until the user has accepted your policy.

GDPR Developer Guide

If you’re looking for a crash course in GDPR compliance, this open-source guide is for you. Through 16 chapters, you’ll find information regarding everything from identifying personal data to working with analytics. The overarching goal is to help developers build with privacy regulations in mind.

GDPR is Here for the Long Haul

While the chaos and extensive news coverage may fade, GDPR isn’t going anywhere. It certainly may see some tweaks in the future, but it is the new normal for web designers worldwide. The old way of doing things is, for better or worse, over.

The resources above could prove to be a big help as we navigate the many facets that GDPR presents. Use them to help develop processes that will ensure compliance by default. That way, this regulation becomes just another part of your job, rather than an extra burden to think about.

The post 7 Best Free Resources For GDPR Compliance appeared first on Speckyboy Design Magazine.

It has become more important to think about the tools we use. Nowhere is this more evident than in online privacy. The potential ramifications are serious.

That’s due to a combination of factors. First, there is more awareness of privacy issues. Regulations such as GDPR also play a role. And we can’t forget about opportunistic people. Many are testing boundaries with lawsuits.

As usual, web designers are caught in the middle. Some features we routinely implement for clients have become controversial. And we’re often the first point of contact when a problem arises. It’s awkward at best – and extremely stressful at worst.

So, how can we navigate this treacherous minefield? Here’s how online privacy is impacting web designers – and what we can do about it.

What’s at Stake for Web Designers?

Web designers often act as a liaison between clients and third-party services. That puts us in a unique position when it comes to privacy.

No, we’re not the ones tracking the site’s users. But we implement such software. Therefore, it’s important to understand our risks and responsibilities.

Imagine a scenario where a lawsuit is filed against your client. Someone is claiming that the client’s website (which you built) is violating privacy laws.

A reasonable client likely wouldn’t blame you. After all, you don’t control the data collection policies of another company.

But not everyone is reasonable or rational. They may be looking for an easy scapegoat. And you could be a target.

The outcome could be costly both mentally and monetarily. And it could impact your business immeasurably.

It’s bad enough if this type of incident happens once. But what’s to stop it from happening again?

Your risk would be multiplied by every website you build. It might drive up the cost of doing business. Or it could convince you to leave the industry altogether.

No one wants that. So, how do we minimize the possibility?

Recognize the Risk of Third-Party Tools

Third-party tools have long been a part of web design. We add social media feeds. And we help clients gauge site traffic via analytics.

We perform these tasks over and over. But how many of us have considered the impact?

Privacy concerns are nothing new. The issues posed by Facebook, Google, etc., have been discussed for years.

But it feels like those discussions were very broad. We’ve talked about the policies and practices of these companies. However, not much is said about what it means to the average website.

The focus has narrowed. It’s not unusual for website owners to be singled out by lawyers. And in many cases, a third-party tool is part of the alleged violation.

This is a mess for web designers and their clients. Therefore, the days of adding these features by default are over.

Discuss Online Privacy With Your Clients

Clients may not understand the correlation between online privacy and their website. Thus, it’s worth discussing third-party tracking tools with them.

The idea isn’t to dissuade them from using these tools. Rather, it’s about making them aware of the implications. For example, giving them a broad outline of what Facebook Pixel is used for.

This empowers them to make an informed decision. In some cases, a tool may offer more risk than reward.

Also, some industries have stringent privacy regulations. The healthcare and government sectors, for example, may rule out the use of certain tools.

And there are some questions web designers can’t answer. We’re not lawyers. Therefore, encourage your clients to seek an expert opinion when necessary.

Proactively discussing these issues brings them to the forefront. Hopefully, that will lead to more focus on privacy.

Service Providers Must Evolve With Privacy Standards

We could forgo the use of analytics, ad networks, and social media. But that’s not realistic. Each of these areas is still important. They help with decision-making, marketing, and revenue.

There are alternative services that focus on privacy, however. For example, analytics apps that don’t log user-specific information. And you might use federated social networks that don’t track a user’s every move.

The downside is that clients may be giving up some advanced features. Not to mention the reach offered by the biggest names in these spaces.

That’s why service providers must evolve. Neither website owners nor web designers should be put at risk by using these tools. Instead, they should be confident that they’re doing right by users (and the law).

Google Analytics 4 is a step in the right direction. It eschews much of the user-specific data of its predecessor. Yet there are still questions regarding compliance with GDPR and other regulations.

It behooves big data providers to take privacy seriously. Otherwise, the risk of using their products will be too high.

Privacy Is Yet Another Web Battleground

There’s no shortage of challenges for web designers. Privacy has taken its rightful place alongside security and accessibility. Each has real-world consequences.

And like those other two concerns, there are steps we can take to mitigate risk. Caution and communication are the keys.

First, we must understand how privacy is impacted by third-party tools and services. We can scrutinize them and avoid the worst offenders.

Secondly, we can use our role as educators to keep clients informed. We can make them aware of privacy concerns so that they can act accordingly.

It’s also important to protect ourselves. That means including language about privacy in contracts. And also pointing clients toward legal professionals for advice.

None of this is simple. But it’s a growing part of what freelancers and small agencies must manage.

The post How Online Privacy Is Impacting Web Designers appeared first on Speckyboy Design Magazine.

You see, the world is a very complicated place. We web designers were never completely immune to its problems, but suddenly it feels like we’re thrown in the middle of it all.

Between the expected launch of the WordPress Gutenberg editor, GDPR (EU General Data Protection Regulation) taking effect and now Google’s announcement that, oh yeah, you’re going to have to pay for using their Maps API, web professionals are going to sweat a bit more in the summer heat. The sense of impending doom swirls like a fly that’s landed in our fancy umbrella drink.

It almost makes you cringe to think about what the next unpleasant reality will be. Mandatory summer school? Hosting blackouts? A return of IE6? I shudder at the mere thought.

But, like all challenges that are in our way, we have the ability to thrive (or at least survive). So, before it’s too late, let’s dig into your official survival guide to this summer of headaches.

Accept the New Reality

Yes, denial is usually the first step in recovery – but we’re talking survival here. The fact is that our jobs are starting to entail more responsibility. This is especially so for freelancers who don’t have a dedicated team to help with all of the real messes created by these virtual entities. It is our new reality, whether we like it or not.

Things are only going to get more complex from here. The best way to tackle this challenge is to put processes in place that:

• Inform affected clients of impending changes
• Proactively prevent problems before they occur
• Put security at the forefront

Of course, we can’t always predict outcomes. But we can prepare ourselves by learning as much as we can about these issues and taking proactive steps to put our projects in the best possible position to adjust as needed.

So, while dealing with many of these issues can be a pain, we’re better off adjusting our workflows to account for them. If that doesn’t work, then it may be worthwhile to simply hide under a beach towel until said issues pass us by.

Say Goodbye to the Days of Free APIs (From Google, at Least)

To some developers, hearing that Google was going to start charging everyone for API access (even with their “free” $200 per month credit) was a bit like getting hit in the back with a lawn dart. In other words, it was a shock that this seemingly-benevolent company was putting longtime users behind the proverbial 8-ball.

There’s no doubt that Google, like any other company on the planet, is all about making money. That’s their right. But the timing of this change couldn’t have been worse, what with the other aforementioned major changes the web is facing. The fact that they are giving developers just over a month to scramble to get their accounts straightened out brings to mind the chaos of a bunch of kids chasing after an ice cream truck. Sorry kids, no more free samples.

In many respects, we all should have seen this coming. Google has been tightening up other tools like Analytics in recent years – it was only a matter of time before the APIs followed suit.

Beyond the actual “we’re going to charge you” fiasco, even worse is the horribly confusing UI Google has implemented in their developer dashboard. Finding the right page in the incredibly dense hierarchy is akin to winning one of those rigged carnival games.

And, while they let you set quotas to limit API usage for a project (ostensibly to avoid unwanted charges on the billing account they now force you to create), the interface is confusing to us mere mortals. There are no less than 49(!?!) different items listed and, get this, you can only set daily quotas. Yet they are charging us by monthly API access. We’re going to need a mathematician and an archaeologist to get through this thing.

Rants aside, it’s wise to assume that there is going to be a cost to add these types of features to a website. And it’s on us to advise clients that the use of anything from Google could incur a cost at any time.

Take it One Challenge at a Time

When taken together, it sure seems like a lot of issues for designers to deal with. And there’s no doubt that things have the potential to be very hectic with these large changes happening all in short order.

Gutenberg, for its part, is sort of an unknown quantity in that we don’t know the exact day it will ship. We’re simply told that it will be released as part of WordPress 5.0 when it’s ready. The best we can do is prepare sites and hold back on using the new editor if it isn’t 100% compatible. And, since it’s pre-release version is available as a plugin, we can at least do some testing while we wait for the editor to be merged into WordPress core.

On the other hand, we know that GDPR hits on May 25 and that Google Maps APIs will start requiring both a valid key and billing information to continue working beginning on June 11. It doesn’t give us much time, but at least we know the do-or-die dates.

These issues all affect us differently, depending largely on what’s in our maintenance portfolio. But if you’re in that unlucky crowd where all three impact your workflow for the summer and beyond, don’t let yourself feel overwhelmed.

Instead, prepare for the extra work that may come your way and expect that there will be complications. Then, knock things off of your to-do list one challenge at a time.

Who knows, if you find a way to handle everything in an efficient enough manner, you might even be able to take that vacation after all.

The post The Grumpy Designer’s Summer Survival Guide appeared first on Speckyboy Design Magazine.