• Django
• postgis
• pg_routing
• ExtJS
• GeoExt
• OpenLayers

My client is a market leader in GPS wandering and track planning, who needed a complex CMS to publish and promote his activities.

The project’s goal was to develop a Geographic CMS multi-site, multi-admin (resellable) , multi-language using open source tools. Among other interesting features, we needed to support all well-known mapping providers (Google Maps, Yahoo Maps, OpenStreet Map etc.) plus an internal maps with tracks arc-node network, suitable for routing calculations.

The new website(s) are reachable at www.movimentolento.it at the time of this writing, the Italian language is the only one with some contents.

Python vs. PHP

After more than seven years of PHP programming, the language switch was a risky move, but I rapidly fell in love with Python and its vibrant users community. I usually avoid flame wars about programming languages, but I’m now deeply convinced that Python is far more advanced than PHP, even if PHP has its own advantages, expecially when deployment time comes.

(Geo)Django a powerful framework

The choice of Django as the barebone framework was dictated by Django being the one having an advanced support of Geographic extensions (GeoDjango) and by its beautiful documentation. Of course the ideal framework does not exists (yet) and is maybe impossible to create since they are always a compromise between ready-to-use functionalities and flexibility. Django authors must have had a good time providing (almost) all the necessary hooks for customization.

I’ve found Django a very interesting project for many reasons:

Lack of “magic”

While most widespread principles like DRY and convention over configuration are valuable, I’ve often found confusing for first time users the lot of under the hood features that are are triggered because you’ve named a function or a class in a certain way, I think Django has wisely chose to not implement too much of this outside of the ORM DB design phase. The result is a clean application design flow without too many conventions that you must have in the top of your head.

Powerful ORM

I really like the way you can build complex queries and retrieve related object in Django, even M2M relations can be handled in an understandable way. If you need multi-class (multi-table) references you can build them quite easily with the ContenType contribution classes.

Flexible templates

This is maybe what I love much in Django: the templating engine is so powerful and flexible that it can really save you a lot of work allowing you to put presentation logic inside the template itself. I agree that separating concerns in a pure MVC patterns (presentation and controller logic) is a must but think of Django templates like they were the presentation part of the view component and you’ve got the point.

Rsable apps

“Reusable apps” are ready to use applications that you should be able to drop into your applications, and they are reusable indeed. Even if I probably had to modify most of them in order to add multilingual and multi-site support, reusable apps can save you a lot of time.

Missing features

This is a short description of the main problems I’ve encountered when developing missing features in Django. I ended up without core modifications and with a single real patch, so it wasn’t that bad after all.

Multisite

Django comes with the “Sites” framework, it allows you to share the same DB from different websites, but you are supposed to run each website into a different Django instance. While this remains the recommended way, my clients required new sites to be added from the control panel in  an easy way.

Site ID is hardcoded in the settings and due to the fact that static class methods are shared among processes (and moreover among threads, of course) you cannot use it directly without modifications. I’ve had to modify queryst managers and to create a middleware to change Site ID on the fly based on the requested domain. A catch-all DNS record allows to create third level domains within the control panel having them online within minutes.

Something similar is available as reusable app: django-multisite.

Multilingual

Django does not support multiple language for the content (it does for the interface static strings).  I started from a reusable app (transmeta) and did some modifications to allow for optional translations and to easy control panel interface development and presentation. FTS integrations was also added.

Full text search (FTS)

DB is Postgresql which now comes with integrated FTS, I added some triggers and management commands  to support multilanguage FTS. Django doesn’t provide any utility to handle FTS.

This page is a collection of small recipes and hints about Simple ACL Joomla component.

Note: this article is still a work in progress, please leave a message if you find errors, typos or if you have any suggestion or proposal.

Abbreviations in the recipes:

• UX = “User X” where X is a number (for example U1 = User 1, U2 = User 2 etc.)
• SX = ”Section X” where X is a number (for example S1 = Section 1, S2 = Section 2 etc.)
• ACL = a single Access Control List rule

Recipe 1 : prevent authors to edit their own articles after being approved (workflow)

Scenario

