@DConnolly: Thanks for the info... I think it's about time we update our accessiblity software on our testing network then to something that supports WCAG 2.0. We're still using Hi-Software's AccVerify tool which only covers WCAG 1 priorities 1,2 & 3 and Section 508.
I know the WCAG 1.0 was published in 1999 but it looks like it was still valid until as recently as last year.
I would still like to see XPages use an unobtrusive technique with a valid href (instead of '#') on the view links. This would allow the link to fall back on the href url in the event of a user not having JS enabled and would also make the links work when opening them in a new browser tab.
Nick mentions that you can obviously code your own html links, similarly to how you could always use your own HTML in domino views, but I believe this should be the default behviour of the links property, not something extra you have to code in yourself.
@DConnolly: Thanks for the info... I think it's about time we update our accessiblity software on our testing network then to something that supports WCAG 2.0. We're still using Hi-Software's AccVerify tool which only covers WCAG 1 priorities 1,2 & 3 and Section 508.
I know the WCAG 1.0 was published in 1999 but it looks like it was still valid until as recently as last year.
I would still like to see XPages use an unobtrusive technique with a valid href (instead of '#') on the view links. This would allow the link to fall back on the href url in the event of a user not having JS enabled and would also make the links work when opening them in a new browser tab.
Nick mentions that you can obviously code your own html links, similarly to how you could always use your own HTML in domino views, but I believe this should be the default behviour of the links property, not something extra you have to code in yourself.