Get Familiar with WCAG 2.1: WCAG 2.1 is like the rulebook for web accessibility. It's split into four parts: Perceivable, Operable, Understandable, and Robust (POUR). For instance, "Perceivable" includes rules like giving all images a text description (alt text) for folks who can't see them. Run an Accessibility Audit: Use tools like Google Lighthouse or WAVE to scan your site. They'll flag up stuff like missing alt text, low color contrast, or form fields without labels. Manual Testing: Automated tools can't catch everything. You'll need up roll to your sleeves and do some manual testing. Try navigating your site using only your keyboard, or using a screen reader like NVDA or VoiceOver. You're checking that all content and functionality is accessible. Write an Accessibility Statement: This is a page on your site where you talk about your commitment to accessibility. You could mention that you're aiming for WCAG 2.1 Level AA compliance, lis
Git Client
Installation:
For using command line, go to url https://git-scm.com/downloads and download the git client(Git Bash) for
windows.
For using windows GUI tool, go to url https://desktop.github.com/ and download the GIT Desktop tool for
windows.
Git Bash Usage:
For cloning remote repository to local repository(in your
windows machine), first set your present working directory to local repository
parent folder by using below command:
Command Syntax:
cd <working directory>
Example:
cd C://Users/123456/git repo
Then Use below command to clone:
Command Syntax:
git clone <git url for repo>
Example:
git clone https://github.com/jetway/Sitewide-frontend_VS.git
By default, it will be checked out to master branch.
Then in order to checkout to another feature branch which is
already created in remote repository in git server, below command needs to be
used.
Command Syntax:
git checkout <feature_branch>
Example:
git checkout APFI2_100
If remote repository don’t have the feature branch created,
then we can create new feature branch with below command:
Command Syntax:
git checkout -b <new feature branch> <reference
branch>
Example:
git checkout –b APFI2_100
master
If new feature branch is created locally which is not in
remote server, use below command to upload to remote repository for first time
so that there will be a mapping established between local and remote repository
for the feature branch:
Command Syntax:
git push --set-upstream origin <feature_branch>
Example:
git push --set-upstream origin APFI2_100
In order to know status at any time, below command needs to
be used:
Command Syntax:
git status
After making file changes in local machine, in order to add
the local changes to local repository below command needs to be used:
Command Syntax:
git add <file name>
Example:
git add Sample.java
After changes are finalized in local repository in order to
push the changes to staging, below command needs to be used:
Command Syntax:
git commit
Note: If many files are changed in local machine, then using
git add command all files can be added one after the other and finally one time
you can run the command “git commit”.
In order to push the changes from stating to remote
repository, below command needs to be used:
Command Syntax:
git push
For day to day work, in order to get latest code from a
branch from remote repository use below command:
Command Syntax:
git pull origin <branch_name>
Example:
git pull origin
APFI2_100
Before pulling the changes from remote repository to local
repository, if you want to preserve your local changes, then below command
needs to be used. This will keep your changes in a private virtual place for
later recovery:
Command Syntax:
git stash
In order to apply your stashed changes to your local file
system, below command needs to be used:
Command Syntax:
git stash apply
Below command is used for deleting local repository branch:
Command Syntax:
git branch -D <feature_branch>
Example:
git branch –D APFI2_100
Note: This will just delete the branch in your local
repository which is in your local machine. It will not delete the branch in
remote repository which is in git server.
Very important
thing to note:
You should not fork any of the Delta/Virgin Code from Jetway
organization to your public profile. If you click “Fork button” at the top
right of Github.com repo page, it will take a copy of the repo to your public
profile. It is a security violation. So you shouldn’t do it at any time.
Comments
Post a Comment