• You have many authors submitting content that you or some other admins approve before being published
• Joomla 1.5 does not prevent an author to edit again  his/her content once published
• you want to avoid editing after approval, only admins will be able to do that

Procedure

The strategy here is to block content update to all users, admins and back-end users will retain the standard Joomla behaviour.

1. Set the default ACL to prevent all the users to update or delete content: in Components->Simple ACL->Parameters set
   • Create = Allow
   • Update = Deny
   • Retrieve = Allow
   • Delete = Deny (not implemented from Joomla front-end, but Just in case)

Recipe 2 : public website with some section editors

Scenario

• Your website is public, everybody can see everything
• you have one section for each department in your company (S1 and S2 in this example)
• each section has one or more users  that can add or edit content (U1 can edit S1, U2 can edit S2 and U3 can edit both)

Procedure

The strategy here is to allow content retrieval by default and only block content creation or editing, individual ACLs allow editing to some selected sections/users.

1. First thing to do is set the default ACL to prevent all the users to create or update content: in Components->Simple ACL->Parameters set
   • Create = Deny
   • Update = Deny
   • Retrieve = Allow
   • Delete = Deny
2. Save the new parameters (hit “Save”)
3. Now open S1 to U1 and U3, create the following ACLs:
   • Section S1, User U1:  check all permissions
   • Section S1, User U3:  check all permissions
4. Now open  S2 to U2 and U3, create the following ACLs:
   • Section S2, User U2:  check all permissions
   • Section S2, User U3:  check all permissions

Recipe 3 : public website with some private sections

Scenario

• Your website is mostly public but you have
  • some private sections (S1, S2 and S3)  available for browsing and/or editing to selected employees
  • some private sections (S4, S5) for your customers
• all your employees (U1, U2, U3) are registered users with level “author”
• all your customers are registered users with level “registered”
• since S1, S2 and S3 are not public, their Joomla access level must be set to “Registered”  (in this case it would be also possible to set it as  ”Special”  since our employees level is  ”Author”)
• since S4 and S5 are not public, their Joomla access level must be set to “Registered“
• we want to set thing up such that
  • U1 can view and edit S1
  • U2 can view and edit S2
  • every employee can view S3 (but nobody below admins can edit it from the front-end)
  • every employee can view and edit content in S4
  • every customer can view content in S4 and S5

Procedure

Here we are choosing a different strategy: keep all sections closed by default and selectively open sections to users.

Because in this example we have Customers and Employees belonging to different Joomla levels (Registered and Author) we can create some group ACLs instead of individual ones.

1. First thing to do is set the default ACL to prevent all the users to retrieve, create, update content: in Components->Simple ACL->Parameters set
   • Create = Deny
   • Update = Deny
   • Retrieve = Deny
   • Delete = Deny
2. Save the new parameters (hit “Save”)
3. Grant all users with level “Author” permission to retrieve content from S3: create an ACL on group “Author” and section S3 with Retrieve permission only
4. Open S1 to U1: create the following ACLs:
   • Section S1, User U1:  check all permissions
5. Open  S2 to U2: create the following ACLs:
   • Section S2, User U2:  check all permissions
6. Grant all users with level “Author” permission to create, retrieve and update content from S4: create an ACL on group “Author” and section S4, check all permissions
7. Grant all users with level “Registered” permission to retrieve content from S4: create an ACL on group “Registered” and section S4 with Retrieve permission only
8. Grant all users with level “Registered” permission to retrieve content from S5: create an ACL on group “Registered” and section S5 with Retrieve permission only

After further investigations we came into the conclusion that routing all static content (images, CSS, Js) through apache webserver was opening too many connections and was one of the major causes of the website’s slowness .

The most obvious solution would be to serve static content from a different subdomain pointing to the same IP where Joomla is hosted, routing all the static requests through a different and faster webserver (enginx or lighhttpd to cite a few)  would,  at the same time, speed up page rendering because the browser could parallelize requests to different domains.

Unfortunately, Joomla does not support serving static content from a different (sub)domain,  so we started writing a plugin that allows us to serve static content from a different domain.

We are now in the testing phase, the plugin will be open-sourced and GPL’d but we will probably require a small fee to download in order to cover development and assistance costs.

If you are interested or have questions or ideas, please leave a comment below.

Logo Linux Day 2009

ItOpen partecipa all’organizzazione del Linux Day 2009 a Torre Pellice.

Il Linux Day è un’iniziativa a livello nazionale, volta a favorire la diffusione e la conoscenza del software libero e del sistema operativo Linux.

Il Linux Day di Torre Pellice si terrà il 24 ottobre dalle ore 10 alle 18 alla Biblioteca di Torre Pellice.

Per ulteriori informazioni consultate il sito dell’Asssociazione SLIP.

QGIS logo

In the past few days I’ve been actively working on a new GeoCoding python plugin for the open source GIS software QGIS.

This new plugin allows a user to obtain geographic coordinates of a location knowing its address, the geocoding process is handled by Google webservices. Additionally, GeoCoding plugin allows “reverse geocoding”, i.e. to obtain an address, from the point coordinates (clic on the map canvas). All geocoded points are automatically added to a point layer.

You can find the new plugin on QGIS the 3rd parties repository.

GeoContent Logo

GeoContent is a new Joomla! 1.5 component that allows embedding Google Maps into a Joomla! website.

Standard Joomla Articles, can be bound to geographic features such as POINTs, LINEs and POLYGONs and the resulting maps can be shown in the article page and in an overview map.

A single article can be represented by more than one geographic type: so that you can have simultaneously a set of POINTS, some POLYGONS and some LINES for a single Joomla article.

Articles on the map are grouped by layers, appearance can be fully customized through layers configuration.

See the full manual.

See the demo site.

20/08/2009 – UPDATE: the new version has front-end map editing support

Download

ComGeocontent is open source software, distributed under AGPL software license and it is also free software, where “free” means that you can do (almost) whatever you want with this software but it does not mean that it costs nothing. We distribute the component only in bundle with paid 12 month support service that costs 45 €.

To receive a copy of GeoContent you are kindly requested to make a donation of at least 45 €, using the buttons located at the top or at the bottom of this page. You will receive a regular invoice at the end of the month.

The money you donate will be used to further develop GeoContent and to provide professional assistance and support to those that will need it.

Together with 12 months support you will get lifetime software updates, that means that you can pay just once and use the software forever in how many Joomla installations you like.

Please use the PayPal donation link at the bottom of this page, specifying the email where the component will be sent.

Thank you for supporting free software GeoContent project!

Why a new Google Map component? Don’t we have enough already?

Yes, there are many components out there that allow Google Maps embedding into a Joomla website,  and most of them are gratis!.  Nevertheless, I believe that none of them have the unique and full set of features that GeoContent has.

Ok, so what makes GeoContent so unique among Google Maps Joomla components?

Professional support

This component is professionally supported, this means that I will

• fix bugs
• provide reliable remote assistance and support on the component for 12 months from your subscription
• send you all the updates of the component, forever.

Advanced input methods: GPX and direct draw POINTs, POLYGONs and LINEs on the embedded Google Map

Perhaps the coolest feature, is the availability of two advanced input methods for your geographic objects:

• users can directly draw geographic feature from the control panel through an embedded Google Map editor
• users can load geographic data from a GPX (standard GPS format) file

KML export

Coming to the output methods, an interesting optional feature is KML export : yes, you can directly publish your GeoContent powered  Joomla! website into Google Earth!

Fully configurable

Since articles are grouped by layers, you can change the appearance of a layer and have all map items that belong to that layer changed accordingly.

For each layer, you can style:

• Line color
• Line width
• Polygon line color
• Polygon fill color
• Polygon line transparency
• Polygon fill transparency
• Point icon
• Point icon size (KML only: not supported in the embedded map)

Of course you can configure several aspects of the main map appearance:

• Table Of Content (TOC) type (hidden, list, select)
• TOC position (left, top, right, bottom)
• TOC and main map width (onyl useful for TOC position left and right)
• Which layers should be activated at start (none, all, selected)
• Map dimensions
• KML icon (hide or show)

