Skip to content
This repository was archived by the owner on Jun 30, 2018. It is now read-only.

Mitsue-Links Accessibility Dept. Comment on SC 3.2.7 Change of Content: Avoid using the term "control" #506

Closed
ghost opened this issue Oct 10, 2017 · 9 comments

Comments

@ghost
Copy link

ghost commented Oct 10, 2017

The second exception of SC 3.2.7 Change of Content should avoid using the term "control," because a "change of content" could be triggered by user action without using any controls of a page (e.g. tilting the device).

Currently the second exception is written as below,

The user has been advised of the change of content before, or as a result of using the control;

Though SC 2.6.1 Device Sensors requires alternative methods for functionalities which require specific device sensors, users who intentionally use specific device sensors should be advised.

@DavidMacDonald
Copy link
Contributor

DavidMacDonald commented Oct 10, 2017

WCAG 2 uses control in 1.1.1 and as part of the definition for UI component,
Perhaps "triggering mechanism"?

The user has been advised of the change of content before, or as a result of using the triggering mechanism;

Or else a note on UI component that it includes tilting etc... ?

@DavidMacDonald DavidMacDonald self-assigned this Oct 10, 2017
DavidMacDonald added a commit that referenced this issue Oct 10, 2017
Added a term before the first brackets to make them make grammatical sense. May need another tweak because the line ends with "other essential visual indication". This could probably be deleted but should have some discussion first.
@ghost
Copy link
Author

ghost commented Oct 10, 2017

It is fine for us to use “triggering mechanism”.

DavidMacDonald added a commit that referenced this issue Oct 10, 2017
Changed "control that triggers it" with "triggering mechanism"
@DavidMacDonald
Copy link
Contributor

Proposed response:

We have created a pull request to replace "control that triggers it" with "triggering mechanism"

#521

@awkawk
Copy link
Member

awkawk commented Oct 11, 2017

Pull request needs to only address this change, currently it makes a bunch of other changes.

@DavidMacDonald
Copy link
Contributor

@awkawk Actually the edit is exactly what it says it is
513c371
Now other requests are part of that branch. Not sure what to do about that.

@alastc
Copy link
Contributor

alastc commented Oct 16, 2017

You're both right: if you make a pull request and then add changes to that branch, it adds them to the change request.
I would either revert the branch back to the point with just those changes, or do that locally and create a separate branch to apply the edits.

@joshueoconnor
Copy link
Contributor

@DavidMacDonald
Copy link
Contributor

DavidMacDonald commented Oct 17, 2017

Amended response as per meeting oct 17.
First bullet would become

  • There is a programmatically determined relationship between the new content and triggering mechanism

The second would become

  • The user has been advised of the change of content before, or as a result of taking the action

@joshueoconnor
Copy link
Contributor

RESOLUTION: Accept David’s 2 edits. https://www.w3.org/2017/10/17-ag-minutes.html

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants