Re: See all SC and title attributes

> I would be in favor of making it an individual SC. 
> Any ideas on how best we could phrase it?
   
I don’t think we should try to ban title attributes per-se, but the scenarios we are trying to prevent are:
- Causing pop-overs that cover important information.
- Putting important information in title attributes that are not readable.

The second scenario is in common with screenreaders as well, which tend to ignore title attributes unless you fiddle with the settings.

As a starter for 10, how about:
Metadata in a webpage that is shown on mouse-over does not include information necessary to understanding the content or functionality.

It is hard to word without also affecting things like ARIA landmarks, and actual pop-over dialogues that are done properly.


> we may want to consider if we need the Seeing All Interface Elements SC. 
> Shawn or Wayne or others may have a different perspective, but for me 
> the latest sizing SCs seem to cover the other “without loss of content 
> or functionality” aspect.

Agree, that and the new text-sizing SC could be deprecated. 

I mean, don’t delete the pages because those pages have useful information and depending on how things go we might come back to them. (For example, if the Sizing ones get changed the “See all” one might become relevant again). However, I’d withdraw them from active work and not propose them to WCAG for now.

Is that something for the next meeting? 

Cheers,

-Alastair

Received on Friday, 7 October 2016 14:41:20 UTC