Accessibility best practices, device testing and SEO
- Using rems/ems instead of px so that the font scales in a uniform way for the webpage or app. So if the user was to change the font size for their browser to something smaller or bigger. All of the font on the website would scale in proportion. So it is very good for accessibility and people who have vision problems. The same applies to everything in the box model too like margin and padding.
- Using developer browser tools like google lighthouse and Accessibility Developer Tools, to audit for performance, accessibility, progressive web apps, and more
- Using buttons for performing actions and anchor tags for leading somewhere
- Using aria-label for buttons with icons as it allows screen readers to give an audio representation of what the button is. As people with disabilities might not be able to see the button clearly or at all
- Using flex box or css grid for tab order. Because if you use floats it breaks the positioning for tab order and keyboard accessibility which works from left to right. Or right to left if you are using a language like Arabic.
- Having an appropriate focused outline colour for focused html elements on a web page. The default colour is blue so if you have a blue button, you could change it to red. Or you could change it to another colour depending on the brand style of your website.
Device and Browser Testing
Use the built in Simulator App for simulating iOS devices
Use system preferences > display to scale the display resolution up and down
Make sure that its installed first
npm install -g lighthouse
# or use yarn:
# yarn global add lighthouse
Using the Node CLI
lighthouse --view https://www.google.com/
Replace the website address with whatever website you want to test
Use for testing apps running native
Use the Inspect Element
Use browser developer tools (React and Vue)
Use Responsive Design mode and the CSS Grid Layout Inspector in Firefox
Windows, Android and Linux
Bug and error tracking
SEO optimisation ideas