Re: Support as an SC prefix?

>All I’m suggesting (as per the commenter) is an indicator at the start of
some SCs, so linearize is currently:
>Linearization: A mechanism is available to view content as a single
column, except for parts of the content where the spatial layout is
essential to the function and understanding of the content.
>That would become:
>Support linearization: Content can be viewed as a single column, except
for parts of the content where the spatial layout is essential to the
function and understanding of the content.

I don't think you can add a word to the "handle" and then remove words from
the SC. That would change the meaning of the SC. The SC's need to be able
to stand on their own without the handle.

I think the question on the table is whether to have an easy identifier in
the handle. I think whether or not we remove "a mechanism is available" is
a different question. If we switch it for some manifestation of "support"
then we'd need that in the SC text itself also.

Support linearization: A mechanism is available to view content as a single
column, except for parts of the content where the spatial layout is
essential to the function and understanding of the content.

Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*

Tel:  613.235.4902

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd

GitHub <https://github.com/DavidMacDonald>

www.Can-Adapt.com <http://www.can-adapt.com/>



*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy
<http://www.davidmacd.com/disclaimer.html>

On Wed, Mar 8, 2017 at 1:27 PM, Work <james.nurthen@oracle.com> wrote:

>
> On Mar 8, 2017, 9:54 AM -0800, Alastair Campbell <acampbell@nomensa.com>,
> wrote:
>
> James wrote:
>
> > I have always read the WCAG2 “Mechanism is available” to mean that you
> must ensure that either the user agent the user can do it - or if that
> can’t be guaranteed (i.e. the user could be using a user agent which does
> not support it) then the content must provide that support itself.
>
>
>
> Indeed, so I think these new SCs are different, they are asking the author
> to do (or avoid) certain things so that the user-agent side can work. So:
>
> -       “Mechanism is available” means one or the other, the user-agent
> supports it (accessibility supported) or you provide something.
>
> -       “Support X” means enable the user-agent to work properly.
>
> I agree that it is different.
>
>
>
>
>
> > Pretty much every browser now supports muting an individual tab. Can we
> essentially assume this is now a pass a a browser supports this so it is
> now the user agent’s issue rather than the content’s problem?
>
>
>
> Just on that case (not the broader point), is there a keyboard method of
> muting a tab? I can’t find one for Chrome, only right-click on the tab seem
> to bring that up.
>
> Not as far as I’m aware. IMO this is a chrome bug. Firefox allows you to
> press CTRL+M when your focus is on the tab to do this though - so this is
> supported in at least one platform.
>
>
>
> So the broader point would be that I’m not convinced the user-agent aspect
> is accessibility supported for 1.4.2, so probably not, yet.
>
> I agree with you - but this is more than the level of support for some of
> these proposed success criteria so I wanted to be clear that we need a new
> term as the mechanism is available one is not appropriate.
>
>
>
> Cheers,
>
>
>
> -Alastair
>
>