CK source developed a paid/premium plugin: Accessibility Checker. This plugin was co-developed by Dutch government and Dutch government agencies are offered a free, perpetual license key.
I have received a generic license key for the DvG distribution. This key can not be redistributed *with* the DvG distribution, but it can easily be obtained from the DvG foundation. Alternatively, DvG users can obtain their own license key.
Vught will sponsor the addition of the plugin to DvG. We welcome others to sponsor this too!
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | add_ckeditor-2532902-8.patch | 3.78 KB | BarisW |
Comments
Comment #1
mgiffordThat's kinda strange that they have a paid service that is built on http://quailjs.org/
This is also something that someone may develop in Tenon or other APIs http://blog.tenon.io/best-practices-tips-and-ideas-for-creating-custom-c...
Anyways, also wanted to standardize on the more commonly used accessibility tag.
Comment #2
frankschaap commentedWhat surprises and irks me is indeed that my government has paid for the development of a closed addition/plugin to an already open source package. Nevertheless, it is a nice addition to the DvG distribution.
Comment #3
tessa bakkerUrl to the free version: https://www.drupal.org/project/accessibility
Comment #4
mgifford@Tessa Bakker - I don't think that's getting a lot of love these days.
@frankschaap - It's not surprising that governments do things like this, but it's sad. Would be so good of governments around the world started thinking like 18F:
https://18f.gsa.gov/2015/06/03/giving-back-to-open-source/
EDIT: Also another good link for establishing a precedent https://www.gov.uk/design-principles#tenth
Comment #5
frankschaap commented@mgifford Gov.uk was a big inspiration for the DvG distribution :-)
Comment #6
BarisW commentedComment #7
BarisW commentedComment #8
BarisW commentedHere's a start to get the ball rolling. We can't commit this unless this goes in: #2570883: Add CKEditor Accessibility Checker to the whitelist.
Comment #9
BarisW commentedComment #10
frankschaap commentedQuestion: Is it possible for DvG to include the Accessibility Checker in another way? Maybe as an installer or configuration option?
It would still have to be a generic/universal process, but it may be acceptable to have some administrative actions to get this to work.
Meanwhile I have contacted KINGgemeenten and they will look into the possibility of having the Checker re/dual licensed to be compatible with GPL. Wouldn't hold my breath though.
Comment #11
tessa bakkerWe could exploit Libraries to include the plugin.
It's very simple to get the path to the library and even check for the correct version.
There is also the possibility to download the plugin with a drush command.
Comment #12
frankschaap commentedPending a license change, I propose we implement one of these alternative ways of installing the Accessibility Checker library.
We need to check though:
- does the checker play nice with the "Kop 1" / "Kop 2" solution we use in the DvG
- the default Checker "repair option" showed more heading levels than we use/allow in the editor
The current implementation of the editor is pretty bullet proof, adding the Checker should not add new problems.
Comment #13
BarisW commentedThe editor now uses a GPL licence and the dowload URL has changed to http://ckeditor.com/addon/a11ychecker
So we can package it with DVG using the default workflow.
This still leaves the question on how we can change/add tests, to answer Frank's points regarding:
- does the checker play nice with the "Kop 1" / "Kop 2" solution we use in the DvG
- the default Checker "repair option" showed more heading levels than we use/allow in the editor
Comment #14
askibinski commented@bskibinski could you test the checker (patch) and answer the questions?
Comment #15
mgiffordJust wanted to make sure folks have seen this https://www.drupal.org/project/ckeditor_a11ychecker
Comment #16
frankschaap commentedExcellent! Thanks for the heads up!
Comment #17
joshahubbers commentedNo new DvG7 sites will be started, so we will not spend time on this issue.