General Accessibility Standards and requirements for interface

In this blog I will use the four principles to cover web general Accessibility Standards and their requirements.

 

Standard - Perceivable: 

The designer/developer must make sure the interface & content are easily perceived

Requirements

1.     Add text alternatives for all non-text items so users can use others options for perceiving such as braille or speech output devices.

2.     Give ability to pause or slow time-based media

3.     Make sure your code allows your content to be presented in different ways without losing information or detail

4.     Use clear layout so it is easier to see & distinguish content on the page. (eg foreground & background)

5.     Any information conveyed with colour is also conveyed without colour 

6.     Add to frames a title so as to identify & navigate it

7.     If unable to comply with accessibility standards then provide a text only page with all same information, they will need to be updated at the same time.

8.     The page must contain a way of skipping repetitive links

 

Standard - Operable:

Ensure layout of page & ability to use navigation must be available to as many people as possible including those with disabilities

Requirements

1.     Code it to have full keyboard function

2.     Use a client-side site map so users can easily navigate & find their location in the site.

3.     Make sure to give users enough time to read, understand & use content on the site.

4.     Don’t use flashing in text or images with frequency >2 Hz & < 55 Hz or high pitch frequencies in audio as these may induce seizures.

5.     Provide usability through various inputs other than keyboard.

6.     Any documents should be made readable without associated style sheet.

7.     If using an online form ensure to provide access to the fields & submission by assistive technology

8.     If using scripting for content or elements then this information needs to be identified with functional text that can be read by assistive devices

9.     If the page/interface requires the user to have a plug-in or app to utilize it then the page/interface must contain a link to the product.

 

Standard - Understandable: 

you must ensure that the interface can understood by majority users

Requirements:

1.     Use clear & simple language, explain any complicated, unusual, foreign, or made up words that you have used

2.     Use a clear layout on pages & have them behave in predictable ways.

3.     Make it simple for the user to go back if they need to fix a mistake.

4.     Tables should have Row & column headers

 

Standard - Robust: 

ensure that the interface can be accessed by Multiple browsers & multiple assistive devices

Requirements:

ensure you update the interface to the most available compatibility levels across the board so that it will be compatible with future technologies.

 

Reference Websites

·       https://www.w3.org/WAI/people-use-web/abilities-barriers/

·       https://usability.yale.edu/web-accessibility/articles/types-disabilities

·       https://accessibletech.org/accessibility-standards/

·       https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards

·       https://buyict4all.org/ict-accessibility-standard

·       https://buyict4all.org/ict-accessibility-standard/web-content-accessibility-guidelines-wcag-2-1

·       https://www.etsi.org/deliver/etsi_en/301500_301599/301549/01.01.01_60/en_301549v010101p.pdf

·       https://www.accessibility.org.au/guides/what-is-the-wcag-standard/

·       https://en.wikipedia.org/wiki/Web_Content_Accessibility_Guidelines

·       https://www.w3.org/WAI/WCAG21/quickref/?versions=2.0

·       https://buyict4all.org/ict-accessibility-standard/introduction-to-the-en-301-549

·       https://www.soswebdesign.com/gallery/webstandards.cfm

Comments

Post a Comment

Popular posts from this blog

my site and testing

I have started a recipe site it is only just started so very basic. here is a link to the site  https://mycook-recipes.000webhostapp.com there are many options for testing out there, you will find them listed on the following sites https://www.w3.org/WAI/ER/tools/ https://www.digitala11y.com/free-mobile-accessibility-testing-tools/ https://www.digitala11y.com/accessibility-plug-ins-ie-chrome-firefox-browsers/ https://dynomapper.com/blog/27-accessibility-testing/246-top-25-awesome-accessibility-testing-tools-for-websites these were the pages I looked through while looking at which I would use to check my sites accessibility. in testing my site I did multiple types of tests: 1. I validated it through the  w3c validator 2.  I  tested that it work the way  I   intened  in the browsers  I  have on my computer these include safari,  Firefox & chrome 3. I signed up to BrowserStack so as to check that it worked in other browsers that I...
Read more

Web users & accessibility requirements

Hi in this Blog I’m going to address different user groups with disabilities & their accessibility requirements in regards to using websites & search engines.   Each type of disabilities can vary in level from partial to minor to complete that impact the user’s ability to use web pages, search engines.   To aid in web accessibility for all there are a few code/design requirements we can implement to help these people use the website    For all groups whether with or without disabilities a website & search engines should use  Simple wording & Understandable language.   Visual Some of the visual conditions are: colour blindness, low vision, blindness. Requirements :  1.       Use  proper HTML mark-up for the site this will aid in the use of a   Screen reader or   Braille output device as the person can set it to just read out headings until they find what they want (allowing them to skip data they d...
Read more