I recently started using the Domino Designer 9.0.1 client, and immediately noticed this slightly alarming warning in my XPages applications. The product help page "What's new in IBM Domino Designer 9.0.1 Social Edition?" lists several XML elements for which a "role" property is deprecated (search for "Obsoleting of the role property") but it was unclear whether it would still work anyway and how any difference in the build version versus the execution version was a factor. Role is used to tag elements for accessibility, so it's important to us in meeting our accessibility compliance targets.
So I called up the appropriate developer and quizzed him. Here's what I learned:
- The "role" property isn't completely deprecated. There are other elements not in that list, to which it still applies. You still have to specify the role for those.
- For those XPage elements, including viewPanel and pager for instance, that are on the list, the Domino server now automatically supplies a "role" value, so you need not specify a role for those elements.
- However, the property still works, letting you override the server's choice if you need to. You'll just get a warning in the Problems view.
- Since the code to determine the correct role is in the runtime, not in the "build" code, if the application is built by 9.0.1 but executed by an earlier version, the role attribute will not be included in the HTML unless you have specified it– just like now. In that situation, ignore the warning and specify the role anyway.
Andre Guirard | 1 November 2013 08:45:45 AM ET | | Comments (1)