It would be nice if the appropriate form_*() functions allowed for generation of the accesskey XHTML parameter for elements where it made sense, e.g. fieldset, input, textarea, etc.

One can kludge in an accesskey parameter in the attributes argument (probably), and by hand patch in a "span" to underline or otherwise highlight the access key, but it's all hacks to do it right now.

Comments

coreb’s picture

Version: x.y.z » 6.x-dev

Moving from x.y.z queue to 6.x-dev. I don't know the api well enough to know if this functionality exists or not.

Pasqualle’s picture

Version: 6.x-dev » 7.x-dev

what is accesskey XHTML parameter?

effulgentsia’s picture

Title: Generate accesskey parameters in form elements » Add #accesskey property to element types
Version: 7.x-dev » 8.x-dev
Component: theme system » base system
Priority: Minor » Normal
Issue tags: +Usability, +Rendering, +Accessibility

I think this is a really good idea, but too late for D7. I think the D7 render system makes it possible for a contrib module to solve this (add a #accesskey property, and use #pre_render/#theme/#theme_wrappers or CSS3 to add some visible indicator for what the access key is). I'd love to see a worked out solution make it into D8 core.

mgifford’s picture

Status: Active » Closed (won't fix)

Accesskeys are an old idea that just can't work without standardization between Assistive Technology providers. See:
#23628: Automatic access keys

I've marked this as won't fix, for the same reason as the issue above.

mgifford’s picture

Issue summary: View changes
Issue tags: +accesskey