Word accessibility in WordPress

 key image with disabled logo

The advantages of web accessibility can be summarized in the following quote from Steven Pemberton, president of W3C forms and HTML working groups:

Your most important user is blind. Half of the visits to your site come from Google, and Google only sees what a blind person can see. If your site is not accessible, you will have fewer visits. End of the story

Google sees your site practically as a blind visitor would so there you have a good element of reflection, right? But there is more, much more …

:: Advantages of web accessibility ::

In case you are not worth these arguments there are more advantages of offering a site according to web accessibility standards :

  1. Increase the number of potential visitors to the website : this is a very important reason for a company that wants to attract new customers. When a web page is accessible it does not present barriers that hinder its access, regardless of the user's conditions. A web page that meets the standards is more likely to be displayed correctly on any device with any browser. According to data from the INE (1999), 9% of the population in Spain has some disability, in total 3,528,221 people.
  2. Reduces the costs of development and maintenance : although initially learn to make a accessible web page implies a cost (just as it costs to learn to use any new technology), once you have the knowledge, the cost of developing and maintaining an accessible web page is less than that of an inaccessible web page accessible web is a well-made page, less prone to contain errors and easier to update.
  3. Reduces the loading time of the web pages and the load of the web server : by separating the content of the information about the presentation of a web page through CSS reduces the size of web pages and, therefore, reduces the loading time of web pages.
  4. Demonstrates social responsibility . You fulfill a citizen's right to participation and non-discrimination because of disability.
  5. You comply with the legislative provisions in this regard, both by the Public Administration, which is obliged to do so before the public, and by private networks that aspire to participate in contracts with the Administration or public financing.
  6. When designing according to accessibility standards, we guarantee the equivalence of contents between different browsers and devices ;
  7. Better indexing in the engines of search . The fulfillment of the guidelines, both in code and in semantic contents (for example, links with sense) allows the search engines to better identify the contents, and consequently, greater possibilities of positioning in the search engines.
  8. Improvement the usability of the web . Although they are not equivalent, accessibility has a close relationship with the usability of a site. By meeting basic accessibility requirements in the technical elements of a website (content structure, links, color contrast, effects and movements, forms, tables, etc.), the conditions of use for most people improve. [19659022] :: Spanish legislation on web accessibility ::

    And, if that were not enough motive, there is sufficient reason to take it into account based on the Spanish legislation that regulates the rights to accessibility on the web :

    • Law 34/2002 of July 11, on services of the information society and electronic commerce.
    • Law 51/2003 of December 2 on Equality of Opportunities, Non-Discrimination and Universal Accessibility with disability (LIONDAU).
    • Royal Decree 366/2007 of March 16, on accessibility and non-discrimination of persons with disabilities in their relations with the General State Administration.
    • Law 27/2007, of October 23 re, by which the Spanish sign languages ​​are recognized and the means of support for oral communication of deaf people, hearing impaired and deafblind are regulated.
    • Royal Decree 1494/2007, of November 12, by the that the Regulation on the basic conditions for the access of persons with disabilities to the information society is approved.
    • Law 49/2007, of December 26, establishing the regime of infractions and sanctions in matter of equal opportunities, non-discrimination and universal accessibility for people with disabilities

    :: Problems related to web accessibility ::

    The main limitations that must be taken into account when making our website accessible would be the following:

    • Visuals : In its different degrees, from low vision to total blindness, in addition to problems to distinguish colors (Daltonism).
    • Motrice s : Difficulty or inability to use the hands, including tremors, muscle slowness, etc., due to diseases such as Parkinson's, muscular dystrophy, cerebral palsy, amputations, among others.
    • Auditory : Deafness or auditory deficiencies
    • Cognitive : Learning difficulties (dyslexia, dyscalculia, etc.) or cognitive disabilities that affect memory, attention, pas logical skills, etc.
    • Old age : People with disabilities can add the group of people of the "third age", since the deficiencies and problems of the physical media, as well as many times the content, mean that these people are also at risk of infoexclusión.

    Based on this, people with these difficulties may encounter a series of accessibility problems:

    • Device management : Telephones, computer is, ATMs and digital television most of the time are not designed and placed, in the case of ATMs, paying attention to the needs of people with disabilities. The variety of terminals is very large, what you should look for is to follow the tendency to reduce them and access all the services through a few. More and more websites are visited with all kinds of devices
    • Interaction with interfaces : Menus, navigation bars and buttons are not usually accessible from a variety of adapted terminals.
    • Access to content : The contents that are accessed from the same device are increasing and this rapid growth does not usually address the specific needs of the disability.

    :: Levels of priority and compliance with web accessibility ::

    Web accessibility is divided into a spectrum of three priority levels :

    1. Priority 1: are those points that a Web developer has to meet since , otherwise, certain user groups could not access to the website information.
    2. Priority 2: are those points that a Web developer should comply with, otherwise, , be very difficult to access information for certain groups of users.
    3. Priority 3: are those points that a Web developer should comply with because, otherwise, some users would experience certain difficulties in accessing information .

    Based on these verification points, the levels of compliance are established:

    1. Level of Conformance "A": all points Priority 1 verification is satisfied.
    2. "Double A" Level of Conformity: all priority check points 1 and 2 are satisfied.
    3. "Triple A" Compliance Level: all the checkpoints of priority 1,2 and 3 are satisfied.

    :: Basic rules of web accessibility ::

    To create an accessible web it is necessary to follow the 14 guidelines and its control points but there are some some basic rules, which summarize them in the following:

    1. Follow the W3C standards . Currently the two standard languages ​​for the creation of websites are HTML 4.01 and XHTML 1.0. Fulfilling any of the two standards facilitates accessibility.
    2. All images must have an alternative text (alt attribute) that will be displayed by browsers that do not show images (screen readers, computers with a slow connection, text browsers). This attribute must contain the description of the image (not the name) unless this description is purely decorative.
    3. The links must have a significant name of the place they are pointing to. This text must be comprehensible outside its context and, therefore, it does not serve the much used "click here."
    4. To organize the information within the webpage you must use the h1, h2 …, ] with them we must organize both the content and the format of the titles.
    5. The use of tables for layout should be avoided, unless they are essential. If they are used, make sure that the content can be read in a linear manner and ensure that the different cells do not have excessive content.
    6. Whenever possible, style sheets (CSS) should be used to separate the content of the presentation and should be syntactically correct.
    7. In case of adding multimedia content (sound, animations and / or video) subtitles (for sound) must be provided ] or description of animations and videos.
    8. If using frames a label must be used that incorporates the necessary links for navigation. Each frame should be perfectly identified
    9. If scripts, applets or plugins not accessible are used, alternative content should be offered.
    10. If used Images with long or complex information should be properly described. For this, the longdesc attribute can be used
    11. If image maps are used, it is convenient to provide redundant links in text format for each active zone of the map.
    12. They should be used easy-to-read letter typologies .

    In this video, we review some standards and the importance of web accessibility:

    Now how do we accomplish all this if we use WordPress?

     search for accessible themes in wordpress

    :: Word Accessibility in WordPress ::

    WordPress offers a special page on web accessibility that offers us tips and tools to make our WordPress accessible. There is also a summary of practices from accessibility in CODEX . However, although much better than the rickety reference page in WordPress.com they are not the best sources of knowledge about it, so I recommend that you review all the other points discussed in this article, and especially the references at the end of it.

    The first thing to keep in mind is that WordPress is not different from any other web so the guidelines and rules to follow are exactly the same. same as we have already seen . However we can take some shortcut that will save us work:

    1. Uses an accessible WordPress theme . Although there are not many, in the official repository there are some issues, specifically eight, that comply with the tag " accessibility-ready ". One of them is the default WordPress theme, TwentyFourteen. Also there is a child theme of the TwentyTen theme that complies with the accessibility standards.
    2. Use accessible plugins . Always use some accessible version of the plugins you use, in addition to those that help you meet the accessibility guidelines:
      • Search plugins that comply with the WAI-ARIA standard . It's not all we need to meet but it's a good start. Do not search for " accessibility " or " accessible " because what you find is a broken sack where you'll see access control plugins, user permissions and a little bit of everything.
      • WP Accessibility . It's a good start because it identifies and solves common accessibility errors (some fixes them automatically) as incorrect link attributes (which I'm very much guilty of) and adaptations of standard WordPress tags to accessibility guidelines. Highly recommended .
      • WP Accessible . Despite its name, today it does not even look like the previous one because it only offers an accessible Twitter timeline widget, the rest is yet to come, but for one thing it starts.
      • Contact Form 7 : Accessible defaults : Convert the Contact Form 7 plugin forms to accessible in all their fields.
      • SOGO Accessibility : Add several settings to adapt WordPress to users with accessibility problems, such as contrast , sizes, etc.
      • BotDetect Captcha is a plugin that offers a system of control of undesirable users but complying with the accessibility norms, so as not to make undesirable users who are not, only for their disability.
      • YouTube Shortcode . A short code version (or shortcode ) to insert YouTube videos on your site but in an accessible way.
      • Accessible tag cloud . An accessible alternative to the WordPress tag cloud widget.
      • Accessibility widget . Add to your sidebar a widget from which to increase or decrease the font size of your site, very useful for users with eyesight and other problems.
      • Zoom widget . Like the previous one, add a widget to increase the size of your website's elements.
      • Accessible_blank . Open the links in another window or tab but complying with the accessibility standards. Great plugin, although not updated long ago, of our friend Cristina Eslava.
      • Accessible external links . Similar to the previous one, it offers a way to apply the link destination but in an accessible way.

    Manrique López did a good summary in this presentation that exposed the past WPDay Madrid :

    :: How to check the accessibility of your website ::

    There are a series of practices you can carry out to check the accessibility of your website:

    1. Use an automatic accessibility tool and a browser validation tool. Please, check that the software of the tools deals with all accessibility problems, such as the meaning of the text of the link, the applicability of a textual equivalent, etc. Following this list you have a couple of good free online tools.
    2. Validate syntax (For example, HTML, XML, etc.).
    3. Validate style sheets (For example, CSS)
    4. Uses a text-only browser or an emulator.
    5. Uses various graphics browsers with:
      • Sounds and graphics loaded.
      • Graphics not uploaded.
      • Sounds not loaded.
      • Without mouse.
      • Frames, scripts, style sheets and applets not loaded.
    6. Uses several browsers old and new.
    7. Uses a browser by voice, a screen reader, a magnification software, a small visualizer, etc.
    8. Uses spelling and grammar verifiers . Anyone who reads the page with a speech synthesizer may not be able to decipher what the synthesizer plays because of a misspelling. Eliminating grammatical problems increases comprehension.
    9. Check your website for clarity and simplicity . Readability statistics, such as those generated by some word processors, can be useful indicators of clarity and simplicity. Better yet, ask an experienced (human) editor to review the clarity of the written text. Editors can also increase the usefulness of a text by identifying potential intercultural problems that may arise because of the language or icons used.
    10. Invites people with disabilities to check the web . Skilled and novice disabled users will provide valuable feedback on accessibility or problems of use and its severity.

    Finally, it never hurts to use tools from automatic web accessibility check like these: [19659024] eXaminator (in Spanish)

  9. HERA (in several languages, also in Spanish)
  10. Both offer a quick tool that analyzes if your website complies web accessibility standards offering advice on how to solve it

    Does this blog comply with accessibility standards ?, sadly not yet.

    Web accessibility is not easy if you do not apply it from the beginning. In many cases they are habits that you must acquire when inserting links or content, so it is better if you start as soon as possible, and I have been doing it for many years, which I suppose would have to have a good time to make it accessible … but I am in it little by little and I hope to have it nice and accessible in a short time.

    The advantages are obvious, as we have seen, and in fact it is not so complicated if you follow some simple guidelines and get used to them.

    References:

    1. Benefits of web accessibility .
    2. Spanish legislation on web accessibility .
    3. Brief Web Accessibility Guide (W3C).
    4. Web Accessibility Guidelines in DiscapNET .
    5. web accessibility .
    6. Repository Official WordPress Theme .

    NOTICE : This publication is from two years ago or more. If it's a code or a plugin it might not work in the latest versions of WordPress, and if it's a news story it might be obsolete. Then do not say we have not warned you.

    Loading …

    That may also help you:

