diff --git a/files/en-us/glossary/hyperlink/index.md b/files/en-us/glossary/hyperlink/index.md index f19ba2fae3b816b..0dfbcc2f4d1dcab 100644 --- a/files/en-us/glossary/hyperlink/index.md +++ b/files/en-us/glossary/hyperlink/index.md @@ -12,7 +12,5 @@ Hyperlinks connect webpages or data items to one another. In HTML, {{HTMLElement - [Hyperlink](https://en.wikipedia.org/wiki/Hyperlink) on Wikipedia - [Creating links](/en-US/docs/Learn_web_development/Core/Structuring_content/Creating_links) -- [Links in HTML Documents - W3C](https://www.w3.org/TR/1999/REC-html401-19991224/struct/links.html) -- [HTML a - hyperlink - W3C](https://w3c.github.io/html-reference/a.html) - [`` on MDN](/en-US/docs/Web/HTML/Element/a) - [`` on MDN](/en-US/docs/Web/HTML/Element/link) diff --git a/files/en-us/related/imsc/imsc_and_other_standards/index.md b/files/en-us/related/imsc/imsc_and_other_standards/index.md index 3bc713323c41b80..c205851aa9ba52d 100644 --- a/files/en-us/related/imsc/imsc_and_other_standards/index.md +++ b/files/en-us/related/imsc/imsc_and_other_standards/index.md @@ -12,7 +12,7 @@ IMSC is the result of an international effort to bring together popular profiles IMSC was designed to be a practical application of SMPTE-TT ([SMPTE ST 2052-1](https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=7291854)), which is designated as a safe-harbor format by the [FCC](https://www.law.cornell.edu/cfr/text/47/79.103). As a result, most SMPTE-TT documents should render correctly using IMSC renderers (see [the limitations](https://www.w3.org/TR/ttml-imsc1.0.1/#smpte-tt-smpte-st-2052-1)), and the conversion guidelines from CTA 608/708 to SMPTE-TT ([SMPTE RP 2052-10](https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=7289645) and [SMPTE RP 2052-11](https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=7290363)) are also applicable to IMSC. -IMSC is also a syntactic superset of both [SDP-US](https://www.w3.org/TR/ttml10-sdp-us/) and [EBU-TT-D](https://tech.ebu.ch/publications/tech3380), such that documents that conform to either of these two formats are valid IMSC documents and can be rendered by IMSC renderers — see [Compatibility with other TTML-based specifications](https://www.w3.org/TR/2018/REC-ttml-imsc1.0.1-20180424/#interop-examples) for more details. +IMSC is also a syntactic superset of both [SDP-US](https://www.w3.org/TR/ttml10-sdp-us/) and [EBU-TT-D](https://tech.ebu.ch/publications/tech3380), such that documents that conform to either of these two formats are valid IMSC documents and can be rendered by IMSC renderers — see [Compatibility with other TTML-based specifications](https://w3c.github.io/imsc/imsc1/spec/ttml-ww-profiles.html#interop-examples) for more details. IMSC traces its origins to the CFF-TT format, and [CFF-TT documents](https://www.w3.org/TR/ttml-imsc1.1/#cff-tt) can be converted to IMSC relatively easily. diff --git a/files/en-us/web/accessibility/seizure_disorders/index.md b/files/en-us/web/accessibility/seizure_disorders/index.md index ae4371366f944c6..11c74b8b085dc58 100644 --- a/files/en-us/web/accessibility/seizure_disorders/index.md +++ b/files/en-us/web/accessibility/seizure_disorders/index.md @@ -626,7 +626,7 @@ Along with the Harding tool, is generally recognized to be one of the two "gold - [CSS Color Module Level 3](https://www.w3.org/TR/css-color-3/) - [Personalization Semantics Explainer 1.0](https://www.w3.org/TR/personalization-semantics-1.0/). Working Draft -- [Personalization Tools 1.0](https://www.w3.org/TR/2019/WD-personalization-semantics-tools-1.0-20190711/) Working Draft +- [WAI-Adapt: Tools Module](https://www.w3.org/TR/adapt-tools/) Working Draft - [Three Flashes or Below Threshold Understanding SC 2.3.1](https://www.w3.org/TR/UNDERSTANDING-WCAG20/seizure-does-not-violate.html) Understanding WCAG 2.0 (Older, but contains some explanations of references made in the WCAG 2.1 criteria) - [Three Flashes or Below Threshold Understanding Success Criterion 2.3.1](https://www.w3.org/WAI/WCAG21/Understanding/three-flashes-or-below-threshold.html) Understanding WCAG 2.1 - [Understanding Success Criteria 1.4.3: Contrast (Minimum)](https://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum.html) diff --git a/files/en-us/web/api/csskeyframerule/style/index.md b/files/en-us/web/api/csskeyframerule/style/index.md index de1c0a53fb2f6e4..45238fed8b874d0 100644 --- a/files/en-us/web/api/csskeyframerule/style/index.md +++ b/files/en-us/web/api/csskeyframerule/style/index.md @@ -8,7 +8,7 @@ browser-compat: api.CSSKeyframeRule.style {{ APIRef("CSSOM") }} -The read-only **`CSSKeyframeRule.style`** property is the {{ domxref("CSSStyleDeclaration") }} interface for the [declaration block](https://www.w3.org/TR/1998/REC-CSS2-19980512/syndata.html#block) of the {{ domxref("CSSKeyframeRule") }}. +The read-only **`CSSKeyframeRule.style`** property is the {{ domxref("CSSStyleDeclaration") }} interface for the declaration block of the {{ domxref("CSSKeyframeRule") }}. ## Value diff --git a/files/en-us/web/api/cssstylerule/style/index.md b/files/en-us/web/api/cssstylerule/style/index.md index 1a32ede01fd2a12..547082a4e1e41c7 100644 --- a/files/en-us/web/api/cssstylerule/style/index.md +++ b/files/en-us/web/api/cssstylerule/style/index.md @@ -8,7 +8,7 @@ browser-compat: api.CSSStyleRule.style {{ APIRef("CSSOM") }} -The read-only **`style`** property is the {{ domxref("CSSStyleDeclaration") }} interface for the [declaration block](https://www.w3.org/TR/1998/REC-CSS2-19980512/syndata.html#block) of the {{ DOMXref("CSSStyleRule") }}. +The read-only **`style`** property is the {{ domxref("CSSStyleDeclaration") }} interface for the declaration block of the {{ DOMXref("CSSStyleRule") }}. ## Value diff --git a/files/en-us/web/api/datatransfer/getdata/index.md b/files/en-us/web/api/datatransfer/getdata/index.md index adab232e5a85b5f..e8449e0829215e2 100644 --- a/files/en-us/web/api/datatransfer/getdata/index.md +++ b/files/en-us/web/api/datatransfer/getdata/index.md @@ -30,16 +30,7 @@ getData(format) A string representing the drag data for the specified `format`. If the drag operation has no data or the operation has no data for the specified `format`, this method returns an empty string. -### Caveats - -- Data availability - - - : The [HTML Drag and Drop Specification](https://www.w3.org/TR/2011/WD-html5-20110113/dnd.html#drag-data-store-mode) dictates a `drag data store mode`. - This may result in unexpected behavior, being - **`DataTransfer.getData()`** not returning an expected - value, because not all browsers enforce this restriction. - - During the `dragstart` and `drop` events, it is safe to access the data. For all other events, the data should be considered unavailable. Despite this, the items and their formats can still be enumerated. +Note that `DataTransfer.getData()` may not return an expected value, because it only allows reading and writing data for specified events. During the `dragstart` and `drop` events, it is safe to access the data. For all other events, the data should be considered unavailable. Despite this, the items and their formats can still be enumerated. ## Examples diff --git a/files/en-us/web/api/document/createattributens/index.md b/files/en-us/web/api/document/createattributens/index.md index cb979d01025c291..549db16158d0d1f 100644 --- a/files/en-us/web/api/document/createattributens/index.md +++ b/files/en-us/web/api/document/createattributens/index.md @@ -23,9 +23,13 @@ createAttributeNS(namespaceURI, qualifiedName) ### Parameters - `namespaceURI` - - : A string that specifies the [namespace URI](https://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/glossary.html#dt-namespaceURI) to associate with the attribute. - The {{DOMxRef("Attr.namespaceURI", "namespaceURI")}} property of the created attribute is initialized with the value of `namespaceURI`. - See [Valid Namespace URIs](#important_namespace_uris). + - : A string that specifies the {{DOMxRef("Attr.namespaceURI", "namespaceURI")}} to associate with the attribute. Some important namespace URIs are: + - [HTML](/en-US/docs/Web/HTML) + - : `http://www.w3.org/1999/xhtml` + - [SVG](/en-US/docs/Web/SVG) + - : `http://www.w3.org/2000/svg` + - [MathML](/en-US/docs/Web/MathML) + - : `http://www.w3.org/1998/Math/MathML` - `qualifiedName` - : A string that specifies the name of attribute to be created. The {{DOMxRef("Attr.name", "name")}} property of the created attribute is initialized with the value of `qualifiedName`. @@ -37,19 +41,10 @@ The new {{domxref("Attr")}} node. ### Exceptions - `NamespaceError` {{domxref("DOMException")}} - - : Thrown if the [`namespaceURI`](#namespaceuri) value is not a valid [namespace URI](https://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/glossary.html#dt-namespaceURI). + - : Thrown if the [`namespaceURI`](#namespaceuri) value is not a valid namespace URI. - `InvalidCharacterError` {{domxref("DOMException")}} - : Thrown if the [`qualifiedName`](#qualifiedname) value is not a valid [XML name](https://www.w3.org/TR/REC-xml/#dt-name); for example, it starts with a number, hyphen, or period, or contains characters other than alphanumeric characters, underscores, hyphens, or periods. -## Important Namespace URIs - -- [HTML](/en-US/docs/Web/HTML) - - : `http://www.w3.org/1999/xhtml` -- [SVG](/en-US/docs/Web/SVG) - - : `http://www.w3.org/2000/svg` -- [MathML](/en-US/docs/Web/MathML) - - : `http://www.w3.org/1998/Math/MathML` - ## Examples ```js diff --git a/files/en-us/web/api/document/createelementns/index.md b/files/en-us/web/api/document/createelementns/index.md index 7109428c9c99fc1..2e1de002efad1a7 100644 --- a/files/en-us/web/api/document/createelementns/index.md +++ b/files/en-us/web/api/document/createelementns/index.md @@ -23,9 +23,13 @@ createElementNS(namespaceURI, qualifiedName, options) ### Parameters - `namespaceURI` - - : A string that specifies the [namespace URI](https://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/glossary.html#dt-namespaceURI) to associate with the element. - The {{DOMxRef("element.namespaceURI", "namespaceURI")}} property of the created element is initialized with the value of _namespaceURI_. - See [Valid Namespace URIs](#important_namespace_uris). + - : A string that specifies the {{DOMxRef("element.namespaceURI", "namespaceURI")}} to associate with the element. Some important namespace URIs are: + - [HTML](/en-US/docs/Web/HTML) + - : `http://www.w3.org/1999/xhtml` + - [SVG](/en-US/docs/Web/SVG) + - : `http://www.w3.org/2000/svg` + - [MathML](/en-US/docs/Web/MathML) + - : `http://www.w3.org/1998/Math/MathML` - `qualifiedName` - : A string that specifies the type of element to be created. The {{DOMxRef("node.nodeName", "nodeName")}} property of the created element is initialized with the value of _qualifiedName_. @@ -45,19 +49,10 @@ The new {{DOMxRef("Element")}}. ### Exceptions - `NamespaceError` {{domxref("DOMException")}} - - : Thrown if the [`namespaceURI`](#namespaceuri) value is not a valid [namespace URI](https://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/glossary.html#dt-namespaceURI). + - : Thrown if the [`namespaceURI`](#namespaceuri) value is not a valid namespace URI. - `InvalidCharacterError` {{domxref("DOMException")}} - : Thrown if the [`qualifiedName`](#qualifiedname) value is not a valid [XML name](https://www.w3.org/TR/REC-xml/#dt-name); for example, it starts with a number, hyphen, or period, or contains characters other than alphanumeric characters, underscores, hyphens, or periods. -## Important Namespace URIs - -- [HTML](/en-US/docs/Web/HTML) - - : `http://www.w3.org/1999/xhtml` -- [SVG](/en-US/docs/Web/SVG) - - : `http://www.w3.org/2000/svg` -- [MathML](/en-US/docs/Web/MathML) - - : `http://www.w3.org/1998/Math/MathML` - ## Examples This creates a new `
` element in the {{Glossary("XHTML")}} namespace and @@ -113,4 +108,3 @@ elements from two different namespaces within a single document: - {{DOMxRef("document.createElement()")}} - {{DOMxRef("document.createTextNode()")}} - {{DOMxRef("Element.namespaceURI")}} -- [Namespaces in XML](https://www.w3.org/TR/1999/REC-xml-names-19990114/) diff --git a/files/en-us/web/api/document/evaluate/index.md b/files/en-us/web/api/document/evaluate/index.md index 0620b803c3ea33b..c4e1a9d651b71a0 100644 --- a/files/en-us/web/api/document/evaluate/index.md +++ b/files/en-us/web/api/document/evaluate/index.md @@ -24,7 +24,7 @@ evaluate(xpathExpression, contextNode, namespaceResolver, resultType, result) - `xpathExpression` - : A string representing the _xpath_ to be evaluated. - `contextNode` - - : The _context node_ for the query (see the [XPath specification](https://www.w3.org/TR/1999/REC-xpath-19991116/)). + - : The _context node_ for the query. It's common to pass `document` as the context node. - `namespaceResolver` - : A function that will be passed any namespace prefixes diff --git a/files/en-us/web/api/element/clientheight/index.md b/files/en-us/web/api/element/clientheight/index.md index 5f63c5728643698..a789a329a0bbe4f 100644 --- a/files/en-us/web/api/element/clientheight/index.md +++ b/files/en-us/web/api/element/clientheight/index.md @@ -18,7 +18,7 @@ scrollbars (if present). When `clientHeight` is used on the root element (the `` element), (or on `` if the document is -in quirks mode), the viewport's height (excluding any scrollbar) is returned. [This is a special case of `clientHeight`](https://www.w3.org/TR/2016/WD-cssom-view-1-20160317/#dom-element-clientheight). +in quirks mode), the viewport's height (excluding any scrollbar) is returned. > [!NOTE] > This property will round the value to an integer. If you need diff --git a/files/en-us/web/api/element/clientwidth/index.md b/files/en-us/web/api/element/clientwidth/index.md index 8c055ebfe3b7b59..b68ec4ca2a002c8 100644 --- a/files/en-us/web/api/element/clientwidth/index.md +++ b/files/en-us/web/api/element/clientwidth/index.md @@ -15,7 +15,7 @@ present). When `clientWidth` is used on the root element (the `` element), (or on `` if the document is -in quirks mode), the viewport's width (excluding any scrollbar) is returned. [This is a special case of `clientWidth`](https://www.w3.org/TR/2016/WD-cssom-view-1-20160317/#dom-element-clientwidth). +in quirks mode), the viewport's width (excluding any scrollbar) is returned. > [!NOTE] > This property will round the value to an integer. If you need diff --git a/files/en-us/web/api/element/innerhtml/index.md b/files/en-us/web/api/element/innerhtml/index.md index 99ea7180f67b063..acbe5bc93ec745f 100644 --- a/files/en-us/web/api/element/innerhtml/index.md +++ b/files/en-us/web/api/element/innerhtml/index.md @@ -128,7 +128,7 @@ name = ""; el.innerHTML = name; // harmless in this case ``` -Although this may look like a [cross-site scripting](https://en.wikipedia.org/wiki/Cross-site_scripting) attack, the result is harmless. HTML specifies that a {{HTMLElement("script")}} tag inserted with `innerHTML` [should not execute](https://www.w3.org/TR/2008/WD-html5-20080610/dom.html#innerhtml0). +Although this may look like a [cross-site scripting](https://en.wikipedia.org/wiki/Cross-site_scripting) attack, the result is harmless. A {{HTMLElement("script")}} tag inserted with `innerHTML` will not execute. However, there are ways to execute JavaScript without using {{HTMLElement("script")}} elements, so there is still a security risk whenever you use `innerHTML` to set strings over which you have no control. For example: diff --git a/files/en-us/web/api/svgaelement/target/index.md b/files/en-us/web/api/svgaelement/target/index.md index 9516cf603b7c44f..9c8c770393995f0 100644 --- a/files/en-us/web/api/svgaelement/target/index.md +++ b/files/en-us/web/api/svgaelement/target/index.md @@ -14,9 +14,7 @@ This property is used when there are multiple possible targets for the ending re ## Value -An {{domxref("SVGAnimatedString")}} indicating the ending resource target that opens the document when the link is activated. - -Sample values can be found [here](https://www.w3.org/TR/2011/REC-SVG11-20110816/linking.html#AElementTargetAttribute) +An {{domxref("SVGAnimatedString")}} indicating the ending resource target that opens the document when the link is activated. See {{SVGAttr("target")}} for valid values. ## Examples diff --git a/files/en-us/web/api/xmlhttprequest/xmlhttprequest/index.md b/files/en-us/web/api/xmlhttprequest/xmlhttprequest/index.md index 673f472aaa21aad..8329a7054c36189 100644 --- a/files/en-us/web/api/xmlhttprequest/xmlhttprequest/index.md +++ b/files/en-us/web/api/xmlhttprequest/xmlhttprequest/index.md @@ -15,11 +15,18 @@ creates a new {{domxref("XMLHttpRequest")}}. ```js-nolint new XMLHttpRequest() +// Non-standard +new XMLHttpRequest(options) ``` ### Parameters -None. +There are no standard parameters. However, Firefox allows a non-standard parameter: + +- `options` {{non-standard_inline}} + - : An object that can contain the following flag: + - `mozAnon` + - : A boolean. When setting this flag to `true` will cause the browser not to expose the {{Glossary("origin")}} and user credentials when fetching resources. Most important, this means that {{Glossary("Cookie", "cookies")}} will not be sent unless explicitly added using `setRequestHeader`. ### Return value @@ -27,29 +34,6 @@ A new {{domxref("XMLHttpRequest")}} object. The object must be prepared by at le calling {{domxref("XMLHttpRequest.open", "open()")}} to initialize it before calling {{domxref("XMLHttpRequest.send", "send()")}} to send the request to the server. -## Non-standard Firefox syntax - -Firefox 16 added a non-standard parameter to the constructor that can enable anonymous -mode (see [Firefox bug 692677](https://bugzil.la/692677)). Setting the `mozAnon` flag to `true` -effectively resembles the [`AnonXMLHttpRequest()`](https://www.w3.org/TR/2012/WD-XMLHttpRequest-20120117/#dom-anonxmlhttprequest) -constructor described in older versions of the XMLHttpRequest specification. - -```js -const request = new XMLHttpRequest(paramsDictionary); -``` - -### Parameters (non-standard) - -- `objParameters` - - - : One flag you can set: - - - `mozAnon` - - : Boolean: Setting this flag to `true` will cause the browser not to - expose the {{Glossary("origin")}} and [user credentials](https://www.w3.org/TR/2012/WD-XMLHttpRequest-20120117/#user-credentials) when fetching resources. Most important, this means that - {{Glossary("Cookie", "cookies")}} will not be sent unless explicitly added using - setRequestHeader. - ## Specifications {{Specifications}} diff --git a/files/en-us/web/api/xmlhttprequest_api/using_xmlhttprequest/index.md b/files/en-us/web/api/xmlhttprequest_api/using_xmlhttprequest/index.md index 2df6f3be3362e42..05d927bd8c19e90 100644 --- a/files/en-us/web/api/xmlhttprequest_api/using_xmlhttprequest/index.md +++ b/files/en-us/web/api/xmlhttprequest_api/using_xmlhttprequest/index.md @@ -265,7 +265,7 @@ The recommended way to enable cross-site scripting is to use the `Access-Control ### XMLHttpRequests being stopped -If you conclude with an XMLHttpRequest receiving `status=0` and `statusText=null`, this means the request was not allowed to be performed. It was [`UNSENT`](https://xhr.spec.whatwg.org/#dom-xmlhttprequest-unsent). A likely cause for this is when the [`XMLHttpRequest` origin](https://www.w3.org/TR/2010/CR-XMLHttpRequest-20100803/#xmlhttprequest-origin) (at the creation of the XMLHttpRequest) has changed when the XMLHttpRequest is subsequently `open()`. This case can happen, for example, when one has an XMLHttpRequest that gets fired on an onunload event for a window, the expected XMLHttpRequest is created when the window to be closed is still there, and finally sending the request (in other words, `open()`) when this window has lost its focus and another window gains focus. The most effective way to avoid this problem is to set a listener on the new window's {{domxref("Element/DOMActivate_event", "DOMActivate")}} event which is set once the terminated window has its {{domxref("Window/unload_event", "unload")}} event triggered. +If you conclude with an XMLHttpRequest receiving `status=0` and `statusText=null`, this means the request was not allowed to be performed. It was [`UNSENT`](https://xhr.spec.whatwg.org/#dom-xmlhttprequest-unsent). A likely cause for this is when the `XMLHttpRequest` origin (at the creation of the XMLHttpRequest) has changed when the XMLHttpRequest is subsequently `open()`. This case can happen, for example, when one has an XMLHttpRequest that gets fired on an onunload event for a window, the expected XMLHttpRequest is created when the window to be closed is still there, and finally sending the request (in other words, `open()`) when this window has lost its focus and another window gains focus. The most effective way to avoid this problem is to set a listener on the new window's {{domxref("Element/DOMActivate_event", "DOMActivate")}} event which is set once the terminated window has its {{domxref("Window/unload_event", "unload")}} event triggered. ## Specifications diff --git a/files/en-us/web/api/xsltprocessor/transformtodocument/index.md b/files/en-us/web/api/xsltprocessor/transformtodocument/index.md index 8c2b0833a4c062b..6fbd44f903576a5 100644 --- a/files/en-us/web/api/xsltprocessor/transformtodocument/index.md +++ b/files/en-us/web/api/xsltprocessor/transformtodocument/index.md @@ -23,7 +23,7 @@ transformToDocument(source) ### Return value -A {{domxref("Document")}}. The actual interface depends on the [output method](https://www.w3.org/TR/1999/REC-xslt-19991116#output) of the stylesheet: +A {{domxref("Document")}}. The actual interface depends on the output method of the stylesheet, as specified by [``](/en-US/docs/Web/XML/XSLT/Reference/Element/output) element's `method`. | Output method | Result interface | | ------------- | ------------------------------------------------------------------------------------------------------ | diff --git a/files/en-us/web/css/-moz-user-input/index.md b/files/en-us/web/css/-moz-user-input/index.md index 435ca69cd5edc54..3fbadb6a3766736 100644 --- a/files/en-us/web/css/-moz-user-input/index.md +++ b/files/en-us/web/css/-moz-user-input/index.md @@ -14,7 +14,7 @@ In Mozilla applications, **`-moz-user-input`** determines if an element will acc As of Firefox 60, this property can no longer grant an element the ability to accept user input if it normally does not. It may only be used to disable user input. -> **Note:** `-moz-user-input` was one of the proposals leading to the proposed CSS 3 {{cssxref("user-input")}} property, which has not yet reached Candidate Recommendation (call for implementations). A similar property, `user-focus`, was proposed in [early drafts of a predecessor of the User Interface for CSS3 specification](https://www.w3.org/TR/2000/WD-css3-userint-20000216), but was rejected by the working group. +The `user-input` property is currently not on a standards track. ## Syntax diff --git a/files/en-us/web/css/background-image/index.md b/files/en-us/web/css/background-image/index.md index 18cbf2fd0266520..b6574d65cc85f02 100644 --- a/files/en-us/web/css/background-image/index.md +++ b/files/en-us/web/css/background-image/index.md @@ -56,7 +56,7 @@ To specify multiple background images, supply multiple values, separated by a co Browsers do not provide any special information on background images to assistive technology. This is important primarily for screen readers, as a screen reader will not announce its presence and therefore convey nothing to its users. If the image contains information critical to understanding the page's overall purpose, it is better to describe it semantically in the document. - [MDN Understanding WCAG, Guideline 1.1 explanations](/en-US/docs/Web/Accessibility/Understanding_WCAG/Perceivable#guideline_1.1_—_providing_text_alternatives_for_non-text_content) -- [Understanding Success Criterion 1.1.1 | W3C Understanding WCAG 2.0](https://www.w3.org/TR/2016/NOTE-UNDERSTANDING-WCAG20-20161007/text-equiv-all.html) +- [Understanding Success Criterion 1.1.1 | W3C Understanding WCAG 2.0](https://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html) Additionally, it is important to ensure that the contrast ratio between the background image and the foreground text is high enough that people with low vision can read the page content. diff --git a/files/en-us/web/css/background/index.md b/files/en-us/web/css/background/index.md index d6d97c288bba8e1..3c5748b883d4c23 100644 --- a/files/en-us/web/css/background/index.md +++ b/files/en-us/web/css/background/index.md @@ -101,7 +101,7 @@ background: repeat scroll 0% 0% / auto padding-box border-box none transparent; Browsers do not provide any special information on background images to assistive technology. This is important primarily for screen readers, as a screen reader will not announce its presence and therefore convey nothing to its users. If the image contains information critical to understanding the page's overall purpose, it is better to describe it semantically in the document. - [MDN Understanding WCAG, Guideline 1.1 explanations](/en-US/docs/Web/Accessibility/Understanding_WCAG/Perceivable#guideline_1.1_—_providing_text_alternatives_for_non-text_content) -- [Understanding Success Criterion 1.1.1 | W3C Understanding WCAG 2.0](https://www.w3.org/TR/2016/NOTE-UNDERSTANDING-WCAG20-20161007/text-equiv-all.html) +- [Understanding Success Criterion 1.1.1 | W3C Understanding WCAG 2.0](https://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html) ## Examples diff --git a/files/en-us/web/css/border-image/index.md b/files/en-us/web/css/border-image/index.md index fcb6d6185c55d65..d752790b70d4017 100644 --- a/files/en-us/web/css/border-image/index.md +++ b/files/en-us/web/css/border-image/index.md @@ -70,7 +70,7 @@ The `border-image` property may be specified with anywhere from one to five of t Assistive technology cannot parse border images. If the image contains information critical to understanding the page's overall purpose, it is better to describe it semantically in the document. - [MDN Understanding WCAG, Guideline 1.1 explanations](/en-US/docs/Web/Accessibility/Understanding_WCAG/Perceivable#guideline_1.1_—_providing_text_alternatives_for_non-text_content) -- [Understanding Success Criterion 1.1.1 | Understanding WCAG 2.0](https://www.w3.org/TR/2016/NOTE-UNDERSTANDING-WCAG20-20161007/text-equiv-all.html) +- [Understanding Success Criterion 1.1.1 | Understanding WCAG 2.0](https://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html) ## Formal definition diff --git a/files/en-us/web/css/content/index.md b/files/en-us/web/css/content/index.md index 6002e086eef2aee..5b003c03d2d1d20 100644 --- a/files/en-us/web/css/content/index.md +++ b/files/en-us/web/css/content/index.md @@ -136,7 +136,7 @@ If inserted content is not decorative, check that the information is provided to - [Accessibility support for CSS generated content – Tink](https://tink.uk/accessibility-support-for-css-generated-content/) (2015) - [WCAG, Guideline 1.3: Create content that can be presented in different ways](/en-US/docs/Web/Accessibility/Understanding_WCAG/Perceivable#guideline_1.3_—_create_content_that_can_be_presented_in_different_ways) - [Understanding Success Criterion 1.3.1 | W3C Understanding WCAG 2.0](https://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.html) -- [Failure of Success Criterion 1.3.1: inserting non-decorative generated content](https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/F87) Techniques for WCAG 2.0 +- [Failure of Success Criterion 1.3.1: inserting non-decorative generated content](https://www.w3.org/TR/WCAG20-TECHS/F87) Techniques for WCAG 2.0 ## Examples diff --git a/files/en-us/web/css/cross-fade/index.md b/files/en-us/web/css/cross-fade/index.md index 686f4d76195d0be..663de2969ad5ee2 100644 --- a/files/en-us/web/css/cross-fade/index.md +++ b/files/en-us/web/css/cross-fade/index.md @@ -97,7 +97,7 @@ If the image contains information critical to understanding the page's overall p When using background images, make sure the contrast in color is great enough that any text is legible over the image as well as if the images are missing. - [MDN Understanding WCAG, Guideline 1.1 explanations](/en-US/docs/Web/Accessibility/Understanding_WCAG/Perceivable#guideline_1.1_—_providing_text_alternatives_for_non-text_content) -- [Understanding Success Criterion 1.1.1 | W3C Understanding WCAG 2.0](https://www.w3.org/TR/2016/NOTE-UNDERSTANDING-WCAG20-20161007/text-equiv-all.html) +- [Understanding Success Criterion 1.1.1 | W3C Understanding WCAG 2.0](https://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html) ## Formal syntax diff --git a/files/en-us/web/css/gradient/conic-gradient/index.md b/files/en-us/web/css/gradient/conic-gradient/index.md index 67b6c411fabd7fa..35594e77a05ffcb 100644 --- a/files/en-us/web/css/gradient/conic-gradient/index.md +++ b/files/en-us/web/css/gradient/conic-gradient/index.md @@ -124,7 +124,7 @@ And, yes, you can mix and match different angle units, but don't. The above is h Browsers do not provide any special information on background images to assistive technology. This is important primarily for screen readers, as a screen reader will not announce its presence and therefore convey nothing to its users. While it is possible to create pie charts, checkerboards, and other effects with conic gradients, CSS images provide no native way to assign alternative text, and therefore the image represented by the conic gradient will not be accessible to screen reader users. If the image contains information critical to understanding the page's overall purpose, it is better to describe it semantically in the document. - [MDN Understanding WCAG, Guideline 1.1 explanations](/en-US/docs/Web/Accessibility/Understanding_WCAG/Perceivable#guideline_1.1_—_providing_text_alternatives_for_non-text_content) -- [Understanding Success Criterion 1.1.1 | W3C Understanding WCAG 2.0](https://www.w3.org/TR/2016/NOTE-UNDERSTANDING-WCAG20-20161007/text-equiv-all.html) +- [Understanding Success Criterion 1.1.1 | W3C Understanding WCAG 2.0](https://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html) ## Examples diff --git a/files/en-us/web/css/gradient/repeating-conic-gradient/index.md b/files/en-us/web/css/gradient/repeating-conic-gradient/index.md index 9b5dcedab0da99b..be770ed7c65f4b3 100644 --- a/files/en-us/web/css/gradient/repeating-conic-gradient/index.md +++ b/files/en-us/web/css/gradient/repeating-conic-gradient/index.md @@ -108,7 +108,7 @@ While you can mix and match different angle units, don't. It makes CSS hard to r Browsers do not provide any special information on background images to assistive technology. This is important primarily for screen readers, as a screen reader will not announce its presence and therefore convey nothing to its users. While it is possible to create pie charts, checkerboards, and other effects with conic gradients, CSS images provide no native way to assign alternative text, and therefore the image represented by the conic gradient will not be accessible to screen reader users. If the image contains information critical to understanding the page's overall purpose, it is better to describe it semantically in the document. - [MDN Understanding WCAG, Guideline 1.1 explanations](/en-US/docs/Web/Accessibility/Understanding_WCAG/Perceivable#guideline_1.1_—_providing_text_alternatives_for_non-text_content) -- [Understanding Success Criterion 1.1.1 | W3C Understanding WCAG 2.0](https://www.w3.org/TR/2016/NOTE-UNDERSTANDING-WCAG20-20161007/text-equiv-all.html) +- [Understanding Success Criterion 1.1.1 | W3C Understanding WCAG 2.0](https://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html) ## Examples diff --git a/files/en-us/web/css/image/image-set/index.md b/files/en-us/web/css/image/image-set/index.md index b5a25ea0ea51542..c28d2c155712046 100644 --- a/files/en-us/web/css/image/image-set/index.md +++ b/files/en-us/web/css/image/image-set/index.md @@ -60,7 +60,7 @@ image-set( Browsers do not provide any special information on background images to assistive technology. This is important primarily for screen readers, as a screen reader will not announce its presence and therefore convey nothing to its users. If the image contains information critical to understanding the page's overall purpose, it is better to describe it semantically in the document. - [MDN Understanding WCAG, Guideline 1.1 explanations](/en-US/docs/Web/Accessibility/Understanding_WCAG/Perceivable#guideline_1.1_—_providing_text_alternatives_for_non-text_content) -- [Understanding Success Criterion 1.1.1 | W3C Understanding WCAG 2.0](https://www.w3.org/TR/2016/NOTE-UNDERSTANDING-WCAG20-20161007/text-equiv-all.html) +- [Understanding Success Criterion 1.1.1 | W3C Understanding WCAG 2.0](https://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html) ## Examples diff --git a/files/en-us/web/css/image/image/index.md b/files/en-us/web/css/image/image/index.md index ff0dd3f310f130b..dc2cca8648cc049 100644 --- a/files/en-us/web/css/image/image/index.md +++ b/files/en-us/web/css/image/image/index.md @@ -85,7 +85,7 @@ The size of the color swatch can be set with the {{CSSxRef("background-size")}} Browsers do not provide any special information on background images to assistive technology. This is important primarily for screen readers, as a screen reader will not announce its presence and therefore convey nothing to its users. If the image contains information critical to understanding the page's overall purpose, it is better to describe it semantically in the document. - [MDN Understanding WCAG, Guideline 1.1 explanations](/en-US/docs/Web/Accessibility/Understanding_WCAG/Perceivable#guideline_1.1_—_providing_text_alternatives_for_non-text_content) -- [Understanding Success Criterion 1.1.1 | W3C Understanding WCAG 2.0](https://www.w3.org/TR/2016/NOTE-UNDERSTANDING-WCAG20-20161007/text-equiv-all.html) +- [Understanding Success Criterion 1.1.1 | W3C Understanding WCAG 2.0](https://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html) This feature can help improve accessibility by providing a fallback color when an image fails to load. While this can and should be done by including a background-color on every background image, the CSS `image()` function allows adding allows only including background colors should an image fail to load, which means you can add a fall back color should a transparent PNG/GIF/WebP not load. diff --git a/files/en-us/web/css/image/index.md b/files/en-us/web/css/image/index.md index 2ef9e889d500e08..fd7ca48ad73a6b2 100644 --- a/files/en-us/web/css/image/index.md +++ b/files/en-us/web/css/image/index.md @@ -58,7 +58,7 @@ The concrete object size is calculated using the following algorithm: Browsers do not provide any special information on background images to assistive technology. This is important primarily for screen readers, as a screen reader will not announce its presence and therefore convey nothing to its users. If the image contains information critical to understanding the page's overall purpose, it is better to describe it semantically in the document. - [MDN Understanding WCAG, Guideline 1.1 explanations](/en-US/docs/Web/Accessibility/Understanding_WCAG/Perceivable#guideline_1.1_—_providing_text_alternatives_for_non-text_content) -- [Understanding Success Criterion 1.1.1 | W3C Understanding WCAG 2.0](https://www.w3.org/TR/2016/NOTE-UNDERSTANDING-WCAG20-20161007/text-equiv-all.html) +- [Understanding Success Criterion 1.1.1 | W3C Understanding WCAG 2.0](https://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html) ## Formal syntax diff --git a/files/en-us/web/css/named-color/index.md b/files/en-us/web/css/named-color/index.md index 0b8ca97203ea259..d0ad4518fdda630 100644 --- a/files/en-us/web/css/named-color/index.md +++ b/files/en-us/web/css/named-color/index.md @@ -887,7 +887,7 @@ In addition to these 16 colors, about 150 other colors have a keyword associated -Initially, in [CSS Level 1](https://www.w3.org/TR/REC-CSS1/#color-units), only 16 basic colors were defined, with `orange` added in [CSS Level 2](https://www.w3.org/TR/CSS2/syndata.html#value-def-color). Web designers found this list too short, and browser vendors added numerous names for colors based on the X11 color names. In [SVG 1.0](https://www.w3.org/TR/2001/REC-SVG-20010904/), then in [CSS Colors Level 3](https://www.w3.org/TR/css-color-3/#svg-color), these names got standardized, formally defined, and made uniform (some had different spellings that are now aliases). They are called _extended color keywords_, _X11 colors_, or _SVG colors_. +Initially, in [CSS Level 1](https://www.w3.org/TR/REC-CSS1/#color-units), only 16 basic colors were defined, with `orange` added in [CSS Level 2](https://www.w3.org/TR/CSS2/syndata.html#value-def-color). Web designers found this list too short, and browser vendors added numerous names for colors based on the X11 color names. In [SVG 1](https://www.w3.org/TR/SVG11/types.html#DataTypeColor), then in [CSS Colors Level 3](https://www.w3.org/TR/css-color-3/#svg-color), these names got standardized, formally defined, and made uniform (some had different spellings that are now aliases). They are called _extended color keywords_, _X11 colors_, or _SVG colors_. In [CSS Colors Level 4](https://www.w3.org/TR/css-color-4/#named-colors), an additional color, `rebeccapurple` was added to honor [web pioneer Eric Meyer](https://meyerweb.com/eric/thoughts/2014/06/19/rebeccapurple/). diff --git a/files/en-us/web/svg/attribute/accumulate/index.md b/files/en-us/web/svg/attribute/accumulate/index.md index 32c13cd95f1a096..11af530c4bfc519 100644 --- a/files/en-us/web/svg/attribute/accumulate/index.md +++ b/files/en-us/web/svg/attribute/accumulate/index.md @@ -51,4 +51,4 @@ This attribute will be ignored if the animation function is specified with only ## See also -- [SMIL Animation specification](https://www.w3.org/TR/2001/REC-smil-animation-20010904/#AccumulateAttribute) +- [SVG animation with SMIL](/en-US/docs/Web/SVG/SVG_animation_with_SMIL) diff --git a/files/en-us/web/svg/attribute/additive/index.md b/files/en-us/web/svg/attribute/additive/index.md index 42580db33bf9cca..ea29f363cfc30b2 100644 --- a/files/en-us/web/svg/attribute/additive/index.md +++ b/files/en-us/web/svg/attribute/additive/index.md @@ -39,7 +39,7 @@ You can use this attribute with the following SVG elements: - sum - : Specifies that the animation will add to the underlying value of the attribute and other lower priority animations. - replace - - : Specifies that the animation will override the underlying value of the attribute and other lower priority animations. This is the default, however the behavior is also affected by the animation value attributes {{SVGAttr("by")}} and {{SVGAttr("to")}}, as described in [SMIL Animation: How from, to and by attributes affect additive behavior](https://www.w3.org/TR/2001/REC-smil-animation-20010904/#FromToByAndAdditive). + - : Specifies that the animation will override the underlying value of the attribute and other lower priority animations. This is the default, however the behavior is also affected by the animation value attributes {{SVGAttr("by")}} and {{SVGAttr("to")}}, as described in [SMIL Animation: How from, to and by attributes affect additive behavior](https://www.w3.org/TR/smil-animation/#FromToByAndAdditive). ## Specifications @@ -47,4 +47,4 @@ You can use this attribute with the following SVG elements: ## See also -- [SMIL Animation specification](https://www.w3.org/TR/2001/REC-smil-animation-20010904/#AdditiveAttribute) +- [SVG animation with SMIL](/en-US/docs/Web/SVG/SVG_animation_with_SMIL) diff --git a/files/en-us/web/svg/attribute/attributename/index.md b/files/en-us/web/svg/attribute/attributename/index.md index 675b6ca8a7133c7..9d368172e85d9a9 100644 --- a/files/en-us/web/svg/attribute/attributename/index.md +++ b/files/en-us/web/svg/attribute/attributename/index.md @@ -69,4 +69,4 @@ svg { ## See also -- [SMIL Animation specification](https://www.w3.org/TR/2001/REC-smil-animation-20010904/#AccumulateAttribute) +- [SVG animation with SMIL](/en-US/docs/Web/SVG/SVG_animation_with_SMIL) diff --git a/files/en-us/web/svg/attribute/attributetype/index.md b/files/en-us/web/svg/attribute/attributetype/index.md index e12488b5ee51137..00449e4205c4e56 100644 --- a/files/en-us/web/svg/attribute/attributetype/index.md +++ b/files/en-us/web/svg/attribute/attributetype/index.md @@ -75,4 +75,4 @@ svg { ## See also -- [SMIL Animation specification](https://www.w3.org/TR/2001/REC-smil-animation-20010904/#AccumulateAttribute) +- [SVG animation with SMIL](/en-US/docs/Web/SVG/SVG_animation_with_SMIL) diff --git a/files/en-us/web/svg/attribute/begin/index.md b/files/en-us/web/svg/attribute/begin/index.md index 9d653f9c9e2bebd..59d653d4e22a170 100644 --- a/files/en-us/web/svg/attribute/begin/index.md +++ b/files/en-us/web/svg/attribute/begin/index.md @@ -9,7 +9,7 @@ spec-urls: https://svgwg.org/specs/animations/#BeginAttribute The **`begin`** attribute defines when an animation should begin. -The attribute value is a semicolon separated list of values. The interpretation of a list of start times is detailed in the SMIL specification in ["Evaluation of begin and end time lists"](https://www.w3.org/TR/2001/REC-smil-animation-20010904/#Timing-EvaluationOfBeginEndTimeLists). Each individual value can be one of the following: ``, ``, ``, ``, ``, `` or the keyword `indefinite`. +The attribute value is a semicolon separated list of values. The interpretation of a list of start times is detailed in the SMIL specification in ["Evaluation of begin and end time lists"](https://www.w3.org/TR/smil-animation/#Timing-EvaluationOfBeginEndTimeLists). Each individual value can be one of the following: ``, ``, ``, ``, ``, `` or the keyword `indefinite`. You can use this attribute with the following SVG elements: @@ -412,3 +412,7 @@ _This example is embedded in an iFrame. If you want to activate the key events, ## Specifications {{Specifications}} + +## See also + +- [SVG animation with SMIL](/en-US/docs/Web/SVG/SVG_animation_with_SMIL) diff --git a/files/en-us/web/svg/attribute/calcmode/index.md b/files/en-us/web/svg/attribute/calcmode/index.md index 930e8e0510d602c..a12a4a4d2519406 100644 --- a/files/en-us/web/svg/attribute/calcmode/index.md +++ b/files/en-us/web/svg/attribute/calcmode/index.md @@ -54,4 +54,4 @@ You can use this attribute with the following SVG elements: ## See also -- [SMIL Animation specification](https://www.w3.org/TR/2001/REC-smil-animation-20010904/#AccumulateAttribute) +- [SVG animation with SMIL](/en-US/docs/Web/SVG/SVG_animation_with_SMIL) diff --git a/files/en-us/web/svg/attribute/href/index.md b/files/en-us/web/svg/attribute/href/index.md index f4760f7fce7422f..f97f67dcbc2f0ae 100644 --- a/files/en-us/web/svg/attribute/href/index.md +++ b/files/en-us/web/svg/attribute/href/index.md @@ -100,7 +100,7 @@ If the `href` attribute or the deprecated {{SVGAttr("xlink:href")}} attribute is Refer to the descriptions of the individual animation elements for any restrictions on what types of elements can be targets of particular types of animations. -Except for any SVG-specific rules explicitly mentioned in this specification, the normative definition for this attribute is the {{Glossary("SMIL")}} Animation specification. In particular, see [SMIL Animation: Specifying the animation target](https://www.w3.org/TR/2001/REC-smil-animation-20010904/#SpecifyingAnimationTarget). +Except for any SVG-specific rules explicitly mentioned in this specification, the normative definition for this attribute is the {{Glossary("SMIL")}} Animation specification. In particular, see [SMIL Animation: Specifying the animation target](https://www.w3.org/TR/smil-animation/#SpecifyingAnimationTarget). diff --git a/files/en-us/web/svg/content_type/index.md b/files/en-us/web/svg/content_type/index.md index 71317eb63184d45..ed278c788b9718d 100644 --- a/files/en-us/web/svg/content_type/index.md +++ b/files/en-us/web/svg/content_type/index.md @@ -42,13 +42,13 @@ SVG makes use of a number of data types. This article lists these types along wi anything ::= Char* ``` - where [Char](https://www.w3.org/TR/2008/REC-xml-20081126/#NT-Char) is the production for a character, as defined in XML 1.0, section 2.2. + where Char is any valid non-control Unicode character. ## Clock-value - \ - - : Clock values have the same syntax as in [SMIL Animation](https://www.w3.org/TR/2001/REC-smil-animation-20010904/) specification. The grammar for clock values is repeated here: + - : Clock values have the same syntax as in [SMIL Animation](https://www.w3.org/TR/smil-animation/#Timing-ClockValueSyntax) specification. The grammar for clock values is repeated here: ```plain Clock-val ::= Full-clock-val | Partial-clock-val @@ -92,23 +92,7 @@ SVG makes use of a number of data types. This article lists these types along wi - : The basic type \ is a CSS2 compatible specification for a color in the sRGB color space. \ applies to SVG's use of the {{SVGAttr("color")}} attribute and is a component of the definitions of attributes {{SVGAttr("fill")}}, {{SVGAttr("stroke")}}, {{SVGAttr("stop-color")}}, {{SVGAttr("flood-color")}}, and {{SVGAttr("lighting-color")}}, which also offer optional ICC-based color specifications. - SVG supports all of the syntax alternatives for \ defined in [CSS2 syntax and basic data types](https://www.w3.org/TR/2008/REC-CSS2-20080411/syndata.html#value-def-color), and (depend on the implementation) in the future [CSS Color Module Level 3](https://www.w3.org/TR/css-color-3/). - - A \ is either a keyword or a numerical RGB specification. - - In addition to these color keywords, users may specify keywords that correspond to the colors used by objects in the user's environment. The normative definition of these keywords is found in [User preferences for colors](https://www.w3.org/TR/2008/REC-CSS2-20080411/ui.html#system-colors) (CSS2, section 18.2). - - The format of an RGB value in hexadecimal notation is a `#` immediately followed by either three or six hexadecimal characters. The three-digit RGB notation (`#rgb`) is converted into six-digit form (`#rrggbb`) by replicating digits, not by adding zeros. For example, `#fb0` expands to `#ffbb00`. This ensures that white (`#ffffff`) can be specified with the short notation (`#fff`) and removes any dependencies on the color depth of the display. The format of an RGB value in the functional notation is an RGB start-function, followed by a comma-separated list of three numerical values (either three integer values or three percentage values) followed by `)`. An RGB start-function is the case-insensitive string `rgb(`, for example `RGB(` or `rGb(`. For compatibility, the all-lowercase form `rgb(` is preferred. The integer value `255` corresponds to `100%`, and to `F` or `FF` in the hexadecimal notation: `rgb(255 255 255)` = `rgb(100% 100% 100%)` = `#FFF`. White space characters are allowed around the numerical values. All RGB colors are specified in the sRGB color space. Using sRGB provides an unambiguous and objectively measurable definition of the color, which can be related to international standards. - - ```plain - color ::= "#" hexdigit hexdigit hexdigit (hexdigit hexdigit hexdigit)? - | "rgb("integer integer integer")" - | "rgb("integer "%" integer "%" integer "%)" - | color-keyword - hexdigit ::= [0-9A-Fa-f] - ``` - - where `color-keyword` matches (case insensitively) one of the color keywords listed in [CSS Color Module Level 3](https://www.w3.org/TR/css-color-3/), or one of the system color keywords listed in [User preferences for colors](https://www.w3.org/TR/2008/REC-CSS2-20080411/ui.html#system-colors) (CSS2, section 18.2). + The definition of \ in SVG is exactly the same as the CSS {{cssxref("color_value", "<color>")}} definition. ## Coordinate