Re: Font Family failure

On 14 Jan 2017, at 17:28, Steve Faulkner wrote:

> On 14 January 2017 at 16:23, Wayne Dick <wayneedick@gmail.com> wrote:
>
>> Jason, we probably need an ARIA role like "visual-style" to indicate 
>> that
>> a void element like <span> or <div> is just for presentation.
>
>
> we already have role=presentation or role=none
> https://www.w3.org/TR/wai-aria-1.1/#none

Just double checking… We don’t want to require authors to label 
every div and span with a role, right?

https://www.w3.org/TR/html/textlevel-semantics.html#the-span-element
https://www.w3.org/TR/html/grouping-content.html#the-div-element

They don’t have a default role set, so they are semantically neutral 
as far as ARIA is considered.

The thing with the user style is that it also needs to respect the 
cascade and that is a more complicated thing to do with more complex 
HTML structures.

With CSS Cascade 3 you should be able to do something like:

```
h1 {
   font-family: “Proxima Nova”;
   color: red;
}

h1 * {
   all: unset;
}
```

which basically uses all the default styling for elements inside the 
headings (<strong> is bold ect. – they would be red and in the 
specified font-family as those initial values are inherited from the 
h1).

Browser support: http://caniuse.com/#search=all

Eric

>
>
> --
>
> Regards
>
> SteveF
> Current Standards Work @W3C
> <http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>





--

Eric Eggert
Web Accessibility Specialist
Web Accessibility Initiative (WAI) at World Wide Web Consortium (W3C)