How to comply with Spanish cookies legislation

 law cookies españa

A few days ago the first fines have fallen to two Spanish websites for violating the legal rules on cookies . The fines have been of 3,000 and 500 euros respectively, but could have amounted to the not insignificant figure of 30,000 euros .

According to the sentence one of the sites, ] created with WordPress (although it confuses wordpress.org with wordpress.com), it used JetPack cookies ( _qca ), SlimStat (from the statistics module) and Quancast ( mc ]).

Of all this, some plugin warns us like Cookilian that we already saw in the article of how to comply with the cookie legislation in WordPress and it would not hurt install it and check the cookies that are on your site and create a page that adequately reports them, mostly to not get you upset.

What are the implications of these first two sentences? I personally think that it sends very bad messages …

The first thing is that, with all the big companies, and all of the IBEX, ignoring the flagrant legislation of cookies, that the Data Protection Agency breastfeed with two small companies I do not know if qualify it as a way to get noticed by setting an example against the little ones who can not or know how to defend themselves well, or as a warning to sailors to scare, again, the little ones.

Meanwhile, what is achieved is that every small business that tries to prosper on the Internet end up closing or moving your business to another country where they do not get so great with something that should be corrected with a software solution, by the hand of Microsoft, Google or Apple, then with a line code could perfectly block cookies unless expressly approved and for all, in their browsers.

