Sweet chilli chicken

Things init

• Carrot
• Cucumber
• Spring onion
• Radish
• Beansprouts
• Red chilli
• Toasted sesame oil
• Walnut oil
• Cajun spice
• Sweet chilli sauce

What you gotta do to make it

1. Cut cucumber, carrot and spring onion into match sticks
2. Lightly fry beansprouts and carrot to remove crunch
3. Add to the spring onion, chilli, radish and cucumber and mix with 1 teaspoon of toasted sesame oil
4. Add cajun spice to chicken, cover with a small dab of walnut oil and grill until cooked
5. Place over salad and drizzle with sweet chilli sauce

Who’s recipe is it?

Good housekeeping – chicken

POUR Principles of Web Accessibility

The POUR Principles of accessibility: Perceivable, Operable, Understandable and Robust form the foundation of the Web Accessibility Guidelines (WCAG) 2.0.

Perceivable

As a minimum requirement for accessibility people need to be able to perceive – that is see, hear or touch web content. Information that cannot reach the brain is inaccessible. There are four guidelines under this principle:

• Text alternatives – known as ‘alt’ text. All non-text content such as images must be provided with alt text. This text can be converted into different formats such as audio or Braille as required. The alt text should be meaningful, descriptive and reflect the purpose of the image. If the image does not convey meaning and is purely for decoration, you can specify an empty or null text for screen readers to avoid unnecessary clutter.
• Time based media - Time based means it runs over time like audio or video, rather than static content such as images and text. Audio content requires an alternative description for users with hearing impairments. This could be in the form of captions synchronized with the media. Video content that contains more than just dialogue, such as an action sequence would need an alternative text transcript or audio description so those with visual impairments can understand and make sense of the change in events. A text transcript is the minimum required for multimedia content to be made accessible.
• Adaptable – People with disabilities often need to change the way the information is presented to them, so it is easier to perceive and understand. E.g A dyslexic user may want to have the page read out to them via text or might want to change the colours and text size so that it is easier to read and understand. Web pages should be coded semantically using headers, lists and paragraphs to add a logical, non-visual structure to the page.
• Distinguishable – It’s important not to rely on colour alone to convey information. For instance, don’t rely on colour as the only way to distinguish segments in a pie chart, don’t start audio or video on a page automatically unless you provide a way of turning it off. Screen reader users may find it difficult to hear the speech output of their software if audio or video is playing at the same time.

Operable

Users should be able to find, navigate through and interact with web content such as forms and menus using a range of input methods and assistive technologies. There are four guidelines under this principle:

• Keyboard Accessible - Some people with mobility impairments and some people who use screen readers only use a keyboard to navigate a website. Keyboard users typically tab through a web page to interact with links, jump to the next question on a form and interaction with other controls. Websites that are not accessible with a keyboard only results in users getting stuck at a particular point on the site and cannot navigate back or forward. They then have to close the page and start again, this is very frustrating. This is often found with flash content such as a media player.
• Enough time - Some users will require longer than others to perform tasks on a website so it is important to give users enough time or adjust the flexibility of time required for tasks. For example, extending or doubling the duration of timeout.Content that moves or auto updates can cause problems for those who read stationary text slowly, or anyone who has trouble tracking moving objects. Blinking or scrolling content that lasts longer than five seconds should include the ability to pause, stop or be hidden by the user.
• Seizures - It is important that websites do not contain any features that flash or flicker more frequently than 3 times a second to avoid the risk of causing seizures for those with photosensitive epilepsy. PEAT, an online photosensitive epilepsy analysis tool can be used to test flashing or content that flickers.
• Navigable – Users should be able to easily navigate around a web page. Users should also be able to bypass or skip large blocks of content with the help of skip links. The focus order of links as you tab through a page should be logical and not jump around the page. Visual should be used to identify the current tab position. Screen readers often have problems with hyperlinks that do not make sense by them selves. At a minimum it should be possible to work out from the context of the link where it will take you. There for avoid using link phrases such as ‘click here’ or ‘more’, instead make them more descriptive.

Understandable

All web content should make sense and its behavior should be predictable. In addition any feedback provided about errors should be clear and helpful. There are three guidelines under this principle:

