I saw a demo of the Views 3.0 module today at Berkeley Drupal Users Group (BDUG) today. The presenter noted that if a page that is part of a tabbed-pages view differs from the default of the view, the differing options are displayed in the Views UI as italics. I haven't seen the view source of the page, so it may well be empasis tags.
But the larger issue, is marking content with italics or emphasis to distinguish that it has a certain quality, e.g., not a default value, considered sufficient for accessibility, without some other indication that would be read out, e.g., an asterisk?
I note it appears to be optional in NVDA as to whether to read out text attributes, and I'd guess it is in JAWS. So it would seem to be at least necessary for the UI to explicitly spell out that non-default values on the UI are marked with italics.
Am I correctly reading this as an accessibliity issue, or am I reading the requirements too restrictively?
Comments
You are correct that this is
You are correct that this is a problem for accessibility. But, it is as much a problem for usability. The emphasis on the text is ambiguous to all.
I am not sure what the best way to resolve this would be, without further congesting the UI. From a screen-reader accessibility perspective it is reasonably clear what the status of the property is once you attempt to edit its value.
Accessibility Consultant & Web Developer - Zufelt.ca
@ezufelt on Twitter | LinkedIn profile