Flexible binding between geographic objects and Joomla articles

GeoContent allows you to bind articles to the map in several ways:

• a single article is not tied to a single layer (it can belong to many layers)
• a single article can be represented by one or more geographic objects: POINT(s), POLYGON(s), LINE(s)

Translations

They go in a language file, at the moment only English translation is in the distribution, but you have to translate no more than a dozen of strings to localize the front-end side of the component.

Screenshots

Here below you can see some screenshots of GeoContent editing interface and public map view, there is also a test site here (not much content so far though).

]]> http://www.itopen.it/2009/05/11/geocontent-a-new-google-maps-joomla-component/feed/ 59 http://www.itopen.it/2008/10/09/joomla-fap-al-miopen/ http://www.itopen.it/2008/10/09/joomla-fap-al-miopen/#comments Thu, 09 Oct 2008 12:53:20 +0000 Alessandro Pasotti http://www.itopen.it/?p=207 Le slide dell’intervento su Joomla! FAP:

Il prossimo 25 ottobre a Milano si parlerà di Joomla! FAP.

Sono stato invitato a parlare del progetto che seguo ormai da qualche tempo e che si sta dimostrando un prodotto molto valido.

Allego il comunicato:

Il 24 e 25 ottobre 2008 a Milano,
presso il Palazzo Affari ai Giureconsulti ,
si svolgerà la 2a edizione di MiOpen, evento sull’open source promosso ed
organizzato dalla CNA per far conoscere le soluzioni tecnologiche basate sul
software libero da royalty.

Questo appuntamento, che lo scorso anno ha riscosso notevole successo, è
l’unica occasione Italiana per prendere contatto con il mondo delle
soluzioni gestionali Open Source disponibili per le aziende.

Si parlerà degli investimenti all’innovazione: il mondo imprenditoriale si
confronta con venture capital, banche, governo centrale e istituzioni locali
su cosa si sta facendo e su cosa si dovrebbe fare per sostenere lo sviluppo
del sistema Italia.

E’ la prima volta che in Italia si parla dell’aspetto finanziario dei
progetti OSS; in altri paesi, a più alto tasso di sviluppo, i progetti OSS
di successo si sono sviluppati grazie al supporto finanziario, in Italia non
ci sono casi simili.

L’occasione è importante per il mondo degli sviluppatori e per le comunità
OS italiane che, a causa delle caratteristiche dell’Open Source, hanno
difficoltà ad accedere ai normali canali di finanziamento.

L’evento riunisce nello stesso luogo chi ha le idee e chi ha le possibilità
di finanziarle.

L’imprenditore ed il professionista possono, inoltre, vedere ed entrare in
contatto con soluzioni aperte per:

- la gestione integrata dell’azienda (ERP),
- la gestione delle relazioni con la clientela (CRM),
- l’automazione integrata dell’ufficio (suite di Office),
- la domotica – controllo e programmazione di apparecchiature e sensori,
- sistemi di gestione e d’integrazione del WEB,
- produzione e trasmissione di prodotti televisivi via web,
- la gestione e l’interconnessione delle aziende in rete via Internet,
- le soluzioni per virtualizzare i server, i personal, i desktop, le
applicazioni.

In questo contesto i grandi dell’informatica IBM, HP,  Microsoft e SUN,
partecipano illustrando a loro volta le loro realizzazioni, i progetti e la
loro politica nel settore Open Source.

La partecipazione è gratuita.

Per visionare il programma e per iscriversi all’evento:
http://www.miopen.it

Simple ACL

SimpleACL for Joomla helps you to restrict front-end access to particular user/section combinations. You can independently set permission to read, insert and update content items based on the section they belongs to.

The component does not override default Joomla roles, those roles are always checked first.

SimpleACL plays only with default com_content component and doesn’t affect other components or modules.

You can set a default access permission and selectively enable/block users to access content items in selected sections.

What can I do with this component?

A typical scenario:

• Your site is a company site and the company has several departments.
• Every department has a user who is in charge for editing web content for the department.
• Every department has its own section for content items.
• Users should only be able to edit content in their own department.
• There is a user who is the public relation manager, he must be able to edit content in all sections (without being Administrator).
• There are some section whose content should be readable only by selected users.

