-
Notifications
You must be signed in to change notification settings - Fork 237
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
SCR19: This can cover onchange on checkbox / radio besides select controls #109
Comments
Adam, can you give us a rough ETA for a draft technique for this issue? Thanks |
if you want to add to the agenda for this week i can have it ready (the On Sat, Aug 29, 2015 at 11:11 AM, joshueoconnor notifications@github.com
|
Proposed response: Regarding your suggestion to associate this technique with criteria 2.4.3 and 1.3.2, we feel that the technique is not in fact relevant to those criteria. Despite the description mentioning an important note that dynamic content changes triggered by the onchange event must be updated after the trigger element, this is a side issue. The main issue of the technique is the absence of a change in context resulting from the onchange event. This technique could very well include scripting examples which do not update actual content in the DOM, and which would therefore not be relevant to the aforementioned criteria. |
Ready for survey https://www.w3.org/2002/09/wbs/35422/charter_policy_update_2015/ |
Hi Adam, can we add a link to the definition of change of context, http://www.w3.org/TR/2008/REC-WCAG20-20081211/#context-changedef. I would add a link to the first match in the technique text. Thanks, Moe |
[NEEDSINFO] |
Sailesh, the working group agree that "This technique is indeed applicable to change events in both radio buttons and check boxes. Therefore, we will amend the technique to include two more examples. In addition, the word select in the procedure will be replaced by "user interface component", and the language of the procedure will be amended to reflect general scripting chaneges resulting from the onchange event, as opposed to a specific use case. The description will mention these three types of components specifically. Regarding your suggestion to associate this technique with criteria 2.4.3 and 1.3.2, we feel that the technique is not in fact relevant to those criteria." Do you want to update the technique and submit it as a pull request? |
We had a request to add a change of context definition to SCR19. Its included here. [1] [1] #109
Sorry Maureen, I just saw your request now. It must have slipped through. On Tue, Sep 15, 2015 at 6:07 PM, Maureen (Moe) Kraft <
|
Josh / Adam, "It is important to note that the select item which is modified is after the trigger select element in the reading order of the Web page. This ensures that |
I still agree with the WG's previous decision that this is not about 2.4.3 or 1.3.2. I would agree that almost everything is about 1.3.2 and 2.4.3 when you look at an example, but the focus of the technique is not these SCs. I think that this technique was originally made because the select box with onChange was so commonly a problem. It is fine as it is, but it doesn't hurt to add the radio button situation as the procedure will be quite similar. Perhaps a separate technique is needed for the checkbox situation? |
Andrew, |
I am only clear on my desire to see that radio buttons and check boxes are included and that is very clear in the technique. |
I like the addition of radio buttons and checkboxes but do not support mapping to SC 1.3.2 and 2.4.3. |
Without new information we should regard assigning SCR19 to 1.3.2 and 2.4.3 as settled. The working group considered this question last year and decided that it did not agree. |
@adamsolomon This could be made more generic as it is applicable to radio boxes. |
@adamsolomon to create updated technique |
Preparing to mark as deferred due to inactivity and group resource constraints (https://www.w3.org/WAI/GL/wiki/Handling_Issues). |
On 4/12/16, Andrew Kirkpatrick notifications@github.com wrote:
|
my bad. as i recall we basically had a consensus (as i remember though we should check the survey) |
That would be great @adamsolomon - thanks. |
It appears the question of applying to other SCs is settled, there was just a task to update SCR19. However, there are higher-priority techniques to do, so unless someone volunteers to do this, we'll close the issue in a few days. |
SCR19 is limited to change of context caused by onchange on select controls.
In fact this technique can be enhanced to cover radio buttons and checkboxes that present conditional content based on onchange.
Also, should SC 2.4.3 and SC 1.3.2 be added as applicable SCs?
Thanks,
Sailesh
The text was updated successfully, but these errors were encountered: