Closed shraddhaapatil closed 2 years ago
We typically should not be doing this testing directly against https://try.dot.net, as it's intended to be a component in other services via an IFRAME, and the Run button is not rendered by Try .NET in those cases. Also, direct access to try.dot.net without an IFRAME will be disabled in the coming months.
Closing this because the Run buttons in the hosting sites do not come from https://try.dot.net/.
@jonsequitur The issue is after the run button as focus is not visible on any control after run button. If still its not own by ( https://try.dot.net/) then please share external team details who owns this. So that we can route it to correct team, please share all the details of external team.
GitHubTags:#A11ySev2;#A11yTCS;#A11yWCAG2.1;#DesktopWeb;#.NET Websites;#Win10;#P2-TrydotNetWebsite-Aug21;#WCAG2.4.7;#Focus Visible;#FTP;#P2-WCP;#Keyboard
Environment Details:
Application Name: TrydotNetWebsite Standard Violated: WCAG2.4.7
Repro Steps:
1.Hit the URL https://try.dot.net 2.Tab till Run button. 3.Verify whether focus is visible or not after pressing tab after Run button.
Actual Result:
Keyboard focus is not visible when we press 'Tab' after run button.
Expected Result:
Keyboard focus should be visible when we press 'Tab' after run button.
User Impact:
Keyboard users will face difficulty in navigation if Keyboard focus is not visible when we press 'Tab' after run button.