WCA protocol Improved : Covering Issue #859 and #858 #934
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
barchakuz
changed the title
|
Please make your forks based off of develop if you can. |
@birm sorry, could you please bit elobrate it, i have created seprate branch for each task to implement it. |
|
This PR is stale because it has been open 45 days with no activity. |
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
In this pull request, I address the issue of inaccessible pages that cannot be accessed directly, thus improving compliance with Web Content Accessibility (WCA) standards. The pages that were previously inaccessible are now made accessible through various enhancements.
Motivation
To improve google search engine ranking.
Testing
Test done using Web accessability evaluation powered by WebAIM tools
##screenshot
