Review Hub ← Back to hub Live site ↗

Provenance

Library standards referenced

Each improvement to the datascalehr homepage is grounded in a defined object in the standards library. Below is every object file referenced — 95 in total across 15 groups — with why it applied and its full text reproduced verbatim (expand to read). Paths are relative to library/standards/.

1 · Semantic Web & Structured Data — Schema.org · 9

standards/schema-org/types/Organization.md The @graph Organization node (name, url, logo, sameAs LinkedIn) identifying datascalehr as the publisher.
---
id: "schema:Organization"
label: Organization
kind: type
standard: schema-org
standard_title: Schema.org
standard_version: 30.0
source_url: "https://schema.org/Organization"
license: CC-BY-SA-3.0
domain: [1]
subClassOf: [Thing]
---

# Organization

> An organization such as a school, NGO, corporation, club, etc.

**Kind:** Type (`rdfs:Class`) · **Standard:** Schema.org · **Source:** https://schema.org/Organization

## Parent types
- [[Thing]]

## Direct subtypes
- [[Airline]]
- [[Consortium]]
- [[Cooperative]]
- [[Corporation]]
- [[EducationalOrganization]]
- [[FundingScheme]]
- [[GovernmentOrganization]]
- [[LibrarySystem]]
- [[LocalBusiness]]
- [[MedicalOrganization]]
- [[NGO]]
- [[NewsMediaOrganization]]
- [[OnlineBusiness]]
- [[PerformingGroup]]
- [[PoliticalParty]]
- [[Project]]
- [[ResearchOrganization]]
- [[SearchRescueOrganization]]
- [[SportsOrganization]]
- [[WorkersUnion]]

## Properties (domain includes this type)
- [[acceptedPaymentMethod]]
- [[actionableFeedbackPolicy]]
- [[address]]
- [[agentInteractionStatistic]]
- [[aggregateRating]]
- [[alumni]]
- [[areaServed]]
- [[award]]
- [[awards]]
- [[brand]]
- [[companyRegistration]]
- [[contactPoint]]
- [[contactPoints]]
- [[correctionsPolicy]]
- [[department]]
- [[dissolutionDate]]
- [[diversityPolicy]]
- [[diversityStaffingReport]]
- [[duns]]
- [[email]]
- [[employee]]
- [[employees]]
- [[ethicsPolicy]]
- [[event]]
- [[events]]
- [[faxNumber]]
- [[founder]]
- [[founders]]
- [[foundingDate]]
- [[foundingLocation]]
- [[funder]]
- [[funding]]
- [[globalLocationNumber]]
- [[hasCertification]]
- [[hasCredential]]
- [[hasGS1DigitalLink]]
- [[hasMemberProgram]]
- [[hasMerchantReturnPolicy]]
- [[hasOfferCatalog]]
- [[hasPOS]]
- [[hasShippingService]]
- [[interactionStatistic]]
- [[isicV4]]
- [[iso6523Code]]
- [[keywords]]
- [[knowsAbout]]
- [[knowsLanguage]]
- [[legalAddress]]
- [[legalName]]
- [[legalRepresentative]]
- [[leiCode]]
- [[location]]
- [[logo]]
- [[makesOffer]]
- [[member]]
- [[memberOf]]
- [[members]]
- [[naics]]
- [[nonprofitStatus]]
- [[numberOfEmployees]]
- [[ownershipFundingInfo]]
- [[owns]]
- [[parentOrganization]]
- [[publishingPrinciples]]
- [[review]]
- [[reviews]]
- [[seeks]]
- [[serviceArea]]
- [[skills]]
- [[slogan]]
- [[sponsor]]
- [[subOrganization]]
- [[taxID]]
- [[telephone]]
- [[unnamedSourcesPolicy]]
- [[vatID]]
standards/schema-org/types/WebSite.md The WebSite node tying the page to the site and its publisher.
---
id: "schema:WebSite"
label: WebSite
kind: type
standard: schema-org
standard_title: Schema.org
standard_version: 30.0
source_url: "https://schema.org/WebSite"
license: CC-BY-SA-3.0
domain: [1]
subClassOf: [CreativeWork]
---

# WebSite

> A WebSite is a set of related web pages and other items typically served from a single web domain and accessible via URLs.

**Kind:** Type (`rdfs:Class`) · **Standard:** Schema.org · **Source:** https://schema.org/WebSite

## Parent types
- [[CreativeWork]]

## Properties (domain includes this type)
- [[issn]]
standards/schema-org/types/WebPage.md The WebPage node describing the homepage and linking it to the software it is about.
---
id: "schema:WebPage"
label: WebPage
kind: type
standard: schema-org
standard_title: Schema.org
standard_version: 30.0
source_url: "https://schema.org/WebPage"
license: CC-BY-SA-3.0
domain: [1]
subClassOf: [CreativeWork]
---

# WebPage

> A web page. Every web page is implicitly assumed to be declared to be of type WebPage, so the various properties about that webpage, such as `breadcrumb` may be used. We recommend explicit declaration if these properties are specified, but if they are found outside of an itemscope, they will be assumed to be about the page.

**Kind:** Type (`rdfs:Class`) · **Standard:** Schema.org · **Source:** https://schema.org/WebPage

## Parent types
- [[CreativeWork]]

## Direct subtypes
- [[AboutPage]]
- [[CheckoutPage]]
- [[CollectionPage]]
- [[ContactPage]]
- [[FAQPage]]
- [[ItemPage]]
- [[MedicalWebPage]]
- [[ProfilePage]]
- [[QAPage]]
- [[RealEstateListing]]
- [[SearchResultsPage]]

## Properties (domain includes this type)
- [[breadcrumb]]
- [[lastReviewed]]
- [[mainContentOfPage]]
- [[primaryImageOfPage]]
- [[relatedLink]]
- [[reviewedBy]]
- [[significantLink]]
- [[significantLinks]]
- [[speakable]]
- [[specialty]]
standards/schema-org/types/SoftwareApplication.md Models the product (KMod) with applicationCategory BusinessApplication — the node carrying the rating and reviews.
---
id: "schema:SoftwareApplication"
label: SoftwareApplication
kind: type
standard: schema-org
standard_title: Schema.org
standard_version: 30.0
source_url: "https://schema.org/SoftwareApplication"
license: CC-BY-SA-3.0
domain: [1]
subClassOf: [CreativeWork]
---

# SoftwareApplication

> A software application.

**Kind:** Type (`rdfs:Class`) · **Standard:** Schema.org · **Source:** https://schema.org/SoftwareApplication

## Parent types
- [[CreativeWork]]

## Direct subtypes
- [[MobileApplication]]
- [[OperatingSystem]]
- [[RuntimePlatform]]
- [[VideoGame]]
- [[WebApplication]]

## Properties (domain includes this type)
- [[applicationCategory]]
- [[applicationSubCategory]]
- [[applicationSuite]]
- [[availableOnDevice]]
- [[countriesNotSupported]]
- [[countriesSupported]]
- [[device]]
- [[downloadUrl]]
- [[featureList]]
- [[fileSize]]
- [[installUrl]]
- [[memoryRequirements]]
- [[operatingSystem]]
- [[permissions]]
- [[processorRequirements]]
- [[releaseNotes]]
- [[requirements]]
- [[runtimePlatform]]
- [[screenshot]]
- [[softwareAddOn]]
- [[softwareHelp]]
- [[softwareRequirements]]
- [[softwareVersion]]
- [[storageRequirements]]
- [[supportingData]]
standards/schema-org/types/AggregateRating.md The 5/5 aggregate over the five customer reviews attached to the SoftwareApplication.
---
id: "schema:AggregateRating"
label: AggregateRating
kind: type
standard: schema-org
standard_title: Schema.org
standard_version: 30.0
source_url: "https://schema.org/AggregateRating"
license: CC-BY-SA-3.0
domain: [1]
subClassOf: [Rating]
---

# AggregateRating

> The average rating based on multiple ratings or reviews.

**Kind:** Type (`rdfs:Class`) · **Standard:** Schema.org · **Source:** https://schema.org/AggregateRating

## Parent types
- [[Rating]]

## Direct subtypes
- [[EmployerAggregateRating]]

## Properties (domain includes this type)
- [[itemReviewed]]
- [[ratingCount]]
- [[reviewCount]]
standards/schema-org/types/Review.md Each of the five testimonials became a Review with author + reviewRating instead of undifferentiated text.
---
id: "schema:Review"
label: Review
kind: type
standard: schema-org
standard_title: Schema.org
standard_version: 30.0
source_url: "https://schema.org/Review"
license: CC-BY-SA-3.0
domain: [1]
subClassOf: [CreativeWork]
---

# Review

> A review of an item - for example, of a restaurant, movie, or store.

**Kind:** Type (`rdfs:Class`) · **Standard:** Schema.org · **Source:** https://schema.org/Review

## Parent types
- [[CreativeWork]]

## Direct subtypes
- [[ClaimReview]]
- [[CriticReview]]
- [[EmployerReview]]
- [[MediaReview]]
- [[Recommendation]]
- [[UserReview]]

## Properties (domain includes this type)
- [[associatedClaimReview]]
- [[associatedMediaReview]]
- [[associatedReview]]
- [[itemReviewed]]
- [[negativeNotes]]
- [[positiveNotes]]
- [[reviewAspect]]
- [[reviewBody]]
- [[reviewRating]]
standards/schema-org/types/FAQPage.md The four solution tabs re-expressed as an FAQPage so search / AI answer engines can lift the Q&As.
---
id: "schema:FAQPage"
label: FAQPage
kind: type
standard: schema-org
standard_title: Schema.org
standard_version: 30.0
source_url: "https://schema.org/FAQPage"
license: CC-BY-SA-3.0
domain: [1]
subClassOf: [WebPage]
---

# FAQPage

> A [[FAQPage]] is a [[WebPage]] presenting one or more "[Frequently asked questions](https://en.wikipedia.org/wiki/FAQ)" (see also [[QAPage]]).

**Kind:** Type (`rdfs:Class`) · **Standard:** Schema.org · **Source:** https://schema.org/FAQPage

## Parent types
- [[WebPage]]
standards/schema-org/types/Question.md Each FAQ entry’s Question (the tab’s problem framing).
---
id: "schema:Question"
label: Question
kind: type
standard: schema-org
standard_title: Schema.org
standard_version: 30.0
source_url: "https://schema.org/Question"
license: CC-BY-SA-3.0
domain: [1]
subClassOf: [Comment]
---

# Question

> A specific question - e.g. from a user seeking answers online, or collected in a Frequently Asked Questions (FAQ) document.

**Kind:** Type (`rdfs:Class`) · **Standard:** Schema.org · **Source:** https://schema.org/Question

## Parent types
- [[Comment]]

## Properties (domain includes this type)
- [[acceptedAnswer]]
- [[answerCount]]
- [[eduQuestionType]]
- [[parentItem]]
- [[suggestedAnswer]]
standards/schema-org/types/Answer.md Each Question’s acceptedAnswer (datascalehr’s solution text).
---
id: "schema:Answer"
label: Answer
kind: type
standard: schema-org
standard_title: Schema.org
standard_version: 30.0
source_url: "https://schema.org/Answer"
license: CC-BY-SA-3.0
domain: [1]
subClassOf: [Comment]
---

# Answer

> An answer offered to a question; perhaps correct, perhaps opinionated or wrong.

**Kind:** Type (`rdfs:Class`) · **Standard:** Schema.org · **Source:** https://schema.org/Answer

## Parent types
- [[Comment]]

## Properties (domain includes this type)
- [[answerExplanation]]
- [[parentItem]]

2 · Web Platform — Semantic HTML (html-elements) · 7

standards/html-elements/elements/main.md The single <main> landmark wrapping the page’s primary content.
---
id: "element:main"
label: main
kind: element
standard: html-elements
standard_title: HTML / SVG / MathML elements
source_url: "https://html.spec.whatwg.org/multipage/grouping-content.html#the-main-element"
license: reference
domain: [2]
ingest: full
group: html
dom_interface: HTMLElement
---

# main

The `<main>` HTML element, defined in HTML Standard. DOM interface: `HTMLElement`.

**Kind:** Element · **Group:** html · **DOM interface:** `HTMLElement` · **Source:** https://html.spec.whatwg.org/multipage/grouping-content.html#the-main-element
standards/html-elements/elements/nav.md The <nav> landmark around primary navigation (was a generic Divi menu container).
---
id: "element:nav"
label: nav
kind: element
standard: html-elements
standard_title: HTML / SVG / MathML elements
source_url: "https://html.spec.whatwg.org/multipage/sections.html#the-nav-element"
license: reference
domain: [2]
ingest: full
group: html
dom_interface: HTMLElement
---

# nav

The `<nav>` HTML element, defined in HTML Standard. DOM interface: `HTMLElement`.

**Kind:** Element · **Group:** html · **DOM interface:** `HTMLElement` · **Source:** https://html.spec.whatwg.org/multipage/sections.html#the-nav-element
standards/html-elements/elements/section.md Each content block is a labelled <section> (aria-labelledby its heading).
---
id: "element:section"
label: section
kind: element
standard: html-elements
standard_title: HTML / SVG / MathML elements
source_url: "https://html.spec.whatwg.org/multipage/sections.html#the-section-element"
license: reference
domain: [2]
ingest: full
group: html
dom_interface: HTMLElement
---

# section

The `<section>` HTML element, defined in HTML Standard. DOM interface: `HTMLElement`.

**Kind:** Element · **Group:** html · **DOM interface:** `HTMLElement` · **Source:** https://html.spec.whatwg.org/multipage/sections.html#the-section-element
standards/html-elements/elements/blockquote.md Testimonials are real <blockquote>s rather than styled <div>s.
---
id: "element:blockquote"
label: blockquote
kind: element
standard: html-elements
standard_title: HTML / SVG / MathML elements
source_url: "https://html.spec.whatwg.org/multipage/grouping-content.html#the-blockquote-element"
license: reference
domain: [2]
ingest: full
group: html
dom_interface: HTMLQuoteElement
---

# blockquote

The `<blockquote>` HTML element, defined in HTML Standard. DOM interface: `HTMLQuoteElement`.

**Kind:** Element · **Group:** html · **DOM interface:** `HTMLQuoteElement` · **Source:** https://html.spec.whatwg.org/multipage/grouping-content.html#the-blockquote-element
standards/html-elements/elements/dl.md Stat pairs (number + label) use <dl>/<dt>/<dd> to bind value to meaning.
---
id: "element:dl"
label: dl
kind: element
standard: html-elements
standard_title: HTML / SVG / MathML elements
source_url: "https://html.spec.whatwg.org/multipage/grouping-content.html#the-dl-element"
license: reference
domain: [2]
ingest: full
group: html
dom_interface: HTMLDListElement
---

# dl

The `<dl>` HTML element, defined in HTML Standard. DOM interface: `HTMLDListElement`.

**Kind:** Element · **Group:** html · **DOM interface:** `HTMLDListElement` · **Source:** https://html.spec.whatwg.org/multipage/grouping-content.html#the-dl-element
standards/html-elements/elements/link.md The <link rel="canonical"> and font <link>s in the head.
---
id: "element:link"
label: link
kind: element
standard: html-elements
standard_title: HTML / SVG / MathML elements
source_url: "https://html.spec.whatwg.org/multipage/semantics.html#the-link-element"
license: reference
domain: [2]
ingest: full
group: html
dom_interface: HTMLLinkElement
---

# link

The `<link>` HTML element, defined in HTML Standard. DOM interface: `HTMLLinkElement`.

**Kind:** Element · **Group:** html · **DOM interface:** `HTMLLinkElement` · **Source:** https://html.spec.whatwg.org/multipage/semantics.html#the-link-element
standards/html-elements/elements/meta.md The <meta> description / OG / Twitter / viewport / robots tags.
---
id: "element:meta"
label: meta
kind: element
standard: html-elements
standard_title: HTML / SVG / MathML elements
source_url: "https://html.spec.whatwg.org/multipage/semantics.html#meta"
license: reference
domain: [2]
ingest: full
group: html
dom_interface: HTMLMetaElement
---

# meta

The `<meta>` HTML element, defined in HTML Standard. DOM interface: `HTMLMetaElement`.

**Kind:** Element · **Group:** html · **DOM interface:** `HTMLMetaElement` · **Source:** https://html.spec.whatwg.org/multipage/semantics.html#meta

2 · Web Platform — CSS & interoperable baseline · 9

standards/css/functions/clamp.md The fluid type scale and spacing use clamp() so sizes respond without breakpoints.
---
id: "css:clamp()"
label: clamp()
kind: function
standard: css
standard_title: CSS (mdn-data)
source_url: "https://developer.mozilla.org/docs/Web/CSS/clamp"
license: CC0-1.0
domain: [2]
ingest: full
css_status: standard
---

# clamp()

CSS function.

**Syntax:** `clamp( <calc-sum>#{3} )`

**Groups:** CSS Values and Units

**Kind:** Function · **Standard:** CSS (mdn-data) · **Status:** standard · **Source:** https://developer.mozilla.org/docs/Web/CSS/clamp
standards/css/selectors/focus-visible.md The :focus-visible selector powering keyboard-only focus rings.
---
id: "css::focus-visible"
label: ":focus-visible"
kind: selector
standard: css
standard_title: CSS (mdn-data)
source_url: "https://developer.mozilla.org/docs/Web/CSS/:focus-visible"
license: CC0-1.0
domain: [2]
ingest: full
css_status: standard
---

# :focus-visible

CSS selector.

**Syntax:** `:focus-visible`

**Groups:** Selectors

**Kind:** Selector · **Standard:** CSS (mdn-data) · **Status:** standard · **Source:** https://developer.mozilla.org/docs/Web/CSS/:focus-visible
standards/css/properties/backdrop-filter.md The translucent sticky header uses backdrop-filter.
---
id: "css:backdrop-filter"
label: backdrop-filter
kind: property
standard: css
standard_title: CSS (mdn-data)
source_url: "https://developer.mozilla.org/docs/Web/CSS/backdrop-filter"
license: CC0-1.0
domain: [2]
ingest: full
css_status: standard
---

# backdrop-filter

CSS property.

**Syntax:** `none | <filter-value-list>`

**Inherited:** no
**Initial:** `none`
**Percentages:** no
**Applies to:** allElementsSVGContainerElements
**Groups:** Filter Effects

**Kind:** Property · **Standard:** CSS (mdn-data) · **Status:** standard · **Source:** https://developer.mozilla.org/docs/Web/CSS/backdrop-filter
standards/baseline/features/prefers-reduced-motion.md Animations/scroll-behavior are disabled under prefers-reduced-motion.
---
id: "baseline:prefers-reduced-motion"
label: prefers-reduced-motion media query
kind: web-feature
standard: baseline
standard_title: Baseline (web-features)
source_url: "https://drafts.csswg.org/mediaqueries-5/#prefers-reduced-motion"
license: Apache-2.0
domain: [2]
ingest: full
baseline: high
group: ""
baseline_since: 2020-01-15
---

# prefers-reduced-motion media query

> The prefers-reduced-motion CSS media query sets styles based on whether the user prefers to minimize the amount of non-essential animations on the device, such as scrolling, panning, zooming, and strobing.

**Baseline:** Widely available (Baseline) · since 2020-01-15

**Kind:** Web feature · **Standard:** Baseline (web-features) · **Source:** https://drafts.csswg.org/mediaqueries-5/#prefers-reduced-motion

## Browser support (min version)
| Browser | Since |
|---|---|
| Chrome | 74 |
| Edge | 79 |
| Firefox | 63 |
| Safari | 10.1 |

## Links
- [Can I Use](https://caniuse.com/prefers-reduced-motion)
- [Specification](https://drafts.csswg.org/mediaqueries-5/#prefers-reduced-motion)
- [Web Platform Status](https://webstatus.dev/features/prefers-reduced-motion)
standards/baseline/features/prefers-color-scheme.md The dark theme is delivered via prefers-color-scheme (the original was light-only).
---
id: "baseline:prefers-color-scheme"
label: prefers-color-scheme media query
kind: web-feature
standard: baseline
standard_title: Baseline (web-features)
source_url: "https://drafts.csswg.org/mediaqueries-5/#prefers-color-scheme"
license: Apache-2.0
domain: [2]
ingest: full
baseline: high
group: ""
baseline_since: 2020-01-15
---

# prefers-color-scheme media query

> The prefers-color-scheme CSS media query sets styles based on the requested color scheme, light or dark.

**Baseline:** Widely available (Baseline) · since 2020-01-15

**Kind:** Web feature · **Standard:** Baseline (web-features) · **Source:** https://drafts.csswg.org/mediaqueries-5/#prefers-color-scheme

## Browser support (min version)
| Browser | Since |
|---|---|
| Chrome | 76 |
| Edge | 79 |
| Firefox | 67 |
| Safari | 12.1 |

## Links
- [Specification](https://drafts.csswg.org/mediaqueries-5/#prefers-color-scheme)
- [Web Platform Status](https://webstatus.dev/features/prefers-color-scheme)
standards/baseline/features/font-display.md The webfont loads with font-display:swap to avoid invisible text.
---
id: "baseline:font-display"
label: font-display
kind: web-feature
standard: baseline
standard_title: Baseline (web-features)
source_url: "https://drafts.csswg.org/css-fonts-4/#font-display-desc"
license: Apache-2.0
domain: [2]
ingest: full
baseline: high
group: ""
baseline_since: 2020-01-15
---

# font-display

> The font-display CSS descriptor sets whether to show a substitute font or nothing while a font face loads. The property manages what's known as a flash of unstyled text or flash of invisible text.

**Baseline:** Widely available (Baseline) · since 2020-01-15

**Kind:** Web feature · **Standard:** Baseline (web-features) · **Source:** https://drafts.csswg.org/css-fonts-4/#font-display-desc

## Browser support (min version)
| Browser | Since |
|---|---|
| Chrome | 60 |
| Edge | 79 |
| Firefox | 58 |
| Safari | 11.1 |

## Links
- [Can I Use](https://caniuse.com/css-font-rendering-controls)
- [Specification](https://drafts.csswg.org/css-fonts-4/#font-display-desc)
- [Web Platform Status](https://webstatus.dev/features/font-display)
standards/baseline/features/loading-lazy-media.md Below-the-fold media / iframes use loading="lazy".
---
id: "baseline:loading-lazy-media"
label: Lazy-loading media
kind: web-feature
standard: baseline
standard_title: Baseline (web-features)
source_url: "https://github.com/whatwg/html/pull/11980"
license: Apache-2.0
domain: [2]
ingest: full
baseline: False
group: ""
---

# Lazy-loading media

> The loading="lazy" attribute for  and  elements defers loading the media resource until the element is near the viewport. This matches the lazy-loading behavior for  and  elements.

**Baseline:** Limited availability

**Kind:** Web feature · **Standard:** Baseline (web-features) · **Source:** https://github.com/whatwg/html/pull/11980

## Browser support (min version)
| Browser | Since |
|---|---|
| Chrome | 150 |
| Edge | 150 |

## Links
- [Can I Use](https://caniuse.com/loading-lazy-media)
- [Specification](https://github.com/whatwg/html/pull/11980)
- [Web Platform Status](https://webstatus.dev/features/loading-lazy-media)
standards/baseline/features/meta-theme-color.md Theme-aware <meta name="theme-color"> for light and dark.
---
id: "baseline:meta-theme-color"
label: "<meta name=\"theme-color\">"
kind: web-feature
standard: baseline
standard_title: Baseline (web-features)
source_url: "https://html.spec.whatwg.org/multipage/semantics.html#meta-theme-color"
license: Apache-2.0
domain: [2]
ingest: full
baseline: False
group: ""
---

# <meta name="theme-color">

> The name="theme-color" attribute for the  HTML element suggests a color that the browser can use to customize the display of the page or the browser user interface.

**Baseline:** Limited availability

**Kind:** Web feature · **Standard:** Baseline (web-features) · **Source:** https://html.spec.whatwg.org/multipage/semantics.html#meta-theme-color

## Browser support (min version)
| Browser | Since |
|---|---|
| Safari | 15 |

## Links
- [Can I Use](https://caniuse.com/meta-theme-color)
- [Specification](https://html.spec.whatwg.org/multipage/semantics.html#meta-theme-color)
- [Web Platform Status](https://webstatus.dev/features/meta-theme-color)
standards/css/properties/color-scheme.md The color-scheme: light dark declaration so native controls (range sliders, checkboxes) and scrollbars render correctly in the dark theme — an improvement over the light-only live site.
---
id: "css:color-scheme"
label: color-scheme
kind: property
standard: css
standard_title: CSS (mdn-data)
source_url: "https://developer.mozilla.org/docs/Web/CSS/color-scheme"
license: CC0-1.0
domain: [2]
ingest: full
css_status: standard
---

# color-scheme

CSS property.

**Syntax:** `normal | [ light | dark | <custom-ident> ]+ && only?`

**Inherited:** yes
**Initial:** `normal`
**Percentages:** no
**Applies to:** allElementsAndText
**Groups:** CSS Color

**Kind:** Property · **Standard:** CSS (mdn-data) · **Status:** standard · **Source:** https://developer.mozilla.org/docs/Web/CSS/color-scheme

3 · Accessibility — WCAG 2.2 success criteria · 13

standards/wcag-2.2/success-criteria/3.1.1-language-of-page.md Backs the valid, programmatically-determinable lang="en" on <html>.
---
id: "wcag:3.1.1"
label: 3.1.1 Language of Page
kind: success-criterion
standard: wcag-2.2
standard_title: WCAG 2.2
source_url: "https://www.w3.org/TR/WCAG22/#language-of-page"
license: W3C-Document
domain: [3]
ingest: full
number: 3.1.1
level: A
principle: Understandable
guideline: Readable
---

# 3.1.1 Language of Page

**Level A**

> The default human language of each web page can be programmatically determined.

**Kind:** Success Criterion · **Standard:** WCAG 2.2 · **Level:** A · **Source:** https://www.w3.org/TR/WCAG22/#language-of-page

## Context
- Principle: [[3-understandable|Understandable]]
- Guideline: [[3.1-readable|Readable]]
standards/wcag-2.2/success-criteria/1.3.1-info-and-relationships.md Core fix for the broken heading structure: single H1, ordered H2/H3, landmarks, blockquote, dl.
---
id: "wcag:1.3.1"
label: 1.3.1 Info and Relationships
kind: success-criterion
standard: wcag-2.2
standard_title: WCAG 2.2
source_url: "https://www.w3.org/TR/WCAG22/#info-and-relationships"
license: W3C-Document
domain: [3]
ingest: full
number: 1.3.1
level: A
principle: Perceivable
guideline: Adaptable
---

# 1.3.1 Info and Relationships

**Level A**

> Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

**Kind:** Success Criterion · **Standard:** WCAG 2.2 · **Level:** A · **Source:** https://www.w3.org/TR/WCAG22/#info-and-relationships

## Context
- Principle: [[1-perceivable|Perceivable]]
- Guideline: [[1.3-adaptable|Adaptable]]
standards/wcag-2.2/success-criteria/2.4.10-section-headings.md Every section is introduced by a real heading, so the page is navigable by heading.
---
id: "wcag:2.4.10"
label: 2.4.10 Section Headings
kind: success-criterion
standard: wcag-2.2
standard_title: WCAG 2.2
source_url: "https://www.w3.org/TR/WCAG22/#section-headings"
license: W3C-Document
domain: [3]
ingest: full
number: 2.4.10
level: AAA
principle: Operable
guideline: Navigable
---

# 2.4.10 Section Headings

**Level AAA**

> Section headings are used to organize the content.

   "Heading" is used in its general sense and includes titles and other ways to add a
      heading to different types of content.

   This success criterion covers sections within writing, not user interface components. User interface components are covered under [Success Criterion 4.1.2](#name-role-value).

**Kind:** Success Criterion · **Standard:** WCAG 2.2 · **Level:** AAA · **Source:** https://www.w3.org/TR/WCAG22/#section-headings

## Context
- Principle: [[2-operable|Operable]]
- Guideline: [[2.4-navigable|Navigable]]
standards/wcag-2.2/success-criteria/1.1.1-non-text-content.md Backs alt/aria on logo, icons and marks — verified 0 images missing alt.
---
id: "wcag:1.1.1"
label: 1.1.1 Non-text Content
kind: success-criterion
standard: wcag-2.2
standard_title: WCAG 2.2
source_url: "https://www.w3.org/TR/WCAG22/#non-text-content"
license: W3C-Document
domain: [3]
ingest: full
number: 1.1.1
level: A
principle: Perceivable
guideline: Text Alternatives
---

# 1.1.1 Non-text Content

**Level A**

> All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below.

      Controls, Input

If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to [Success Criterion 4.1.2](#name-role-value) for additional requirements for controls and content that accepts user input.)

      Time-Based Media

If non-text content is time-based media, then text alternatives at least provide descriptive
            identification of the non-text content. (Refer to [Guideline 1.2](#time-based-media) for additional requirements for media.)

      Test

If non-text content is a test or exercise that would be invalid if presented in text, then text alternatives at least provide descriptive identification of the non-text
            content.

      Sensory

If non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text
            content.

      CAPTCHA

If the purpose of non-text content is to confirm that content is being accessed by
            a person rather than a computer, then text alternatives that identify and describe
            the purpose of the non-text content are provided, and alternative forms of CAPTCHA
            using output modes for different types of sensory perception are provided to accommodate
            different disabilities.

      Decoration, Formatting, Invisible

If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented
            in a way that it can be ignored by assistive technology.

**Kind:** Success Criterion · **Standard:** WCAG 2.2 · **Level:** A · **Source:** https://www.w3.org/TR/WCAG22/#non-text-content

## Context
- Principle: [[1-perceivable|Perceivable]]
- Guideline: [[1.1-text-alternatives|Text Alternatives]]
standards/wcag-2.2/success-criteria/1.4.3-contrast-minimum.md Reason the accent was darkened to --brand-ink for text/links on white.
---
id: "wcag:1.4.3"
label: 1.4.3 Contrast (Minimum)
kind: success-criterion
standard: wcag-2.2
standard_title: WCAG 2.2
source_url: "https://www.w3.org/TR/WCAG22/#contrast-minimum"
license: W3C-Document
domain: [3]
ingest: full
number: 1.4.3
level: AA
principle: Perceivable
guideline: Distinguishable
---

# 1.4.3 Contrast (Minimum)

**Level AA**

> The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following:

      Large Text

Large-scale text and images of large-scale text have a contrast ratio of at least 3:1;

      Incidental

Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant
            other visual content, have no contrast requirement.

      Logotypes

Text that is part of a logo or brand name has no contrast requirement.

**Kind:** Success Criterion · **Standard:** WCAG 2.2 · **Level:** AA · **Source:** https://www.w3.org/TR/WCAG22/#contrast-minimum

## Context
- Principle: [[1-perceivable|Perceivable]]
- Guideline: [[1.4-distinguishable|Distinguishable]]
standards/wcag-2.2/success-criteria/2.4.1-bypass-blocks.md Backs the “Skip to main content” link past the sticky header and nav.
---
id: "wcag:2.4.1"
label: 2.4.1 Bypass Blocks
kind: success-criterion
standard: wcag-2.2
standard_title: WCAG 2.2
source_url: "https://www.w3.org/TR/WCAG22/#bypass-blocks"
license: W3C-Document
domain: [3]
ingest: full
number: 2.4.1
level: A
principle: Operable
guideline: Navigable
---

# 2.4.1 Bypass Blocks

**Level A**

> A mechanism is available to bypass blocks of content that are repeated on multiple web pages.

**Kind:** Success Criterion · **Standard:** WCAG 2.2 · **Level:** A · **Source:** https://www.w3.org/TR/WCAG22/#bypass-blocks

## Context
- Principle: [[2-operable|Operable]]
- Guideline: [[2.4-navigable|Navigable]]
standards/wcag-2.2/success-criteria/2.4.7-focus-visible.md Backs the visible focus ring on every interactive control.
---
id: "wcag:2.4.7"
label: 2.4.7 Focus Visible
kind: success-criterion
standard: wcag-2.2
standard_title: WCAG 2.2
source_url: "https://www.w3.org/TR/WCAG22/#focus-visible"
license: W3C-Document
domain: [3]
ingest: full
number: 2.4.7
level: AA
principle: Operable
guideline: Navigable
---

# 2.4.7 Focus Visible

**Level AA**

> Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.

**Kind:** Success Criterion · **Standard:** WCAG 2.2 · **Level:** AA · **Source:** https://www.w3.org/TR/WCAG22/#focus-visible

## Context
- Principle: [[2-operable|Operable]]
- Guideline: [[2.4-navigable|Navigable]]
standards/wcag-2.2/success-criteria/2.4.11-focus-not-obscured-minimum.md Scroll offsets keep a focused target from hiding behind the sticky header.
---
id: "wcag:2.4.11"
label: 2.4.11 Focus Not Obscured (Minimum)
kind: success-criterion
standard: wcag-2.2
standard_title: WCAG 2.2
source_url: "https://www.w3.org/TR/WCAG22/#focus-not-obscured-minimum"
license: W3C-Document
domain: [3]
ingest: full
number: 2.4.11
level: AA
principle: Operable
guideline: Navigable
change_2.2: New
---

# 2.4.11 Focus Not Obscured (Minimum)

**Level AA** · _New in WCAG 2.2_

> When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.

    Where content in a configurable interface can be repositioned by the user, then only the initial positions of user-movable content are considered for testing and conformance of this success criterion.

    Content opened by the *user* may obscure the component receiving focus. If the user can reveal the focused component without advancing the keyboard focus, the component with focus is not considered visually hidden due to author-created content.

**Kind:** Success Criterion · **Standard:** WCAG 2.2 · **Level:** AA · **Source:** https://www.w3.org/TR/WCAG22/#focus-not-obscured-minimum

## Context
- Principle: [[2-operable|Operable]]
- Guideline: [[2.4-navigable|Navigable]]
standards/wcag-2.2/success-criteria/2.4.13-focus-appearance.md Drives focus-ring thickness (3px) and contrast so the state is perceivable.
---
id: "wcag:2.4.13"
label: 2.4.13 Focus Appearance
kind: success-criterion
standard: wcag-2.2
standard_title: WCAG 2.2
source_url: "https://www.w3.org/TR/WCAG22/#focus-appearance"
license: W3C-Document
domain: [3]
ingest: full
number: 2.4.13
level: AAA
principle: Operable
guideline: Navigable
change_2.2: New
---

# 2.4.13 Focus Appearance

**Level AAA** · _New in WCAG 2.2_

> When the keyboard focus indicator is visible, an area of the focus indicator meets all the following:

        is at least as large as the area of a 2 CSS pixel thick perimeter of the unfocused component or sub-component, and
        has a contrast ratio of at least 3:1 between the same pixels in the focused and unfocused states.

Exceptions:

        The focus indicator is determined by the user agent and cannot be adjusted by the author, or
        The focus indicator and the indicator's background color are not modified by the author.

    What is perceived as the user interface component or sub-component (to determine the perimeter) depends on its visual presentation. The visual presentation includes the component's visible content, border, and component-specific background. It does not include shadow and glow effects outside the component's content, background, or border.

    Examples of sub-components that may receive a focus indicator are menu items in an opened drop-down menu, or focusable cells in a grid.

    Contrast calculations can be based on colors defined within the technology (such as HTML, CSS, and SVG). Pixels modified by user agent resolution enhancements and anti-aliasing can be ignored.

**Kind:** Success Criterion · **Standard:** WCAG 2.2 · **Level:** AAA · **Source:** https://www.w3.org/TR/WCAG22/#focus-appearance

## Context
- Principle: [[2-operable|Operable]]
- Guideline: [[2.4-navigable|Navigable]]
standards/wcag-2.2/success-criteria/2.5.8-target-size-minimum.md New in 2.2: controls are ≥44px; icon buttons meet the 24px minimum.
---
id: "wcag:2.5.8"
label: 2.5.8 Target Size (Minimum)
kind: success-criterion
standard: wcag-2.2
standard_title: WCAG 2.2
source_url: "https://www.w3.org/TR/WCAG22/#target-size-minimum"
license: W3C-Document
domain: [3]
ingest: full
number: 2.5.8
level: AA
principle: Operable
guideline: Input Modalities
change_2.2: New
---

# 2.5.8 Target Size (Minimum)

**Level AA** · _New in WCAG 2.2_

> The size of the target for pointer inputs is at least 24 by 24 CSS pixels, except when:

        Spacing
        Undersized targets (those less than 24 by 24 CSS pixels) are positioned so that if a 24 CSS pixel diameter circle is centered on the bounding box of each, the circles do not intersect another target or the circle for another undersized target;
        Equivalent
        The function can be achieved through a different control on the same page that meets this criterion;
        Inline
        The target is in a sentence or its size is otherwise constrained by the line-height of non-target text;
        User Agent Control
        The size of the target is determined by the user agent and is not modified by the author;
        Essential
        A particular presentation of the target is essential or is legally required for the information being conveyed.

    Targets that allow for values to be selected spatially based on position within the target are considered one target for the purpose of the success criterion. Examples include sliders, color pickers displaying a gradient of colors, or editable areas where you position the cursor.

    For inline targets the line-height should be interpreted as perpendicular to the flow of text. For example, in a language displayed vertically, the line-height would be horizontal.

**Kind:** Success Criterion · **Standard:** WCAG 2.2 · **Level:** AA · **Source:** https://www.w3.org/TR/WCAG22/#target-size-minimum

## Context
- Principle: [[2-operable|Operable]]
- Guideline: [[2.5-input-modalities|Input Modalities]]
standards/wcag-2.2/success-criteria/1.4.4-resize-text.md The viewport allows zoom; text resizes to 200%.
---
id: "wcag:1.4.4"
label: 1.4.4 Resize Text
kind: success-criterion
standard: wcag-2.2
standard_title: WCAG 2.2
source_url: "https://www.w3.org/TR/WCAG22/#resize-text"
license: W3C-Document
domain: [3]
ingest: full
number: 1.4.4
level: AA
principle: Perceivable
guideline: Distinguishable
---

# 1.4.4 Resize Text

**Level AA**

> Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.

**Kind:** Success Criterion · **Standard:** WCAG 2.2 · **Level:** AA · **Source:** https://www.w3.org/TR/WCAG22/#resize-text

## Context
- Principle: [[1-perceivable|Perceivable]]
- Guideline: [[1.4-distinguishable|Distinguishable]]
standards/wcag-2.2/success-criteria/1.4.10-reflow.md The layout reflows to one column with no horizontal scroll down to 320px.
---
id: "wcag:1.4.10"
label: 1.4.10 Reflow
kind: success-criterion
standard: wcag-2.2
standard_title: WCAG 2.2
source_url: "https://www.w3.org/TR/WCAG22/#reflow"
license: W3C-Document
domain: [3]
ingest: full
number: 1.4.10
level: AA
principle: Perceivable
guideline: Distinguishable
---

# 1.4.10 Reflow

**Level AA**

> Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for:

       Vertical scrolling content at a width equivalent to 320 CSS pixels;
       Horizontal scrolling content at a height equivalent to 256 CSS pixels.

Except for parts of the content which require two-dimensional layout for usage or meaning.

  320 CSS pixels is equivalent to a starting viewport width of 1280 CSS pixels wide at 400% zoom. For web content which is designed to scroll horizontally (e.g., with vertical text), 256 CSS pixels is equivalent to a starting viewport height of 1024 CSS pixels at 400% zoom.

   Examples of content which requires two-dimensional layout are images required for understanding (such as maps and diagrams), video, games, presentations, data tables (not individual cells), and interfaces where it is necessary to keep toolbars in view while manipulating content. It is acceptable to provide two-dimensional scrolling for such parts of the content.

**Kind:** Success Criterion · **Standard:** WCAG 2.2 · **Level:** AA · **Source:** https://www.w3.org/TR/WCAG22/#reflow

## Context
- Principle: [[1-perceivable|Perceivable]]
- Guideline: [[1.4-distinguishable|Distinguishable]]
standards/wcag-2.2/success-criteria/4.1.2-name-role-value.md Backs the ARIA on the tabs and aria-label’d icon buttons — correct name/role/state.
---
id: "wcag:4.1.2"
label: "4.1.2 Name, Role, Value"
kind: success-criterion
standard: wcag-2.2
standard_title: WCAG 2.2
source_url: "https://www.w3.org/TR/WCAG22/#name-role-value"
license: W3C-Document
domain: [3]
ingest: full
number: 4.1.2
level: A
principle: Robust
guideline: Compatible
---

# 4.1.2 Name, Role, Value

**Level A**

> For all user interface components (including but not limited to: form elements, links and components generated by scripts),
     the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.

   This success criterion is primarily for web authors who develop or script their own
      user interface components. For example, standard HTML controls already meet this success
      criterion when used according to specification.

**Kind:** Success Criterion · **Standard:** WCAG 2.2 · **Level:** A · **Source:** https://www.w3.org/TR/WCAG22/#name-role-value

## Context
- Principle: [[4-robust|Robust]]
- Guideline: [[4.1-compatible|Compatible]]

3 · Accessibility — WAI-ARIA (roles & APG pattern) · 5

standards/aria-apg/patterns/Tabs.md The exact pattern the “Problems we solve” tabs implement: roles + arrow/Home/End keys.
---
id: "aria-apg:tabs"
label: Tabs
kind: pattern
standard: aria-apg
standard_title: ARIA Authoring Practices Guide (APG)
source_url: "https://www.w3.org/WAI/ARIA/apg/patterns/tabs/"
license: W3C-Document
domain: [3]
ingest: reference
---

# Tabs

Tabs organize content into layered panels where only one panel is shown at a time, selected by a row of tab controls. A role=tablist contains role=tab elements whose aria-selected and aria-controls tie each tab to its role=tabpanel, and a roving tabindex keeps only the active tab tabbable. Left/Right or Up/Down arrows move between tabs, Home and End jump to the first and last tab, and activation can follow focus automatically or wait for Enter or Space.

**Kind:** Pattern · **Standard:** ARIA Authoring Practices Guide (APG) · **Source:** https://www.w3.org/WAI/ARIA/apg/patterns/tabs/
standards/wai-aria/roles/banner.md The header maps to the banner landmark role.
---
id: "aria:banner"
label: banner
kind: role
standard: wai-aria
standard_title: WAI-ARIA 1.2
source_url: "https://www.w3.org/TR/wai-aria-1.2/#banner"
license: W3C-Document
domain: [3]
ingest: full
abstract: false
---

# banner

WAI-ARIA role.

**Kind:** Role · **Standard:** WAI-ARIA 1.2 · **Source:** https://www.w3.org/TR/wai-aria-1.2/#banner

## Inherits from
- [[landmark]]

## Supported states & properties
- [[aria-atomic]]
- [[aria-busy]]
- [[aria-controls]]
- [[aria-current]]
- [[aria-describedby]]
- [[aria-details]]
- [[aria-dropeffect]]
- [[aria-flowto]]
- [[aria-grabbed]]
- [[aria-hidden]]
- [[aria-keyshortcuts]]
- [[aria-label]]
- [[aria-labelledby]]
- [[aria-live]]
- [[aria-owns]]
- [[aria-relevant]]
- [[aria-roledescription]]

## Name from
- author
standards/wai-aria/roles/navigation.md The nav maps to the navigation landmark role.
---
id: "aria:navigation"
label: navigation
kind: role
standard: wai-aria
standard_title: WAI-ARIA 1.2
source_url: "https://www.w3.org/TR/wai-aria-1.2/#navigation"
license: W3C-Document
domain: [3]
ingest: full
abstract: false
---

# navigation

WAI-ARIA role.

**Kind:** Role · **Standard:** WAI-ARIA 1.2 · **Source:** https://www.w3.org/TR/wai-aria-1.2/#navigation

## Inherits from
- [[landmark]]

## Supported states & properties
- [[aria-atomic]]
- [[aria-busy]]
- [[aria-controls]]
- [[aria-current]]
- [[aria-describedby]]
- [[aria-details]]
- [[aria-dropeffect]]
- [[aria-flowto]]
- [[aria-grabbed]]
- [[aria-hidden]]
- [[aria-keyshortcuts]]
- [[aria-label]]
- [[aria-labelledby]]
- [[aria-live]]
- [[aria-owns]]
- [[aria-relevant]]
- [[aria-roledescription]]

## Name from
- author
standards/wai-aria/roles/contentinfo.md The footer maps to the contentinfo landmark role.
---
id: "aria:contentinfo"
label: contentinfo
kind: role
standard: wai-aria
standard_title: WAI-ARIA 1.2
source_url: "https://www.w3.org/TR/wai-aria-1.2/#contentinfo"
license: W3C-Document
domain: [3]
ingest: full
abstract: false
---

# contentinfo

WAI-ARIA role.

**Kind:** Role · **Standard:** WAI-ARIA 1.2 · **Source:** https://www.w3.org/TR/wai-aria-1.2/#contentinfo

## Inherits from
- [[landmark]]

## Supported states & properties
- [[aria-atomic]]
- [[aria-busy]]
- [[aria-controls]]
- [[aria-current]]
- [[aria-describedby]]
- [[aria-details]]
- [[aria-dropeffect]]
- [[aria-flowto]]
- [[aria-grabbed]]
- [[aria-hidden]]
- [[aria-keyshortcuts]]
- [[aria-label]]
- [[aria-labelledby]]
- [[aria-live]]
- [[aria-owns]]
- [[aria-relevant]]
- [[aria-roledescription]]

## Name from
- author
standards/wai-aria/roles/tablist.md The role behind the tab strip (with tab/tabpanel) implementing the pattern above.
---
id: "aria:tablist"
label: tablist
kind: role
standard: wai-aria
standard_title: WAI-ARIA 1.2
source_url: "https://www.w3.org/TR/wai-aria-1.2/#tablist"
license: W3C-Document
domain: [3]
ingest: full
abstract: false
---

# tablist

WAI-ARIA role.

**Kind:** Role · **Standard:** WAI-ARIA 1.2 · **Source:** https://www.w3.org/TR/wai-aria-1.2/#tablist

## Inherits from
- [[composite]]

## Supported states & properties
- [[aria-activedescendant]]
- [[aria-atomic]]
- [[aria-busy]]
- [[aria-controls]]
- [[aria-current]]
- [[aria-describedby]]
- [[aria-details]]
- [[aria-disabled]]
- [[aria-dropeffect]]
- [[aria-flowto]]
- [[aria-grabbed]]
- [[aria-hidden]]
- [[aria-keyshortcuts]]
- [[aria-label]]
- [[aria-labelledby]]
- [[aria-level]]
- [[aria-live]]
- [[aria-multiselectable]]
- [[aria-orientation]]
- [[aria-owns]]
- [[aria-relevant]]
- [[aria-roledescription]]

## Name from
- author

4 · Performance — Core Web Vitals · 3

standards/core-web-vitals/metrics/Largest-Contentful-Paint-LCP.md Why fonts use preconnect + swap and the hero is text/CSS — LCP paints without a blocking round-trip.
---
id: "core-web-vitals:lcp"
label: Largest Contentful Paint (LCP)
kind: metric
standard: core-web-vitals
standard_title: "Core Web Vitals & Web Vitals metrics"
source_url: "https://web.dev/articles/lcp"
license: reference
domain: [4]
ingest: reference
---

# Largest Contentful Paint (LCP)

LCP records how long it takes for the single largest image or text block in the viewport to render, marking the point at which the main content has visibly loaded. It is the Core Web Vital for perceived loading speed. Slow LCP usually traces back to server response time, render-blocking resources, or heavy hero assets.

**Kind:** Metric · **Standard:** Core Web Vitals & Web Vitals metrics · **Source:** https://web.dev/articles/lcp

- **good:** <2.5s
- **needs_improvement:** 2.5s-4.0s
- **poor:** >4.0s
- **measures:** loading performance
- **type:** core

## Related
- [[Time-to-First-Byte-TTFB|Time to First Byte (TTFB)]]
- [[First-Contentful-Paint-FCP|First Contentful Paint (FCP)]]
standards/core-web-vitals/metrics/Cumulative-Layout-Shift-CLS.md Why layout reserves space (font fallback, sized media, no late banners) to avoid shifting.
---
id: "core-web-vitals:cls"
label: Cumulative Layout Shift (CLS)
kind: metric
standard: core-web-vitals
standard_title: "Core Web Vitals & Web Vitals metrics"
source_url: "https://web.dev/articles/cls"
license: reference
domain: [4]
ingest: reference
---

# Cumulative Layout Shift (CLS)

CLS sums the unexpected movement of visible elements during the page's lifespan, scoring how often content jumps as fonts, images, or ads load in. It is the Core Web Vital for visual stability and is a unitless score rather than a time. Reserving space for media and embeds is the most common way to keep it low.

**Kind:** Metric · **Standard:** Core Web Vitals & Web Vitals metrics · **Source:** https://web.dev/articles/cls

- **good:** <0.1
- **needs_improvement:** 0.1-0.25
- **poor:** >0.25
- **measures:** visual stability
- **type:** core

## Related
- [[Largest-Contentful-Paint-LCP|Largest Contentful Paint (LCP)]]
standards/core-web-vitals/metrics/First-Contentful-Paint-FCP.md Why CSS is inlined and JS minimal/deferred — nothing render-blocking delays first paint.
---
id: "core-web-vitals:fcp"
label: First Contentful Paint (FCP)
kind: metric
standard: core-web-vitals
standard_title: "Core Web Vitals & Web Vitals metrics"
source_url: "https://web.dev/articles/fcp"
license: reference
domain: [4]
ingest: reference
---

# First Contentful Paint (FCP)

FCP captures the moment the browser paints the first piece of DOM content, giving the user their first signal that the page is actually loading. It is a supporting diagnostic metric rather than a Core Web Vital and helps explain slow LCP. Render-blocking CSS and JavaScript are its typical bottlenecks.

**Kind:** Metric · **Standard:** Core Web Vitals & Web Vitals metrics · **Source:** https://web.dev/articles/fcp

- **good:** <1.8s
- **needs_improvement:** 1.8s-3.0s
- **poor:** >3.0s
- **measures:** loading (first paint)
- **type:** supporting

## Related
- [[Largest-Contentful-Paint-LCP|Largest Contentful Paint (LCP)]]
- [[Time-to-First-Byte-TTFB|Time to First Byte (TTFB)]]

5 · Search, SEO & GEO · 13

standards/open-graph/properties/og-type.md The og:type=website on the homepage.
---
id: "open-graph:og-type"
label: "og:type"
kind: property
standard: open-graph
standard_title: Open Graph Protocol
source_url: "https://ogp.me/#types"
license: reference
domain: [5]
ingest: reference
---

# og:type

Declares what kind of object the page represents, for example website, article, or music.song, which in turn unlocks a set of type-specific properties. If omitted it defaults to website. The chosen value determines which vertical vocabulary (article:, book:, music:, video:, profile:) may be attached.

**Kind:** Property · **Standard:** Open Graph Protocol · **Source:** https://ogp.me/#types

- **required:** yes
- **default:** website

## Related
- [[article]]
- [[book]]
- [[music.song]]
- [[video.movie]]
- [[profile]]
- [[website]]
standards/open-graph/properties/og-title.md The og:title used for social/link unfurls.
---
id: "open-graph:og-title"
label: "og:title"
kind: property
standard: open-graph
standard_title: Open Graph Protocol
source_url: "https://ogp.me/#metadata"
license: reference
domain: [5]
ingest: reference
---

# og:title

Sets the human-readable title of the object as it should appear in the graph, such as a headline or product name. It is one of the four properties every Open Graph page is required to declare. Sharing surfaces usually render it as the bold heading of the preview card.

**Kind:** Property · **Standard:** Open Graph Protocol · **Source:** https://ogp.me/#metadata

- **required:** yes
- **group:** basic

## Related
- [[og-type|og:type]]
- [[og-description|og:description]]
- [[og-url|og:url]]
standards/open-graph/properties/og-image.md The og:image added for sharing previews (was missing on the live site).
---
id: "open-graph:og-image"
label: "og:image"
kind: property
standard: open-graph
standard_title: Open Graph Protocol
source_url: "https://ogp.me/#structured"
license: reference
domain: [5]
ingest: reference
---

# og:image

Points to an image URL that visually represents the object in the graph and appears as the thumbnail in shared previews. A page may list several og:image tags so consumers can pick the best fit. It anchors a family of structured sub-properties describing the image's dimensions, type, and alt text.

**Kind:** Property · **Standard:** Open Graph Protocol · **Source:** https://ogp.me/#structured

- **required:** yes
- **repeatable:** yes

## Related
- [[og-image-url|og:image:url]]
- [[og-image-secure_url|og:image:secure_url]]
- [[og-image-alt|og:image:alt]]
standards/open-graph/properties/og-image-alt.md Accessible alt text for the OG image.
---
id: "open-graph:og-image-alt"
label: "og:image:alt"
kind: property
standard: open-graph
standard_title: Open Graph Protocol
source_url: "https://ogp.me/#structured"
license: reference
domain: [5]
ingest: reference
---

# og:image:alt

Supplies a text description of the image for people who cannot see it, mirroring an HTML alt attribute. It should describe the picture rather than restate the page title. Accessible sharing surfaces expose it to assistive technology.

**Kind:** Property · **Standard:** Open Graph Protocol · **Source:** https://ogp.me/#structured

- **group:** image
- **accessibility:** yes

## Related
- [[og-image|og:image]]
standards/open-graph/properties/og-description.md The og:description for unfurls.
---
id: "open-graph:og-description"
label: "og:description"
kind: property
standard: open-graph
standard_title: Open Graph Protocol
source_url: "https://ogp.me/#optional"
license: reference
domain: [5]
ingest: reference
---

# og:description

Offers a one- or two-sentence summary of the object shown beneath the title in preview cards. It is optional but strongly recommended because it drives click-through. Keeping it concise avoids truncation across different platforms.

**Kind:** Property · **Standard:** Open Graph Protocol · **Source:** https://ogp.me/#optional

- **group:** optional

## Related
- [[og-title|og:title]]
- [[og-site_name|og:site_name]]
standards/google-rich-results/rich-result-types/Software-app.md The rich-result type the SoftwareApplication markup targets.
---
id: "google-rich-results:software-app"
label: Software app
kind: rich-result-type
standard: google-rich-results
standard_title: Google-supported structured data (rich result) types
source_url: "https://developers.google.com/search/docs/appearance/structured-data/software-app"
license: reference
domain: [5]
ingest: reference
---

# Software app

Describes an application with its rating, price, and operating system so Google can present an app rich result. It highlights key install and quality signals in Search. Aimed at app publishers and download pages.

**Kind:** Rich Result Type · **Standard:** Google-supported structured data (rich result) types · **Source:** https://developers.google.com/search/docs/appearance/structured-data/software-app

- **schema:** SoftwareApplication

## Related
- [[Review-snippet|Review snippet]]
standards/google-rich-results/rich-result-types/Review-snippet.md The rich-result type behind the Review/AggregateRating markup (star snippets).
---
id: "google-rich-results:review-snippet"
label: Review snippet
kind: rich-result-type
standard: google-rich-results
standard_title: Google-supported structured data (rich result) types
source_url: "https://developers.google.com/search/docs/appearance/structured-data/review-snippet"
license: reference
domain: [5]
ingest: reference
---

# Review snippet

Attaches a rating or short review excerpt to another entity such as a product, business, or recipe. Google can then show star ratings in the result. Aggregate ratings summarize many reviews into a single score.

**Kind:** Rich Result Type · **Standard:** Google-supported structured data (rich result) types · **Source:** https://developers.google.com/search/docs/appearance/structured-data/review-snippet

- **schema:** Review / AggregateRating

## Related
- [[Product]]
- [[Local-business|Local business]]
- [[Movie]]
standards/twitter-cards/tags/summary_large_image.md The corrected Twitter card — the original leaked a blog post’s byline/read-time via twitter:label/data.
---
id: "twitter-cards:summary-large-image"
label: summary_large_image
kind: tag
standard: twitter-cards
standard_title: X (Twitter) Cards
source_url: "https://developer.x.com/en/docs/x-for-websites/cards/overview/summary-card-with-large-image"
license: reference
domain: [5]
ingest: reference
---

# summary_large_image

Is a card type that places a large, edge-to-edge image above the title and description. It is favored for visually driven content where the picture leads. It uses the same tags as summary but renders the image much larger.

**Kind:** Tag · **Standard:** X (Twitter) Cards · **Source:** https://developer.x.com/en/docs/x-for-websites/cards/overview/summary-card-with-large-image

- **group:** card-type

## Related
- [[summary]]
- [[twitter-image|twitter:image]]
standards/robots-txt/directives/Robots-meta-tag.md The mechanism behind the <meta name="robots"> index/follow directive.
---
id: "robots-txt:robots-meta-tag"
label: Robots meta tag
kind: directive
standard: robots-txt
standard_title: Robots Exclusion Protocol (RFC 9309)
source_url: "https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag"
license: IETF-Trust
domain: [5]
ingest: reference
---

# Robots meta tag

Is an HTML meta element in a page's head that carries per-page indexing directives such as noindex or nofollow to crawlers. Unlike robots.txt it controls indexing and link following rather than fetching. It only works if the crawler is allowed to fetch the page in the first place.

**Kind:** Directive · **Standard:** Robots Exclusion Protocol (RFC 9309) · **Source:** https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag

- **concept:** yes
- **location:** html head

## Related
- [[noindex]]
- [[nofollow]]
- [[X-Robots-Tag]]
standards/google-search-essentials/policies/Descriptive-titles-and-snippets.md Backs the de-duplicated, descriptive <title> (was “datascalehr … - datascalehr”).
---
id: "google-search-essentials:descriptive-titles"
label: Descriptive titles and snippets
kind: policy
standard: google-search-essentials
standard_title: "Google Search Essentials & Spam Policies"
source_url: "https://developers.google.com/search/docs/appearance/title-link"
license: reference
domain: [5]
ingest: reference
---

# Descriptive titles and snippets

Clear, accurate title elements and meta descriptions help both users and Google understand what a page offers. Unique, descriptive titles improve how results are presented and clicked. Vague or duplicated titles weaken a page's presentation in Search.

**Kind:** Policy · **Standard:** Google Search Essentials & Spam Policies · **Source:** https://developers.google.com/search/docs/appearance/title-link

- **category:** best-practice

## Related
- [[Helpful-people-first-content|Helpful, people-first content]]
standards/google-search-essentials/policies/Descriptive-alt-text-for-images.md Backs descriptive alt text on imagery.
---
id: "google-search-essentials:image-alt-text"
label: Descriptive alt text for images
kind: policy
standard: google-search-essentials
standard_title: "Google Search Essentials & Spam Policies"
source_url: "https://developers.google.com/search/docs/appearance/google-images"
license: reference
domain: [5]
ingest: reference
---

# Descriptive alt text for images

Alt attributes describe an image's content so Google and assistive technologies can interpret it. Meaningful alt text improves accessibility and helps images rank in image search. Missing or keyword-stuffed alt text reduces its value.

**Kind:** Policy · **Standard:** Google Search Essentials & Spam Policies · **Source:** https://developers.google.com/search/docs/appearance/google-images

- **category:** best-practice

## Related
- [[Keyword-stuffing|Keyword stuffing]]
standards/google-search-essentials/policies/Mobile-friendly-and-fast-pages.md Backs the responsive, fast, render-blocking-free build.
---
id: "google-search-essentials:mobile-friendly"
label: Mobile-friendly and fast pages
kind: policy
standard: google-search-essentials
standard_title: "Google Search Essentials & Spam Policies"
source_url: "https://developers.google.com/search/docs/appearance/page-experience"
license: reference
domain: [5]
ingest: reference
---

# Mobile-friendly and fast pages

Because Google indexes with a mobile crawler, pages should render well and load quickly on phones. A responsive layout and good page experience help users and support performance in Search. Poor mobile usability can limit visibility.

**Kind:** Policy · **Standard:** Google Search Essentials & Spam Policies · **Source:** https://developers.google.com/search/docs/appearance/page-experience

- **category:** best-practice

## Related
- [[Indexable-content-format|Indexable content format]]
standards/eeat-qrg/concepts/Experience.md E-E-A-T rationale for keeping first-hand reviews + independently-validated metrics as trust signals.
---
id: "eeat-qrg:experience"
label: Experience
kind: concept
standard: eeat-qrg
standard_title: "Search Quality Rater concepts (E-E-A-T & Page Quality)"
source_url: "https://developers.google.com/search/blog/2022/12/google-raters-guidelines-e-e-a-t"
license: reference
domain: [5]
ingest: reference
---

# Experience

Assesses whether the content creator has first-hand or life experience with the topic they cover. A review written by someone who actually used a product, or a guide by someone who has done the task, carries more weight. It is the first pillar added to the older E-A-T framework, making it E-E-A-T.

**Kind:** Concept · **Standard:** Search Quality Rater concepts (E-E-A-T & Page Quality) · **Source:** https://developers.google.com/search/blog/2022/12/google-raters-guidelines-e-e-a-t

- **pillar:** E-E-A-T

## Related
- [[Expertise]]
- [[Trust]]

6 · Design Systems & UX · 6

standards/dtcg-tokens/token-types/design-token.md The design-token concept behind expressing color/space/type/radius/shadow as CSS custom properties.
---
id: "dtcg-tokens:design-token"
label: design token
kind: token-type
standard: dtcg-tokens
standard_title: Design Tokens Format Module
source_url: "https://www.designtokens.org/tr/drafts/format/#design-token"
license: CC-BY-4.0
domain: [6]
ingest: reference
---

# design token

A design token is the fundamental unit of the format: a named entity that stores a single design decision such as a color or spacing value. In JSON it is an object carrying at least a $value, and it may add a $type and $description. Tokens let teams share design values across tools and platforms.

**Kind:** Token Type · **Standard:** Design Tokens Format Module · **Source:** https://www.designtokens.org/tr/drafts/format/#design-token

- **category:** concept

## Related
- [[value|$value]]
- [[type|$type]]
- [[group]]
standards/dtcg-tokens/token-types/color.md The color token type — basis for the --brand / --ink / --line palette in both themes.
---
id: "dtcg-tokens:color"
label: color
kind: token-type
standard: dtcg-tokens
standard_title: Design Tokens Format Module
source_url: "https://www.designtokens.org/tr/drafts/format/#color"
license: CC-BY-4.0
domain: [6]
ingest: reference
---

# color

The color type represents a color value used for fills, text, borders, and other visual properties. In the current specification its value is an object with a color space plus channel components, allowing colors beyond the sRGB gamut. Tools resolve it to whatever format a target platform requires.

**Kind:** Token Type · **Standard:** Design Tokens Format Module · **Source:** https://www.designtokens.org/tr/drafts/format/#color

- **category:** basic

## Related
- [[type|$type]]
- [[value|$value]]
- [[gradient]]
- [[shadow]]
standards/gestalt-principles/principles/Proximity.md Why related items (stat + label, quote + attribution) are grouped tightly.
---
id: "gestalt-principles:proximity"
label: Proximity
kind: principle
standard: gestalt-principles
standard_title: Gestalt Principles of Visual Perception
source_url: "https://www.nngroup.com/articles/gestalt-proximity/"
license: reference
domain: [6]
ingest: reference
---

# Proximity

Objects positioned close together are perceived as more related than objects that are farther apart. Spatial grouping lets designers convey relationships using layout alone, without borders or lines. Deliberate spacing organizes content and signals which items belong together.

**Kind:** Principle · **Standard:** Gestalt Principles of Visual Perception · **Source:** https://www.nngroup.com/articles/gestalt-proximity/


## Related
- [[Common-Region|Common Region]]
- [[Similarity]]
standards/gestalt-principles/principles/Common-Region.md Why testimonials, metrics and audiences sit in bordered cards — a shared region reads as a unit.
---
id: "gestalt-principles:common-region"
label: Common Region
kind: principle
standard: gestalt-principles
standard_title: Gestalt Principles of Visual Perception
source_url: "https://www.nngroup.com/articles/common-region/"
license: reference
domain: [6]
ingest: reference
---

# Common Region

Elements enclosed within a shared boundary are perceived as a single group, even overriding proximity. Backgrounds, borders, and containers create strong grouping cues. Cards and panels rely on this principle to bundle related content.

**Kind:** Principle · **Standard:** Gestalt Principles of Visual Perception · **Source:** https://www.nngroup.com/articles/common-region/


## Related
- [[Proximity]]
standards/gestalt-principles/principles/Similarity.md Why repeated components share one visual language so like elements read as like.
---
id: "gestalt-principles:similarity"
label: Similarity
kind: principle
standard: gestalt-principles
standard_title: Gestalt Principles of Visual Perception
source_url: "https://www.nngroup.com/articles/similarity-principle-in-visual-design/"
license: reference
domain: [6]
ingest: reference
---

# Similarity

Elements that look alike in attributes such as color, shape, or size are perceived as part of the same group. Shared styling creates a sense of connection even when items are spread apart. This helps users recognize categories and relationships across an interface.

**Kind:** Principle · **Standard:** Gestalt Principles of Visual Perception · **Source:** https://www.nngroup.com/articles/similarity-principle-in-visual-design/


## Related
- [[Proximity]]
standards/nng-heuristics/heuristics/Flexibility-and-Efficiency-of-Use.md The manual light/dark theme switcher lets users personalise appearance (an accelerator) — the light-only live site offers no such control.
---
id: "nng-heuristics:7"
label: Flexibility and Efficiency of Use
kind: heuristic
standard: nng-heuristics
standard_title: Nielsen Norman 10 Usability Heuristics
source_url: "https://www.nngroup.com/articles/flexibility-efficiency-heuristic/"
license: reference
domain: [6]
ingest: reference
---

# Flexibility and Efficiency of Use

Systems should serve both novices and experts, letting frequent users tailor and accelerate common actions. Shortcuts, accelerators, and personalization allow experienced people to work faster while remaining invisible to newcomers. Catering to a range of skill levels makes the product efficient without sacrificing approachability.

**Kind:** Heuristic · **Standard:** Nielsen Norman 10 Usability Heuristics · **Source:** https://www.nngroup.com/articles/flexibility-efficiency-heuristic/


## Related
- [[Recognition-Rather-Than-Recall|Recognition Rather Than Recall]]

7 · Content & Editorial · 2

standards/plain-language/guidelines/Use-headings.md Backs using real, descriptive headings to organize the preserved copy.
---
id: "plain-language:headings"
label: Use headings
kind: guideline
standard: plain-language
standard_title: Federal Plain Language Guidelines
source_url: "https://www.plainlanguage.gov/guidelines/design/use-headings/"
license: US-Gov-PublicDomain
domain: [7]
ingest: reference
---

# Use headings

Break content into sections with informative headings, including question-form headings that mirror what readers ask. Clear headings let people skim and jump to the part that concerns them. They also reveal the document's structure at a glance.

**Kind:** Guideline · **Standard:** Federal Plain Language Guidelines · **Source:** https://www.plainlanguage.gov/guidelines/design/use-headings/

- **group:** Design your document

## Related
- [[Organize-the-information|Organize the information]]
- [[Use-lists-and-tables|Use lists and tables]]
standards/plain-language/guidelines/Use-lists-and-tables.md Backs expressing stat groups and audience options as lists/definition lists.
---
id: "plain-language:lists-and-tables"
label: Use lists and tables
kind: guideline
standard: plain-language
standard_title: Federal Plain Language Guidelines
source_url: "https://www.plainlanguage.gov/guidelines/design/use-lists/"
license: US-Gov-PublicDomain
domain: [7]
ingest: reference
---

# Use lists and tables

Convert complex sequences, conditions, or comparisons into bulleted or numbered lists and tables that readers can scan. Structured layout exposes relationships that get buried inside long prose paragraphs. Lists and tables make eligibility rules and steps far easier to follow.

**Kind:** Guideline · **Standard:** Federal Plain Language Guidelines · **Source:** https://www.plainlanguage.gov/guidelines/design/use-lists/

- **group:** Design your document

## Related
- [[Use-headings|Use headings]]
- [[Organize-the-information|Organize the information]]

O2 · GEO / answer-engine optimization · 5

standards/geo-tactics/tactics/Cite-sources.md Why the “independently validated” benchmark line now names its source.
---
id: "geo-tactics:cite-sources"
label: Cite sources
kind: tactic
standard: geo-tactics
standard_title: Generative Engine Optimization tactics
source_url: "https://arxiv.org/abs/2311.09735"
license: reference
domain: [5]
ingest: reference
---

# Cite sources

Adding citations to credible external sources for the claims made in the content. In the GEO study this was among the most effective tactics, meaningfully raising a source's visibility in generated answers. It signals reliability that generative engines reward when composing responses.

**Kind:** Tactic · **Standard:** Generative Engine Optimization tactics · **Source:** https://arxiv.org/abs/2311.09735

- **effect:** improves visibility
- **strength:** top performer

## Related
- [[Add-quotations|Add quotations]]
- [[Add-statistics|Add statistics]]
standards/geo-tactics/tactics/Add-statistics.md The quantified, liftable claims (75%, <1 hour, 16x, 2M) that answer engines cite.
---
id: "geo-tactics:add-statistics"
label: Add statistics
kind: tactic
standard: geo-tactics
standard_title: Generative Engine Optimization tactics
source_url: "https://arxiv.org/abs/2311.09735"
license: reference
domain: [5]
ingest: reference
---

# Add statistics

Enriching content with relevant quantitative data and statistics instead of qualitative claims alone. The study found it consistently boosted visibility across metrics and paired well with fluency optimization for peak results. It was particularly strong for law, government, and opinion-type queries.

**Kind:** Tactic · **Standard:** Generative Engine Optimization tactics · **Source:** https://arxiv.org/abs/2311.09735

- **effect:** improves visibility
- **strength:** top performer

## Related
- [[Cite-sources|Cite sources]]
- [[Add-quotations|Add quotations]]
- [[Fluency-optimization|Fluency optimization]]
standards/geo-tactics/tactics/Authoritative-tone.md Definitional, confident lead sentences that read as citable answers.
---
id: "geo-tactics:authoritative-tone"
label: Authoritative tone
kind: tactic
standard: geo-tactics
standard_title: Generative Engine Optimization tactics
source_url: "https://arxiv.org/abs/2311.09735"
license: reference
domain: [5]
ingest: reference
---

# Authoritative tone

Rewriting content to sound more confident and authoritative about the subject. The study reported this as a helpful, positive tactic for improving visibility in generated responses. Its impact was solid though generally below the citation, quotation, and statistics methods.

**Kind:** Tactic · **Standard:** Generative Engine Optimization tactics · **Source:** https://arxiv.org/abs/2311.09735

- **effect:** improves visibility
- **strength:** moderate

## Related
- [[Add-statistics|Add statistics]]
standards/geo-tactics/tactics/Add-quotations.md Attributed customer quotations retained as first-hand, quotable evidence.
---
id: "geo-tactics:add-quotations"
label: Add quotations
kind: tactic
standard: geo-tactics
standard_title: Generative Engine Optimization tactics
source_url: "https://arxiv.org/abs/2311.09735"
license: reference
domain: [5]
ingest: reference
---

# Add quotations

Inserting relevant quotations from experts or authoritative figures into the content. It was one of the strongest performers in the study, contributing to visibility gains of up to roughly 40 percent. It proved especially effective for explanation, history, and society-oriented queries.

**Kind:** Tactic · **Standard:** Generative Engine Optimization tactics · **Source:** https://arxiv.org/abs/2311.09735

- **effect:** improves visibility
- **strength:** top performer

## Related
- [[Cite-sources|Cite sources]]
- [[Add-statistics|Add statistics]]
standards/google-rich-results/rich-result-types/Speakable.md The WebPage.speakable specification marking the hero + how-it-works sentences for voice/assistant surfacing.
---
id: "google-rich-results:speakable"
label: Speakable
kind: rich-result-type
standard: google-rich-results
standard_title: Google-supported structured data (rich result) types
source_url: "https://developers.google.com/search/docs/appearance/structured-data/speakable"
license: reference
domain: [5]
ingest: reference
---

# Speakable

Marks the sections of a news article best suited to being read aloud by text-to-speech assistants. It helps voice devices select concise, spoken-friendly passages. Currently a beta feature limited mainly to news content in supported languages.

**Kind:** Rich Result Type · **Standard:** Google-supported structured data (rich result) types · **Source:** https://developers.google.com/search/docs/appearance/structured-data/speakable

- **schema:** Speakable

## Related
- [[Article]]

O3 · Expanded structured data · 5

standards/schema-org/types/ContactPoint.md Organization.contactPoint (sales) added for a richer entity / knowledge panel.
---
id: "schema:ContactPoint"
label: ContactPoint
kind: type
standard: schema-org
standard_title: Schema.org
standard_version: 30.0
source_url: "https://schema.org/ContactPoint"
license: CC-BY-SA-3.0
domain: [1]
subClassOf: [StructuredValue]
---

# ContactPoint

> A contact point—for example, a Customer Complaints department.

**Kind:** Type (`rdfs:Class`) · **Standard:** Schema.org · **Source:** https://schema.org/ContactPoint

## Parent types
- [[StructuredValue]]

## Direct subtypes
- [[PostalAddress]]

## Properties (domain includes this type)
- [[areaServed]]
- [[availableLanguage]]
- [[contactOption]]
- [[contactType]]
- [[email]]
- [[faxNumber]]
- [[hoursAvailable]]
- [[productSupported]]
- [[serviceArea]]
- [[telephone]]
standards/schema-org/types/Service.md A Service node (“Payroll data connectivity & reconciliation”) provided by the Organization.
---
id: "schema:Service"
label: Service
kind: type
standard: schema-org
standard_title: Schema.org
standard_version: 30.0
source_url: "https://schema.org/Service"
license: CC-BY-SA-3.0
domain: [1]
subClassOf: [Intangible]
---

# Service

> A service provided by an organization, e.g. delivery service, print services, etc.

**Kind:** Type (`rdfs:Class`) · **Standard:** Schema.org · **Source:** https://schema.org/Service

## Parent types
- [[Intangible]]

## Direct subtypes
- [[BroadcastService]]
- [[CableOrSatelliteService]]
- [[FinancialProduct]]
- [[FoodService]]
- [[GovernmentService]]
- [[Taxi]]
- [[TaxiService]]
- [[WebAPI]]

## Properties (domain includes this type)
- [[aggregateRating]]
- [[areaServed]]
- [[audience]]
- [[availableChannel]]
- [[award]]
- [[brand]]
- [[broker]]
- [[category]]
- [[hasCertification]]
- [[hasOfferCatalog]]
- [[hoursAvailable]]
- [[isRelatedTo]]
- [[isSimilarTo]]
- [[logo]]
- [[offers]]
- [[produces]]
- [[provider]]
- [[providerMobility]]
- [[review]]
- [[serviceArea]]
- [[serviceAudience]]
- [[serviceOutput]]
- [[serviceType]]
- [[slogan]]
- [[termsOfService]]
standards/schema-org/types/Offer.md The Offer on the SoftwareApplication (licensing quoted separately).
---
id: "schema:Offer"
label: Offer
kind: type
standard: schema-org
standard_title: Schema.org
standard_version: 30.0
source_url: "https://schema.org/Offer"
license: CC-BY-SA-3.0
domain: [1]
subClassOf: [Intangible]
---

# Offer

> An offer to transfer some rights to an item or to provide a service — for example, an offer to sell tickets to an event, to rent the DVD of a movie, to stream a TV show over the internet, to repair a motorcycle, or to loan a book.\n\nNote: As the [[businessFunction]] property, which identifies the form of offer (e.g. sell, lease, repair, dispose), defaults to http://purl.org/goodrelations/v1#Sell; an Offer without a defined businessFunction value can be assumed to be an offer to sell.\n\nFor [GTIN](http://www.gs1.org/barcodes/technical/idkeys/gtin)-related fields, see [Check Digit calculator](http://www.gs1.org/barcodes/support/check_digit_calculator) and [validation guide](http://www.gs1us.org/resources/standards/gtin-validation-guide) from [GS1](http://www.gs1.org/).

**Kind:** Type (`rdfs:Class`) · **Standard:** Schema.org · **Source:** https://schema.org/Offer

## Parent types
- [[Intangible]]

## Direct subtypes
- [[AggregateOffer]]
- [[OfferForLease]]
- [[OfferForPurchase]]

## Properties (domain includes this type)
- [[acceptedPaymentMethod]]
- [[addOn]]
- [[additionalProperty]]
- [[advanceBookingRequirement]]
- [[aggregateRating]]
- [[areaServed]]
- [[asin]]
- [[availability]]
- [[availabilityEnds]]
- [[availabilityStarts]]
- [[availableAtOrFrom]]
- [[availableDeliveryMethod]]
- [[businessFunction]]
- [[category]]
- [[checkoutPageURLTemplate]]
- [[deliveryLeadTime]]
- [[eligibleCustomerType]]
- [[eligibleDuration]]
- [[eligibleQuantity]]
- [[eligibleRegion]]
- [[eligibleTransactionVolume]]
- [[gtin]]
- [[gtin12]]
- [[gtin13]]
- [[gtin14]]
- [[gtin8]]
- [[hasAdultConsideration]]
- [[hasGS1DigitalLink]]
- [[hasMeasurement]]
- [[hasMerchantReturnPolicy]]
- [[includesObject]]
- [[ineligibleRegion]]
- [[inventoryLevel]]
- [[isFamilyFriendly]]
- [[itemCondition]]
- [[itemOffered]]
- [[leaseLength]]
- [[mobileUrl]]
- [[mpn]]
- [[offeredBy]]
- [[price]]
- [[priceCurrency]]
- [[priceSpecification]]
- [[priceValidUntil]]
- [[review]]
- [[reviews]]
- [[seller]]
- [[serialNumber]]
- [[shippingDetails]]
- [[sku]]
- [[validForMemberTier]]
- [[validFrom]]
- [[validThrough]]
- [[warranty]]
standards/schema-org/types/SearchAction.md WebSite.potentialAction SearchAction — eligible for a sitelinks search box.
---
id: "schema:SearchAction"
label: SearchAction
kind: type
standard: schema-org
standard_title: Schema.org
standard_version: 30.0
source_url: "https://schema.org/SearchAction"
license: CC-BY-SA-3.0
domain: [1]
subClassOf: [Action]
---

# SearchAction

> The act of searching for an object.\n\nRelated actions:\n\n* [[FindAction]]: SearchAction generally leads to a FindAction, but not necessarily.

**Kind:** Type (`rdfs:Class`) · **Standard:** Schema.org · **Source:** https://schema.org/SearchAction

## Parent types
- [[Action]]

## Properties (domain includes this type)
- [[query]]
standards/schema-org/types/ImageObject.md The hero graphic modelled as an ImageObject carrying provenance fields (see O5).
---
id: "schema:ImageObject"
label: ImageObject
kind: type
standard: schema-org
standard_title: Schema.org
standard_version: 30.0
source_url: "https://schema.org/ImageObject"
license: CC-BY-SA-3.0
domain: [1]
subClassOf: [MediaObject]
---

# ImageObject

> An image file.

**Kind:** Type (`rdfs:Class`) · **Standard:** Schema.org · **Source:** https://schema.org/ImageObject

## Parent types
- [[MediaObject]]

## Direct subtypes
- [[Barcode]]
- [[ImageObjectSnapshot]]

## Properties (domain includes this type)
- [[caption]]
- [[embeddedTextCaption]]
- [[exifData]]
- [[representativeOfPage]]

O4 · Accessibility conformance (VPAT) · 3

standards/vpat/sections/Conformance-levels.md The Supports / Partially / Does-not-support vocabulary used in accessibility.html.
---
id: "vpat:conformance-levels"
label: Conformance levels
kind: section
standard: vpat
standard_title: VPAT / Accessibility Conformance Report
source_url: "https://www.section508.gov/sell/how-to-create-acr-with-vpat/"
license: reference
domain: [3]
ingest: reference
---

# Conformance levels

Each criterion is rated with one of a fixed set of terms: Supports when at least one method meets it without known defects, Partially Supports when some functionality does not meet it, and Does Not Support when most functionality fails it. Not Applicable marks criteria irrelevant to the product, while Not Evaluated may be used only for the WCAG Level AAA table. Every rating is paired with a remarks and explanations column giving the supporting detail.

**Kind:** Section · **Standard:** VPAT / Accessibility Conformance Report · **Source:** https://www.section508.gov/sell/how-to-create-acr-with-vpat/

- **part:** terms

## Related
- [[Report-introduction|Report introduction]]
- [[Perceivable-table|Perceivable table]]
standards/en-301-549/clauses/Clause-11-Software.md The EU ICT accessibility clause the statement claims against alongside WCAG 2.2 AA.
---
id: "en-301-549:clause-11-software"
label: Clause 11 Software
kind: clause
standard: en-301-549
standard_title: EN 301 549
source_url: "https://www.etsi.org/deliver/etsi_en/301500_301599/301549/03.02.01_60/en_301549v030201p.pdf"
license: reference
domain: [3]
ingest: reference
---

# Clause 11 Software

Applies WCAG-derived success criteria to non-web software and adds software-specific requirements for interoperability with assistive technology and user preferences. It covers desktop and mobile applications. Exposing accessibility information to platform services is a key theme.

**Kind:** Clause · **Standard:** EN 301 549 · **Source:** https://www.etsi.org/deliver/etsi_en/301500_301599/301549/03.02.01_60/en_301549v030201p.pdf

- **clause:** 11

## Related
- [[Clause-9-Web|Clause 9 Web]]
- [[Clause-10-Non-web-documents|Clause 10 Non-web documents]]
standards/section-508/provisions/Chapter-5-software.md The US Section 508 software provisions a full VPAT edition would also cover.
---
id: "section-508:chapter-5-software"
label: Chapter 5 software
kind: provision
standard: section-508
standard_title: Revised Section 508 Standards
source_url: "https://www.access-board.gov/ict/#chapter-5-software"
license: US-Gov-PublicDomain
domain: [3]
ingest: reference
---

# Chapter 5 software

Sets technical requirements for software, including interoperability with assistive technology and support for platform accessibility services. It covers applications and authoring tools. Non-web software also draws on WCAG 2.0 success criteria applied to software.

**Kind:** Provision · **Standard:** Revised Section 508 Standards · **Source:** https://www.access-board.gov/ict/#chapter-5-software

- **chapter:** 5

## Related
- [[Chapter-4-hardware|Chapter 4 hardware]]
- [[WCAG-2.0-incorporation|WCAG 2.0 incorporation]]

O5 · Content provenance on media · 6

standards/c2pa/concepts/Content-Credentials.md The Content Credentials manifest that should be embedded in the hero asset at export.
---
id: "c2pa:content-credentials"
label: Content Credentials
kind: concept
standard: c2pa
standard_title: C2PA Content Provenance
source_url: "https://contentcredentials.org/"
license: reference
domain: [10]
ingest: reference
---

# Content Credentials

Content Credentials is the user-facing brand and presentation layer for C2PA provenance data, shown through a recognizable icon and detail panel. It lets people inspect who made a piece of media and how it was altered. The name and its symbol give the technical standard a consistent public identity.

**Kind:** Concept · **Standard:** C2PA Content Provenance · **Source:** https://contentcredentials.org/

- **category:** presentation

## Related
- [[Manifest]]
standards/c2pa/concepts/Assertion.md The signed assertions (creator, actions) a C2PA manifest carries.
---
id: "c2pa:assertion"
label: Assertion
kind: concept
standard: c2pa
standard_title: C2PA Content Provenance
source_url: "https://c2pa.org/specifications/specifications/2.1/specs/C2PA_Specification.html"
license: reference
domain: [10]
ingest: reference
---

# Assertion

An assertion is an individual statement about the content, such as who created it, what edits were applied, or which capture device was used. Assertions are the granular building blocks of provenance that a claim collects and signs. Each one describes a specific fact about the asset.

**Kind:** Concept · **Standard:** C2PA Content Provenance · **Source:** https://c2pa.org/specifications/specifications/2.1/specs/C2PA_Specification.html

- **category:** structure

## Related
- [[Claim]]
- [[Ingredient]]
standards/iptc-photo-metadata/properties/Creator.md Mapped to ImageObject.creator on the hero graphic.
---
id: "iptc-photo-metadata:creator"
label: Creator
kind: property
standard: iptc-photo-metadata
standard_title: IPTC Photo Metadata Standard
source_url: "https://www.iptc.org/std/photometadata/documentation/userguide/"
license: reference
domain: [10]
ingest: reference
---

# Creator

The Creator property identifies the person or organization that made the image, such as the photographer or illustrator. It is the primary attribution field for authorship and underpins credit and rights management. Multiple creators can be listed where a work has more than one author.

**Kind:** Property · **Standard:** IPTC Photo Metadata Standard · **Source:** https://www.iptc.org/std/photometadata/documentation/userguide/

- **type:** property

## Related
- [[Credit-Line|Credit Line]]
- [[Copyright-Notice|Copyright Notice]]
standards/iptc-photo-metadata/properties/Credit-Line.md Mapped to ImageObject.creditText.
---
id: "iptc-photo-metadata:credit-line"
label: Credit Line
kind: property
standard: iptc-photo-metadata
standard_title: IPTC Photo Metadata Standard
source_url: "https://www.iptc.org/std/photometadata/documentation/userguide/"
license: reference
domain: [10]
ingest: reference
---

# Credit Line

The Credit Line is a short, free-text acknowledgement of how the image should be credited when published, for example an agency or photographer byline. It reflects contractual or editorial credit requirements rather than legal ownership. Publishers typically reproduce it verbatim alongside the image.

**Kind:** Property · **Standard:** IPTC Photo Metadata Standard · **Source:** https://www.iptc.org/std/photometadata/documentation/userguide/

- **type:** property

## Related
- [[Creator]]
- [[Copyright-Notice|Copyright Notice]]
standards/iptc-photo-metadata/properties/Copyright-Notice.md Mapped to ImageObject.copyrightNotice.
---
id: "iptc-photo-metadata:copyright-notice"
label: Copyright Notice
kind: property
standard: iptc-photo-metadata
standard_title: IPTC Photo Metadata Standard
source_url: "https://www.iptc.org/std/photometadata/documentation/userguide/"
license: reference
domain: [10]
ingest: reference
---

# Copyright Notice

The Copyright Notice is a free-text statement asserting the copyright status and owner of the image, often including a year and rights-holder name. It communicates the legal claim over the work to anyone inspecting the file. It complements, rather than replaces, machine-readable rights fields.

**Kind:** Property · **Standard:** IPTC Photo Metadata Standard · **Source:** https://www.iptc.org/std/photometadata/documentation/userguide/

- **type:** property

## Related
- [[Web-Statement-of-Rights|Web Statement of Rights]]
- [[Licensor]]
standards/iptc-photo-metadata/properties/Description-Caption.md Mapped to ImageObject.caption + the img alt text.
---
id: "iptc-photo-metadata:description"
label: Description (Caption)
kind: property
standard: iptc-photo-metadata
standard_title: IPTC Photo Metadata Standard
source_url: "https://www.iptc.org/std/photometadata/documentation/userguide/"
license: reference
domain: [10]
ingest: reference
---

# Description (Caption)

The Description, historically called the caption, is a textual account of what the image depicts, including the who, what, when, and where. It supports search, accessibility, and editorial reuse of the image. It is one of the most widely populated descriptive fields in the standard.

**Kind:** Property · **Standard:** IPTC Photo Metadata Standard · **Source:** https://www.iptc.org/std/photometadata/documentation/userguide/

- **type:** property

## Related
- [[Headline]]
- [[Keywords]]

O6 · INP, Lighthouse & readability · 3

standards/core-web-vitals/metrics/Interaction-to-Next-Paint-INP.md Why the tab/carousel/ROI handlers use passive listeners and avoid layout thrash.
---
id: "core-web-vitals:inp"
label: Interaction to Next Paint (INP)
kind: metric
standard: core-web-vitals
standard_title: "Core Web Vitals & Web Vitals metrics"
source_url: "https://web.dev/articles/inp"
license: reference
domain: [4]
ingest: reference
---

# Interaction to Next Paint (INP)

INP observes every tap, click, and key press across the whole page visit and reports a value near the worst latency between the interaction and the next frame painted in response. It is the Core Web Vital for overall responsiveness, having replaced First Input Delay in 2024. High INP points to long JavaScript tasks blocking the main thread.

**Kind:** Metric · **Standard:** Core Web Vitals & Web Vitals metrics · **Source:** https://web.dev/articles/inp

- **good:** <200ms
- **needs_improvement:** 200ms-500ms
- **poor:** >500ms
- **measures:** interactivity / responsiveness
- **type:** core

## Related
- [[Total-Blocking-Time-TBT|Total Blocking Time (TBT)]]
standards/lighthouse/audits/unused-javascript.md The build ships one small inline script — no framework/unused JS to flag.
---
id: "lighthouse:unused-javascript"
label: Reduce unused JavaScript
kind: audit
standard: lighthouse
standard_title: Lighthouse audits
source_url: "https://github.com/GoogleChrome/lighthouse/blob/main/core/audits/byte-efficiency/unused-javascript.js"
license: Apache-2.0
domain: [4]
ingest: full
category: performance
---

# Reduce unused JavaScript

> Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn how to reduce unused JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unused-javascript/).

**Kind:** Audit · **Standard:** Lighthouse audits · **Category:** performance · **Audit id:** `unused-javascript`
standards/readability-formulas/formulas/Automated-Readability-Index-ARI.md The lens for a future copy pass on dense sentences (e.g. the Workday-GPC paragraph), kept verbatim for now.
---
id: "readability-formulas:ari"
label: Automated Readability Index (ARI)
kind: formula
standard: readability-formulas
standard_title: Readability Formulas
source_url: "https://en.wikipedia.org/wiki/Automated_readability_index"
license: PublicDomain
domain: [7]
ingest: reference
---

# Automated Readability Index (ARI)

Produces a grade level from characters per word and words per sentence, again sidestepping syllable counting. Designed for real-time machine scoring on typewriters, it responds directly to the character count of the text. Its output maps to a US grade rather than an age band.

**Kind:** Formula · **Standard:** Readability Formulas · **Source:** https://en.wikipedia.org/wiki/Automated_readability_index

- **formula:** 4.71 x (characters/words) + 0.5 x (words/sentences) - 21.43
- **inputs:** characters, words, sentences
- **output:** US grade level

## Related
- [[Coleman-Liau-Index|Coleman-Liau Index]]