Personal tools
You are here: Home Products Plone Roadmap #109: Make accesskeys configurable
Document Actions

#109: Make accesskeys configurable

Contents
  1. Motivation
  2. Proposal
  3. Implementation
  4. Deliverables
  5. Risks
by Geir Baekholt last modified June 11, 2006 - 00:21
Make the Plone acceskeys for disabled use configurable on a per-site basis instead of hardcoded in the templates
Proposed by
Geir Bækholt
Seconded by
Matt Lee
Proposal type
User interface
State
being-discussed

Motivation

Accesskeys are hardcoded in Plone. Even if they now follow W3 WAIS guidelines, some organisations have deviating standards they need to follow ( for example the UK Government acessibility standards ). This currently requires site implementors to hack and override templates.

Proposal

Make the base set of accesskeys configurable by site administrators. A new control panel with a form to set the new accesskeys.

Implementation

Make a control panel for setting accesskeys. Somewhere to store the data.

Change the templates that set the accesskeys

Change the accessibility page to look up the dynamic values.

Deliverables

Find somewhere in Plone to store the values for the accesskeys. The structure makes sense to store in something like a dictionary. A second best solution would be a list of string properties.

Create a control panel to set the accesskeys

Create form handlers to save the accesskeys

Have the accessibility page look up thhe dynamic values instead of listing the hardcoded ones.

Change the templates that define the templates to do dynamic lookup.

Risks

This could possibly conflict with i18n of accesskeys if that is in use.


For any issues with the web site functionality, please file a ticket.

Please consult the policy on plone.org content if you want your content published on this site.

Servers and hosting by