- From: Gregg Vanderheiden <gregg@raisingthefloor.org>
- Date: Tue, 1 Dec 2015 13:40:34 -0600
- To: Mike Elledge <melledge@yahoo.com>
- Cc: GLWAI Guidelines WG org <w3c-wai-gl@w3.org>
- Message-Id: <862EAAFC-F7D2-4FFB-BB1B-DD0F8F0FECC3@raisingthefloor.org>
Hi If there is nothing on the page that is visible (or audio) to anyone — then there is no accessibility issue. If there is a message that appears during the forward - and this is not accessible to AT - then it is an accessibility issue and is covered under SC 1.1.1 ( PS Failures are "documented common failures of SC”. They don’t allow or forbid anything that is not allowed or forbidden by an SC. If something is not a failure of an SC, it can’t be documented as a failure. So failures cannot be used to extend or amend WCAG. Their purpose was just to make it clearer that some things were failures when they commonly occur - or when they are commonly misunderstood. ) > On Dec 1, 2015, at 12:36 PM, Mike Elledge <melledge@yahoo.com> wrote: > > Hi Everyone-- > > This is to seek your comments (toward consensus) for Issue #102 (https://github.com/w3c/wcag/issues/102). > > In summary, Issue #102 occurs when a browser prevents auto-redirection to a new page and doesn't provide an explanation, forwarding link or address to the user. > > Point of view #1: It is a usability issue, and not specific to persons with disabilities, since everyone will have the same negative experience. > > Point of view #2: It will affect PWD more significantly, so it is an accessibility issue. Mapping it to a guideline is a problem, however. Success criteria for the most relevant guideline (3.2--Predictable) are not relevant since receiving focus (SC 3.2.1) or changing a setting (SC 3.2.2) do not change context. A possibility is to add this as an Advisory Technique to 3.2 or make it a failure. > > Thoughts? Thanks! > > Mike
Received on Tuesday, 1 December 2015 19:41:06 UTC