• Readable – Ensure the site is readable and understood and ensure it is coded using the right HTML language, such as English, French or Spanish. The language can be set for the whole page or part of a page, for example when a quote is used from another language. Screen Readers rely on the correct code language being used so they can use the correct speech engine to read out.
• Predictable – Ensuring pages are predictable helps users with visual disabilities, cognitive and motor impairments. When navigating through web pages it reduces the chance that a change of context will occur unexpectedly and cause confusion. Ensure elements are in the same place on each page and place elements where users would expect to see them – for instance your logo should be top left on every page and the search top right. Don’t allow changes to happen when tabbing of focusing on elements such as submitting data on a form submit button when the user tabs onto the submit button. Another example is when a form refreshes without warning. This is confusing for a screen reader user as they are sent back to the start of the page. Warning users of change will mean they will be less disorientated.
• Input Assistance – People with disabilities may be more likely to make mistakes when inputting information and at the same time it can be harder for them to detect an error. It is important to provide accessible input assistance such as error messages to avoid and then help them correct mistakes. Form errors, ideally should be marked with strong red text and ideally a hazard or warning symbol. Form fields should provide clear labels, cues and instructions providing enough guidance so users know what to do. If mistakes are made provide clear, helpful instruction on how to correct them as the nature of the error may not be obvious to people with visual or learning disabilities.

Robust

People use different operating systems, browsers and versions of browsers yet despite these different technologies they call expect the web to work. There is one guideline to this principle:

• Compatible – To maximize compatibility use good quality code that adheres to web standards such as the WC3, HTML and XHTML standards. Ensure that the code is checked against validation tools, errors are fixed and ensure multimedia movies such as Flash have descriptive labels associated with them.

Chorizo & Cherry Tomato

Things init

• Chorizo
• Cherry tomatoes
• New potatoes
• Sherry
• Red pepper
• Garlic
• White onion
• Paprika
• Chopped parsley
• Rice and bread to serve

What you gotta do to make it

1) Cut and par-boil potatoes then fry until they begin to color

2) Add the onion and fry until soft

3) Add the chorizo, garlic and red pepper and cook until chorizo begins to color

4) Add the sherry, tomatoes and paprika and reduce sherry by half

5) Sprinkle with chopped parsley and serve with rice and crusty bread

Who’s recipe is it?

Good Housekeeping – One Pot

Chorizo Hash

Things init

• Chorizo
• Baby Potatoes
• White Onion
• Garlic
• Paprika
• Seasoning
• Parsley

What you gotta do to make it

1) Cut the potatoes into small cubes and boil for 15min or until soft

2) Fry the onion on low heat until soft and not brown

3) Add the chorizo, garlic and paprika and cook until golden

4) Add the potatoes and cook until they begin to brown

5) Crack a couple of eggs over and cook in the oven until eggs are cooked

6) Sprinkle with parsley

Who’s recipe is it

Jamie Oliver

Web Accessibility: BS 8878

BS 8878 is the British Standard for web accessibility introduced in 2010.

The British Standard BS 8878 is not another WCAG (Website Content Accessibility Guideline) but recommends that the WCAG 2.0 is used in the creation of websites or web product.

BS 8878 is about putting the user centred approach, now recognised as the key of creating a successful website, at the heart of accessibility.

The British Standard BS 8878 provides a framework for organisation to ensure their web products are accessible. This framework includes creating policies and procedures and involving disabled people in developing and testing.

BS 8878 provides a 16 step process for creating accessible web products which are covered under six stages:

Stage 1: Requirements Gathering

The requirements gathering stage involves conducting the right research and thinking before launching into the development of the web product, such as defining the purpose of the web product and its users while targeting their needs.

Stage 2: Strategic Decision

The strategic decision stage involves strategic decision making based on the findings in the requirements gathering stage, such as what degrees of user experience you want to web product to meet and what browser, OS (Operating System) and AT (Assistive Technology) you want to support.

Stage 3: Production

The production process involves choosing the development technologies you will use to build your web product and select the appropriate accessibility guidelines.

Stage 4: Accessibility Insurance (Testing Plan)

This stage requires you to create and implement an accessibility testing plan. An accessibility test plan may often take the form of a flow chart, starting with identifying the route a user will take within your web product, the challenges they may face and resolving those challenges. Disabled or abled users can be included for live testing during the test plan process.

Stage 5: Communication

In the communication stage you create an accessibility statement for the web product to communicate what you have done to make the website more accessible.

Stage 6: Maintenance and Review

Lastly, the maintenance and review stage involves making continuous accessibility improvements based on user feedback and technological changes.

Further Information

Further information on BS 8878 can be found here:

http://www.hassellinclusion.com/bs8878/#content