Skip to main content

Accessibility Testing

Accessibility Testing is a non-functional testing type. This means anyone can use a particular web application, mobile application, website, or any other software package. Any human means not only perfect men or women but also differently able people as well.

Things can be used for testing, 
  • Zooming tools,
  • Hearing tools,
  • Speech recognition tools,
  • Dynamic brail printers. 
  • Color blindness testing by changing CSS files.

Basics we can do,
  • Alternative texts, 
  • Color contrast.
  • Use standards for HTML coding.
  • Tips should work(Alter tag should be used).
  • For decorative images should have alter tag but empty. 
  • One H1 tag per page.
  • Every page should have a title.
  • Every frame should have a title.
  • Tabs keys should work with the system and a particular element should have a focus indicator. 
  • Labels should be associated with correct input fields. 
  •  Every page should have a lang attribute. 

Comments

Popular posts from this blog

Differences between Severity ,Priority and Status

In market there are many bug tracking and project management tools available. These tools allow us to keep essential information of a bug or task. You will see there are three places have to fill when key in a task. Those three places are Status, Priority and Status of a bug/task. Let's see what those stand for.  Severity Priority Status Connotation Severity of a bug means how much it affecting to functionality of the software. Total damage it can do. Priority means how fast a bug or task should be resolve. Status means the current position of the bug/task. Types            Critical            Major            Moderate            Minor           Cosmetic           Low           Medium           High           New           Active/Open           Resolved/Fixed           QA In progress           Reopen           Closed/Completed 

MVC Architecture

Model-View-Controller (MVC) is a design pattern recently most popular among software engineers for applications which are needed to provide multiple views with using same data. I am suggesting MVC is better than WCF, because of this module separation. For an examples       ·          Multiple views and controllers can interface with same model for modification even those never exist before add this model.       ·          It is supporting all type of HTML verbs.       ·          No view state and post back events.       ·          Easy integration with JavaScript framework.       ·          Helps to decrease complexity of project       ·          Provides RAD development ( http://en.wikipedia.org/wiki/Rapid_application_development ).