As long as all the selected options are always part of the set of a clearly related set of 'functions' and we don't shoe horn other options in as a nice easy fix. We don't want a polymorphic attribute as there is then extra work to figure out what it means and to perform validation. Steve Lee OpenDirective http://opendirective.com On 10 May 2015 at 06:12, lisa.seeman <lisa.seeman@zoho.com> wrote: > > Suggestion to simplify ARIA proposal at > https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Syntax_for_adaptable_links_and_buttons > > Instead of having lots of new aria roles for different functions we simply > have one new attribute such as aria-function > aria-function can then be set to any of types proposed in the issue paper > > For example > > <a role="button" aria-function="next"> > > All the best > > Lisa Seeman > > Athena ICT Accessibility Projects > LinkedIn, Twitter > >Received on Sunday, 10 May 2015 15:38:33 UTC
This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:23:53 UTC