-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Meeting notes with stakeholders #111
Comments
If I understood the Vispero meeting notes correctly, it was suggested that instead of testing with Firefox, it would be better to test with Edge. I don't think that's a good idea, because in my opinion the AT support of Chrome and Edge are hardly different. I.e. the test results for Chrome will mostly apply to Edge as well. Firefox, however, is a significantly different browser. In my tests with JAWS, I have not seen any differences between Chrome and Edge, but I have seen many differences between Chrome and Firefox. Therefore I think that a test with Firefox makes sense. Otherwise we should use this table https://webaim.org/projects/screenreadersurvey8/#browsercombos as a guide |
Thanks, @JAWS-test. Let's continue that discussion in #116 |
On 2020-03-19, we gave an introductory presentation about the ARIA-AT project to Aaron Leventhal, Zack Goldberg, Shawn Lauriat, Kim Bae (Google). Meeting notes. |
On 2020-11-12, I met with NVDA developers @feerrenrut and @michaelDCurran to talk about the automation prototype (#321). Meeting notes. |
I'm filing this as an issue to be transparent about these meetings (with their consent), and to have something to point to in new issues we'll file for things that was brought up in these meetings.
On 2020-03-02, we gave an introductory presentation about the ARIA-AT project to @cookiecrook (Apple). Meeting notes.
On 2020-03-03, we gave an introductory presentation about the ARIA-AT project to Brett Lewis, Glen Gordon, Eric Damery (Vispero). Meeting notes.
The text was updated successfully, but these errors were encountered: