Fix broken links in HTML accessibility API Mappings 1.0 (#447) #555
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This update addresses and fixes broken references found in the HTML Accessibility API Mappings 1.0 specification. Specifically, the following changes have been made:
param
attribute: Replaced the incorrect link to theparam
attribute documentation with the correct one.itemprop
attribute: Corrected the link pointing to theitemprop
attribute section in the microdata specification.sectioning-root
: Updated the link to the correct section in the HTML specification for sectioning root elements.Details:
https://html.spec.whatwg.org/multipage/iframe-embed-object.html#attr-param-name
https://html.spec.whatwg.org/multipage/microdata.html#attr-itemprop
https://html.spec.whatwg.org/multipage/sections.html#sectioning-root
Implementation:
Closes: #447
@arbaz686
💥 Error: 500 Internal Server Error 💥
PR Preview failed to build. (Last tried on Aug 2, 2024, 6:57 AM UTC).
More
PR Preview relies on a number of web services to run. There seems to be an issue with the following one:
🚨 Spec Generator - Spec Generator is the web service used to build specs that rely on ReSpec.
🔗 [Related URL]([object Object])
If you don't have enough information above to solve the error by yourself (or to understand to which web service the error is related to, if any), please file an issue.