JAWS-test

Results 395 comments of JAWS-test

Sometimes the greyed out days can also be activated. They are only gray to indicate that they belong to the previous or next month. So here the correct output of...

> Our concern with this is that it does not seem to be reflect normal operation. For instance, the established interaction in a menu is that disabled menu items are...

@mbgower Chrome seems to me to be an exception. In the rest of the desktop apps I checked on Windows 10, disabled menuitems get the focus (as I wrote above,...

@sivakusayan > It seems like in web at least, screen reader users can technically find disabled elements using the virtual cursor. This is not always true. E.g. a submenu or...

@mbgower I don't fully understand your concerns. When I read through the entire chapter https://w3c.github.io/aria-practices/#kbd_disabled_controls, I see that no standard is set here, but rather recommendations are made. It is...

@mbgower > You also said this is "based on the standard of desktop applications." Can you please provide me with some references? In most Windows desktop applications, disabled menu items...

When the pattern is finished, it may also be used for WCAG. See the discussion: * https://github.com/w3c/wcag/issues/915 * https://github.com/w3c/wcag/issues/914

@idoros Perhaps the WCAG people have ideas on how it would be correct according to SC 1.4.13 (you could ask at https://github.com/w3c/wcag/issues)

I think that's a border case. The element itself is exactly 320 px wide (tablist+tabpanel), but with the padding from the body it happens that not the tabpanel has to...

Yes, especially because [tablist](https://w3c.github.io/aria/#tablist) does not have an "Accessible Name Required".