But no, here we are more asshole and stupendous than anyone and we are dedicated to fuck the Easter to our SMEs to put obstacles in the way of entrepreneurs, to prevent electronic commerce from emerging and being able to give employment.

It is true that the laws are to comply with them but also administrations have the responsibility and the duty to make life easier for their managers, finding the best solution to the problems that arise, and something that could be arranged so easily by talking to the big software companies, instead is attacked the small webs that subsist with scarce penalties, but much easier to penalize with fines that can not be escaped due to lack of legal cabinets that make the processes "sleep" or even win them.

What they get is that something that should be good: guarantee the Internet user's right to privacy, end up being a brake on that same freedom, not to mention the flowering of new opportunities on the web.

So you know, if you're not a big untouchable multinational, you better prepare your website to comply with the cookie legislation. Do not get pimp because you see that the most important newspapers and portals do not comply, they will not touch them, but you do.

That you have not yet gotten to work to comply with the legislation of cookies? and get to work:

  1. Guide on the use of cookies by the Data Protection Agency (pdf)
  2. Guide to comply with the law of cookies in 5 steps of Adigital (pdf )
  3. How to comply with the law of cookies (by Pablo Fernández Burgueño)
  4. How to comply with the legislation of cookies in WordPress
  5. Cookies in WordPress
  6. Examples of privacy pages that comply with the law of cookies : 1 and 2

