W3C

Site Navigation

Nearby

Results of Questionnaire Miscellaneous Issues for October 25, 2016

The results of this questionnaire are available to anybody.

This questionnaire was open from 2016-10-23 to 2017-01-31.

13 answers have been received.

Jump to results for question:

Issue 244
Issue 245

1. Issue 244

We have a comment and proposed response in Issue 244.

Please review the following, related to "Add H97 to 2.4.1 Bypass Blocks" on GitHub.

Summary

Choice	All responders
Choice	Results
Accept the response as proposed	4
Accept with the following changes	5
Do not accept for the following reasons.	2

(2 responses didn't contain an answer to this question)

Details

Responder	Issue 244
Michael Cooper	Accept with the following changes	Seems good in principle. Do we know the technique is in fact accessibility supported? If so, great, otherwise might need to go in the "come back to" pile.
Andrew Kirkpatrick	Accept the response as proposed	Accept pending the AT question Michael raises, but since this is already a 1.3.1 technique it should be. Some screen readers have a "next element" shortcut, which would be a form of support for this meeting 2.4.1. Not sure about for non-AT-using keyboard-only users.
Makoto Ueki	Accept with the following changes	If H97 become a sufficient technique, we should also have "Using the main element to indicate where the main content starts". Because Understanding doc reads "The intent of this Success Criterion is to allow people who navigate sequentially through content more direct access to the primary content of the Web page." in its "Intent of this Success Criterion" section.
Maureen Kraft
Katie Haritos-Shea	Accept with the following changes	Accept pending AT outcome
Jonathan Avila
David MacDonald	Do not accept for the following reasons.	Most users of AT don't want to skip TO the NAV they want to slip over it. We already have ARIA 11 which is to use Landmarks... I don't think this limited example of a landmark is going to add much... if anything we want to get DEV to use <main> ... they don't do that much but are almost always using <nav> these days. I'd reject the suggestion.
Marc Johlic	Accept the response as proposed
James Nurthen	Accept with the following changes	It should be advisory only due to accessibility support.
Michael Gower	Accept the response as proposed	I submitted, so happy to see it being accepted :)
Bruce Bailey	Do not accept for the following reasons.	I think David is correct that this does not add enough utility to warrant adding H97 as a sufficient technique to 2.4.1. AWK mentions screen readers have a "next element" shortcut, but if we allow that to be sufficient, then 2.4.1 is always met.
Laura Carlson	Accept with the following changes	It should be advisory.
Stephen Repsher	Accept the response as proposed

2. Issue 245

We have a comment and proposed response in Issue 245.

Please review the following, related to "Add code example to H49 technique" on GitHub.

Summary

Choice	All responders
Choice	Results
Accept the response as proposed	10
Accept with the following changes	1
Do not accept for the following reasons.

(2 responses didn't contain an answer to this question)

Details

Responder	Issue 245
Michael Cooper	Accept the response as proposed
Andrew Kirkpatrick	Accept with the following changes	pending clarification of this being to add example 5 or replace example 4
Makoto Ueki	Accept the response as proposed
Maureen Kraft
Katie Haritos-Shea	Accept the response as proposed
Jonathan Avila
David MacDonald	Accept the response as proposed
Marc Johlic	Accept the response as proposed	Got word from Mike Gower that this is indeed supposed to be a new Ex 5 - not a replacement for Ex 4
James Nurthen	Accept the response as proposed
Michael Gower	Accept the response as proposed	Again, my submission. I have lots more ready to submit, so glad such things are welcome :)
Bruce Bailey	Accept the response as proposed
Laura Carlson	Accept the response as proposed
Stephen Repsher	Accept the response as proposed