With SimpleACL you can set permissions to selected section/user combinations (or even to “Joomla! standard groups”/section combinations), this allows you to implement such a fine grained access control.

See also Simple ACL recipes (work in progress)

How it works?

SimpleACL works with an independent database table that hold the permissions for user/section combinations. A system plugin checks those access rules when the user access a content item from the front-end.

If you want to know more about the internals of Simple ACL and how it works, please see Decision Flowchart.

Please note that…

1. Default Joomla roles are not overridden and are always checked first.
2. SimpleACL works in the front-end only
3. Only authenticated users are checked for ACLs
4. “Administrator” or “Super Administrator” user are not checked for ACLs.
5. Group support for standard Joomla! groups (author, editor, publisher…) is also available
6. Custom groups creation is not supported (but you won’t miss it!)

License and costs

Simple ACL for Joomla 1.5 is free software (“free” as in “free speech”), licenced under Affero General Public License but I distribute it only in bundle with paid 12 month support service that costs 45 €.

Together with 12 months support you will get lifetime software updates, that means that you can pay just once and use the software forever in how many Joomla installations you like.

Please use the donation link at the top and middle of this page, you will immediately receive a download link.

Thank you for supporting free software and Joomla Simple ACL project!

Translations

They go in a language file, at the moment only English is in the distribution.

If you need more information about the Simple ACL, please read the FAQ at the bottom of this page.

What’s new in version G.x series

This new version brings many enhancements:

• limited group support
• check/uncheck all actions when editing ACLs
• Admin users will not be shown in the user list when creating ACLs
• limited menu integration
• DB backward compatible (will not overwrite your existing ACLs, but make a backup first)

Let’s give a closer look to some of the coolest new features…

Limited group support

You can now add ACLs to the following standard Joomla user groups:

• registered
• author
• editor
• publisher
• manager

In case of ACL conflicts between group-ACLs and user-ACLs, the second will always prevail.

Limited menu integration

Many of you have asked for an ACL-aware menu.

You can now enable menu integration as an experimental option in Simple ACL configuration.

If you enable this option, Simple ACL will try to hide menu items that point to articles, sections or categories that are not accessible by the logged in user.

In some cases, it can happen that all menu items are hiddden, in this case the user will see an empty menu list, but Simple ACL will not be able to hide the title of the menu itself because it operates at a different level in the joomla processing flow.

Screenshots

FAQ

Is this thing “stable” ?

Yes, sure. It’s now used on several production websites.

Can I limit access to a category instead of a section?

Not in the current version.
I will eventually implement it in a future version (but please don’t ask me when )

Will Simple ACL alter in any way menu items or search results depending on user ACLs ?

Yes, Simple ACL comes with some companion plugins to hide unaccessible items from search results amd the latest version has also an experimental feature to hide unaccessible menu items from menus.

How will I receive the software after the donation?

After a successful payment, you will receive a download link via email.

The email is automatically sent immediately after a successful payment, please check your spam folder if you don’t receive it in a few minutes.

Why should I pay for a free software component?

I think an explanation is needed: in my career I developed a couple of free (“free” as in “free speech”) software projects (KMLMapserver, MapStorer, Joomla FAP, SWFslideshow to cite a few), all of them are also “free” as in “free lunch” but in more than ten years I did not receive one cent as a donation, most of the time those projects were funded by one or more of my customers.

After keeping Simple ACL unpublished for a while, I simply felt I couldn’t spend time to publish, promote and give assistance on another free software project for nothing, I was simply dedicating too much time in open-source free projects without receiving back any money.

That’s why instead of keeping Simple ACL hidden in my desktop I decided to distribute it for a small fee, please note that this fee goes to cover the plain costs of assistance (answering to emails, writing documentation etc.) and development of Simple ACL, I will certainly not get rich with this fees.

This is not in contrast with free-software philosophy: GNU Free Software Foundation philosophy not only says that you can distribute free software for money, but encourage you to do so:

http://www.fsf.org/licensing/licenses/gpl-faq.html#DoesTheGPLAllowMoney