Cabreo I have hear!

NOTICE : this publication is from two years ago or more. If it's a code or a plugin it might not work in the latest versions of WordPress, and if it's a news story it might be obsolete. Then do not say we have not warned you.

Loading …

That may also help you:

WordPress has democratized Internet publishing • WordPress Help

Last Friday there was a debate about the WordPress world in which I had the honor of being invited along with a good number of professionals who, as they say, were not all what they are but if they are all that were .

It would be very pretentious, as well as impossible, to quote here everything that was said in the more than 2 hours of debate that everyone I was able to follow live using the Google+ Hangouts system and broadcast live on YouTube, so it's best to see it yourself and select which parts interest you the most.

In a rough way, topics like what is WordPress ?, what do we like more and less about WordPress? what about cookies and European legislation? where does WordPress go? ]and much more, where of course consultations were attended to by all those who followed the debate on YouTube, Google+ and Twitter.

Comply with European legislation on cookies in WordPress

 wordpress cookies

For some time now we have seen the requirements of European legislation regarding cookies and I think it was time for to see some plugins that can help us to comply with the law on our website in a simple way, without complicating us.

I have been testing some of the ones available to date so I tell you my impressions of each one …

EU Cookie Law / EU Cookie Directive Compliance Plugin
Once installed, ask visitors to your website if they agree to allow your site to create cookies. In addition to this basic function provides a link to the page of your website at cookiecert.com where you can see the existing cookies on your site.

The page of settings is very complete in terms of appearance of the notice, being able to adjust all type of details of colors, links and locations, but it does not allow to personalize the text, a substantial failure under my point of view so I discarded it at once.

WP EU Cookie Law
Simple but at least this allows you to customize the main texts to be displayed, but not the buttons, a silly mistake. You can also choose between a pop-up window ( explicit ) or a higher banner ( implicit ).

It works instantly but I did not like it not allowing you to customize buttons and links, and that in the case of the banner does not follow the reader when doing scroll.

Cookie warning
Until now it is perhaps the one I liked the most, at least in effectiveness. Once installed, it shows a pop-up message that does not allow you to go forward on the web unless you take action.

If you accept cookies, you can browse normally, and if you do not accept, it takes you to the link that you personalize and deletes cookies of initial session of the site, so it is currently the best complies with European legislation .

You can customize the text that will appear, as well as the URL of the link in case of not accepting the storage of cookies, and also the text of the buttons of acceptance or not of the cookies, so in this aspect it is well covered.

What I like less is the default appearance of the pop-up window, because for example the default text is very small … and as a whole its appearance is a bit ugly. However, it fulfills the function for which it is intended.

 cookie warning adjustments

Cookie control
If it depended on the page of plugin information you would never choose it but nevertheless it is very complete and works great, being able to customize a lot of fundamental settings.

Once active you have your own settings page, very large, where you can configure the texts, the appearance and even have settings to disable Google Analytics cookies until there is no express approval of the visitor or, for experts, fields to add callbacks in JavaScript depending on the user's action.

I especially like that you keep a fixed icon on your website, from which activate or deactivate cookies at will . But it has some drawback, which is not as restrictive as Cookie warning, which we have seen before, because it allows you to browse normally even if you have not given your consent to cookies, and it does not delete the WordPress session cookies either.

that visually is the most but in effectiveness it sins something.

Electric Studio EU Cookie Law Compliance
I'm sure you'll love it if you can customize messages in an editor like WordPress. Otherwise it works very well and the default styles are great, unless you want to adapt them to the stylesheet of your active theme.

Once the user accepts cookies, they remain for 2 years, unless they empty the cache of the same. in the settings of your browser.

Not the most effective but complies with the basics.

 electric studio cookie law

EU Cookie Law compliance
Simple and allows to adjust some conditions and JavaScript codes, although the putada is that you have to modify the texts directly in the plugin files. On the other hand the operation is somewhat erratic and does not erase or block cookies so discarded altogether.

Cookie law info
It is the most configurations allows, with enormous difference being able to even create several warning messages in the style of personalized input types.

Custom messages offer a series of shortcodes to choose where to display and how the buttons of acceptance, links and others. You can also customize styles, fonts, colors, everything.

Among the settings you find you can choose where the warning will be displayed, the time it lasts, type of warning and many more options.

Do not delete cookies directly but it complies with the basics, and at the personalization level is as complete as it is . In addition, always leave a small link on the site to access the information message.

 cookie law info

COOKILIAN
] It is the one I am currently active after unsuccessful experiments with virtually all that exist and verify that they do not fulfill their purpose – for the annoying Spanish legislation – of not install cookies without permission .

su ghastly and tacky default pop-up window design which you can modify on your settings page as the author points out (and gives examples ), works wonders but, above all, offers some more interesting extra.

One of them is that it offers a shortcode through which to automatically display the list of cookies on your site on your page of pr policy Ivacity, for example.

 shortcode cookie list

In addition, and linked with it, it has a settings page in which to delete, add, modify or change descriptions of existing cookies s (which it detects and displays), and can even group them by sections. Very practical and useful.

 Cookilian cookie management

Let's not say the interesting thing about having cookie acceptance statistics for which It also offers an exclusive screen.

 cookilian statistics cookies

Equally useful is the page of configurations where not only it incorporates the possibility of personalizing the messages but it adds functionalities that you do not find in other plugins or scripts, and I quote some:

  • GeoIP to determine the visitors from which countries the cookie alert will be displayed
  • GeoIP Cache
  • Alternative GeoIP Server in case it fails the first, even accommodation in local
  • Consent by default or not (better choose not for Spanish legislation)
  • Custom alert texts that allow HTML
  • Custom CSS
  • Insertion box of scripts in the subject
  • Deletion of cookies before or after the visitor's decision
  • Cookie administration screen
  • Statistics
  • … a lot more

] In short, of the most complete that there is and, above all, that does what it should . For example, if you do not accept cookies, you only save a cookie, the one of the plugin to remember this decision, otherwise, and until you make a decision, if you have configured it in this way, it does not save anything.

[Nota: he detectado que en según qué instalaciones el plugin Wordfence (seguridad) instala una cookie que no es capaz de parar ningún script ni plugin, y que no está documentado que yo sepa donde evitarlo]

Anyway, keep in mind that all these plugins warn the reader and ask for their consent, with that all comply, but most do not block cookies, as there is much that deletes the initials if it is not accepted, so there are many of them who would not comply with the legislation in its strictest way (Spanish, for example, although the one in the United Kingdom), as it only gives the visitor the option to accept cookies and little else according to the chosen one, but something is something, in fact much more than what other websites do, including the government websites, which do not even comply minimally with their own legislation .

In any case there are honorable exceptions .

Which one to choose? because I encourage you to review the legislation of your country and use the one that best suits you.

In any case it is always better to put at least the notice, the user can always delete the cookies or navigate privately if you wish, although the legislator will verify that at least you have a page that reports the privacy policies, and better if it is clearly visible.

NOTICE : this publication is two years ago or plus. If it's a code or a plugin it might not work in the latest versions of WordPress, and if it's a news story it might be obsolete. Then do not say we have not warned you.

