Ticket #9528 (closed PLIP: wontfix)

Opened 7 years ago

Last modified 5 years ago

Make accesskeys configurable

Reported by: dukebody Owned by:
Priority: minor Milestone: Future
Component: General Version:
Keywords: Cc:

Description

(Moved from  http://plone.org/products/plone/roadmap/109)

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.

Change History

comment:1 Changed 5 years ago by rossp

  • Status changed from new to closed
  • Resolution set to wontfix

PLEASE READ THIS AND RE-OPEN VALID PLIPS!

As we launch the new PLIP process we'd like to see which PLIPs:

  • are still appropriate/needed
  • still have owners/proposers/champions
  • still have available implementers

If this PLIP should still be considered for future releases of Plone please do re-open this ticket and assign an appropriate milestone. If it should be considered for the next release of Plone, use the 4.2 milestone. Also be sure to update the PLIP description, requester, owner, etc. and include a comment detailing recent progress and new plans. We will use all these details in the new continuous PLIP process.

comment:2 Changed 4 years ago by davisagli

  • Component changed from Infrastructure to General
Note: See TracTickets for help on using tickets.