Comments (6)
@mcking65 - I started to review the checkbox tests and have the following notes.
- The exact path of execution is not always clear. For example, the test "Reading checked checkbox in interaction mode" has two instructions. The first is to put the screen reader into forms mode. The second is to read the checkbox with the supplied commands. This makes sense, however, in order to create consistent, easily understandable, and reproducible results, I think we need an additional step that answers the question 'how did the user navigate to the checkbox'?. In other words, it's missing an instruction that says something like "press the tab key until the first checkbox is focused". Exactly how the user navigated to an element may impact how the element was read. I've seen this in previous versions of JAWS. This is also true for the operation tests. Note that there are situations where keyboard focus may remain on a previous input, while virtual focus is moved to a new input, which can cause some screen readers to convey incorrect information. I believe this was a problem in JAWS 2019 and was fixed in the 2020 version. All of that to say: providing detailed instructions on the path of execution to get to the desired element is pretty important.
- Reading mode commands are listed for "Navigating to checkbox in interaction mode." Actually, "Navigating to checkbox in reading mode" describes interaction mode instructions, so I think the names just got swapped.
from aria-at.
I'll make a PR to add missing navigation instructions and fix test titles
from aria-at.
Also, virtual is misspelled
from aria-at.
also change "spoken" to "conveyed"
from aria-at.
Update: I submitted two pull requests related to the issues outlined here.
However, I also noticed that the number of steps is hardcoded in the test harness.
I think it would still be good to add an instruction like "click the button to open the test page and wait for the first checkbox to automatically receive focus", but I'm not sure about the best way to do that yet given the architecture.
from aria-at.
I think this review has been completed!
from aria-at.
Related Issues (20)
- Support test plans that specify a command assertion exception that does not include an assertion priority prefix HOT 1
- Support specifying a minimum required AT version in the name of a commands.csv file
- Define assertion verdicts in glossary HOT 1
- Resolve conflicts in Safari testing for Navigate out of a radio group (Radio Group Example Using aria-activedescendant, Test 5 and 6, V24.03.12)
- Resolve conflicts in Safari testing for Navigate backwards into a radio group (Radio Group Example Using aria-activedescendant, Tests 2 and 4 V24.03.12)
- Feedback: "Navigate backwards to a menu button" (Action Menu Button Example Using aria-activedescendant, Test 6, V22.03.17) HOT 4
- Feedback: "Open a menu" (Action Menu Button Example Using aria-activedescendant, Test 12, V22.03.17) HOT 2
- Feedback: "Open a menu" (Action Menu Button Example Using aria-activedescendant, Test 12, V22.03.17) HOT 2
- Feedback: "Navigate to the first item in a menu" (Action Menu Button Example Using aria-activedescendant, Test 18, V22.03.17) HOT 1
- Feedback: "Activate a menu item" (Action Menu Button Example Using aria-activedescendant, Test 24, V22.03.17) HOT 1
- Outdated NVDA Bot responses: "Open a modal dialog" (Modal Dialog Example, Test 1, V24.05.02) HOT 3
- Feedback: "Open a modal dialog" (Modal Dialog Example, Test 1, V24.05.02) Remove Assertions for JAWS and NVDA HOT 1
- Feedback: "Navigate forward from the last focusable element to the first focusable element in a modal dialog" (Modal Dialog Example, Test 11, V24.05.08)
- Feedback: "Open a modal dialog" (Modal Dialog Example, Test 3, V24.05.09) HOT 3
- Incorrect NVDA Bot responses: "Navigate to the bottom of a modal dialog" (Modal Dialog Example, Test 14.1, V24.05.09) HOT 5
- Conflicting VoiceOver test results: "Close a modal dialog" (Modal Dialog Example, Test 6, V24.05.09) HOT 3
- Conflicting VoiceOver test results: "Navigate to the top of a modal dialog" (Modal Dialog Example, Test 5, V24.05.09) HOT 3
- `npm run update-reference` is out of date
- Conflicting JAWS results: "Close a modal dialog" Test 2 in V24.05.09 HOT 2
- Feedback: "Bump into the top edge of a modal dialog" (Modal Dialog Example, Test 8, V24.05.09) HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from aria-at.