Loading …

That may also help you:

Check the age before accessing your WordPress site

I'm sure you've often found a form asking you to verify your age before accessing a site . It does not prevent you from lying to him but at least you have accepted a condition, voluntarily, that sometimes downloads to the web of responsibilities depending on the current legislation.

Well, if you have a website and you want to incorporate a system of this type, for that the visitor indicates that he has the minimum age necessary to see the contents you can do it very easily in WordPress.

You just have to install the plugin called Age Verify and configure it a bit. Let's see the possibilities …

What we get is something like trying to access the site, and " protected " against pubesters who do not know how to lie to a drop-down form , of course …

Cookies, WordPress and legislation • WordPress Help

With the last legislative changes in relation to electronic commerce and websites in general it is becoming increasingly complicated to have a website legally, but everything is to respect the privacy of users right?

There are extremely rigorous cases, such as the United Kingdom, perhaps the most punctilious in the previous notice of cookies to the visitors, but where it gets especially tricky is in Spain because we have to add the requirements of the previous notice of storage of cookies to that here, because we are cooler than anyone, practically all web, and blog, it is considered e-commerce so only in very specific cases we would be exempt from applying the law on cookies.

But I do not say it, because as good quotes my friend Pablo Burgueño , abo Expert in new technologies …

The Cookies Act (or Cookie Act) obliges the owners of professional websites to prevent cookies from being installed on their users' computers, unless they have given their informed consent beforehand.

So what do we do with our WordPress?

Well the first thing is to know what cookies WordPress stores that, in a standard installation, and without active plugins, would be these:

The security cookies, the secret keys of WordPress and session are these:

  • AUTH_KEY
  • SECURE_AUTH_KEY
  • LOGGED_IN_KEY
  • NONCE_KEY

The duration by default of these keys is:

  • 48 hours or browser shutdown
  • 14 days by checking the box in the access of " remind me "

This behavior can be modified, even the expiration of the cookies of session manually or by means of plugins, extending or reducing the time.

Some ways of modifying times would be these:

  1. Manually changing the session cookies in the file wp-config.php with what forces a new access to all users when deleting previous cookies. New cookies you get here
  2. Using some plugin like Configure login timeout that allows you to modify those times by default.

Then there are other cookies for comments, also temporary , which are stored on the visitor's computer under certain conditions, these:

  • comment_author
  • comment_author_email
  • comment_author_url

The duration of these cookies depends, fundamentally, on the browser settings of the visitor they are only saved if you have it configured in the browser. Although by current legislation you should warn if or if .

For these purposes, for a prior notice of acceptance of storage of cookies is not worth having a privacy page ( here an example of privacy page that includes the Dart cookie), but that must be notified to the visitor and have its express acceptance .

There are some plugins They promise to offer this but the truth is that I have tried almost all and are a complete truño. The only decent thing to date is this script which you can see up and running at the web of Abanlex attorneys (the company of my buddy Pablo).

But, As I have already pointed out to you, this is not always the case, because there are plugins that add their own cookies any of the polls, for example. So if you want to know what cookies your WordPress uses with all its plugins installed, you can create a function that, on a page, lists of all of them and their values ​​and times

The first thing is to add this code to your function plugin or file functions.php of the theme you're using:

And then put this shortcode where you want cookies to be displayed:

At least you will know, and your visitors, if you put that information on your privacy page the cookies stored on your WordPress.

Ah, and for the megafans of the social media and the mother who gave birth you know that if you have a corporate page on Facebook, you are also not complying with the Cookies Law .

And now the little question …

 Loading ... "tit le = "Loading ..." class = "wp-polls-image" /> Loading ... </div>
<p> I already tell you, not yet, because I'm still trying to find the best way, but I think I'll choose by the aforementioned scritp. </p>
<div id=

NOTICE : this publication is from two years ago or more. If it's a code or a plugin it might not work in the latest versions of WordPress, and if it's a news story it might be obsolete. Then do not say we have not warned you.

Loading …

That may also help you:

Send to … illegal? – WordPress Help

Not long ago elfran222 echoed in the blog that the Data Protection Agency had published a document that referred to a complaint according to which the same act of ask for the "socialization" of a post in a blog could be considered illegal under current legislation.

We now have an excerpt from TV Netizens where this matter is discussed and some keys on the matter …

And the truth is that we have discussed this issue a little what do you think? is it going to change something this blogosphere or your way of interacting on the network?