Skip to main content

SCRUMble ! - New Book about SCRUM

 SCRUMble ! Hello Blog Readers! Thank you for all your support and encouragement. I have something exciting for you all. I have recently written and published a new book called 'SCRUMble !'. It is currently available on pothi store. It will be soon available on Amazon and Flipkart as well. Please get your copy and do let me know your reviews. -Abhishek Sathe SCRUMble ! Written and Published by: Abhishek Sathe                                                                              Distributed by: pothi.com Order your copy now:  https://store.pothi.com/book/abhishek-sathe-scrumble/ Coming soon on Amazon and Flipkart About the book: Scrum is a framework for solving complex problems largely adapted by Software Development field. There are multiple ag...

Accessibility : An Important consideration in software development

What is Accessibility?

Accessibility is a very important piece of consideration in today's market. It means the quality of being able to be reached or entered. Accessibility focuses on how a physically or mentally disabled person accesses or benefits from a site, system or application. Conformance with accessibility guidelines while developing a web page or an app is important.

What does accessibility mean for software development?


Accessibility isn't about taking away functionality or making things difficult for the software development team. It is about making sure all possible users have a way to use the system. How do information architects and web designers/developers design web pages to be compatible with assistive devices is an important aspect when thinking about accessibility.


What does accessibility mean for software testing?


Accessibility Testing checks if a product is accessible to the people having disabilities. We need to understand accessibility principles to understand why accessibility testing is important and how should it be done. Testing a software for accessibility will enable users with disabilities to access the information.



 Accessibility Principles:

There are 12 accessibility guidelines organized under 4 principles: Perceivable, Operable, Understandable and Robust.

     Perceivable: Information and UI components must be presentable to users in ways they can perceive.
     Operable: UI components and navigation must be operable.
     Understandable: Information and the operation of UI must be understandable.
     Robust: Content must be robust enough that it can be interpreted reliably by a wide variety of user agents.



Government Regulations:


Government agencies all over the world have come out with regulations, which requires that IT products to be accessible by disabled people.

Following are the legal acts by various governments -
     United States: Americans with Disabilities Act - 1990
     United Kingdom: Disability Discrimination Act - 1995
     Australia: Disability Discrimination Act - 1992
     Ireland : Disability Act of 2005



Types of Disabilities:


Disabilities can be classified into 5 major types: Visual (Color Blindness, Low Vision, Complete Blindness), Cognitive/Learning/Neurological (ADHD, Autism, Mental Health Disabilities, Spectrum disorder etc), Auditory (Deafness), Physical (Arthritis, Repetitive Stress Injury, Amputation etc) and Speech (Muteness, Dysarthria, Stuttering)



International Standards:

Web Content Accessibility Guidelines (WCAG) is developed through World Wide Web Consortium (W3C) process which provides a single standard for accessibility. W3C has developed recommendations for Web Content Accessibility Guidelines, Authoring Tool Accessibility Guidelines and User Agent Accessibility Guidelines.

WCAG 1.0:

It provided 3 priorities or levels:
               Priority 1 (Level A) basic requirement for some groups to be able to use web documents.
               Priority 2 (Level AA) better accessibility and removal of significant barriers to accessing the content.
               Priority 3 (Level AAA) improvements to web content accessibility.
  

WCAG 2.0:

WCAG 2.0 is a stable, referenceable technical standard.
For each guideline, testable success criteria are provided to allow WCAG 2.0 to be used where requirements and conformance testing are necessary such as in design specification, purchasing, regulation, and contractual agreements.


In order to meet the needs of different groups and different situations, three levels of conformance are defined: A (lowest), AA, and AAA (highest).  Adherence to a standard means that you meet or satisfy the 'requirements' of the standard. In WCAG 2.0 the 'requirements' are the Success Criteria. To conform to WCAG 2.0, you need to satisfy the Success Criteria, that is, there is no content which violates the Success Criteria.

Comments

Popular posts from this blog

Bipartite and semihamiltonian graphs

Bipartite Graph: A graph is bipartite if its vertex set can be partitioned into two subsets X and Y so that every edge has one end in X and one end in Y; such a partition (X,Y) is called bipartition of the graph, and X and Y its parts. ex.- Notation: We denote a bipartite graph G with bipartition (X,Y) by G[X,Y]. Complete Bipartite Graph: If G[X,Y] is simple and every vertex in X is joined to every vertex in Y, then G is called a Complete Bipartite graph. ex.- Semi-Hamiltonian Graph: A semi-Hamiltonian graph is a graph that contains a Hamiltonian path, but not a Hamilton cycle. Hamiltonian Path: A Hamiltonian path in an undirected or directed graph is a path which visits each vertex exactly once. ex.- C-A-D-B-E is a Hamiltonian path Hamiltonian Cycle: A Hamiltonian cycle or a Hamiltonian Circuit is a Hamiltonian path which is a cycle. This post will be useful in understanding a question: "The nabhi kamal grapg is:" (A)Bipartite graph (B)Semi-...

Android 102

This post is in continuation with an earlier post : Android 101 1. Common attributes used in views and viewgroups: -layout_width -layout_height -layout_marginTop -layout_marginBottom -layout_marginLeft -layout_marginRight -layout_gravity: specifies how child views are positioned -layout_weight: specifies how much of the extra space in the layout should be allocated to the view -layout_x -layout_y 2. LinearLayout: arranges views in a single column or a single row. Child views can be arranged either vertically or horizontally. 3.AbsoluteLayout: enables you to specify the exact location of its children using layout_x and layout_y. AbsoluteLayout has been deprecated since android 1.5 4.TableLayout: groups views into rows and columns. You use <TableRow> element to designate a row in the table. Each row can contain one or more views. Each view you place within a row forms a cell. The width of each column is determined by the largest width of each cell in that column. 5....