General Notes (Feast+)

Answers to how and why certain elements are set up.

Jump to:

Contrast

We use a formula to determine the largest contrast between any given color - whether primary, accent or background - and white or black.

  • If white provides more of a contrast, it's used as the text and hyperlink color
  • If black provides more of a contrast, it's used as the text and hyperlink color

This uses the same formula as services like wave.webaim.org, which saves you from having to check it yourself.

In cases where your feature style (and Advanced Jump To) has a background that would not be accessibility compliant with your hyperlink color, we automatically override the hyperlink color with the appropriate white or black contrast (see above).

Table of Contents

The table of contents automatically has the background and accessibility-compliant foreground color applied to it.

Underlines are removed from the table of contents because the expected behavior is that the entire contents are clickable/links, which means that the text does not need to stand out from the rest.

Pagespeed

Pagespeed is a cumulative effect of many, many different things on your page. Any one individual issue isn't a problem, but compounding each one can lead to failing pagespeed scores and CWV (Core Web Vitals).

You may be barely passing CWV before setting up Feast+, and start to fail after implementing it. This is because the compounding affect of:

  • javascript
  • ads
  • DOM nodes
  • poor server speed
  • incorrect caching
  • user location
  • user device
  • image optimization

And on top of that, making your website more visually appealing with styling can push a page over the threshold from passing to failing. But the styling alone isn't the cause of the problem.

Very often you need to go and re-visit all of the issues listed above and tweak, optimize and remove things in order to once again pass CWV.