A pattern portfolio acts as a reference, not only for developers but for anyone working on the front-end of a website. It is a “living” body of front-end code and documentation for a website which is updated as and when a site develops during its lifetime.
All posts by Emily Coward
Text Resizing Tips
Tips for making sure people can resize the text on your website with content becoming lost or obscured.
Developer tools to help check web accessibility
Three tips for using the web developer toolbar to help check for accessibility issues on your website.
Movement on a website: 5 things to consider
Websites are all about getting people to find and interact with content as quickly as possible. But how do you encourage people to engage with certain pieces of content above others? Some websites choose to do this by adding movement to the content.
Keyboard accessibility quick tip
A quick accessibility tip to help you make sure your web pages aren't reliant on someone using just a mouse and can be operated by someone using a keyboard instead.
Accessible Tabs - Part 2: The Solution
As we saw in Accessible Tabs Part 1 - The Problem, there are several accessibility issues with tabs created for the web compared to those created for use in software applications. Tabs on the web should ideally replicate the functionality used in applications, so they are more intuitive for everyone. In this article we will look at three existing scripts for creating accessible tabs.
Accessible Tabs - Part 1: The Problem
Order of Content
The second installment from Nomensa's How To guides. Emily Coward, Senior Web Developer at Nomensa discusses the importance of making sure the order of content on a website is logical to ensure that it makes sense when it's read through from top to bottom by someone using a screen reader.
- 1 of 2
- Older Posts