mandatory_avar_table

Ensure variable fonts include an avar table.

mandatory_avar_table

• Applies to: TTF
• Fontspector can hotfix?: no
• Fontspector can fix sources?: no

Rationale

Most variable fonts should include an avar table to correctly define axes progression rates.

For example, a weight axis from 0% to 100% doesn't map directly to 100 to 1000, because a 10% progression from 0% may be too much to define the 200, while 90% may be too little to define the 900.

If the progression rates of axes is linear, this check can be ignored. Fontmake will also skip adding an avar table if the progression rates are linear. However, it is still recommended that designers visually proof each instance is at the expected weight, width etc.

Proposal

• https://github.com/fonttools/fontbakery/issues/3100

Profiles

• universal (in section 'Universal Profile Checks')

• googlefonts (in section 'Universal Profile Checks')