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 CHEAT SHEET STAGE & SNAPSHOT Working with snapshots and the Git staging area git status show modified files in working directory, staged for your next commit git add [file] add a file as it looks now to your next commit (stage) git reset [file] unstage a file while retaining the changes in working directory git diff diff of what is changed but not staged git diff --staged diff of what is staged but not yet committed git commit -m “[descriptive message]” commit your staged content as a new commit snapshot SETUP Configuring user information used across all local repositories git config --global user.name “[firstname lastname]” set a name that is identifiable for credit when review version history git config --global user.email “[valid-email]” set an email address that will be associated with each history marker git config --global color.ui auto set automatic command line coloring for Git for easy reviewing SETUP & INIT Configuring user information,...