We're starting our effort to ensure that our application is accessible. I'm finding issues with the ribbon in our app that I've been able to duplicate in your samples. In running your sample browser (Document Editor demo), I noticed the following issues using JAWS 11 (uses WPF's UIA model):
1) The buttons contained within the File menu do not announce their label when you arrow through them. However, if you go to one of the buttons that has a submenu (Print for example), when you arrow the buttons in the submenu, they do announce their label. I find that the buttons within the other ribbon tabs announce their label. I've also noticed that the buttons in the footer don't announce their label either.
2) The RecentDocuments control - neither the file name nor the pin control reads out any information.
3) If you allow the Ribbon to get focus and arrow through the tabs, you'll notice that each tab announces its label except for "Format" (your contextual tab).
4) When a tab has focus, pressing the down arrow moves focus down into the contents of the tab. The particular button that gets focus differs from the Office implementation. In Office 2010, it is the first button in the tab that gets focus. In your sample, it seems to be the button that is closest to the location of the tab.
5) The left/right arrows work when navigating through the contents of a tab. I'm seeing an issue in our application that I don't see in yours (perhaps because you don't have many disabled buttons).
a) Focus is on a PopupButton that is the last button in a group.
b) The 1st button in the next group is disabled.
c) If you press the right arrow, focus goes back up to the tabs instead of going to the 2nd button in the next group.
What is the potential for having these issues addressed in the next release and what is the general timeframe? Are there workarounds that would allow us to fix these issues?
Thanks in advance!
P.S. - Just a side note: I've noticed that, if you're using Jaws, it doesn't read things out correctly if you're running within VS 2010. To try out my app (and yours), I have to run the .exe directly.
[Modified at 04/28/2010 02:50 PM]
1) The buttons contained within the File menu do not announce their label when you arrow through them. However, if you go to one of the buttons that has a submenu (Print for example), when you arrow the buttons in the submenu, they do announce their label. I find that the buttons within the other ribbon tabs announce their label. I've also noticed that the buttons in the footer don't announce their label either.
2) The RecentDocuments control - neither the file name nor the pin control reads out any information.
3) If you allow the Ribbon to get focus and arrow through the tabs, you'll notice that each tab announces its label except for "Format" (your contextual tab).
4) When a tab has focus, pressing the down arrow moves focus down into the contents of the tab. The particular button that gets focus differs from the Office implementation. In Office 2010, it is the first button in the tab that gets focus. In your sample, it seems to be the button that is closest to the location of the tab.
5) The left/right arrows work when navigating through the contents of a tab. I'm seeing an issue in our application that I don't see in yours (perhaps because you don't have many disabled buttons).
a) Focus is on a PopupButton that is the last button in a group.
b) The 1st button in the next group is disabled.
c) If you press the right arrow, focus goes back up to the tabs instead of going to the 2nd button in the next group.
What is the potential for having these issues addressed in the next release and what is the general timeframe? Are there workarounds that would allow us to fix these issues?
Thanks in advance!
P.S. - Just a side note: I've noticed that, if you're using Jaws, it doesn't read things out correctly if you're running within VS 2010. To try out my app (and yours), I have to run the .exe directly.
[Modified at 04/28/2010 02:50 PM]
