Opened 11 years ago

Closed 8 years ago

#5768 closed enhancement (wontfix)

Support new ARIA syntax in templates

Reported by: simonjb Owned by: Becky Gibson
Priority: high Milestone: future
Component: Accessibility Version: 1.0
Keywords: Cc:
Blocked By: Blocking:

Description (last modified by davidb)

Our template syntax is different from, and more verbose than, the new ARIA syntax for setting roles and states. We need some processing of role and state specifications in templates because FF2 does not support the new syntax. However, we could parse the new syntax in templates and make the necessary changes for FF2.

For example:

  • waiRole="menu" vs. role="menu"
  • waiState="labelledby-foo" vs. aria-labelledby="foo"

Change History (7)

comment:1 Changed 11 years ago by davidb

Description: modified (diff)

Note we could probably do this along side 5984. I wouldn't mind taking this one, and maybe pairing with Joseph so he can get a bit of a widget template tour.

comment:2 Changed 11 years ago by Becky Gibson

Milestone: 1.21.3

comment:3 Changed 11 years ago by bill

There are a couple options:

  • change the syntax; this breaks backwards compatibility but I'm doubtful anyone outside of dijit is doing a11y in their templates
  • change the syntax for the 2.0 release
  • support old and new syntax concurrently; I don't want to do that since it adds more overhead to widget instantiation.

Also note that the new syntax can be handled natively by FF3, which would make template rendering faster except for FF2.

comment:4 Changed 10 years ago by bill

Milestone: 1.31.4

Moving to 1.4, when we will desupport FF2.

comment:5 Changed 10 years ago by davidb

I think it is worth considering not supporting FF2 for ARIA.

comment:6 Changed 10 years ago by Becky Gibson

Milestone: 1.4future

comment:7 Changed 8 years ago by bill

Resolution: wontfix
Status: newclosed

FF2 is already desupported, and for 2.0 we'll just remove role/state parsing code from _Templated, since the templates can directly set role and aria state attributes.

Note: See TracTickets for help on using tickets.