Accessible Rich Internet Applications Working Group Teleconference -- 15 Mar 2018

<joanie> agenda: this

<joanie> agenda: be done

Date of next meeting

Joanie: DO we want to meet on 29th immediately after C-SUN?
... I think the working group is done with reviewing and discussing the html

MC: it would be good if we can have pointer for for ARIA working group member but I am okay if we can officially consider it done

Janina: There should be some response from Steve or some kind of follow through after C-SUN

Brayn: Basically what I gathered that plan is use this document for the mapping.

Joanie: we need to done with ARIA and HTML
... we have no burning issue. lets skip to another point.

rssagent, next item

Reminder: Please complete survey for May F2F

<joanie> https://www.w3.org/WAI/ARIA/wiki/Meetings/F2F_Spring_2018

<joanie> https://www.w3.org/2002/09/wbs/83726/2018-05_FtF/

Joanie: we need headcount as soon as possible, please fill out the survey about your availability and meal options
... No question?

AccName: Wide-review Working Draft publication

We have a CFC about accName to publish and after this meeting I'll announce the result.

AccName: 1.1 issues update

<joanie> https://github.com/w3c/accname/issues

Joanie: There are all triage and milestone but I dont see any pull request
... Zakim is working pretty good

AccName: Testing and resultsagenda: be done

<joanie> https://w3c.github.io/test-results/accname/

Joanie: JG has provided results. Thanks, Jon

<joanie> https://w3c.github.io/test-results/accname/all.html

Joanie: if you look the fails results, there are number of results that are technically not failure.

<joanie> https://w3c.github.io/test-results/accname/

<joanie> macOS has multiple properties through which an accessible name can be exposed to platform assistive technologies (e.g. AXDescription and AXTitle). Because what is being tested here is the calculation of the name rather than the specific property through which that value is exposed, these alternatives are being taken into account when determining if a test result is a PASS or FAIL. Taking the AXTitleUIElement

<joanie> into account as part of testing remains to be done.

<joanie> These issues will be resolved, or more clearly identified, prior to releasing the final implementation report.

Joanie: talking about testing approach

JG: Are you saying information is there, its just there where it is supposed to be?
... Its up to the voice over to take the information and make the accessible name. we cant really control what AT does incase of apple.

Joanie: Excellent idea

<joanie> https://w3c.github.io/test-results/accname/complete-fails.html

Joanie: we have a non-trivial number of complete fail. I am going to hopefully solve the completely fail by myself
... if you are a user-agent developer and can help me, now is the time to raise your hand.

JG: is there any special place to file the bug?

<joanie> https://bugzilla.mozilla.org/

Joanie: I will provide you the location where you can file a bug

<joanie> https://bugzilla.mozilla.org/enter_bug.cgi?product=Core

<joanie> Component: Disability Access APIs

Joanie: If it fails across the board then we dont need to worry.

<joanie> https://w3c.github.io/test-results/accname/complete-fails.html

Joanie: If you could provide you report, what is the expected result vs actually result

<joanie> https://bugs.webkit.org/enter_bug.cgi?product=WebKit&component=Accessibility&op_sys=All&rep_platform=All&short_desc=AX%3A%20

Joanie: If you dont want to file a bug, just tell me and I will take care of it.

<joanie> https://bugs.chromium.org/p/chromium/issues/list

Joanie: I'll start filing chrome bug