http://www.gnu.org/philosophy/selling.html

Can I distribute or sell Simple ACL?

Yes, you can. But doing so, you will probably provoke a stop in the development of Simple ACL, since I will not raise enough funds to cover the costs of its development.

It’s up to you.

Is this fee an yearly fee?

No, you donate once, you get the software and one year email assistance to set it up. That’s all.
I will send you all the future versions of the component (if any) for free.

“Delete” ACL rule doesn’t work

True, but this is not my fault, Joomla does not allow article deletion from the font-end, hence this rule is useless at the moment (but I have implemented it in case future Joomla versions support deletion from the front-end).

Why “Simple” ?

Well, because the objectives of this project were limited:

• do not touch the core of Joomla
• be unobstrusive: you can install and remove the component without consequences
• do not interfere with standard Joomla user and permissions: Simple ACL respect standard Joomla permissions levels, and only acts after Joomla has done its checks and controls
• solve a simple problem: let selected users to access and/or edit selected sections

I have 1000 users and 1000 sections, does Simple ACL suit my needs?

Probably not: Simple ACL does not support user defined (custom) groups, this mean that you should set up 1000 ACL’s to bind your 1000 users to their 1000 sections. This is just unpractical.
The latest version has limited group support. You can now add ACLs to the following standard Joomla user groups:

• registered
• author
• editor
• publisher
• manager

In case of ACL conflicts between group-ACLs and user-ACLs, the second will always prevail (see the Decision Flowchart scheme for details).

What kind of default access policy should I choose?

Simple ACL allows you to configure a default access policy on the individual actions (Create, Update, Retrieve and Delete (the lattest not being implemented in Joomla front-end at the moment).

Please remember that Simple ACL rules apply only to registered users, by keeping this in mind you could have two main scenarios (other scenarios or combinations are of course possible):

1 – Your website is completely public (everybody can see everything) but you have (for example) three authors (A, B, C) and two sections (A, B). You want user A to edit only section A, user B to edit only section B and user C to edit both. In this case, you would

• create users A, B and C as authors (or editor or publisher)
• set Joomla standard access to “public” for sections A, B and C (this is the default)
• set Simple ACL default access policy to Retrieve=Allow, Create=Deny, Update=Deny, Delete=Deny
• create one ACL for user A/section A to allow all actions (Create, Retrieve, Update, Delete)
• create one ACL for user B/section B to allow all actions (Create, Retrieve, Update, Delete)
• create one ACL for user C/section A to allow all actions (Create, Retrieve, Update, Delete)
• create one ACL for user C/section B to allow all actions (Create, Retrieve, Update, Delete)

2 – Your website is mainly public, but you have some private sections that you want to be accessible only from selected users. You have (for example) three authors (A, B, C) and two private sections (A, B) and you want user A able to read (and not edit) section A, user B able to read (and not edit) section B, user C able to read (and not edit) all three sections. In this case, you would

• create users A, B and C as registered (remember, they don’t need to edit anything, just read)
• create sections A, B and C and set standard Joomla access level to “registered” otherwise all user (included A and B) would be able to read section A and B while not authenticated (logged in)
• set Simple ACL default access policy to Retrieve=Deny, Create=Deny, Update=Deny, Delete=Deny
• create one ACL for user A/section A to allow Retrieve and deny all other actions
• create one ACL for user B/section B to allow Retrieve and deny all other actions
• create one ACL for user C/section A to allow Retrieve and deny all other actions
• create one ACL for user C/section B to allow Retrieve and deny all other actions

Why two different plugins?

System plugin must always be installed and activated otherwise Simple ACL will not work.

Content plugin is only useful when both of the following conditions apply:

• in your default access policy (as set in component parameters window) Retrieve=deny
• and you have a mixture of articles coming from allowed and denied sections in the front page

If given the conditions above you don’t activate the content plugin, a single denied article in the front page will deny the whole page.

What happens when a logged in user try to access/edit a denied page?

A “denied page” means a page containing an article that belongs to a section non accessible by that user because of Simple ACL restrictions.
The user will be redirected to a page generated by Simple ACL component (or to an URL of your choice, you can configure the URL through the component parameters configuration in the control panel). The generated deny page shows the deny message that you can change through the Simple ACL parameters settings in the control panel. The page shows also the default Simple ACL policy and the existing ACLs for that user so the user can see exactly which sections he can access.

Remote machine is 192.168.1.2 with SSH running on non-standard port 12345

ssh -p12345 -L 3333:localhost:5432 root@192.168.1.2

After this, you can connect to port 3333 on localhost to access remote postgresql DB server.

Questo breve articolo merita una lettura da parte di tutti coloro che sono interessati all’accessibilità e alla possibilità di usare prodotti open source conformi alla normativa italiana (legge “Stanca”).

Joomla FAP non è diverso da joomla. Anzi è joomla. Va installato joomla 1.5.x (in atto 1.5.3). FAP è costituito da un template accessibile, da un componente accesskey, alcune modifiche al core (non modifiche talmente strutturali da comprometterne la sicurezza) e il suggerimento di installare HTMLpurifier (che trovi fra le estensioni di joomla.org al link indicato nel forge).

ASPETTI NORMATIVI:
Teniamo presente che le disposizioni che regolano la materia sono, nell’ordine:
1) Legge 04/01/2004, n° 4;
2) Regolamento di attuazione della Legge 9 gennaio 2004, n. 4 per favorire l’accesso dei soggetti disabili agli strumenti informatici collegamento esterno, approvato con Decreto del Presidente della Repubblica, 1 marzo 2005, n. 75, pubblicato sulla Gazzetta Ufficiale n. 101 del 3 maggio 2005, attuativo dell’articolo 10 della Legge 4/2004;
3) Requisiti tecnici e i diversi livelli per l’accessibilità agli strumenti informatici, approvati con Decreto Ministeriale 8 luglio 2005, pubblicato sulla Gazzetta Ufficiale n. 183 dell’8 agosto 2005, attuativo dell’articolo 11 della Legge 4/2004;
4) Codice dell’amministrazione digitale, ci riferiamo al Decreto Legislativo 7 marzo 2005, n. 82 , pubblicato sulla Gazzetta Ufficiale n. 112 del 16 maggio 2005, modificato e integrato dal Decreto Legislativo 4 aprile 2006, n. 159;

FAP è accessibile dal lato front-end. Secondo alcuni, questo costituirebbe una violazione della Legge Stanca. In realtà, considerando che il back-end costituisce il “lato gestionale” del CMS che non è destinato a “erogare” servizi e informazioni, ma, piuttosto, a riceverli per metterli a disposizione dell’utenza – sotto forma di pagine web – attraverso il front-end, non mi sembra affatto che la mancata rispondenza del back-end del FAP alla Legge Stanca costituisca violazione della stessa.
L’articolo 1 della Legge, infatti, nel declamare gli obiettivi da garantire, recita:

“il diritto di accesso ai servizi informatici e telematici della pubblica amministrazione e ai servizi di pubblica utilità da parte delle persone disabili”

Nella stessa direzione, l’art 2 nel definire il concetto di accessibilità utilizza la locuzione:

“capacità dei sistemi informatici, nelle forme e nei limiti consentiti dalle conoscenze tecnologiche, di erogare servizi e fornire informazioni fruibili, senza discriminazioni, anche da parte di coloro che a causa di disabilità necessitano di tecnologie assistive o configurazioni particolari”

Il back-end, quale lato amministrativo o gestionale del CMS, non fornisce alcuna informazione e non eroga alcun servizio, ma “riceve” tutto questo per, ribadisco, renderlo disponibile all’utenza.
Non vale neppure invocare che:

• i dipendenti di una pubblica amministrazione possono (e debbono, in parte) essere disabili;
• che deve essere garantita parità di trattamento e condizioni lavorative.

