11/10/2023 0 Comments Nvda screen reader vs jaws![]() We will work with the developer to see if scripting and tabindex are the culprits. When we tested the linked buttons using only the keyboard (no screen reader) with Firefox and Chrome, each button gets focus (highlighted) and we can use the enter key to follow the link. We re-tested with JAWS 18 on IE and Firefox and got the same results as with NVDA. To: Matthew Putland Sean Murphy (seanmmur) RE: tab vs. Your buttons/links are keyboard accessible, period. You are now listening to the page as it is coded without css repositioning and other tricks used for visual presentation.ġ. Then make sure you are in Browse mode for NVDA or Virtual PC Cursor on for JAWS and use the Ins+down arrow key to have the screen reader read from that location. ![]() You should hear the same thing as when you put focus directly before the heading in this case, and it may be way before it for that matter. Arrows up and down go through the code, line by line, arrows left and right will go through words and sentences. This is used by actual users of screen readers to navigate the page and content to hear what is on the page. When you use the arrow keys you are navigating the DOM or code and you will hear things but you cannot select them with the Enter key in most cases. The enter key is used during tabbing to select the links/buttons or selectable elements, which you said works in your original email query. To: Schafer, Carmen Matthew Putland Sean Murphy (seanmmur) RE: tab vs. Is this a WCAG 2.0 violation since the individual buttons can be comprehended and accessed using the tab key, but not with the arrow key?įrom: ALAN SMITH [mailto: Tuesday, Octo2:18 PM ![]() When using the down arrow key (read next item) on the three buttons NVDA says “Banner banner landmark clickable list” and moves onto the next section of the webpage. We are trying to distinguish whether this is a WCAG 2.0 violation or normal screen reader behavior. Hi Alan, thank you for your input and sorry to be unclear. To: ALAN SMITH Matthew Putland Sean Murphy (seanmmur) RE: tab vs. ![]() I’d say you are looking for something that is not there. ![]() Good luck if you feel you need to investigate this more. I pasted your code into an html file and it sounds correct to me for how it is coded. Like I mentioned, it is not a WCAG 2.0 violation.ĭown arrows are reading it just like it is coded and intended to be used. To: "Schafer, Carmen", Matthew Putland, "Sean Murphy (seanmmur)", " ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |