Skip to content
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

Accessible Rich Internet Applications 1.3 2024-02-01 #131

Closed
Tracked by #2139
daniel-montalvo opened this issue Feb 2, 2024 · 8 comments
Closed
Tracked by #2139

Accessible Rich Internet Applications 1.3 2024-02-01 #131

daniel-montalvo opened this issue Feb 2, 2024 · 8 comments
Assignees
Labels
close? FPWD Published as First Public Working Draft REVIEW REQUESTED

Comments

@daniel-montalvo
Copy link

The Privacy IG prefers groups to complete a self-review around the time of FPWD. See https://w3ctag.github.io/security-questionnaire/.

If you still want us to review your spec, please provide the information below.

In the issue title above add the document name followed by the date of this request.

Other comments:

@daniel-montalvo daniel-montalvo added FPWD Published as First Public Working Draft pending This issue needs to get a reviewer assigned to it REVIEW REQUESTED labels Feb 2, 2024
@plehegar
Copy link
Contributor

plehegar commented Feb 12, 2024

@daniel-montalvo
Copy link
Author

Hi!

Do you plan to submit review comments?

Can we consider that resolution in Detectability of assistive technology still stands?

Best.

@npdoty npdoty self-assigned this Mar 7, 2024
@npdoty npdoty removed the pending This issue needs to get a reviewer assigned to it label Mar 7, 2024
@npdoty
Copy link
Member

npdoty commented Mar 7, 2024

Apologies for the delay, this request came between a gap in our meetings. I'm looking at the spec (and catching up on the discussion from 1.2 and aria/#1371) now.

@npdoty
Copy link
Member

npdoty commented Mar 7, 2024

My only question is about the new State change notification section, which requires that events be sent. In some previous discussion, it was noted that events may be one way to programmatically determine the use of assistive technologies. And I'm not sure I understand the requirement -- is it just that DOM events be used to communicate changes? Or that user agents should send a different accessibility-related set of events?

@plehegar
Copy link
Contributor

plehegar commented Apr 4, 2024

(I'm told that the ARIA WG will follow up)

@npdoty
Copy link
Member

npdoty commented Apr 15, 2024

PING discussed. We suspect my open question is unlikely to be a privacy issue, although of course happy to hear feedback from the WG experts.

@npdoty npdoty added the close? label Apr 15, 2024
@daniel-montalvo
Copy link
Author

daniel-montalvo commented Apr 16, 2024

Hi @npdoty

Sorry for the late reply on this issue.

We concur, this is not a privacy issue from our perspective. These updates are based on the ARIA states and properties used by the authors, and are irrespective of whether ATs are running.

Maybe @jnurthen or @spectranaut have something more to add.

@npdoty
Copy link
Member

npdoty commented May 6, 2024

We believe this review is completed now. On the larger ongoing question of what features potentially reveal use of assistive technology, we also think that's worth adding to the priv/security questionnaire generally:
w3ctag/security-questionnaire#157

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
close? FPWD Published as First Public Working Draft REVIEW REQUESTED
Projects
None yet
Development

No branches or pull requests

3 participants