3484c6b7b8
The original implementation (which was never merged) had a `<select>` field for the switch, which offered accessibility issues. So I came up with a very bad idea, which was emulating the look and feel of a select field while making it more accessible for keyboard users. This approach is inconvenient because we were using a bunch of ARIA roles to do the same thing that can be done with a list of links, going against the first rule of ARIA, which is: > "Don’t use ARIA if you can achieve the same semantics with a native > HTML element or attribute Not only that, but the control was confusing for people using mobile phones (select fields don't behave the same way), and we were using *invalid* ARIA roles in this situation, leading Axe to report a critical accessibility error: ``` aria-required-children: Certain ARIA roles must contain particular children (critical) https://dequeuniversity.com/rules/axe/4.10/aria-required-children?application=axeAPI The following 1 node violate this rule: Selector: ul[data-dropdown-menu="edw1i2-dropdown-menu"] HTML: <ul class="dropdown menu" wnenu="edw1i2-dropdown-menu" data-disable-hover="true" op="true" role="menubar"> Fix any of the following: - Element has children which are not allowed: button[tabindex] ``` So, at least for now, we're using a simple list of links. We might style it in the future if we find ways to make usability improvements, but, for now, it does the job, and it does it better than the custom control we were using.
CONSUL DEMOCRACY
Citizen Participation and Open Government Application
This is the opensource code repository of the eParticipation website CONSUL DEMOCRACY, originally developed for the Madrid City government eParticipation website, and currently maintained by the open source software community in collaboration with the CONSUL DEMOCRACY Foundation.
Documentation
Check the ongoing documentation to learn more about how to start your own CONSUL DEMOCRACY fork, install it, customize it and learn to use it as an administrator/maintainer.
CONSUL DEMOCRACY Foundation and project website
You can access the main website of the project at http://consuldemocracy.org where you can find information about the use of the platform, the CONSUL DEMOCRACY Foundation, the global community of users and local partners, news, and ways to get more support or get in touch.
Configuration for development and test environments
NOTE: For more detailed instructions, check the local installation docs.
Prerequisites: install git, Ruby 3.2.8, CMake, pkg-config, Node.js 18.20.3, ImageMagick and PostgreSQL (>=9.5).
Note: The bin/setup command below might fail if you've configured a username and password for PostgreSQL. If that's the case, edit the lines containing username: and password: (adding your credentials) in the config/database.yml file and run bin/setup again.
git clone https://github.com/consuldemocracy/consuldemocracy.git
cd consuldemocracy
bin/setup
bin/rake db:dev_seed
Run the app locally:
bin/rails s
You can run the tests with:
bin/rspec
Note: running the whole test suite on your machine might take more than an hour, so it's strongly recommended that you setup a Continuous Integration system in order to run them using parallel jobs every time you open or modify a pull request (if you use GitHub Actions or GitLab CI, this is already configured in .github/workflows/tests.yml and .gitlab-ci.yml) and only run tests related to your current task while developing on your machine. When you configure the application for the first time, it's recommended that you run at least one test in spec/models/ and one test in spec/system/ to check your machine is properly configured to run the tests.
You can use the default admin user from the seeds file:
user: admin@consul.dev pass: 12345678
But for some actions like voting, you will need a verified user, the seeds file also includes one:
user: verified@consul.dev pass: 12345678
Configuration for production environments
See installer
Current state
Development started on 2015 July 15th. Code was deployed to production on 2015 september 7th to decide.madrid.es. Since then new features are added often. You can take a look at the current features at the project's website and future features at the Roadmap and open issues list.
License
Code published under AFFERO GPL v3 (see LICENSE-AGPLv3.txt)
Contributions
See CONTRIBUTING.md