Esistono mansioni che non possono in nessun caso essere svolte da chi è affetto da talune disabilità. Si pensi a mansioni di facchinaggio, operai, giardinieri, autisti e una infinità di altre.
Anche la gestione del back-end rientra fra queste. In presenza di talune disabilità, ad esempio, l’inserimento delle informazioni, l’erogazione dei servizi diventa estremamente gravoso.
Si pensi solo che attraverso il web possono essere erogate svariate tipologie di servizi. Servizi che non potrebbero, in nessun caso, essere erogati da dipendenti con particolari disabilità motorie o sensoriali.
FAP, quindi, risponde ai requisiti richiesti alla legge italiana e non solo (sicuramente risponde alle richieste del bando che hai postato).
Per fare dei test, l’unico validatore automatico esistente in rete è fornito dall’Università di Toronto:
http://checker.atrc.utoronto.ca/index.html

In ogni caso, un ottimo riassunto delle caratteristiche di joomlaFAP lo trovate qui: http://www.itopen.it/wp-content/uploads/2008/05/joomla_fap.pdf

Infine, per quanto riguarda il “bollino” il Decreto del Presidente della Repubblica n. 75 del 1 marzo 2005 dispone che le Pubbliche Amministrazioni autocertifichino l’accessibilità del sito, dopo aver richiesto dichiarazione di conformità al fornitore (tu, nella fattispecie).
L’autocertificazione di conformità, con la tua dichiarazione allegata, va “segnalata” (art. 8 comma 1 del Decreto) al CNIPA (non al Ministero dell’Innovazione Tecnologica) .
L’art. 9 comma 2 dello stesso Decreto, poi, dispone che:

1. Nelle procedure svolte dai soggetti di cui all’articolo 3, comma 1, per l’acquisto di beni e per la fornitura di servizi informatici, i requisiti di accessibilità stabiliti con il decreto di cui all’articolo 11 costituiscono motivo di preferenza a parità di ogni altra condizione nella valutazione dell’offerta tecnica, tenuto conto della destinazione del bene o del servizio. La mancata considerazione dei requisiti di accessibilità o l’eventuale acquisizione di beni o fornitura di servizi non accessibili è adeguatamente motivata.

2. I soggetti di cui all’articolo 3, comma 1, non possono stipulare, a pena di nullità, contratti per la realizzazione e la modifica di siti INTERNET quando non è previsto che essi rispettino i requisiti di accessibilità stabiliti dal decreto di cui all’articolo 11. I contratti in essere alla data di entrata in vigore del decreto di cui all’articolo 11, in caso di rinnovo, modifica o novazione, sono adeguati, a pena di nullità, alle disposizioni della presente legge circa il rispetto dei requisiti di accessibilità, con l’obiettivo di realizzare tale adeguamento entro dodici mesi dalla data di entrata in vigore del medesimo decreto.

Ai sensi dell’articolo 7, comma 1, lettera b), della legge n. 4 del 2004, la Presidenza del Consiglio dei ministri – Dipartimento per l’innovazione e le tecnologie, avvalendosi del Cnipa, previa comunicazione inviata all’amministrazione statale interessata, verifica il mantenimento dei requisiti di accessibilità dei siti e dei servizi forniti e dà notizia dell’esito di tale verifica al dirigente responsabile; qualora siano riscontrate anomalie, viene richiesta all’amministrazione statale medesima la predisposizione del relativo piano di adeguamento con l’indicazione delle attività e dei tempi di realizzazione.

Spero di aver detto tutto

EDIT:
Ecco, qualcosa l’avevo dimenticata. Lo stralcio del bando che tu hai postato presenta forti anomalie. Stranamente viene richiesta la fornitura di un sito non accessibile secondo la Legge italiana, ma poi si pretende la dichiarazione di accessibilità.
Fossi in te predisporrei un sito in 1.0 strict accessibile secondo la normativa italiana.
La legge, infatti, dispone all’art. 4:

Non capisco come possa essere stato emanato un bando di quel genere quando l’art. 9 della Legge, in materia di responsabilità, dispone:

L’inosservanza delle disposizioni della presente legge comporta responsabilità dirigenziale e responsabilità disciplinare ai sensi degli articoli 21 e 55 del decreto legislativo 30 marzo 2001, n. 165, ferme restando le eventuali responsabilità penali e civili previste dalle norme vigenti.