Most voted for AWPSs
You can vote for AWPSs you would most like to become WRI-compliant.
| WordPress | 14% |
| Drupal | 11% |
| Joomla! | 11% |
| MediaWiki | 8% |
| FCKEditor | 6% |
Coding
The WRI aims to enthuse developers of Web Publishing Systems, as well as aid them by offering knowledge and resources. Besides clearly defined certification requirements, WRI plans to provide a knowledge base containing both information on how to overcome typical design problems and actual code, be it snippets, or tools. By sharing experience through these channels, developers help each other solve common problems. This collaberation will also generate a pool of specialised programmers who can offer help based on first-hand experience.
The WRI’s practical role in this will be to act as a central point, offering the necessary collaborative tools (discussion list, wiki, etc.), a database system for the knowledge base, hosting relevant reuseable code and tools, etc.
Through this a community will come to be which does actual work improving the output of Web Publishing Systems, and thus of the accessibility of the Web.
Additionally, the WRI’s ambition is to hire programmers and offer bounties for specific problems to solve, so as to ensure that all of this will not need to rely solely on volunteer enthusiasm; to ensure we have a powerful engine at the base of the WRI.
Initial targets
- Web Publishing Systems that already come closest to producing accessible Web sites
- Web Publishing Systems that allow as much as possible to be improved upon by adding modules/functions, as that will result in code that can be re-used for other systems.
- Inline editors, that are used embedded in Web Publishing Systems, as they will affect multiple Web Publishing Systems.
- Web Publishing Systems that are used a lot