Adjusted some tags to reflect the W3C standards #911
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
I made adjustments to the landing page to align with W3C standards. This included adding a doctype declaration, tag with a lang attribute, and removing the frameborder attribute from the iframe.
Motivation
The motivation behind these changes was to ensure compliance with web standards and improve the overall quality and accessibility of the landing page. By adhering to W3C standards:
The page becomes more interoperable across different browsers and devices.
It enhances accessibility for users with disabilities, ensuring they can access and navigate the content effectively.
Following best practices promotes better SEO performance, potentially improving search engine rankings.
Removal of deprecated attributes like frameborder in iframes ensures compatibility with modern web standards and future-proofing the codebase.
Testing
The changes have been thoroughly tested locally to ensure they render correctly in various browsers and devices. Additionally, I have validated the modifications using online HTML validation tools to confirm adherence to standards.